@sincze - <10 is good... saves power but not approved by wife :) <30 for me... lights on! :)

Thanks @blacey I'll give that a go tomorow and report back, really appreciate you pointing me in the right direction

@Matt-Pitts Excellent! :+1:

@Matt-Pitts For the mqtt client on the dev branch there is a sticky guide in the forum: http://forum.mysensors.org/topic/2352/guide-setting-up-and-testing-mqtt-client-gateway For the message types etc see the serial API. It's my number one visited page on the mysensors web. Although I'm starting to know it by heart now.:wink: http://www.mysensors.org/download/serial_api_15

Have this same issue and it makes me crazy... I use a step up converter DCDC 1.8V up to 3.3 input and output 3.3V. If solder from DCDC Out via 220uF direct soldered after stabilizer of HC501 direct on pcb and sometimes it will detect motion where no motion happens. I use two AA accu and i know that they have together 2,4V. Less voltage less current. But i try also with normal AA 3V then i have this issue not so often. But i have. It will much more if the voltage will more less.

@Matt-Pitts said: I'm wondering if it's possible to set them up to communicate directly with my mqtt broker over wifi rather than adding the radio and going via a gateway?? Yes, this MQTT gateway supports this: https://github.com/mysensors/Arduino/tree/development/libraries/MySensors/examples/GatewayESP8266MQTTClient Just remove the #define MY_RADIO_NRF24

Just calculate how much current flow you need and take relays that can handle it. P=UxI so 9W=240VxI and from there 9W/240V=0.0375A per lamp. With 10A relay you can drive 266 led lamaps ;)

@Matt-Pitts A very small simplification - in your first rule have you tried: if (hall_motion_raw.state == 1) sendCommand(Toggle_2,ON) I am not sure if it works but hall_motion-raw.state is a number so I think it should but it is always hard to predict how Openhab item states works in rules. I hate all these conversions like "as Decimaltype" needed in many places. How simple the rules can be made depends also on the settings of your sensor. My motion sensor (z-wave) sends ON when triggered and OFF after a set time after untriggered. So the rules become really simple. Without knowing how your sensor type and setup thus it is hard to comment much. From reading about the most common type of sensor it seems that If it has the jumper set to retriggering then the signal stays on until motion is no longer detected while set to non-retriggering the signal varies on/off as triggered. If your sensor works the "retriggering" way the rule for "hallLigtOff" may work with something like: rule "hallLightOff" when Item hall_motion_raw changed then if(hall_motion_raw.state ==0) sendCommand(Toggle_2,OFF) end Sorry for not being entirely sure about how this sensor works but I have not used it or experimented with it. I need to try it some day. UPDATE: I tested one of these sensors today (referring to settings described here http://www.mysensors.org/build/motion) : Jumper set to "auto reset"- sketch sends 1 and then a 0 comes when there is no motion and timer runs out. Jumper set to "no reset" - sketch sends 1 and then 0 comes after timer has run out, if motion still detected a 1 is sent again followed by a 0 when timer runs out and so on. So as long as motion is detected this goes on over and over again. When using "auto-reset" the rule above ought to work (if the "DecimalType conversion can be deleted, otherwise with this added)

Thanks guys, I have just placed a order for some of these.