General Discussion

I bought 5 of these from iTead a long time back.. excellent to get going quickly and for testing.! Highly recommend these! This one has been running on my desk just as a light lux sensor for months without needing any attention. IMG_20150808_135557.jpg

Thanks... tried to update. But my serial is a Mega 2560. So it gives an error. Remembers me i found a topic to switch the pins and change them in the sketch.

I tapped into a newer alarm systems door sensors by measuring the voltage via the analog pins. My alarm still works, but I can also see open/closed via mysensors/openhab.

ok cool i understand ...and if people for what ever reason need that kind of accurcy then a simple dunio ntp gateway will do the job ..

@CoolCooler good luck! May the force be with you....

gw.wait is ok. It keeps node awake and process incoming messages. If you sleep the node it becomes more complicated. You could send something to the controller when waking up (and keep the node awake for a short time to receive new commands). And the controller buffers outgoing commands until it receives this "woke-up-message". If you enable ack on outgoing commands from the controller (and the node is sleeping) you won't get and ack message back... which indicates the node is down or is sleeping.

Welcome Harald! And congrats+good luck to dad/mom ;-)

Try the ones you have. Not exactly an exact science this...

@TD22057 said: See here: http://forum.mysensors.org/topic/1034/mqtt-gateway-openhab-mosquitto/2 which connects mosquitto to the gateway using the bridge input. Bridging is used for connecting two brokers together (see http://mosquitto.org/man/mosquitto-conf-5.html "configuring bridges"). I think MySensor's MQTT Gateway is already a broker by itself where clients like OpenHab can connect to. However, if there is a need, you can use a bridge which forwards the messages from a remote broker(MySensor's MQTT Gateway) to a local broker(Mosquitto). Then clients could now also connect to Mosquitto.

There are multiple controller options available on http://www.mysensors.org. Not sure I understand what you mean by control sensor. You only need to act on the sensor output right?

Using watchdog as Mysensors is good idea, but is there any other better way to archive same?

Don't update if it's working.

@NeverDie it was about a year ago

@NeverDie All I can say is that after adding the watchdog I have not had a lockup in 2+ months. Before that, like you, I had random lockups. Based on this positive experience I also added a watchdog to the one repeater I have in my system. Had a brief power outage the other day and everything came back online by itself with no problems.

Hello, GreyGnome here. Glad to see the library is helping you. Sorry to see you had to edit code. In the next upcoming release I will include compiler directives that allow you to comment out conflicting interrupts. Also, as someone else mentioned- don't use attachInterrupt() together with EnableInterrupt(). It just makes the code fatter, and EnableInterrupt() can already cover both interrupt types; eg on an Arduino Uno: enableInterrupt(2, myFunkyExternalInterruptFunction, LOW); enableInterrupt(10, myExcellentPinChangeInterruptFunction, CHANGE); ...note that enableInterrupt will use External interrupts on pin 2 by default. You can force it to use pin change interrupts: enableInterrupt(2 | PINCHANGEINTERRUPT, myFunkyExternalInterruptFunction, FALLING); ...in which case, "myFunkyExternalInterruptFunction" is something of a misnomer. ALSO NOTE: Pin Change Interrupts do not support the LOW state!

cheap and ready to work.... would be nice if it plays with mysensors setup...