Zooz ZSE18 has no entities for vibration sensor

[justintime]

The problem

I have two Zooz ZSE18 Z-wave devices. They both function very well as motion sensors. However, there are no vibration sensor entities set up by HA to allow me to trigger automations based on vibration. The configuration of the device in HA does allow me to verify that the vibration sensor is enabled, but there's no entities on the device for vibration.

What version of Home Assistant Core has the issue?

2023.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

zwave-js

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

zwave_js-96d38870698b6136b1eec3b97092b670-Motion and Vibration Sensor-3016f044ccb257de5f035992dfc7adfe.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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` Change the title of 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]

You should confirm with Zooz how the vibration sensor functionality is supposed to be exposed. I seem to recall from somewhere that they were using the tamper binary sensor, which would for you would be entity binary_sensor.dryer_motion_sensor_sensor_state_tamper.

[justintime]

Support at Zooz is of no help at all, they basically shrugged and sent me here. I'll see if your hunch on it being the tamper sensor is right. Thanks for the tip. Either way, I'll come back and update this issue. There's pretty much zero search results on this topic.

[kpine]

I think the answer you get from Zooz support depends on how you ask it. You should not be asking how to use it with Home Assistant. You should ask the technical details as to how the tamper functionality is supported via Z-Wave.

[justintime]

The tamper sensor doesn't seem to trigger at all. Typically, a tamper sensor means someone opened the unit - opening it didn't trigger the sensor. I shook the sensor for 15 seconds and that didn't trigger it either. I'll try rephrasing my question with support, I'll let you know how that works out.

[kpine]

You're right, but that kind of tamper alarm is usually done via the Notification CC, in this case it's a Binary Sensor CC. Minor difference, which is why it came to mind. There's no "vibration" type of sensor provided by Z-Wave, so it seems they choose to use the deprecated Binary Sensor.

If you want to ask a technical question, I would ask which Z-Wave Command Class the vibration alerts are reported with.

I dug around and this SmartThings device handler for the ZSE18 supports an "acceleration sensor" via the Binary Sensor CC with sensor type Tamper (type 8), which matches the HA tamper sensor. From further reading, it sounds like the sensor is just not very sensitive. For example, the creator of that handler could not get it to work reliably with their dryer.

For reference, here's the definition of the tamper binary sensor in HA:

{
        "domain": "binary_sensor",
        "entity_id": "binary_sensor.dryer_motion_sensor_sensor_state_tamper",
        "original_name": "Sensor state (Tamper)",
        "original_device_class": null,
        "disabled": true,
        "disabled_by": "user",
        "hidden_by": null,
        "original_icon": null,
        "entity_category": null,
        "supported_features": 0,
        "unit_of_measurement": null,
        "value_id": "74-48-0-Tamper",
        "primary_value": {
          "command_class": 48,
          "command_class_name": "Binary Sensor",
          "endpoint": 0,
          "property": "Tamper",
          "property_name": "Tamper",
          "property_key": null,
          "property_key_name": null
        }
      }

If refers to the driver Binary Sensor CC Tamper property, which looks like:

        {
          "endpoint": 0,
          "commandClass": 48,
          "commandClassName": "Binary Sensor",
          "property": "Tamper",
          "propertyName": "Tamper",
          "ccVersion": 2,
          "metadata": {
            "type": "boolean",
            "readable": true,
            "writeable": false,
            "label": "Sensor state (Tamper)",
            "ccSpecific": {
              "sensorType": 8
            }
          },
          "value": false,
          "nodeId": 74
        },

So you can see the value behind that entity is the Binary Sensor CC, with sensor type Tamper (8), same as SmartThings.

[justintime]

Here's what I received back from support regarding the technical specs:

Here are the settings details for the vibration sensor:

Vibration Sensor
Parameter 17: Use it to disable the vibration sensor.
Values: 0 - vibration sensor is disabled, 1 - vibration sensor is enabled (default).
Size: 1 byte dec.

Here are all of the ZSE18's command classes:

COMMAND_CLASS_ASSOCIATION_GRP_INFO
COMMAND_CLASS_ASSOCIATION_V2
COMMAND_CLASS_BATTERY
COMMAND_CLASS_CONFIGURATION
COMMAND_CLASS_DEVICE_RESET_LOCALLY
COMMAND_CLASS_FIRMWARE_UPDATE_MD_V3
COMMAND_CLASS_MANUFACTURER_SPECIFIC_V2
COMMAND_CLASS_NOTIFICATION_V5
COMMAND_CLASS_POWERLEVEL
COMMAND_CLASS_SECURITY
COMMAND_CLASS_SECURITY_S2
COMMAND_CLASS_SUPERVISION
COMMAND_CLASS_TRANSPORT_SERVICE_V2
COMMAND_CLASS_VERSION_V2
COMMAND_CLASS_WAKE_UP_V2
COMMAND_CLASS_ZWAVEPLUS_INFO_V2

The also stated Our techs confirmed the vibration alerts would be COMMAND_CLASS_NOTIFICATION_V5.

[kpine]

The also stated Our techs confirmed the vibration alerts would be COMMAND_CLASS_NOTIFICATION_V5.

You can ask them which notification type and values are reported. There are no notifications for "vibration". So either they are repurposing a different type, like the tamper notification you already have, or using something non-standard. The other option is that the alarm is not an entity, but an event which you can listen for.

Please post driver debug logs of a re-interview, as well as a time frame that captures a vibration alarm being reported. It will be easier to work from that.

[issue-triage-workflows[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.