Open brabbana opened 3 months ago
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!
(message by CodeOwnersMention)
zwave_js documentation zwave_js source (message by IssueLinks)
Is the log showing motion detection, or what is it? That activity corresponds to entity binary_sensor.kitchen_sensor_sensor_state_aux
.
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
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
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.
Similar to the above - I frequently have to:
... Motion sensor is then 'good' for a few weeks.
Ah ha, happy to have found this as I've been encountering the same issue from around the same time after many happy years using many Fibaro FGMS001's. They all seem to now randomly be switching to the Aux sensor after a while: A repair makes it work again for a bit, but then it breaks again :(
11/8/2024, 8:22:17 PM - value updated Arg 0: └─commandClassName: Binary Sensor └─commandClass: 48 └─property: Aux └─endpoint: 0 └─newValue: false └─prevValue: true └─propertyName: Aux
ZwaveJS seems to report 3 binary sensors, but is suddenly ignoring the primary sensor and only reporting aux:
@dalester7 i tried pulling the battery and picking that back in but that didn't work. @iMiMx re-interview and wake up does seem to make it work again. That saves me the trauma of re-pairing them and is a faster workaround, thanks :)
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?
Additional information
No response