I’m trying to get HomeAssistant to update the status of my light switches (DZS15), however it doesn’t update unless I poll. I’ve read that they don’t support instant status updates, however I know that it does, even through some custom method of doing so. For example, SmartThings has no problem updating the status immediately when changed on/off at the switch.
When viewing the logs in HomeAssistant, I do see data coming through when I turn the light on or off. These don’t show up as “Events”, but there are messages that come through the logs. Any idea how I would configure HomeAssistant to recognize these messages?
The switches are being recognized correctly and do work when switching on/off from HomeAssistant. I can also poll them successfully without issue.
Here is the data from the logs, for ON, and OFF. I’m not sure why there are timeout messages. When I send a zwave_js.refresh_value service call, it returns the status just fine, no errors. The switch is only 20 ft. away from the controller. I’ve tried with the same results using the switches paired to SmartThings and used in HomeAssistant as through my USB stick as a secondary controller, and with the Switch paired directly to the USB stick with the same results. Any ideas?
LOG:
ON Physical Push:
2021-10-25T12:59:56.299Z SERIAL « 0x0112004984040c04100325272b2c72869177735b (20 bytes)
2021-10-25T12:59:56.302Z SERIAL » [ACK] (0x06)
2021-10-25T12:59:56.305Z DRIVER « [Node 004] [REQ] [ApplicationUpdateRequest]
payload: 0x84040c04100325272b2c7286917773
2021-10-25T12:59:56.314Z CNTRLR « [Node 004] Received updated node info
2021-10-25T12:59:56.316Z CNTRLR [Node 004] Node does not send unsolicited updates; refreshing actuator and sen
sor values...
2021-10-25T12:59:56.320Z CNTRLR » [Node 004] querying Binary Switch state...
2021-10-25T12:59:56.328Z SERIAL » 0x0109001304022502258362 (11 bytes)
2021-10-25T12:59:56.330Z DRIVER » [Node 004] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 131
└─[BinarySwitchCCGet]
2021-10-25T12:59:56.337Z SERIAL « [ACK] (0x06)
2021-10-25T12:59:56.342Z SERIAL « 0x0104011301e8 (6 bytes)
2021-10-25T12:59:56.343Z SERIAL » [ACK] (0x06)
2021-10-25T12:59:56.345Z DRIVER « [RES] [SendData]
was sent: true
2021-10-25T12:59:56.365Z SERIAL « 0x011800138300000300b17f7f7f7f0101030000000002010000c5 (26 bytes)
2021-10-25T12:59:56.368Z SERIAL » [ACK] (0x06)
2021-10-25T12:59:56.370Z DRIVER « [REQ] [SendData]
callback id: 131
transmit status: OK
2021-10-25T12:59:56.380Z SERIAL « 0x010c000400040422010000ad0079 (14 bytes)
2021-10-25T12:59:56.381Z DRIVER Dropping message because it could not be deserialized: The command class Appli
cation Status is not implemented
2021-10-25T12:59:56.382Z SERIAL » [ACK]
2021-10-25T13:00:06.382Z CNTRLR [Node 004] Timed out while waiting for a response from the node
OFF Physical Push:
2021-10-25T13:01:37.975Z SERIAL « 0x0112004984040c04100325272b2c72869177735b (20 bytes)
2021-10-25T13:01:37.978Z SERIAL » [ACK] (0x06)
2021-10-25T13:01:37.981Z DRIVER « [Node 004] [REQ] [ApplicationUpdateRequest]
payload: 0x84040c04100325272b2c7286917773
2021-10-25T13:01:37.984Z CNTRLR « [Node 004] Received updated node info
2021-10-25T13:01:37.985Z CNTRLR [Node 004] Node does not send unsolicited updates; refreshing actuator and sen
sor values...
2021-10-25T13:01:37.989Z CNTRLR » [Node 004] querying Binary Switch state...
2021-10-25T13:01:38.000Z SERIAL » 0x0109001304022502258465 (11 bytes)
2021-10-25T13:01:38.001Z DRIVER » [Node 004] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 132
└─[BinarySwitchCCGet]
2021-10-25T13:01:38.004Z SERIAL « [ACK] (0x06)
2021-10-25T13:01:38.010Z SERIAL « 0x0104011301e8 (6 bytes)
2021-10-25T13:01:38.011Z SERIAL » [ACK] (0x06)
2021-10-25T13:01:38.013Z DRIVER « [RES] [SendData]
was sent: true
2021-10-25T13:01:38.096Z SERIAL « 0x011800138400000900b37f7f7f7f0101030000000002020000c9 (26 bytes)
2021-10-25T13:01:38.098Z SERIAL » [ACK] (0x06)
2021-10-25T13:01:38.101Z DRIVER « [REQ] [SendData]
callback id: 132
transmit status: OK
2021-10-25T13:01:38.126Z SERIAL « 0x010c000400040422010000b30067 (14 bytes)
2021-10-25T13:01:38.128Z DRIVER Dropping message because it could not be deserialized: The command class Appli
cation Status is not implemented
2021-10-25T13:01:38.129Z SERIAL » [ACK] (0x06)
2021-10-25T13:01:38.158Z SERIAL « 0x010c000400040422010000b30067 (14 bytes)
2021-10-25T13:01:38.160Z DRIVER Dropping message because it could not be deserialized: The command class Appli
cation Status is not implemented
2021-10-25T13:01:38.161Z SERIAL » [ACK]
2021-10-25T13:01:48.110Z CNTRLR [Node 004] Timed out while waiting for a response from the node