Azure IoT and M5Stack with M5Flow Blocky Python - C2D

The M5Flow (blocky) graphical program builder makes it easy to drag and drop a program that receives C2D messages from Azure IoT Hub. 

I've been playing with the M5Stack Core2 devices and wanted to see how hard it would be to create a program that sends data Azure to an IoT device without having to actually write any code.  They support several development environments including a graphical Python builder. The UIFlow IDE includes common cloud integration blocks for Azure and AWS. 

There weren't a lot of samples out there. I hope this will help others can use this as a starting point. You can find a link to a video walkthrough down below.

Azure IoT Hub Cloud-to-Device

From the Microsoft guide https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-c2d-guidance

IoT Hub provides three options for device apps to expose functionality to a back-end app:
  • Direct methods for communications that require immediate confirmation of the result. Direct methods are often used for interactive control of devices such as turning on a fan.
  • Twin's desired properties for long-running commands intended to put the device into a certain desired state. For example, set the telemetry send interval to 30 minutes.
  • Cloud-to-device (C2D) messages for one-way notifications to the device app.

Python Program

The program sends data from Azure to the IoT device for display on the device.  I use the Azure Portal to send data and did not write a cloud data source. That will be a future exercise.

This program was created with M5Flow/UIFlow desktop 1.7.5.  The web version gets updated more often. The current web version 1.8.7 has a different connection setup.

Fun with Blocky

This program listens for Azure IoT Hub generated Cloud-to-Device messages and displays them in a text field.  

Setup

  1. My UI Flow editor was connected via USB so this program has to initialize its own Wi-Fi connection in order to connect to the internet.
  2. Get the current time and display it in a field on the screen and enable RGB 1.
  3. Connect to Azure and enable RGB 2
  4. Update the reported twins with the connect time and enable RGB 3

Loop / Body

A minimal main program loop because the real work is done in the event handler
  1. Flash RGB 5 every 2 seconds to show it is alive.

Subscribe / Callback / Handler

The Subscribe C2D message handler is invoked every time a message is received from Azure
  1. Push the body of the message into the field on the screen
  2. Flip the color of RGB 10 whenever a message is received


The IoT device screen

There are three labels on the screen. 
  • One is purely a label that doesn't change
  • The 2nd one down is a placeholder for messages received from Azure.  It is updated with the content of every message
  • The bottom label is a time field. It is updated with the current time every 2 seconds by the main program loop.

Azure Portal

Our device is bound to a Device in an Azure IoT Hub.  We can view and update data and metadata in the Azure Portal.

IoT Hub Device - C2D - Cloud to Device

This is the main screen for Device-1 in Azure IoT Hub M5Stack-Hub. You can see the hidden connection strings we put into our program to connect to the device.

This screen has links for sending both one-way Message to Device and forrequest/response Direct Method invocations.

Sending the message

We clicked on Message to Device on the screen above. Just enter your message in the Message Body and press the Send Message button. The IoT device receives the Message Body exactly as presented on this screen. 

Video

References

Created 2021/12/03


Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Upd...
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaul...
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS ac...
Read more