ZSE43 Shock Sensor Miscategorized as Diagnostic

Feature Requests
1

The Zooz ZSE43 Tilt and Shock Sensor provides two sensor readings. One is for tilt status and the other for vibration/shock. In HA, the latter sensor is categorized as DIAGNOSTIC - i believe as a result of this line: core/binary_sensor.py at 82798730185dfef0e5c11b5ba006372872982cc8 · home-assistant/core · GitHub

I’d like to suggest removing that categorization. In general, a detection of tampering could indicate an operational issue that requires attention - particularly in the context of a Home Security device.

I know this change will affect more than just this sensor. But I think it’s universally applicable in that this detection should be a core security event, not solely a diagnostic concern.

I can submit a PR, but I don’t have a testing environment built for HA to validate that there are no unintended side effects.

2

Hrm… in the meantime is there a good way to use the shock sensor?

1 Like
3

Any movement on this? I bought one of these for use as a dishwasher sensor. I need both sensors to work for my use case.

1 Like
4

Pinging this thread also, now I have 6 sensors just sitting around doing nothing :\

5

@JackPo @GoodyGizmos @Meeseeks @justindthomas - any of you get this device working?

I’m curious which entities are showing up for you?

By default I saw:
Battery level
Home security - tampering, product cover
Low battery level
Node status

Several sensors were disabled:
Indicator value
Sensor state (unknown 0x00)
Access control - door state
Etc

By default I only see sensor state movement with the home security tampering product cover entity. However it is when I move the device: detects tampering and then gets cleared. It’s like the wires are crossed.

I tried enabling some of the disabled sensors but no change in status was detected.

Is that what you all are seeing too?

I’ll try to file a bug report to better track this - vs - feature request if so…

6

Because I use Node Red, it’s mostly an aesthetic issue for me. The entity still shows up in NR to select and interact with as a Tamper Sensor, so I can build my automations like I normally would.

For folks who use HA automations solely, it may prevent proper operation (i.e., it might be wholly unselectable). That certainly would seem like a bug to me.

7

I ended up talking to thesmartesthome folks extensively, and this is what they told me:

“We are working closely with the JS Z-Wave developers, and they are working towards a resolution, which will hopefully be provided soon.”

So I ended up getting a refund to the existing sensors, and for the moment bought some Aeotec multisensors for now that worked out of the box.

8

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’s been fixed, but no add-ons are updated yet.

1 Like
9

That is promising - I haven’t bought the unit yet but was about to do so… I’ll probably get one and hope the add-ons are ready already… or soon. I do wonder how many add-ons would need to be updated?

10

Any update on this? Just set up my sensor and it’s still using the security feature instead of vibration.

11

I just installed the Zwave JS integration on Saturday (was previously using SmartThings Hub), integrated the ZSE43 sensor and ran into this same problem.

It seems weird that the official HA integration wouldn’t have received any updates between September of 2022 and June of 2023.

12

This looks like it’s still an issue. Any movement?

13

Bummer. I just bough this for black friday and yes. it seems busted still?

14

If you are having a problem with the device, it would be best to post a new issue in the Z-Wave category with a description of the problem, as this post is for a feature request. The feature request doesn’t seem to describe any functional issue (see follow up), just a cosmetic one, the diagnostic category mostly influences how the entity is shown in the UI (e.g. omitted from automatic dashboards). The other comments seem to be unrelated to the feature request and perhaps reference already fixed issues.