It’s now been many months of eating some really good and fresh produce. I’m going to declare the IoT exeperient and learning a success. Next step is to package it into a Sustainable Hack Series that anyone can build.
I hope you enjoyed the Microsoft Developer Cloud Summit today! Thank you very much for attending my session: Automating your home or office with IoT Central and Power Apps” It was a lot of information in 30 min, so here’s the content, resources and source code.
This whole session was done using Home Automation devices combined with OBS. Camera Scene changes were controlled with a standard home remote control. So automation doesn’t have to be traditional garage doors or lighting, you can control you PC life too! 😎 Controlling your OBS Scenes with a Home Automation device
Link to Presentation: Microsoft Developer Cloud Summit 2021 Presentation
You can easily set up a standard 433 Mhz remote control that you use every day in your home to control scenes in OBS (Open Broadcast Software) if you don’t own a fancy Stream Deck.
All you need is a remote, a 433 Mhz Wifi Bridge and some Node-RED magic.
Flash the bridge using these instructions: https://explorationspace.co.za/2021/02/10/sonoff-rf-bridge-433-tasmota/
Install the OBS Websocket plugin: https://github.com/Palakis/obs-websocket/releases/tag/4.9.0
The 433 Mhz Bridge when it detects a signal, it publishes a message with it’s contents via MQTT. These will have codes attached to them and in the case of a remote, that code / data that is sent via the message payload translates to the button pressed. You can “train” your solution with the remotes you have. These can be standard house-hold remotes.
The switch statements routes the flow based on the button data to a specific function.
The function sends a message with the “scene-name” with the parameter of the scene created in OBS.
For additional commands refer to the protocol document:
Happy streaming! 😎
I control a few devices from the Internet, but I don’t want all devices exposed and connected to IoT Central. One solution is to build a gateway locally which routes request messages to switch things on or off to the correct device locally.
In this post we will look at how to send commands from IoT Central and route them using Node-RED to the automation device via MQTT.
This architure uses Node-RED as a gateway, and then uses Eclipse Mosquito as a MQTT server. The Grow Light and Air Conditioner in the diagram is an off the shelf Sonoff POW-R2 device flashed with Tasmota.
With Node-RED you can visually map the flow / sequence of events. Node-RED supports Azure IoT Hubs and Azure IoT Central, so it’s perfect for this job to do quickly and easily without having to write code.
In Azure IoT Central we have a single device linked with a command. The command accepts a parameter, which will be the device name / topic name on the local MQTT server.
The diagram above shows the command with the parameter.
The Node-RED Azure component supports Direct Methods. These are commands that you can directly invoke on a device. In this case, the device is the gateway itself created within Node-RED.
It supports two methods (as per Azure IoT Central template)
With a Node-Red switch statement we can controll the flow with whichever method name was invoked from IoT Central.
If it’s the “DeviceOn” flow, then the device parameter name (payload) is used to build up the topic for the Sonoff device via MQTT. The payload of the message will be “on”.
If it’s the “DeviceOff” flow, then the device parameter name (payload) is used to build up the topic for the Sonoff device via MQTT. The payload of the message will be “off”.
The Sonoff devices are great, but I prefer to use everything within my home and home automation setup to be fully under my control. Tasmota is a great way of doing just that.
I found the easiest way of flashing devices with Tasmota is using a raspberry pi. I’ve done a quick writeup on how to do this.
Start with installing via the installer script
pip install esptool
Clone from the GitHub repository
git clone https://github.com/espressif/esptool.git
Preparing the Raspberry Pi
Connect the Raspberry Pi to the Sonoff Device
The TXD (Transmit) and RXD (Receive) pins are marked on the raspberry pi. We can use these to communicate serially with the Sonoff Device to flash it with the Tasmota firmware.
Each Sonoff device has pins allocated to reflash the device. These boards usually don’t have headers attached. Here I soldered one to the board.
The important pins are VDD, TX, RX and GND.
Connect VDD to an external power supply. The Raspberry Pi will not be able to power the device off it’s own pins. I used an external bench power supply. Ensure the voltage is 3.3V.
Connect the GND on the power supply to both the Raspberry Pi Ground Pins and the Sonoff device’s GND pin
Connect the TXD on the Raspberry Pi to the RX Sonoff pin and connect the RXD on the Raspberry Pi to the TX Sonoff pin.
Download the Tasmota Firmware
curl http://ota.tasmota.com/tasmota/ --output tasmota.bin
This terminal command will download the latest firmware from the Tasmota site to the Raspberry Pi.
sudo ./esptool.py --port /dev/ttyS0 erase_flash
Start by erasing the devices Flash memory
The port to use on a Raspberry Pi 3 or 4 is /dev/ttyS0.
sudo ./esptool.py --port /dev/ttyS0 write_flash -fm dout 0x0 tasmota.bin
Flash the device with the dowloaded firmware.
Once flashed, reassemble the device and power it on. It should appear as an access point on the network as Tasmota-xxxx if all went well.
You can also follow the Tasmota getting started guide to continue the setup: https://tasmota.github.io/docs/Getting-Started/
Node-RED is a programming tool for wiring together hardware devices, APIs and online services in new and interesting ways.
It provides a browser-based editor that makes it easy to wire together flows using the wide range of nodes in the palette that can be deployed to its runtime in a single-click.
Running Node-RED is easiest in a Docker container. This is really easy to set up.
docker pull nodered/node-red
Pull the container from the Docker Repository
sudo docker run -d -p 1880:1880 -v /home/ubuntu/docker-nodered/data:/data --name mynodered nodered/node-red
The default port for Node-RED is 1880. Also ensure that the volumes are mapped to a local folder on the host to preserve the configuration.
Eclipse Mosquitto is an open source (EPL/EDL licensed) message broker that implements the MQTT protocol versions 5.0, 3.1.1 and 3.1. Mosquitto is lightweight and is suitable for use on all devices from low power single board computers to full servers.
The MQTT protocol provides a lightweight method of carrying out messaging using a publish/subscribe model. This makes it suitable for Internet of Things messaging such as with low power sensors or mobile devices such as phones, embedded computers or microcontrollers.
Running Mosquitto is easiest in a Docker container. This is really easy to set up.
docker pull eclipse-mosquitto
Pull the container from the Docker Repository
sudo docker run -d -p 1883:1883 -p 9001:9001 -v mosquitto.conf:/home/ubuntu/mosquitto/config/mosquitto.conf -v /mosquitto/data -v /mosquitto/log eclipse-mosquitto
The default port for Mosquitto is 1883. Also ensure that the volumes are mapped to a local folder on the host to preserve the configuration.