search

home-assistant / addons

:heavy_plus_sign: Docker add-ons for Home Assistant
https://home-assistant.io/hassio/
Apache License 2.0
1.57k stars 1.52k forks source link

Updates Z-Wave JS 0.1.67 and 0.1.66 no longer control TRV #2641

Closed markblinkhorn closed 2 years ago

markblinkhorn commented 2 years ago

Describe the issue you are experiencing

Tried both recent updates to Z-Wave JS. Versions 0.1.67 and 0.1.66 no longer control my fleet of Eurotronics Spirit and Aeotec ZWA021 Thermostatic Radiator Valve. I have had to restore version 0.1.65 to regain control

What type of installation are you running?

Home Assistant Supervised

Which operating system are you running on?

Other (e.g., Raspbian/Raspberry Pi OS/Fedora)

Which add-on are you reporting an issue with?

Z-Wave JS

What is the version of the add-on?

as given in title

Steps to reproduce the issue

  1. Updated via GUI, backing up the earlier version
  2. All TRV come are shown on 'off' state in Lovelace. Command to got to 'Heat' state is ignored

  3. ...

Anything in the Supervisor logs that might be useful for us?

Nothing useful - here's a snip taken around the time of the update. You can see the add-on is started normally...

2022-08-29 15:20:52.122 DEBUG (MainThread) [homeassistant.components.sensor] Not adding entity diskstation2 (Drive 4) Status (Smart) because it's disabled
2022-08-29 15:20:52.125 DEBUG (MainThread) [homeassistant.components.sensor] Not adding entity diskstation2 Last Boot because it's disabled
2022-08-30 17:11:03.575 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.zwave_js
2022-08-30 17:11:03.588 DEBUG (MainThread) [homeassistant.components.sensor] Not adding entity TriSensor: Node Status because it's disabled
2022-08-30 17:11:03.589 DEBUG (MainThread) [homeassistant.components.sensor] Not adding entity Bulb 6 Multi-White: Node Status because it's disabled

Anything in the add-on logs that might be useful for us?

nothing much useful in the add-on log either...

                                   · UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
                                    · UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
                                    · UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
                                    · undefined (0xee)
                                    · UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)
                                    · UNKNOWN_FUNC_ZMEFreqChange (0xf2)
                                    · UNKNOWN_FUNC_ZMEBootloaderFlash (0xf4)
                                    · UNKNOWN_FUNC_ZMECapabilities (0xf5)
                                    · undefined (0xf7)
2022-08-30T16:19:10.630Z DRIVER   Soft reset is enabled through config, but this stick does not support it.
2022-08-30T16:19:10.672Z CNTRLR   querying version info...
2022-08-30T16:19:10.704Z CNTRLR   received version info:
                                    controller type: Static Controller
                                    library version: Z-Wave 4.61
2022-08-30T16:19:10.706Z CNTRLR   querying protocol version info...
2022-08-30T16:19:10.737Z CNTRLR   received protocol version info:
                                    protocol type:             Z-Wave
                                    protocol version:          4.61.0
2022-08-30T16:19:10.739Z CNTRLR   supported Z-Wave features: 
2022-08-30T16:19:10.740Z CNTRLR   querying controller capabilities...
2022-08-30T16:19:10.800Z CNTRLR   received controller capabilities:
                                    controller role:      primary
                                    is the SUC:           true
                                    started this network: true
                                    SIS is present:       true
                                    was real primary:     true
2022-08-30T16:19:10.801Z CNTRLR   querying serial API setup capabilities...
2022-08-30T16:19:10.840Z CNTRLR   supported serial API setup commands:
                                  · GetSupportedCommands
                                  · SetTxStatusReport
2022-08-30T16:19:10.841Z CNTRLR   Enabling TX status report...
2022-08-30T16:19:10.873Z CNTRLR   Enabling TX status report successful...
2022-08-30T16:19:10.873Z CNTRLR   finding SUC...
2022-08-30T16:19:10.896Z CNTRLR   This is the SUC
2022-08-30T16:19:10.896Z CNTRLR   querying additional controller information...
2022-08-30T16:19:11.012Z CNTRLR   received additional controller information:
                                    Z-Wave API version:         6 (legacy)
                                    Z-Wave chip type:           ZW050x
                                    node type                   Controller
                                    controller role:            primary
                                    controller is the SIS:      true
                                    controller supports timers: false
                                    nodes in the network:       1, 7, 9, 13, 17, 18, 19, 23, 24, 26
2022-08-30T16:19:11.082Z CNTRLR   [Node 001] Embedded device config loaded
2022-08-30T16:19:11.104Z CNTRLR   [Node 007] Embedded device config loaded
2022-08-30T16:19:11.222Z CNTRLR   [Node 009] Embedded device config loaded
2022-08-30T16:19:11.233Z CNTRLR   [Node 013] Embedded device config loaded
2022-08-30T16:19:11.252Z CNTRLR   [Node 017] Embedded device config loaded
2022-08-30T16:19:11.270Z CNTRLR   [Node 018] Embedded device config loaded
2022-08-30T16:19:11.288Z CNTRLR   [Node 019] Embedded device config loaded
2022-08-30T16:19:11.304Z CNTRLR   [Node 023] Embedded device config loaded
2022-08-30T16:19:11.313Z CNTRLR   [Node 024] Embedded device config loaded
2022-08-30T16:19:11.324Z CNTRLR   [Node 026] Embedded device config loaded
2022-08-30T16:19:11.339Z CNTRLR   setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2022-08-30T16:19:11.377Z CNTRLR   serial API timeouts overwritten. The old values were: ack = 1000 ms, byte = 15
                                  0 ms
2022-08-30T16:19:11.378Z CNTRLR   Interview completed
Starting server on 0.0.0.0:3000
2022-08-30T16:19:11.416Z CNTRLR   [Node 001] The node is alive.
2022-08-30T16:19:11.418Z CNTRLR   [Node 001] The node is ready to be used
2022-08-30T16:19:11.421Z CNTRLR » [Node 007] pinging the node...
2022-08-30T16:19:11.656Z CNTRLR   [Node 009] The node is asleep.
2022-08-30T16:19:11.660Z CNTRLR   [Node 009] The node is ready to be used
2022-08-30T16:19:11.662Z CNTRLR » [Node 013] pinging the node...
2022-08-30T16:19:11.666Z CNTRLR » [Node 017] pinging the node...
2022-08-30T16:19:11.671Z CNTRLR » [Node 018] pinging the node...
2022-08-30T16:19:11.675Z CNTRLR » [Node 019] pinging the node...
2022-08-30T16:19:11.679Z CNTRLR » [Node 023] pinging the node...
2022-08-30T16:19:11.704Z CNTRLR » [Node 024] pinging the node...
2022-08-30T16:19:11.708Z CNTRLR » [Node 026] pinging the node...
ZwaveJS server listening on 0.0.0.0:3000
2022-08-30T16:19:12.990Z CNTRLR   [Node 007] The node is alive.
2022-08-30T16:19:12.993Z CNTRLR   [Node 007] The node is ready to be used
2022-08-30T16:19:12.999Z CNTRLR « [Node 007] ping successful
2022-08-30T16:19:13.037Z CNTRLR   [Node 013] The node is alive.
2022-08-30T16:19:13.037Z CNTRLR   [Node 013] The node is ready to be used
2022-08-30T16:19:13.048Z CNTRLR « [Node 013] ping successful
2022-08-30T16:19:14.478Z CNTRLR   [Node 017] The node is alive.
2022-08-30T16:19:14.479Z CNTRLR   [Node 017] The node is ready to be used
2022-08-30T16:19:14.485Z CNTRLR « [Node 017] ping successful
2022-08-30T16:19:15.735Z CNTRLR   [Node 018] The node is alive.
2022-08-30T16:19:15.737Z CNTRLR   [Node 018] The node is ready to be used
2022-08-30T16:19:15.747Z CNTRLR « [Node 018] ping successful
2022-08-30T16:19:15.794Z CNTRLR   [Node 019] The node is alive.
2022-08-30T16:19:15.795Z CNTRLR   [Node 019] The node is ready to be used
2022-08-30T16:19:15.804Z CNTRLR « [Node 019] ping successful
2022-08-30T16:19:17.296Z CNTRLR   [Node 023] The node is alive.
2022-08-30T16:19:17.297Z CNTRLR   [Node 023] The node is ready to be used
2022-08-30T16:19:17.302Z CNTRLR « [Node 023] ping successful
2022-08-30T16:19:18.690Z CNTRLR   [Node 024] The node is alive.
2022-08-30T16:19:18.691Z CNTRLR   [Node 024] The node is ready to be used
2022-08-30T16:19:18.697Z CNTRLR « [Node 024] ping successful
2022-08-30T16:19:20.058Z CNTRLR   [Node 026] The node is alive.
2022-08-30T16:19:20.060Z CNTRLR   [Node 026] The node is ready to be used
2022-08-30T16:19:20.061Z CNTRLR   All nodes are ready to be used
2022-08-30T16:19:20.065Z CNTRLR « [Node 026] ping successful
New client
2022-08-30T16:21:25.368Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.

Additional information

Happy to try to grab more detailed logs if you need them. But, for now, I've gone back to 0.1.65 - because it works.

cortado commented 2 years ago

I Lost main entity (binary sensor access control) from Aeotec Door/Window ZW120 , not possible to get back with resets, firmware updates of sensor, remove/add from network, core or add on restarts etc. First became unavailable, after actions over: gone. everything else fine

alfwro13 commented 2 years ago

I have exactly same problem here - as I am new to z-wave I was scratching my head why suddenly my Eurotronics Spirit TRVs stopped responding. Restored it back to 0.1.65 and all is good again. I hope this is going to be fixed soon.

alfwro13 commented 2 years ago

I just would like to add that version 0.1.68 is also affected

christhementalist commented 2 years ago

Running latest 0.1.68 and adding a new Aeotec Door Sensor 7 (ZWA012) is missing the open/close binary sensor eg binary_sensor.bathroom_sliding_door_sensor_access_control_window_door_is_open. Other sensors appear to add ok but also default in a disabled state.

Already had a few of these devices added previously and they are still working fine and have the binary sensor working no problems.

alfwro13 commented 2 years ago

Question for dev team - why this issue has an unsupported label? Does it mean that you are not going to fix this issue? Thanks

markblinkhorn commented 2 years ago

Further note to dev team. This feels like an issue with Aeotec Z-Wave devices (Eurotronics Spirit is a clone of Aeotec ZWA021 {or vice versa}). I have already noted that I am happy to provide more detailed log information - this also includes building a Hassos R-Pi if this is the sole reason you have flagged this issue as Unsupported. Otherwise, please expalin why you have flagged it as Unsupported. Thank you.

cortado commented 2 years ago

I think you might be right @markblinkhorn. I have tried every trick in the book. Also talking with Aeotec support, which stated that since everything else works, it is strange that this binary sensor should not work and data not be sent. Is it possible that this binary sensor (access control entity) is not recognised for this device in new version – is some schema changed for the ZW120? Or is there some hangup in an XML file somewhere that has the ID or hardware address for this sensor and even if it is re-paired, those entity is somehow with errors? (sorry for noob question)

christhementalist commented 2 years ago

Noticed this post also, this is the exact behaviour I am getting but not using Zwavemqtt, just the default ZWaveJS addon - https://community.home-assistant.io/t/missing-door-state-entity-when-adding-ecolink-dwzwave25-sensors/456395

cortado commented 2 years ago

Looking a bit further it seems that the Sensor "Access Control" that gives state On/Off (open/closed) for doors is automatically set up as a door entity (with binary sensor) based on door state report in the Basic CC parameter from hardware sensor? Could there be a general error with door sensors, where the algorithm in Z-Wavs-JS that automatically generates entity has errors, or there is some schema bug?

markblinkhorn commented 2 years ago

Hey Guys - similar issue https://github.com/home-assistant/core/issues/77466 - seems to suggest updating to 0.1.68 and then re-interviewing all your devices fixes the issue. I will test and report back. @cortado @christhementalist @alfwro13

markblinkhorn commented 2 years ago

NBG - back to 0.1.65. Sorry

markblinkhorn commented 2 years ago

OK @mdegat01 I have now reinstalled the whole system with haos_rpi4-64-8.5.img and (unsurprisingly) get the identical behaviour. All versions of Z-Wave JS later than 0.1.65 fail to control the TRV fleet. 0.1.65 is still good. Is this issue still unsupported? If so, please explain why. Thanks

christhementalist commented 2 years ago

How do you restore back to 0.1.65? There's been a lot of changes in my environment since upgrading Z-Wave JS, so wouldn't like to do a full HA restore if I can help it.

markblinkhorn commented 2 years ago

@christhementalist Just go to Settings/System/Backups - click the backup labelled addon_core_zwave_js_0.1.65, select the 2 tick boxes and hit Restore. It will ask for confirmation that you want to do a Partial Restore. That's it.

You can't do a Full Restore anyway, as that will always download the latest versions of the Add-Ins...

cortado commented 2 years ago

@christhementalist Just go to Settings/System/Backups - click the backup labelled addon_core_zwave_js_0.1.65, select the 2 tick boxes and hit Restore. It will ask for confirmation that you want to do a Partial Restore. That's it.

You can't do a Full Restore anyway, as that will always download the latest versions of the Add-Ins...

If I do not have a backup, how do I obtain version 0.1.65? (I would also like to try downgrade)

markblinkhorn commented 2 years ago

@cortado I'm sorry, I don't know the answer to that question!

Meantime - I can confirm that 0.1.69 doesnt fix the issue either.

christhementalist commented 2 years ago

I restored to 0.1.65, removed and readded the Z-Wave devices I was having issues with. The added fine with the binary sensors as expected. I then upgraded to 2022.9.1 with Z-Wave JS 0.1.70 and all is working fine still.....however I haven't tried adding any new devices on this version.

markblinkhorn commented 2 years ago

I concur. Z-Wave JS 0.1.70 does seem to work correctly. Interesting to note the comment from the developer at https://github.com/zwave-js/node-zwave-js/pull/5017 "hopefully now we get to the bottom of whats going on with all these thermostats"

cortado commented 2 years ago

Z-wave-JS 0.1.71 gave me back the binary sensor for door/window Aeotec ZW120!! It is not mentioned in any release notes that I can see, but now it works again after re-interview.