Zwave-JS integration stopped updating everspring SM103 door and window sensor open/close function

[bazmk2]

The problem

Recent update to zwave-js has broken the notification ofnopen close window sensors SM103 by everspring.

What is version of Home Assistant Core has the issue?

core-2021.4.5

What was the last working version of Home Assistant Core?

Unsure but about 2 weeks ago

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Zwave_js and zwavejs2mqtt

Link to integration documentation on our website

https://github.com/hassio-addons/addon-zwavejs2mqtt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Zwave-js logs from debug when 2 separate nodes activated

2021-04-19T18:00:03.712Z CNTRLR [Node 009] treating BasicCC::Set as a report
2021-04-19 19:00:03.720 INFO ZWAVE: Node 9: value added: 32-0-currentValue => 99
2021-04-19 19:00:03.753 INFO ZWAVE: Node 9: value added 9-32-0-currentValue => 99
2021-04-19T18:00:07.150Z CNTRLR [Node 009] treating BasicCC::Set as a report
2021-04-19 19:00:07.159 INFO ZWAVE: Node 9: value updated: 32-0-currentValue 99 => 0
2021-04-19T18:00:28.309Z CNTRLR [Node 013] treating BasicCC::Set as a report
2021-04-19 19:00:28.316 INFO ZWAVE: Node 13: value added: 32-0-currentValue => 99
2021-04-19 19:00:28.348 INFO ZWAVE: Node 13: value added 13-32-0-currentValue => 99
2021-04-19T18:00:35.422Z CNTRLR [Node 013] treating BasicCC::Set as a report
2021-04-19 19:00:35.427 INFO ZWAVE: Node 13: value updated: 32-0-currentValue 99 => 0

Additional information

I have done some testing with this. Initially this was set up as a HASSOS as a ESXi VM with an aeotec gen5 stick on usb pass through.

Rebuilt the zwave network on a OrangePi running Armbian with zwavejs as I was concerned about range and the esx host is in the garage. No joy.

Rebuilt the zwave network on orangepi but with uzb.me stick. No joy.

Built a new Homeassistant VM based on debian10 and supervised install and fresh zwavejs. No joy.

I can see the values changing in the zwavejs debug as shown in the logs above but this is not represented in homeassistant.

Of note I have also observed that the majority of the sm103 sensors I have are just direct magnet to sensor, these are reported as on permanently. I have 3 Set up with the external wires connected to a magnet switch and these are reported as off permanently. In the logs the direct is Node 9 the wired is Node 13

The rest of my zwave devices and the network work OK.

[kpine]

Please attach (drag & drop file into comment) a network dump to help diagnose the problem.

[bazmk2]

zwave_js_dump.zip

[probot-home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with an integration (zwave_js) you are listed as a codeowner for? Thanks! _{^{(message by CodeOwnersMention)}}

[MartinHjelmare]

Which driver (node-zwave-js) version are you running?

[bazmk2]

zwavejs2mqtt: 3.4.0 zwave-js: 7.2.4

Thanks :)

[kpine]

Do you know which version of the driver this device was working in?

[bazmk2]

I am very sorry but no. It was about 2 weeks ago when I updated and I am normally fairly up to date with current release. It was originally on just the zwavejs rather than than zwavejs2mqtt that it is now on as it is currently deployed on an orange pi remote from my esxi host. I only noticed when the main doors stopped going bing when opened as there are no error messages thrown up.

[kpine]

@AlCalzone Considering the comment that this used to work, does this look like another device that needs the basic mapping compat flag? It is a Binary Sensor device type and looks like it uses Basic Set 0/99 to indicate close/open (manual). Do you need any further info to confirm?

[AlCalzone]

@kpine sounds like it. Can you open an issue or PR in the node-zwave-js repo?

[bazmk2]

Thanks for the help with this. I can confirm that the nodes now act as appropriate once the enablebBasicSetMapping flag is set to true (local edit on my container and re-interviewed)

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.