Multi-Sensor FGMS001 Not Reporting Motion through Z-Wave JS Integration

[brabbana]

The problem

This sensor has been working for a long time - it reports temperature, luminosity, motion, etc. It is still reporting temperature and luminosity but I have stopped getting motion events. I have looked at the Z-Wave JS logs and I get an entry when there is motions and again 90 secs later I get the motion off event (entries from log included). Diagnostics also attached.

Appreciate any advice!

What version of Home Assistant Core has the issue?

2024.8.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

Z-Wave JS

Link to integration documentation on our website

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

Diagnostics information

zwave_js-c58531960dbb6679a403c670e6d24831-Motion Sensor-8ee2940376a92a58baa214156fda52ce.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Subscribed to Z-Wave JS Log Messages…
2024-08-14T11:46:33.950Z SERIAL « 0x010900040007033003ff3a                                            (11 bytes)
2024-08-14T11:46:33.960Z SERIAL » [ACK]                                                                   (0x06)
2024-08-14T11:46:33.971Z CNTRLR   [Node 007] [Binary Sensor] Aux: metadata updated                  [Endpoint 0]
2024-08-14T11:46:33.979Z CNTRLR   [Node 007] [~] [Binary Sensor] Aux: false => true                 [Endpoint 0]
2024-08-14T11:46:33.984Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: true
2024-08-14T11:46:33.991Z SERIAL « 0x010900040007032001ff28                                            (11 bytes)
2024-08-14T11:46:33.996Z SERIAL » [ACK]                                                                   (0x06)
2024-08-14T11:46:34.002Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
                                  └─[BasicCCSet]
                                      target value: 255
2024-08-14T11:46:34.006Z CNTRLR   [Node 007] treating BasicCC::Set as a report
2024-08-14T11:46:34.011Z CNTRLR   [Node 007] [~] [Basic] currentValue: 0 => 255                     [Endpoint 0]
2024-08-14T11:48:14.008Z SERIAL « 0x01090004000703300300c5                                            (11 bytes)
2024-08-14T11:48:14.016Z SERIAL » [ACK]                                                                   (0x06)
2024-08-14T11:48:14.026Z CNTRLR   [Node 007] [Binary Sensor] Aux: metadata updated                  [Endpoint 0]
2024-08-14T11:48:14.038Z CNTRLR   [Node 007] [~] [Binary Sensor] Aux: true => false                 [Endpoint 0]
2024-08-14T11:48:14.043Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: false
2024-08-14T11:48:14.051Z SERIAL « 0x01090004000703200100d7                                            (11 bytes)
2024-08-14T11:48:14.057Z SERIAL » [ACK]                                                                   (0x06)
2024-08-14T11:48:14.062Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
                                  └─[BasicCCSet]
                                      target value: 0
2024-08-14T11:48:14.067Z CNTRLR   [Node 007] treating BasicCC::Set as a report
2024-08-14T11:48:14.072Z CNTRLR   [Node 007] [~] [Basic] currentValue: 255 => 0                     [Endpoint 0]

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` 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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[kpine]

Is the log showing motion detection, or what is it? That activity corresponds to entity binary_sensor.kitchen_sensor_sensor_state_aux.

[brabbana]

kpine - thanks. From your comment I can see a new entity has been added called Aux and its state is changing, the old Motion entity is not changing at all. No idea why but I can go and rename and reconnect things now. Appreciate your help

[kpine]

The driver Z-Wave JS decides how the binary sensor is reported. I know there were recent changes related to this area (possibly https://github.com/zwave-js/node-zwave-js/pull/6933), you might confirm whether reporting as an Aux sensor is the correct behavior or not for your device. https://github.com/zwave-js/node-zwave-js/issues/new/choose

[dalester7]

Same issue for me also started a week or 2 ago except I didn't have a new aux entity. I ended up getting it working again by pulling the battery for a few second. All the other sensors were working fine, just not the motion. Bit it's good now.

[iMiMx]

Similar to the above - I frequently have to:

• Re-interview
• Wake up the device a couple of times

... Motion sensor is then 'good' for a few weeks.