misty urchin
For a couple years at least I have been capturing the brightness of one light and setting it on other lights so they match. Recently I started seeing errors in NR logs and today while digging deeper I noticed that the action node no longer has a property called brightness, but still has the brightness_pct property. When I look at the error (pasted below) I see that while I am trying to set brightness, NR is trying to set 112-38-0-targetValue which is the 0-99 brightness_pct property.
Is something changing in the backend or is this a NR related bug?
What is the right way of capturing the brightness of a light so it can be set on another if what I am doing is incorrect / not ideal?
...
data: {
entity_id: 'light.entrance_light',
old_state: {
entity_id: 'light.entrance_light',
state: 'on',
attributes: {
supported_color_modes: [ 'brightness' ],
color_mode: 'brightness',
brightness: 255,
friendly_name: 'Entrance Light ',
supported_features: 32
},
...
new_state: {
entity_id: 'light.entrance_light',
state: 'off',
attributes: {
supported_color_modes: [ 'brightness' ],
color_mode: null,
brightness: null,
friendly_name: 'Entrance Light ',
supported_features: 32
},
...
error: {
message: 'HomeAssistantError: Unable to set value 112-38-0-targetValue: zwave_error: Z-Wave error 1405 - The node failed to decode the message. (ZW1405)',
source: {
...
