Controllers

If you add a new device and then remove it. After that you add another new device it probably get same Id. Clean EPROM and retry.

ok, thanks for the explanation! I'll implement features I need in my own implementation of MyGateway then.

tanks. im going to check it.

If you're talking about SerialGateway.ino.. then yes.

@Rachmat-Aditiya said: fhem is more stable but you need to configure everything manually, configure 'everything' is not entirely true, in respect to MySensors there's an autocreate-mode in FHEM. You will have to manually configure the gateway (e.g. 'define gw MYSENSOR /dev/ttyUSB0'), then activate autocreate (by pressing the include-button on the gateway, or setting the autocreate-attribute on the gateway device), then restart all MySensor-nodes and fhem will create a MYSENSORS_DEVICE-entry for every Sensor that sends presentation-messages while inclusion-mode is active.

Thanks. Then I know I'm on the right track. Looks as if I'm getting something from the gateway in the log but nothing from the temp node yet. Need to investigate more. I figured out the Over the Air just could not see if it was relevant for some reason. /Markus

There are several IOT services out there to which you could send your sensor data - for example see the list here https://iotdb.org/social/imadeit/post/95279811682/iot-datastore-roundup - to which the MySensors cloud service will one way be added perhaps. If you want to run your own, one question is whether you want to retain all data forever, or just a rolling buffer of more recent data. For the latter, something like RRDtool might be more efficient of time and space then a relational database. For full generality a relational database would work, but do calculate how big it's going to get and think of your usage patterns - do you need arbitrary queries? Using something like MQTT might be helpful as an intermediary between the sensor network and a database or datastore; it could also make it possible to run both Home Automation and data logging from the same network. For example, if the sensor network provides a broker, both the HA software and the logging software can subscribe to the relevant topics.

The MySensors controller is currently just a proof of concept node.js program to test the OTA stuff. Currently relies on a serial or ethernet gateway.

@enicky :+1:

@wannabee I really like what you have done here, and I think that this will be my gateway of choice when I finish porting the sensor library to work with the radios I have. I have a few comments for how this could be made even better in the future. I think a good solution could be to model this on the Z wave binding and habmin integration. We can set up habmin to manage the network. This will allow us to view all the nodes, toggle inclusion mode, assign IDs, and so on. We would alsohave build a good binding which could take care of the automatic ID assignment and expose these through habmin. I'm not yet sure how this would be done, but it seems like something that would be really nice to have. Especially if we consider that OpenHAB is an open source initiative, and MySensors is a DIY approach to home automation I think good openhab integration would benefit the entire home automation community :-)

@donnib - I didn't continue this way but instead started using node-js based controller code that connects to a standard Ethernet gateway. @hek merged the code about two weeks ago. I will provide a tutorial on how to set it up from scratch shortly...

@Yveaux Yes that is what I was getting at. I just wanted to know that I wasn't going to end up in the same pit as with the 433MHz modules ... and I know virtually nothing of the workings of the NRF chip. Thank you for reassuring me :-)

This is the fork we're using: https://github.com/TMRh20/RF24 Could you create an issue for TMRh20 here: https://github.com/TMRh20/RF24/issues?state=open