I've been able to get MySensors working with HomeGenie using the MQTT gateway. It doesn't have two-way communication or software-based pairing yet, but I'll work on those in the future.
Hey there @Chaotic ! This is Fay from codebender.cc Thank you for using codebender! I just wanted to let you know that one of the sketches you are using in this comment has been deleted and so it is not available for users to view it. Let me know if you have any question.
Ive started out with openHAB2. I was using a Ethernet gateway and tested the mysensors binding but found the combo was too limited. I much prefer having the MQTT gateway and the data be accessible to anything that subscribes, although I also now use openHAB to republish its item changes to MQTT as well which is probably a better approach.
I don't think the main new features in version 2 are very mature at the moment as well, discovered things for example get put in to a non human readable database and the web ui's are not fully functional.
With that being said I'm using node red to provide node ID's and configuring items manually and since beta3 it's been solid as a rock.
@celonunes generally raspberry pi with serial usb but also you can see some mqtt logs. Same problem with mac os with serial usb.
I also tried rpi uart pins for serial bu there is no logs for it.
Maybe someone gives his Openhab dir i can understand better problem isnt related with hardware
@evb Still haven't had a chance to look at your PR, sorry.
Yes, the database tends to grow I have about 80MB after a year of use. Just added a function to delete all messages older than, say, a year.
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 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.
