I think that:
It does overlap with MySensors for the wireless network. MQTT-SN assumes a network that provides a bi-directional data transfer service between any node and a particular one (a gateway). MySensors wireless network could provide data transfer but the message are really tailored to transport sensor and actuator values.
MQTT-SN for the gateway - controller interface is not needed MQTT is for that more than fine
That said I like the idea of MQTT-SN but for it a "transparent network" makes more sense.
@legeantvert said:
On the same way, i dont understand how and where are stored the values inside the gateway if not used on each reception, are they stored somewhere to be able to answer them when serial request arrive?
You could bypass this on some kind of events obviously !
Actually my perl gateway is acting as the server Vera is for the arduino gateway. So from there I can trigger external URL, store data in a sqlite3 database... and so on !
Thanks for your quick reply!
The solution was indeed to put the ./configure parameters on the same line; I also changed to a serial gateway which is now correctly recognized in Domoticz.
I did not need to change any pin definitions (yet).
Yeah, the two capacitors clearly shown are indeed not very effective for the radio module, there is however another capacitor directly soldered to the radio, which is a bit hidden in the picture.
Thanks again for your help!
@Tommas Hi, now I've posted a device for sale on Tindie, if it's still relevant for you https://www.tindie.com/products/avikmen/usb-rf-gateway-with-stm32-and-nrf24-in-case/
Perhaps my definition about "controller", is a bit broad here.
What could be done, is to have a thin "controller", that receives MQTT from the existing gateway, hands out IDs if they are requested from a new node, and translate the message into homie compliant topics. That is all it has to do, should not care about the rest of the automation at all. Should also be able to translate back from homie compliant to mysensors.
This could be written in python, c#, javascript, rust etc. The benefit is that you have (relatively) easy editing of configurations at hands, without re-uploading sketches to your gateways / nodes, if you decide that node X should be named Y instead.
And I am in no way trying to treat anyone as a fool!
I have posted a question regarding what i think could be the fix to my issue over at: https://community.openhab.org/t/push-state-of-one-mqtt-topic-to-another/27597
Not sure if it will become of anything though. If anyone else has any experience with MQTT and openhab2 over here, then please be sure to shout a thought. It seems that not many people have got this sketch to work with openhab, google searches are bringing up posts from a year or two ago made on our forum here regarding this issue with no clear/simple solution.
