Deconz LED controller odd behaviour

I have recently purchased this Ajax Online LED controller and some RGB LED’s, which are connected through a conbee2 stick

I’m configuring them through Nodered - but I’m also seeing the same behaviour through Scenes & scripts too.

Basically - trying to turn on the RGB light from an automation or through a node in nodered does not turn the light on. If I run a script however it works fine. Also, It works fine turning it on in Lovelace, or in Deconz.

Any ideas? It’s driving me insane!!!

My test automations are below, just to show that there is nothing strange here:

Automation:

- id: 'kitchen_led_test2'
  initial_state: true
  alias: 'Kitchen LED Test2'
  trigger:
  action:   
    - service: light.turn_on
      entity_id: light.cupboard_party
      data:
        brightness_pct: 10

Script:

kitchen_led_test:
  sequence:
    - service: light.turn_on
      entity_id: light.cupboard_party
      data:
        brightness_pct: 10

I have similar issue, after I finally move my Led strips to deconz. All my automations are in Node Red
My office strip works fine it turns on.
As I’m not sending any additional data.
My kitchen one I had setup with additional data setting, brightness, color etc. Found it wouldn’t turn on. Even though it shows that it had been called in Node red. So I setup 2 service call nodes
1st just sends a turn on service call and then another one to set the additional setting made it work correctly.

2 Likes

Thanks for that info - I have managed to do something similar with two calls, but obviously it’s not ideal.

Any thoughts as to why a script would work, but not an automation or single node?