home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.17k stars 31.14k forks source link

Vision Security ZG8101 sensor showing alarm type and level but no values #46982

Closed macf0x closed 3 years ago

macf0x commented 3 years ago

The problem

Vision Security ZG8101 (Garage Door Tilt Sensor) is not presenting all entities in HA. Values for alarm type and level are populate in the Node view of Z-wave-js (notifications/113), but the values aren't shown in HA. Also these initial entities are hidden in HA, when I exclude/include.

These entities never receive values 23-113-0-alarmType 23-113-0-alarmLevel

These appear to be duplicates of the above entities and do have values, but do not appear as addressable entities. 23-113-0-Home Security-Cover status 23-113-0-Home Security-Sensor status 23-113-0-Home Security-unknown

Even when unhiding the entities, the state is never updated. I believe it maybe related to the these values being classed as notifications (113), rather than Binary Sensor(48) or Basic(32).

I have opened an issue with zwave-js2mqtt, but advised to open one here as the no issue was found. https://github.com/zwave-js/zwavejs2mqtt/issues/592

Happy to provide more detail if below is insufficient.

Please see the attached Logs and Entity registry snippet. If you need further details please let me know.

Z-Wave JS to MQTT Current version: 0.4.4 MQTT Gateway disabled Using Mosquitto broker Current version: 5.1

What is version of Home Assistant Core has the issue?

core-2021.2.3

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/

Example YAML snippet

# Put your YAML below this line

Anything in the logs that might be useful for us?

# Put your logs below this line
15:59:22.447 CNTRLR [Node 023] treating BasicCC Set as a report
2021-02-24 15:59:22.450 INFO ZWAVE: Node 23: value updated: 48-0-Any false => true
2021-02-24 15:59:22.508 INFO ZWAVE: Node 23: value updated: 113-0-Home Security-Sensor status 2 => 2
2021-02-24 15:59:23.046 INFO ZWAVE: Node 23: value updated: 113-0-Home Security-unknown 254 => 254
2021-02-24 15:59:26.805 INFO ZWAVE: Node 23: value updated: 113-0-Home Security-unknown 254 => 254
15:59:28.977 CNTRLR [Node 023] treating BasicCC Set as a report
2021-02-24 15:59:28.979 INFO ZWAVE: Node 23: value updated: 48-0-Any true => false
2021-02-24 15:59:29.082 INFO ZWAVE: Node 23: value updated: 113-0-Home Security-Sensor status 2 => 2
15:59:29.680 CNTRLR [Node 023] treating BasicCC Set as a report
2021-02-24 15:59:29.681 INFO ZWAVE: Node 23: value updated: 48-0-Any false => true
2021-02-24 15:59:29.699 INFO ZWAVE: Node 23: value updated: 113-0-Home Security-Sensor status 2 => 2
2021-02-24 15:59:34.302 INFO ZWAVE: Node 23: value updated: 113-0-Home Security-Cover status 0 => 3
2021-02-24 15:59:36.698 INFO ZWAVE: Node 23: value updated: 113-0-Home Security-Cover status 3 => 3
15:59:38.717 CNTRLR « [Node 023] received wakeup notification
2021-02-24 15:59:38.719 INFO ZWAVE: Node 23 is now awake
15:59:38.720 CNTRLR [Node 023] The node is now awake.
2021-02-24 15:59:38.770 INFO ZWAVE: Node 23: value updated: 128-0-level 83 => 83
2021-02-24 15:59:38.771 INFO ZWAVE: Node 23: value updated: 128-0-isLow false => false
15:59:38.774 CNTRLR « [Node 023] received response for battery information:
level: 83
15:59:38.781 CNTRLR [Node 023] WakeUpCC: doing a partial interview...
15:59:38.782 CNTRLR » [Node 023] retrieving wakeup interval from the device...
2021-02-24 15:59:38.836 INFO ZWAVE: Node 23: value updated: 132-0-wakeUpInterval 7200 => 7200
2021-02-24 15:59:38.837 INFO ZWAVE: Node 23: value updated: 132-0-controllerNodeId 1 => 1
15:59:38.841 CNTRLR « [Node 023] received wakeup configuration:
wakeup interval: 7200 seconds
controller node: 1
15:59:38.842 CNTRLR [Node 023] AssociationCC: doing a partial interview...
15:59:38.843 CNTRLR » [Node 023] querying association group #1...
15:59:38.893 CNTRLR « [Node 023] received information for association group #1:
maximum # of nodes: 5
currently assigned nodes: 1
15:59:38.895 CNTRLR [Node 023] BasicCC: doing a partial interview...
15:59:38.896 CNTRLR » [Node 023] querying Basic CC state...
15:59:38.948 CNTRLR « [Node 023] received Basic CC state:
current value: 99
15:59:38.959 CNTRLR [Node 023] BinarySensorCC: doing a partial interview...
15:59:38.960 CNTRLR » [Node 023] querying current value...
2021-02-24 15:59:39.007 INFO ZWAVE: Node 23: metadata updated: 48-0-Any
2021-02-24 15:59:39.009 INFO ZWAVE: Node 23: value updated: 48-0-Any true => true
15:59:39.012 CNTRLR « [Node 023] received current value: true
15:59:39.014 CNTRLR [Node 023] NotificationCC: doing a partial interview...
15:59:39.015 CNTRLR [Node 023] Interview stage completed: CommandClasses
15:59:39.015 CNTRLR [Node 023] Interview stage completed: OverwriteConfig
15:59:39.016 CNTRLR » [Node 023] requesting node neighbors...
15:59:39.065 CNTRLR « [Node 023] node neighbors received: 1, 17
15:59:39.070 CNTRLR [Node 023] Interview stage completed: Neighbors
15:59:39.070 CNTRLR [Node 023] Interview completed
2021-02-24 15:59:39.074 INFO ZWAVE: Node 23: interview completed, all values are updated
15:59:40.076 CNTRLR » [Node 023] Sending node back to sleep...
15:59:51.308 CNTRLR [Node 023] The node did not respond after 1 attempts.
It is probably asleep, moving its messages to the wakeup queue.
2021-02-24 15:59:51.318 INFO ZWAVE: Node 23 is now asleep
15:59:51.320 CNTRLR [Node 023] The node is now asleep.

Entity config 265-2562-8202 (Node23).txt

Zwave-js log showing Basic CC providing value. zwavejs.log

github-actions[bot] commented 3 years ago

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.