@Tore-André-Rosander depending on how many leds you are running you could just put a diode in series with the supply, that will drop the voltage by about .5v which should still be ok. The diode will need to be able to handle the load of your leds though

@Tore-André-Rosander you could do a tail on your gateways serial device. Currently @work so I can't look it up for you. But that should show the serial communication between the gateway and domoticz. Also you can check the log of Domoticz in the log console of Domoticz

What payload do you send in the message? Each scene controller can have multiple buttons. Example: MyMessage msg1(CHILD_ID_3,V_SCENE_ON); MyMessage msg2(CHILD_ID_3,V_SCENE_OFF); send(msg1.set(1)); // Turn on scene button 1 send(msg2.set(1)); // Turn off scene button 1 send(msg1.set(2)); // Turn on scene button 2 send(msg2.set(2)); // Turn off scene button 2

@TheoL said: I would strip the complete sketch and leave only the button part in it. That way it's much easier to detect if there's any mistake. It's really hard to help you with a sketch if this size. You could try to give the debouncer a higher interval, e.g.: debouncer2.interval(25); Thanks for the troubleshooting tip! @mfalkvidd After commenting out almost all of the LCD/temp functions i was left with the last wait that caused the problems, it seems to be working now but havent got the time to run it more than a few minutes.

I have only tried 12V on the raw pin once and that immediately fried the Arduino AND the 1m 60 RGB LED light strip I had connected to one of the io pins.

The RPI loses routing information when restarting (this needs to be fixed!!). So you node must send something, for routing information to re-appear. I would suggest you let your RGB node wake up every 10 second or so and do a sendHeartbeat() or some other information like temperature.