Zooz tilt and shock sensor ZSE43 doesn't work correctly

[lanly-dev]

The problem

When I add this sensor to the HA, and this shows up as:

First of all, the window/door is open item shows up twice (not sure why), and it is corresponding to the tilt sensor which is working. However, the 2 items below it don't seem to change the value and it doesn't seem there is anything that corresponds to the shock sensor of the device.

After I talked with Zooz support, they said:

For the ZSE43, Home Assistant (Z-Wave JS integration and/or zwavejs2mqtt add-on) classifies the vibration sensor as a tamper sensor. There’s a bug in the version of the z-wave driver that the add-ons are using that causes this problem with door sensors (in this case, the tilt sensor). It looks like the add-ons have not been updated yet. Since this is an open-source platform, it doesn't come with any type of dedicated tech support. Instead, their developers asked us to refer customers to the community forums for help and to report issues on GitHub and Discord, and I would recommend following up there as well

So I looked in the logBook it does show it as the tamper sensor

I'm wondering if there is a way to configs the device to behave correctly...

What version of Home Assistant Core has the issue?

core-2023.7.3

What was the last working version of Home Assistant Core?

n/a

What type of installation are you running?

Home Assistant Container

Integration causing the issue

zwave

Link to integration documentation on our website

n/a

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation
zwave_js source
_{^{(message by IssueLinks)}}

[kpine]

Please provide the device diagnostic file as requested in the issue template.

Go to the device page, click ..., click Download diagnostics, and attach to a comment by drag and drop (do not copy and paste contents).

I think Zooz is mistaken in their response though. I would ask them where this has been fixed in Z-Wave JS.

[kpine]

For the ZSE43, Home Assistant (Z-Wave JS integration and/or zwavejs2mqtt add-on) classifies the vibration sensor as a tamper sensor. There’s a bug in the version of the z-wave driver that the add-ons are using that causes this problem with door sensors (in this case, the tilt sensor).

OK, I think I have an answer for this. They are probably referring to #78640 (comment). That was fixed over a year ago.

In your list of disabled sensors you should have a binary sensor corresponding to tilt. The device diagnostic will confirm that.

As for the shock functionality, as you can see in the logbook, that is mapped to the tamper sensor. That is the expected behavior since Zooz has re-purposed the standard tamper notification for shock.

[lanly-dev]

ok, I'm pretty new to HA. Now it works as expected after configs it properly. Thank you!