Every time I update the Z-wave JS add-on; I have to fight to get my Aeotec Door/Window sensors to work again in Home Assistant.
I can open/close the sensors & see data updating in the Z-wave JS add-on logs but I do not see the sensor values updating in Home Assistant specifically.
It only affects 2 Aeotec Door/Window sensors; I have Aeotec plug switches that updating does not break & it also does not effect my ZCOMBOS ironically. Just the door sensors.
I am only using the Z-Wave JS Add-on; as of this moment I am not using Z-wave2mqtt. I was using that but I was having the same issue then so I switched to just using the JS add-on.
Z-Wave JS: Current version: 0.1.76
Home Assistant 2023.2.5
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230202.0 - latest
Are you sure your problem is “every time you update”? How often has this been happening?
At least in this particular case, it’s only something that would be seen in the latest add-on version, 0.1.76, not any version before (Z-Wave JS v10.6.0 and later). Maybe just bad luck. Anyways, here’s the relevant log:
2023-02-22T00:50:35.549Z DRIVER « [Node 014] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 49
└─[SupervisionCCGet]
│ session id: 0
│ request updates: false
└─[NotificationCCReport]
notification type: Access Control
notification status: 255
notification state: Window/door is open
state parameters: Window/door is open in regular position
HA does not currently support the state "Window/door is open in regular position", which was added recently to Z-Wave JS. This currently affects at least the Aeotec Door Sensor 7 Pro. The HA binary sensor will be stuck in the “closed” state. See this issue and related discussion for cause and workarounds, which involve using other sensors than the one you are likely using now. After reviewing those, if you are unable to workaround it, let us know. Be sure to do the re-interview to get the new sensors.
These errors will always occur when you update the add-on. In order to update the add-on, it downloads a new version, installs it and restarts it. When the add-on is restarted, HA loses connection to the web socket server and will reconnect later. As long as the integration is currently connected, those past errors can be ignored.
Thank you for the response; usually in most cases I have seen this issue present after a z-wave.js update. I’ll note that prior to this update I was using the zwave2mqtt plugin but I figured that I would troubleshoot item-by-item. Previously the issue would surprisingly just go away after a bit or sometimes I would have to go thru & exclude then re-interview the devices.
You may be right & this is just an anomaly that ironically has presented specific to that sensor that seems to have been up to this point a culprit.
I will review that discussion doc & work thru the re-interview process also.
Thank you kindly
I have the same issue after the last update of Zwave JS UI. The Aetoec Door Sensor 7 zwave categories have changed. I had to change the event to “Window/door is open in regular position” in my automations. Before it was “window_door_is_open” but this one is not anymore updated after the update. Indeed the values for window_door_is_open changes but are not well mapped by the zwave ui to generate the off/on values.
0.1.76 was a complete fail for me. All things Zwave stopped working and no amount of reloads/reboots/unplugging USB dongle could get things working again. I rolled back to 0.1.75 and it immediately started working again.