addons: Updates Z-Wave JS 0.1.67 and 0.1.66 no longer control TRV
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
- Updated via GUI, backing up the earlier version
- All TRV come are shown on ‘off’ state in Lovelace. Command to got to ‘Heat’ state is ignored
…
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.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19
@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…