GE Enbrighten light switch flips between two brightness settings on command

Configuration Z-Wave
1

I am using Node Red to slowly turn up a light bulb to wake me up. The flow will periodically issue light.turn_on with brightness_pct to the Home Assistant API. Mostly it works correctly, and the light slowly gets brighter. However, in a few cases, it will go dimmer, then brighter when the light.turn_on command is issued. I debugged Node Red and confirmed that the flow was NOT sending these commands. I tailed OZQ_Log.txt and I noticed the following (it is trying to set the brightness_pct to 81):

2019-12-19 15:47:52.817 Info, Node007, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 81
2019-12-19 15:47:52.817 Info, Node007, SwitchMultilevel::Set - Setting to level 81
2019-12-19 15:47:52.817 Detail, Node007, Queuing (Send) SwitchMultilevelCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x26, 0x01, 0x51, 0x25, 0xaa, 0x1b
2019-12-19 15:47:52.817 Detail, Node007, Queuing (Send) SwitchMultilevelCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x26, 0x02, 0x25, 0xab, 0x4a
2019-12-19 15:47:52.817 Detail,
2019-12-19 15:47:52.817 Info, Node007, Sending (Send) message (Callback ID=0xaa, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x26, 0x01, 0x51, 0x25, 0xaa, 0x1b
2019-12-19 15:47:52.824 Detail, Node007,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-12-19 15:47:52.824 Detail, Node007,   ZW_SEND_DATA delivered to Z-Wave stack
2019-12-19 15:47:52.845 Detail, Node007,   Received: 0x01, 0x07, 0x00, 0x13, 0xaa, 0x00, 0x00, 0x03, 0x42
2019-12-19 15:47:52.845 Detail, Node007,   ZW_SEND_DATA Request with callback ID 0xaa received (expected 0xaa)
2019-12-19 15:47:52.845 Info, Node007, Request RTT 28 Average Request RTT 36
2019-12-19 15:47:52.845 Detail,   Expected callbackId was received
2019-12-19 15:47:52.845 Detail,   Expected reply was received
2019-12-19 15:47:52.845 Detail,   Message transaction complete
2019-12-19 15:47:52.845 Detail,
2019-12-19 15:47:52.845 Detail, Node007, Removing current message
2019-12-19 15:47:52.845 Detail,
2019-12-19 15:47:52.845 Info, Node007, Sending (Send) message (Callback ID=0xab, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x26, 0x02, 0x25, 0xab, 0x4a
2019-12-19 15:47:52.853 Detail, Node007,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-12-19 15:47:52.853 Detail, Node007,   ZW_SEND_DATA delivered to Z-Wave stack
2019-12-19 15:47:52.898 Detail, Node007,   Received: 0x01, 0x07, 0x00, 0x13, 0xab, 0x00, 0x00, 0x05, 0x45
2019-12-19 15:47:52.898 Detail, Node007,   ZW_SEND_DATA Request with callback ID 0xab received (expected 0xab)
2019-12-19 15:47:52.898 Info, Node007, Request RTT 52 Average Request RTT 44
2019-12-19 15:47:52.898 Detail,   Expected callbackId was received
2019-12-19 15:47:52.939 Detail, Node007,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x07, 0x03, 0x26, 0x03, 0x51, 0x82
2019-12-19 15:47:52.939 Detail,
2019-12-19 15:47:52.939 Info, Node007, Response RTT 93 Average Response RTT 84
2019-12-19 15:47:52.939 Info, Node007, Received SwitchMultiLevel report: level=81
2019-12-19 15:47:52.939 Detail, Node007, Refreshed Value: old value=79, new value=81, type=byte
2019-12-19 15:47:52.940 Detail, Node007, Changes to this value are not verified
2019-12-19 15:47:52.940 Detail, Node007,   Expected reply and command class was received
2019-12-19 15:47:52.940 Detail, Node007,   Message transaction complete
2019-12-19 15:47:52.940 Detail,
2019-12-19 15:47:52.940 Detail, Node007, Removing current message
2019-12-19 15:47:52.940 Detail, Node007, Notification: ValueChanged
2019-12-19 15:47:52.962 Detail, Node007,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x07, 0x05, 0x26, 0x03, 0x51, 0x51, 0x00, 0xd7
2019-12-19 15:47:52.962 Detail,
2019-12-19 15:47:52.962 Info, Node007, Received SwitchMultiLevel report: level=81
2019-12-19 15:47:52.962 Detail, Node007, Refreshed Value: old value=81, new value=81, type=byte
2019-12-19 15:47:52.962 Detail, Node007, Changes to this value are not verified
2019-12-19 15:47:52.962 Detail, Node007, Notification: ValueChanged

Have you experienced similar behavior with your z-wave light switch?

I also noticed that when I tried to turn_off the light with the Home Assistant UI, the light turned off, turned back on, and then turned off again. This doesn’t always happen, but I noticed it after I finished trying to debug the node red flow.

2

Check out the refresh_value and delay Z-Wave configuration items. You probably don’t have these set correctly for this light.

3

I have not set any device config for any z-wave item. Hence, refresh_value will be false. Do you propose I should set it to true? I’m not yet clear what “refreshing the node value” means.

4

The way the Z-Wave light component works is, after changing a setting on the light it will read its value back. But if the device changes its value slowly, the the value it reads back will be wrong. So the refresh feature makes it read the value back again after the specified delay. Depending on how you turn the light on or off it will either change quickly or slowly. Enabling the refresh feature should ensure that the HA entity representing the device is ultimately updated to represent the correct value of the device.

So the short answer is, yes. At the very least, see if it solves your problem.

1 Like