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.
@ServiceXp said:
@samppa I'm probably miss-understanding you, but wouldn't the electric heater be 100% efficient? In other words, for every watt you consume you would be outputting in thermal energy? I realized in many area's** it's not the cheapest form of heat**, but I think it's 100% efficient?
Yes, but in this case the definition of efficiency that is interesting to know is the heat exchange efficiency i.e. how much of the heat dissipated is preserved and transferred to the fresh air influx. The idea is to save energy and avoid heating with electricity. So the heat in hot air exhausted from the room is re-used to warm the cold outside air.
@sentur since it was launched 6 days ago, I seriously doubt anyone has had the ability to try it.
Anyway, please don't post the same question in multiple places. It wastes people's time. Most users don't have as much time as they would like to spend on projects, and wasting their time by splitting the discussion to multiple threads isn't very nice.
In case anyone wants to follow the existing discussion, head over to https://forum.mysensors.org/post/84076
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.
sensor id is not the same as node id.
sensor id = 255 is used for internal stuff like id request and battery level for node. You can assign 0-254 to your own attached sensors (to the arduino node).
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!
@kunall the best recommendation against openhab for me was ugly interface and problems with running it (java). I was using domoticz since early version with own interface on arduino,now I've switched everything for MySensors.
It still lacks some functions but Inwait for further development as even programmers of domoticz start to use MyS hardware
