core: All Z-Wave JS entities are unavailable
The problem
Since this morning, Z-Wave JS integration displays Network ready but all entities are unavailable, when I restart Home-Assistant or try to reconfigure the integration I have this error:
zwave_js_server.exceptions.FailedZWaveCommand: Z-Wave error 111: The controller does not support soft reset or the soft reset feature has been disabled with a config option or the ZWAVEJS_DISABLE_SOFT_RESET environment variable. (ZW0111)
and on the addon
2023-09-27T08:05:07.734Z CNTRLR [Node 002] The node is alive.
2023-09-27T08:05:07.735Z CNTRLR [Node 002] The node is ready to be used
2023-09-27T08:05:07.736Z CNTRLR All nodes are ready to be used
2023-09-27T08:05:07.737Z CNTRLR « [Node 002] ping successful
New client
Z-Wave JS no longer supports enabling error reporting. If you are using an application that integrates with Z-Wave JS and you receive this error, you may need to update the application.
2023-09-27T08:06:32.458Z CNTRLR The controller does not support soft reset or the soft reset feature has been
disabled with a config option or the ZWAVEJS_DISABLE_SOFT_RESET environment va
riable.
Z-Wave error ZWaveError: The controller does not support soft reset or the soft reset feature has been disabled with a config option or the ZWAVEJS_DISABLE_SOFT_RESET environment variable. (ZW0111)
at Driver.softReset (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2473:10)
at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/driver/message_handler.js:80:30)
at Object.driver (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:41:91)
at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:125:99)
at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:57:45)
at WebSocket.emit (node:events:514:28)
at Receiver.receiverOnMessage (/usr/src/node_modules/ws/lib/websocket.js:1192:20)
at Receiver.emit (node:events:514:28)
at Receiver.dataMessage (/usr/src/node_modules/ws/lib/receiver.js:560:14)
at /usr/src/node_modules/ws/lib/receiver.js:511:23 {
code: 111,
context: undefined,
transactionSource: undefined
}
What version of Home Assistant Core has the issue?
core-2023.9.3
What was the last working version of Home Assistant Core?
core-2023.9.3
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
zwave_js
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Diagnostics information
config_entry-zwave_js-bf8232363f45c5b4d981a6be7de8737a.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
amd64-addon-zwave_js with version 0.1.92
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Reactions: 6
- Comments: 16 (4 by maintainers)
PR is up for a fix, we should have it in the next hour or two. If you can wait that long, you can upgrade once it is released and everything should go back to the way it was.
https://github.com/home-assistant/addons/pull/3232
Problem identified, thanks @Aohzan for actually including the relevant log.
Hard to post anything else than a “same here” comment here, 0.1.92 nuked my Zwave too, all z-wave devices unavailable, the “Manage your Z-Wave Network” control panel is empty or can report an unable to connect error. I have “repairs” notification saying that I have automation with non existent entities (the z-wave ones) .