Fred Larsen
Fred Larsen
I did change the title of this request to make it easier to find, and I will leave it here for others to see. One comment to people not knowing...
Thanks for the interest and contribution. I will leave this post here to help others with the same type of setup.
The reason for using fixed PJON ids is to keep storage and RAM usage small, allowing it to run along with a decently sized user sketch even on a limited...
The modules do not know the PJON id of any other module, not even the master. The master knows the PJON id of each module, as well as a "module...
Just to clarify: the master relates to the modules by their PJON id, not their name. The name given to the constructor in the modules could actually be eliminated as...
Classifying this as "feature request" and leaving it open, to be evaluated and possibly implemented.
Hi, sorry for the late reply in the holiday. Funny that you mention MQTT. I have implemented support for this in ModuleInterface, so that all outputs from all modules are...
In case you wish to proceed without waiting, this is the recipe for pushing values into the database. Create a socket connection to the web server, usually port 80. Send...
@happytm I recently added support for mirroring outputs and settings to MQTT, with support for bidirectional transfer of settings (change in module itself, MQTT or web page and it will...
@happytm Are you still interested in this feature? I recently completed event support (immediate transfer) to and from MQTT and can start on this. What I can see the need...