I have been away for a while but it seams quite some of you are experiencing problems, I'll try to take a look at it. If you find any more details, please let me know!

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).

Hi @doctor64 , How did you solve the battery reporting? Did you implement the changes in h and cpp file from the link and compiled/uploaded the gateway sketch again?

@ericvdb Yes, I know about the 5V. But the adapter brings it down to 3.3V for the radio, that is the reason for using it and the adapter is equipped with the AMS 1117 3.3V chip. Seems to work OK but I really do not have any hard facts to prove it. One thing I may test is to wire the 5V also directly to this adapter instead of taking it out from the Arduino 5V pin. This is to find out if this Arduino Nano clone might have too small capacity for feeding the radio at certain occasions.

Actually, it's not 100% MySensors-related, but I have a working setup consisting of iBeacon (either HM10-based or PI-based) and Beecon app. When Beecon senses the iBeacon it can trigger various actions, eg make http requests or call IFTTT recipes

And be aware of this thread where the ENC module is hanging after a while.. http://forum.mysensors.org/topic/536/problems-with-enc28j60-losing-connection-freezing-using-uipethernet-or-ethershield-read-this

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.

I can nothing say about OpenHAB or PiDome but: Started! 0;0;3;0;9;read: 0-0-0 s=0,c=0,t=0,pt=0,l=0: 0;0;3;0;9;version mismatch 0;0;3;0;9;read: 0-0-0 s=0,c=0,t=0,pt=0,l=0: 0;0;3;0;9;version mismatch Does not look good, it seems an error from the gateway.

Hi John, appLog.txt I also tried using datatype string but it doesen't work. Meanwhile I have studies the log files more detailed and found the following behavior: when defining the device skeletal and when updating the derived device (first approx. 25 lines in the log file V_STATUS is declared as string with values 51 resp. 52 as specified in the web interface. The entity is "Modul 433 MHz". Later on, when using the toggle switch in the web interface the value has changed in the decription in the log file (see line 164 or 185) value has been changed to on/off. With this definition it seem that the mysensors-Plugin is feeded has been changed from the specified values. My conclusion is that the change is taking place somewhere outside the mysensors-plugin. By the way, if I change the type to string do I have to use quotation marks in the web interface? Thanks a lot for your support. Martin

@scurb This looks very interesting and my factor now to save me from having to create my own :-). I have been planning to do the same thing (although maybe on a smaller software scale) by writing a simple Python server that would pull serial packets off of a gateway arduino (either running mysensors or something I write myself) and pipe this through MQTT to openHAB. I have two questions: How do you interface with a sensor network? Do you go through a serial connection to read the serial packet format (a,b,c,d)? I see several implementations that put the mqtt client directly on the Arduino, but it seems much cheaper for me to just plug it into a USB port to get a virtual serial port instead of investing in a separate ethernet shield :-) How does an item configurations look like for a switch in openHAB? I'm looking to build a toggle switch which toggles light on or off every time it is activated, and I cannot really understand how to configure the switch to allow this behaviour for an mqtt input. Feel free to take the second question with me directly since this might not be very interesting to the others in the forum :-)