Dimmable Bulb and updating when turning off

Configuration Z-Wave
1

I have some dimmable bulbs and when turning them off, I see z-wave updates and levels as it dims to off of 66 and 33, but never the final 0 to indicate off. My HA UI never shows completely off until I toggle it to off again.

Are these updates I am seeing being sent as updates by the bulb or does HA send update requests and is just not sending enough to get the last final value for when it is off.

I am just not familiar enough about the process for this.

Here is what I see during an on to off transition.

2019-03-10 18:03:35.765 Info, Node004, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 0

2019-03-10 18:03:35.765 Info, Node004, SwitchMultilevel::Set - Setting to level 0

2019-03-10 18:03:35.769 Detail, Node004, Queuing (Send) SwitchMultilevelCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x26, 0x01, 0x00, 0x25, 0xfb, 0x18

2019-03-10 18:03:35.769 Detail, Node004, Queuing (Send) SwitchMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x26, 0x02, 0x25, 0xfc, 0x1e

2019-03-10 18:03:35.769 Info, Node004, Sending (Send) message (Callback ID=0xfb, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x26, 0x01, 0x00, 0x25, 0xfb, 0x18

2019-03-10 18:03:35.778 Detail, Node004, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8

2019-03-10 18:03:35.779 Detail, Node004, ZW_SEND_DATA delivered to Z-Wave stack

2019-03-10 18:03:35.794 Detail, Node004, Received: 0x01, 0x07, 0x00, 0x13, 0xfb, 0x00, 0x00, 0x02, 0x12

2019-03-10 18:03:35.794 Detail, Node004, ZW_SEND_DATA Request with callback ID 0xfb received (expected 0xfb)

2019-03-10 18:03:35.794 Info, Node004, Request RTT 24 Average Request RTT 24

2019-03-10 18:03:35.795 Detail, Node004, Removing current message

2019-03-10 18:03:35.801 Info, Node004, Sending (Send) message (Callback ID=0xfc, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x26, 0x02, 0x25, 0xfc, 0x1e

2019-03-10 18:03:35.810 Detail, Node004, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8

2019-03-10 18:03:35.810 Detail, Node004, ZW_SEND_DATA delivered to Z-Wave stack

2019-03-10 18:03:35.825 Detail, Node004, Received: 0x01, 0x07, 0x00, 0x13, 0xfc, 0x00, 0x00, 0x02, 0x15

2019-03-10 18:03:35.826 Detail, Node004, ZW_SEND_DATA Request with callback ID 0xfc received (expected 0xfc)

2019-03-10 18:03:35.826 Info, Node004, Request RTT 24 Average Request RTT 24

2019-03-10 18:03:35.837 Detail, Node004, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x04, 0x03, 0x26, 0x03, 0x62, 0xb2

2019-03-10 18:03:35.837 Info, Node004, Response RTT 35 Average Response RTT 35

2019-03-10 18:03:35.837 Info, Node004, Received SwitchMultiLevel report: level=98

2019-03-10 18:03:35.838 Detail, Node004, Refreshed Value: old value=99, new value=98, type=byte

2019-03-10 18:03:35.838 Detail, Node004, Changes to this value are not verified

2019-03-10 18:03:35.838 Detail, Node004, Expected reply and command class was received

2019-03-10 18:03:35.838 Detail, Node004, Message transaction complete

2019-03-10 18:03:35.838 Detail, Node004, Removing current message

2019-03-10 18:03:35.839 Detail, Node004, Notification: ValueChanged

2019-03-10 18:03:36.773 Detail, Node004, Queuing (Send) SwitchMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x26, 0x02, 0x25, 0xfd, 0x1f

2019-03-10 18:03:36.773 Info, Node004, Sending (Send) message (Callback ID=0xfd, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x26, 0x02, 0x25, 0xfd, 0x1f

2019-03-10 18:03:36.782 Detail, Node004, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8

2019-03-10 18:03:36.782 Detail, Node004, ZW_SEND_DATA delivered to Z-Wave stack

2019-03-10 18:03:36.797 Detail, Node004, Received: 0x01, 0x07, 0x00, 0x13, 0xfd, 0x00, 0x00, 0x02, 0x14

2019-03-10 18:03:36.797 Detail, Node004, ZW_SEND_DATA Request with callback ID 0xfd received (expected 0xfd)

2019-03-10 18:03:36.797 Info, Node004, Request RTT 23 Average Request RTT 23

2019-03-10 18:03:36.808 Detail, Node004, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x04, 0x03, 0x26, 0x03, 0x42, 0x92

2019-03-10 18:03:36.809 Info, Node004, Response RTT 35 Average Response RTT 35

2019-03-10 18:03:36.809 Info, Node004, Received SwitchMultiLevel report: level=66

2019-03-10 18:03:36.809 Detail, Node004, Refreshed Value: old value=98, new value=66, type=byte

2019-03-10 18:03:36.809 Detail, Node004, Changes to this value are not verified

2019-03-10 18:03:36.809 Detail, Node004, Expected reply and command class was received

2019-03-10 18:03:36.809 Detail, Node004, Message transaction complete

2019-03-10 18:03:36.809 Detail, Node004, Removing current message

2019-03-10 18:03:36.809 Detail, Node004, Notification: ValueChanged

2019-03-10 18:03:37.774 Detail, Node004, Queuing (Send) SwitchMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x26, 0x02, 0x25, 0xfe, 0x1c

2019-03-10 18:03:37.774 Info, Node004, Sending (Send) message (Callback ID=0xfe, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x26, 0x02, 0x25, 0xfe, 0x1c

2019-03-10 18:03:37.783 Detail, Node004, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8

2019-03-10 18:03:37.783 Detail, Node004, ZW_SEND_DATA delivered to Z-Wave stack

2019-03-10 18:03:37.799 Detail, Node004, Received: 0x01, 0x07, 0x00, 0x13, 0xfe, 0x00, 0x00, 0x02, 0x17

2019-03-10 18:03:37.799 Detail, Node004, ZW_SEND_DATA Request with callback ID 0xfe received (expected 0xfe)

2019-03-10 18:03:37.800 Info, Node004, Request RTT 25 Average Request RTT 24

2019-03-10 18:03:37.809 Detail, Node004, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x04, 0x03, 0x26, 0x03, 0x21, 0xf1

2019-03-10 18:03:37.810 Info, Node004, Response RTT 35 Average Response RTT 35

2019-03-10 18:03:37.810 Info, Node004, Received SwitchMultiLevel report: level=33

2019-03-10 18:03:37.810 Detail, Node004, Refreshed Value: old value=66, new value=33, type=byte

2019-03-10 18:03:37.810 Detail, Node004, Changes to this value are not verified

2019-03-10 18:03:37.810 Detail, Node004, Expected reply and command class was received

2019-03-10 18:03:37.810 Detail, Node004, Message transaction complete

2019-03-10 18:03:37.810 Detail, Node004, Removing current message

2019-03-10 18:03:37.811 Detail, Node004, Notification: ValueChanged

2

You need to set refresh_value: true and an appropriate delay: for the device. See this doc page.

3

I had tried all that before and it didn’t seem to work.

I will revisit and try again.

4

If your bulbs are Domitech, then I have the same issue… haven’t found any workaround for that – other than using e.g. LIFX wifi bulbs instead :slight_smile:

5

You need to make sure the delay value is long enough for the particular dimmer. Also, you can always set up polling for it. I would think one or the other should work, but if not, then I’m stumped.

6

So I went back and added in the refresh setup again and it is now working.

Maybe I typoed something the last time I worked on this which passed the configuration test but wasn’t correct.

Thanks for heading me back in that direction. I still get a couple of off to on to off transitions in the UI, but ultimately it does turn off which is something I can live with.

1 Like
7

Yep, unfortunately that seems to be normal.

8

As I think back, I believe I had used this recommendation from a couple of other threads that I read, but instead of true/false as the values, they have numbers in them. That does get checked as a good config but doesn’t work.

9

Yeah, not sure how that confusion started. refresh_value is a boolean and should be true or false, but because of this code used in the schema, other values are accepted and “coerced” into a boolean. delay is the number of seconds to delay and should be a positive integer, and is only used if refresh_value evaluates to true.