After Update Zwave does not work anymore 
Anybody any ideas? I don’t know how to give attention to Z-Wave
and here is another screenshot:
and my dashboard is completely empty as well
I already did a restore to two weeks ago and then restored the core from this morning (before updating) to get the different installations and changes from the last two weeks back, but it didn’t help
Do I have to set-up HA completely new now?
I came to HA from openHAB only four weeks ago, because an update in openHAB crashed and I was curious for HA and everybody said: This can’t happen in HA… and now I already have a non-working system in the first month
You should be looking in the HA logs. Screenshots don’t really help.
It also helps to provide background information on your installation and situation. Are you using HAOS? If so, which Z-Wave add-on? Which version did you upgrade from?
I don’t have as many entities as you about half as many. All is fine over here. Did you try a full reboot of the server/computer they system is on. Not just a restart a full reboot.
What type or brand of controller are you using?
I have the Zooz S2 Stick 700 (ZST10 700) firmware is 7.18.3
seems to work well.
You might make sure you controller is on the supported list and firmware is at a good level.
Since you came from another project you might just confirm by reading through all seems good.
Here is a Screenshot of the log. But I do not find a button to export it.
I do use the hassio image on a raspberryPI 4, and the z-wave-stick is “ZMEEUZZBB”
I have upgraded the core to 10.5 and then the problems started. I then restored the whole system to the state of 15th october, but it didn’t help. Then I restored the core to 10.3 again, but it didn’t help either
The system has gone one step further.
It seems that all devices do send their status and the sensors to Homeassistant. I do see temperatures, etc.
But they do not react on orders that I place in Homeassistant.
And: I found a log to download:
2023-10-27 17:35:09.290 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2023-10-27 17:35:26.280 WARNING (MainThread) [homeassistant.config_entries] Config entry 'https://192-168-178-78.14030f24b70047d28d47682e3be210d2.plex.direct:32400' for plex integration not ready yet: HTTPSConnectionPool(host='plex.tv', port=443): Max retries exceeded with url: /api/v2/user (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1006)'))); Retrying in background
2023-10-27 17:35:32.543 WARNING (MainThread) [py.warnings] /usr/src/homeassistant/homeassistant/components/wolflink/__init__.py:54: RuntimeWarning: coroutine 'WolfClient.fetch_system_state_list' was never awaited
if not wolf_client.fetch_system_state_list(device_id, gateway_id):
2023-10-27 17:35:33.511 ERROR (MainThread) [denonavr.api] 192.168.178.72: Event callback caused an unhandled exception HTTPStatusError: Client error '403 Forbidden' for url 'http://192.168.178.72/goform/Deviceinfo.xml'
For more information check: https://httpstatuses.com/403
2023-10-27 17:35:55.908 WARNING (Recorder) [homeassistant.components.sensor.recorder] Entity sensor.wall_plug_switch_electric_consumption_kwh has state class total_increasing, but its state is negative. Triggered by state -21474828.6 with last_updated set to 2023-10-21T02:59:59.999999+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue
2023-10-27 17:35:55.909 WARNING (Recorder) [homeassistant.components.sensor.recorder] Entity sensor.wall_plug_switch_electric_consumption_kwh_2 has state class total_increasing, but its state is negative. Triggered by state -21474821.22 with last_updated set to 2023-10-21T02:59:59.999999+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue
2023-10-27 17:36:34.201 WARNING (MainThread) [py.warnings] /usr/src/homeassistant/homeassistant/components/wolflink/__init__.py:54: RuntimeWarning: coroutine 'WolfClient.fetch_system_state_list' was never awaited
if not wolf_client.fetch_system_state_list(device_id, gateway_id):
2023-10-27 17:38:43.313 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.0', 3000)]; Retrying in background
2023-10-27 17:39:19.097 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to start the Z-Wave JS add-on: Another job is running for job group container_addon_core_zwave_js
2023-10-27 17:40:02.139 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to start the Z-Wave JS add-on: Another job is running for job group container_addon_core_zwave_js
2023-10-27 17:42:40.077 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.home_control_metering_plug_3 are missing or not currently available
2023-10-27 17:47:30.716 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.0', 3000)]; Retrying in background
2023-10-27 17:48:47.804 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.home_control_metering_plug_3 are missing or not currently available
2023-10-27 18:20:10.339 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 18:20:55.001 WARNING (MainThread) [py.warnings] /usr/src/homeassistant/homeassistant/components/wolflink/__init__.py:54: RuntimeWarning: coroutine 'WolfClient.fetch_system_state_list' was never awaited
if not wolf_client.fetch_system_state_list(device_id, gateway_id):
2023-10-27 18:23:10.350 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 18:55:05.057 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 18:58:05.061 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 19:09:33.534 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 19:12:33.537 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 19:22:17.171 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 19:25:17.175 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 19:33:19.688 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 19:36:19.692 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 20:05:08.662 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 20:08:08.665 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.mini_plug_switch_with_metering_gen5_2 are missing or not currently available
2023-10-27 20:09:34.164 WARNING (MainThread) [py.warnings] /usr/src/homeassistant/homeassistant/components/wolflink/__init__.py:54: RuntimeWarning: coroutine 'WolfClient.fetch_system_state_list' was never awaited
if not wolf_client.fetch_system_state_list(device_id, gateway_id):
2023-10-27 20:12:31.099 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.0', 3000)]; Retrying in background
2023-10-27 20:13:49.355 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.home_control_metering_plug_3 are missing or not currently available
So it means the integration cannot talk to the add-on. You’ll want to go to the add-on logs next and see what’s happening over there.
you mean this?:
2023-10-27T18:13:31.182Z CNTRLR « [Node 036] ping successful
2023-10-27T18:13:31.299Z CNTRLR [Node 015] The node is alive.
2023-10-27T18:13:31.301Z CNTRLR [Node 015] The node is ready to be used
2023-10-27T18:13:31.304Z CNTRLR « [Node 015] ping successful
2023-10-27T18:13:41.311Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
New client
2023-10-27T18:13:54.057Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:14:01.827Z CNTRLR The controller is unresponsive
2023-10-27T18:14:01.832Z DRIVER Controller missed Send Data callback. Attempting to recover...
2023-10-27T18:14:01.844Z 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.
2023-10-27T18:14:01.846Z CNTRLR [Node 026] ping failed: Timeout while waiting for a callback from the controll
er (ZW0200)
2023-10-27T18:14:20.614Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:14:35.664Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:14:54.393Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:14:59.616Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:16:00.372Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:16:15.897Z CNTRLR [Node 025] The node is now alive.
2023-10-27T18:16:15.902Z CNTRLR [Node 025] The node is ready to be used
2023-10-27T18:18:05.386Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:19:01.547Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:19:18.589Z DRIVER Dropping message because it could not be deserialized: The command class All S
witch is not implemented (ZW0303)
2023-10-27T18:19:18.614Z DRIVER Dropping message because it could not be deserialized: The command class All S
witch is not implemented (ZW0303)
2023-10-27T18:19:18.642Z DRIVER Dropping message because it could not be deserialized: The command class All S
witch is not implemented (ZW0303)
2023-10-27T18:19:28.150Z DRIVER no handlers registered!
2023-10-27T18:19:37.168Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:19:39.423Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:19:48.211Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:20:15.274Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:20:24.336Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:20:37.941Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:21:01.071Z DRIVER Dropping message because it could not be deserialized: The command class unkno
wn (0x24) is not implemented (ZW0303)
2023-10-27T18:21:12.237Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:21:18.825Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:22:15.918Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:22:18.768Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:22:22.376Z CNTRLR « [Node 010] received wakeup notification
2023-10-27T18:22:22.380Z CNTRLR [Node 010] The node is now awake.
2023-10-27T18:22:22.642Z CNTRLR » [Node 010] Sending node back to sleep...
2023-10-27T18:23:18.436Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:23:31.804Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:23:55.513Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:24:31.029Z DRIVER Dropping message because it could not be deserialized: The command class unkno
wn (0x24) is not implemented (ZW0303)
2023-10-27T18:24:34.124Z CNTRLR [Node 012] is unknown - discarding received command...
2023-10-27T18:24:49.197Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:24:55.213Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:25:11.382Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:25:21.878Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:25:42.376Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:26:47.994Z CNTRLR « [Node 013] TODO: no handler for application command
2023-10-27T18:27:08.386Z DRIVER Dropping message because it could not be deserialized: The command class unkno
wn (0x24) is not implemented (ZW0303)
2023-10-27T18:27:21.892Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:27:30.868Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:28:24.192Z CNTRLR « [Node 013] TODO: no handler for application command
2023-10-27T18:29:14.222Z CNTRLR « [Node 013] TODO: no handler for application command
2023-10-27T18:29:42.652Z DRIVER Dropping message because it could not be deserialized: The command class Contr
oller Replication is not implemented (ZW0303)
2023-10-27T18:30:24.174Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:30:40.082Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:31:24.789Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:31:25.489Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:32:15.161Z CNTRLR « [Node 015] Received updated node info
2023-10-27T18:32:15.164Z CNTRLR [Node 015] Node does not send unsolicited updates; refreshing actuator and sen
sor values...
2023-10-27T18:32:15.168Z CNTRLR » [Node 015] querying Binary Switch state...
2023-10-27T18:32:20.291Z CNTRLR « [Node 015] Received updated node info
2023-10-27T18:32:20.294Z CNTRLR [Node 015] Node does not send unsolicited updates; refreshing actuator and sen
sor values...
2023-10-27T18:32:20.298Z CNTRLR » [Node 015] querying Binary Switch state...
2023-10-27T18:32:35.622Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:32:54.164Z CNTRLR « [Node 013] TODO: no handler for application command
Z-Wave error ZWaveError: Cannot check for firmware updates for node 4: fingerprint or firmware version is unknown! (ZW0260)
at ZWaveController.getAvailableFirmwareUpdates (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:6653:10)
at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:211:54)
at Object.controller (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:40:99)
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:517:28)
at Receiver.receiverOnMessage (/usr/src/node_modules/ws/lib/websocket.js:1192:20)
at Receiver.emit (node:events:517: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: 260,
context: undefined,
transactionSource: undefined
}
2023-10-27T18:34:07.547Z CNTRLR [Node 141] is unknown - discarding received command...
2023-10-27T18:34:14.676Z CNTRLR [Node 044] is unknown - discarding received command...
2023-10-27T18:35:12.220Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
2023-10-27T18:36:02.349Z DRIVER Dropping message because it could not be deserialized: The command class unkno
wn (0x24) is not implemented (ZW0303)
2023-10-27T18:37:11.298Z CNTRLR [Node 013] does not support CC Meter - discarding received command...
Yes, if you refresh it you might see it restarting?
I also have been having a lot of issues with my zwave setup recently. I believe I have an in-between setup with my zwave setup.
I still have the official Zwave JS add-on installed and running. And I have Z-wave JS UI also installed and running. I believe I set this up when Zwave JS was not the official zwave method and zwavejs UI was still kinda a beta option. I followed some guide when I did it.
I’ve been noticed some of the recent updates to Zwave have been breaking my setup so it sounds like I might need to take the jump over to full zwave js UI setup.
I plan on following this guide soon:
Hi freshcoast,
I now just tried to uninstall the zwave-integration and then reinstall again.
It shows:
And when I click on “konfigurieren” it shows:
And I have absolutely no idea what I shall do. This is since the update from last thursday.
Any help would be very appreciated,
Torsten
Revert back to previous version before you did the upgrade.
That’s what backups are for.
Hi,
I have backuped to October 15th but it didn’t help. I will try again.
I have backed up to October 15th again (where it still worked)
It now shows this:
Other things that have worked before are not working anymore as well after the backup:
I think I will completely set the system up as new. What a pity
Well TBH, we can’t really help you because your images are in a different language. This is an English only server for a reason, and that reason is to get proper help from everyone.
Hi,
I got it working: I had to change the USB-Port to /dev/ttyACM0 in the YAML-configuration after the update:
even if it is not shown now in the visual builder:
But anyway: It works again 
If you use /dev/serial/by-id it won’t happen in the future either 
1 Like
Are you able to point me in the direction of how to find this file to edit?