Hello Joe,
Thanks for the reply. I am currently using Mosquitto for my broker.
- Code: Select all
mosquitto version 1.4.15
mosquitto is an MQTT v3.1.1/v3.1 broker.
As my sensor network expands beyond Indigo (to include remote weather stations, Home Assistant for a sensor running off a Raspberry Pi, etc), I want to be able to abstract my Command and Control architecture away from solely talking to Indigo. Having Indigo publish to and consume from topics from the new C&C architecture (aka Mosquitto) is where I am headed.
In another case, I FINALLY got account linking working for a native Alexa Smart Home Skill (because they greatly simplified the process if you choose to use Amazon as your identity provider), which means I will take my
https://github.com/msreynolds/askIndigo skill and make it work without having to invoke the "indigo" skill name. So we can just say Alexa, turn on the kitchen light, etc. To make this skill even better, instead of talking directly to Indigo via its public Reflector URL, I could send the commands to the MQTT broker instead. Were an Indigo bridge subscribed to the right topics, it could respond as needed.
As a user I want to:
1) Configure a MQTT Bridge plugin for Indigo to point to a given MQTT server URL (with username/password) TLS or WSS
2) Publish messages to a configurable topic when a given device changes state.
3) Publish messages to a configurable topic when a given action is run.
4) Publish messages to a configurable topic when a given variables change value.
5) Subscribe to a configurable topic and in response to incoming messages, run a custom script (I would create 3 of these instances, one custom script for each to handle devices, actions and variables)
There is nothing inherent about the MQTT schema being used, only referenced in the configurable topics and likely within the script that runs when an incoming message is received.
Hope thats enough to go on? I have private hosting/repos on GitHub, let me know if you need or want to collaborate there?
Thanks,
Matt