As a predominantly IoT project, I'd like to see an MQTT implementation.
I have a strong dislike for IFTTT, in fact I religiously avoid cloud-based IoT solutions. I (almost exclusively) run TASMOTA and I'm extremely pleased with it. The only place my IoT network touches the internet is the Home Assistant web interface.
This thread is offered as a discussion document as to what an MQTT implementation might look like. One suggestion is that the firmware might subscribe to an MQTT topic on a given broker. That topic would publish a list of "commands" and "queries". This would allow those commands and queries to be dynamically published on the web server or by MQTT direct.
This creates a boolean button, allowing on/off of lights, and a numeric display of temperature, along with the MQTT publications / subscriptions required to populate the display, and take commands from the web server.
As a predominantly IoT project, I'd like to see an MQTT implementation.
I have a strong dislike for IFTTT, in fact I religiously avoid cloud-based IoT solutions. I (almost exclusively) run TASMOTA and I'm extremely pleased with it. The only place my IoT network touches the internet is the Home Assistant web interface.
This thread is offered as a discussion document as to what an MQTT implementation might look like. One suggestion is that the firmware might subscribe to an MQTT topic on a given broker. That topic would publish a list of "commands" and "queries". This would allow those commands and queries to be dynamically published on the web server or by MQTT direct.
For example, an IoT controller might publish
This creates a boolean button, allowing on/off of lights, and a numeric display of temperature, along with the MQTT publications / subscriptions required to populate the display, and take commands from the web server.