Aktueller Fehler in Zwave js und JSUi

Robert · 12. September 2023 um 10:11

Hi Zusammen,

Aktuell ist im zwave js 1.89 und JS Ui 1.15.10 Bug vorhanden…

github.com/home-assistant/core

Zwave

offen 01:17PM - 06 Sep 23 UTC

geschlossen 02:18PM - 13 Sep 23 UTC

kuzi6522

integration: zwave_js

### The problem Zwave stops working on all devices. After restart works for a…while then stops. All devices can be seen on dashboard but no control. I rolled back to previous version with the same issue ### What version of Home Assistant Core has the issue? Current ### What was the last working version of Home Assistant Core? Current ### What type of installation are you running? Home Assistant Core ### Integration causing the issue Zwave ### Link to integration documentation on our website NA ### Diagnostics information ``` Front Door Light Sunset: Error executing script. Unexpected error for call_service at pos 1: '5ee498498a304eb681669eda6bced32b' 9:06:55 AM – (ERROR) Automation - message first occurred at 9:06:54 AM and shows up 2 times Garage Light Off BD Closed: Error executing script. Unexpected error for call_service at pos 1: 'e27f9c7316674bbc9af2f76ec40b51d0' 9:06:55 AM – (ERROR) Automation - message first occurred at September 4, 2023 at 5:02:36 PM and shows up 6 times Garage Light On BD Open: Error executing script. Unexpected error for call_service at pos 1: 'fb0dd455e5b942e3baecdf5a7bc2243f' 9:06:55 AM – (ERROR) Automation - message first occurred at September 4, 2023 at 5:02:36 PM and shows up 6 times [2546299816] '47c6fe9112c845d3935456f27da71c04' 9:06:54 AM – (ERROR) Home Assistant WebSocket API - message first occurred at September 4, 2023 at 5:02:36 PM and shows up 11 times Error executing service: <ServiceCall light.turn_off (c:01H9MDSVF8STMBKTRYV7SH42D1): entity_id=['light.cabinet_light_3'], params=> 9:06:54 AM – (ERROR) components/zwave_js/entity.py - message first occurred at 9:06:54 AM and shows up 12 times Error doing job: Task exception was never retrieved 9:06:54 AM – (ERROR) components/zwave_js/update.py - message first occurred at September 4, 2023 at 11:50:07 AM and shows up 11 times Back Lock (L5001US): Failed to connect to the lock: Back Lock (L5001US) - 78:9C:85:34:04:0A: Failed to connect after 7 attempt(s): failed to discover services, device disconnected 9:05:53 AM – (ERROR) runner.py - message first occurred at September 3, 2023 at 7:49:20 PM and shows up 2110 times A message handler raised an exception: 'org.bluez.Device1'. Traceback (most recent call last): File "src/dbus_fast/message_bus.py", line 811, in dbus_fast.message_bus.BaseMessageBus._process_message File "/usr/local/lib/python3.11/site-packages/bleak/backends/bluezdbus/manager.py", line 854, in _parse_msg condition_callback() File "/usr/local/lib/python3.11/site-packages/bleak/backends/bluezdbus/manager.py", line 709, in callback self._properties[device_path][defs.DEVICE_INTERFACE][property_name] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^ KeyError: 'org.bluez.Device1' 9:01:33 AM – (ERROR) runner.py - message first occurred at September 3, 2023 at 8:01:21 PM and shows up 7938 times Garage Light Off BD Closed: Already running 9:01:24 AM – (WARNING) Automation - message first occurred at September 4, 2023 at 4:13:49 PM and shows up 16 times Garage Light On BD Open: Already running 9:01:18 AM – (WARNING) Automation - message first occurred at September 4, 2023 at 4:13:31 PM and shows up 16 times Update of climate.home is taking over 10 seconds 8:58:20 AM – (WARNING) helpers/entity.py - message first occurred at September 4, 2023 at 7:50:14 PM and shows up 11 times Referenced entities switch.jasco_products_14288_duplex_receptacle_switch are missing or not currently available 7:05:06 AM – (WARNING) helpers/service.py - message first occurred at September 4, 2023 at 1:01:12 AM and shows up 17 times API returned 403 from /portal/Device/CheckDataSession/8222562 request 7:00:12 AM – (ERROR) components/honeywell/climate.py - message first occurred at September 4, 2023 at 2:58:04 AM and shows up 30 times Back Lock (L5001US): Bluetooth error updating 6:19:02 AM – (ERROR) /usr/local/lib/python3.11/site-packages/yalexs_ble/push.py - message first occurred at September 3, 2023 at 9:40:14 PM and shows up 30 times Error fetching speedtestdotnet data: Selected server is not found. 4:55:37 AM – (ERROR) Speedtest.net - message first occurred at September 4, 2023 at 4:52:10 AM and shows up 3 times Error fetching tesla-wallconnector data: Could not fetch data from Tesla WallConnector at 192.168.200.44: Timeout 2:58:15 AM – (ERROR) Tesla Wall Connector - message first occurred at September 5, 2023 at 6:29:07 AM and shows up 3 times Giving up async_request(...) after 3 tries (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.200.44) 2:58:15 AM – (ERROR) components/tesla_wall_connector/__init__.py - message first occurred at September 5, 2023 at 6:29:07 AM and shows up 3 times Error fetching Ring history data for device 54e0191c6028: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 12:04:05 AM – (WARNING) Ring Login as kuzi6522@gmail.com failed September 5, 2023 at 3:03:48 PM – (ERROR) components/honeywell/climate.py - message first occurred at September 4, 2023 at 2:58:06 AM and shows up 6 times :0:0 Script error. September 5, 2023 at 1:35:56 PM – (ERROR) components/system_log/__init__.py Failed to start the Z-Wave JS add-on: Another job is running for job group container_addon_core_zwave_js September 5, 2023 at 1:35:01 PM – (ERROR) Z-Wave - message first occurred at September 5, 2023 at 1:34:49 PM and shows up 2 times 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.1', 3000)]; Retrying in background September 5, 2023 at 1:34:43 PM – (WARNING) config_entries.py - message first occurred at September 4, 2023 at 11:50:07 AM and shows up 3 times Error setting up entry Denon AVR for denonavr September 5, 2023 at 11:39:02 AM – (ERROR) components/denonavr/receiver.py Error fetching 192.168.200.18 data: 192.168.200.18: device stopped responding after 4 requests to send state September 5, 2023 at 10:59:11 AM – (ERROR) Magic Home - message first occurred at September 5, 2023 at 9:41:13 AM and shows up 2 times Unexpectedly disconnected from Roomba 192.16 ``` ### Example YAML snippet ```yaml NA ``` ### Anything in the logs that might be useful for us? ```txt 2023-09-06T13:07:56.805Z CNTRLR [Node 022] Embedded device config loaded 2023-09-06T13:07:56.813Z CNTRLR [Node 023] Embedded device config loaded 2023-09-06T13:07:56.831Z CNTRLR [Node 024] Embedded device config loaded 2023-09-06T13:07:56.841Z CNTRLR [Node 025] Embedded device config loaded 2023-09-06T13:07:56.877Z CNTRLR [Node 026] Embedded device config loaded 2023-09-06T13:07:56.898Z CNTRLR [Node 028] Embedded device config loaded 2023-09-06T13:07:56.918Z CNTRLR [Node 030] Embedded device config loaded 2023-09-06T13:07:56.940Z CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms 2023-09-06T13:07:56.954Z CNTRLR serial API timeouts overwritten. The old values were: ack = 1500 ms, byte = 15 0 ms 2023-09-06T13:07:56.955Z CNTRLR Interview completed Starting server on 0.0.0.0:3000 2023-09-06T13:07:56.990Z CNTRLR [Node 001] The node is alive. 2023-09-06T13:07:56.992Z CNTRLR [Node 001] The node is ready to be used 2023-09-06T13:07:56.998Z CNTRLR Interviewing nodes and/or determining their status: 10, 3, 4, 9, 22, 24, 8, 7, 2, 25, 21, 6, 5, 11, 23, 30, 12, 26, 15, 28, 18, 19, 29 2023-09-06T13:07:56.999Z CNTRLR » [Node 010] pinging the node... 2023-09-06T13:07:57.141Z CNTRLR » [Node 003] pinging the node... 2023-09-06T13:07:57.144Z CNTRLR » [Node 004] pinging the node... 2023-09-06T13:07:57.149Z CNTRLR » [Node 009] pinging the node... 2023-09-06T13:07:57.152Z CNTRLR » [Node 022] pinging the node... 2023-09-06T13:07:57.155Z CNTRLR » [Node 024] pinging the node... 2023-09-06T13:07:57.158Z CNTRLR » [Node 008] pinging the node... 2023-09-06T13:07:57.162Z CNTRLR » [Node 007] pinging the node... 2023-09-06T13:07:57.166Z CNTRLR » [Node 002] pinging the node... 2023-09-06T13:07:57.169Z CNTRLR » [Node 025] pinging the node... 2023-09-06T13:07:57.173Z CNTRLR » [Node 021] pinging the node... 2023-09-06T13:07:57.176Z CNTRLR » [Node 006] pinging the node... 2023-09-06T13:07:57.178Z CNTRLR » [Node 005] pinging the node... 2023-09-06T13:07:57.182Z CNTRLR » [Node 011] pinging the node... 2023-09-06T13:07:57.185Z CNTRLR » [Node 023] pinging the node... 2023-09-06T13:07:57.189Z CNTRLR [Node 030] The node is asleep. 2023-09-06T13:07:57.193Z CNTRLR [Node 030] The node is ready to be used 2023-09-06T13:07:57.195Z CNTRLR [Node 012] The node is asleep. 2023-09-06T13:07:57.196Z CNTRLR [Node 012] The node is ready to be used 2023-09-06T13:07:57.198Z CNTRLR [Node 026] The node is asleep. 2023-09-06T13:07:57.200Z CNTRLR [Node 026] The node is ready to be used 2023-09-06T13:07:57.201Z CNTRLR [Node 015] The node is asleep. 2023-09-06T13:07:57.203Z CNTRLR [Node 015] The node is ready to be used 2023-09-06T13:07:57.206Z CNTRLR [Node 028] The node is asleep. 2023-09-06T13:07:57.207Z CNTRLR [Node 028] The node is ready to be used 2023-09-06T13:07:57.209Z CNTRLR [Node 018] The node is asleep. 2023-09-06T13:07:57.213Z CNTRLR [Node 018] Beginning interview - last completed stage: ProtocolInfo 2023-09-06T13:07:57.215Z CNTRLR » [Node 018] querying node info... 2023-09-06T13:07:57.220Z CNTRLR [Node 019] The node is asleep. 2023-09-06T13:07:57.222Z CNTRLR [Node 019] Beginning interview - last completed stage: ProtocolInfo 2023-09-06T13:07:57.223Z CNTRLR » [Node 019] querying node info... 2023-09-06T13:07:57.226Z CNTRLR [Node 029] The node is asleep. 2023-09-06T13:07:57.229Z CNTRLR [Node 029] Beginning interview - last completed stage: ProtocolInfo 2023-09-06T13:07:57.229Z CNTRLR » [Node 029] querying node info... ZwaveJS server listening on 0.0.0.0:3000 2023-09-06T13:07:57.309Z CNTRLR [Node 010] The node is alive. 2023-09-06T13:07:57.311Z CNTRLR [Node 010] The node is ready to be used 2023-09-06T13:07:57.314Z CNTRLR « [Node 010] ping successful 2023-09-06T13:07:57.389Z CNTRLR [Node 003] The node is alive. 2023-09-06T13:07:57.390Z CNTRLR [Node 003] The node is ready to be used 2023-09-06T13:07:57.393Z CNTRLR « [Node 003] ping successful 2023-09-06T13:07:57.429Z CNTRLR [Node 004] The node is alive. 2023-09-06T13:07:57.430Z CNTRLR [Node 004] The node is ready to be used 2023-09-06T13:07:57.433Z CNTRLR « [Node 004] ping successful 2023-09-06T13:07:57.502Z CNTRLR [Node 009] The node is alive. 2023-09-06T13:07:57.505Z CNTRLR [Node 009] The node is ready to be used 2023-09-06T13:07:57.508Z CNTRLR « [Node 009] ping successful 2023-09-06T13:07:57.543Z CNTRLR [Node 022] The node is alive. 2023-09-06T13:07:57.545Z CNTRLR [Node 022] The node is ready to be used 2023-09-06T13:07:57.548Z CNTRLR « [Node 022] ping successful 2023-09-06T13:07:57.608Z CNTRLR [Node 024] The node is alive. 2023-09-06T13:07:57.611Z CNTRLR [Node 024] The node is ready to be used 2023-09-06T13:07:57.615Z CNTRLR « [Node 024] ping successful 2023-09-06T13:07:57.652Z CNTRLR [Node 008] The node is alive. 2023-09-06T13:07:57.653Z CNTRLR [Node 008] The node is ready to be used 2023-09-06T13:07:57.655Z CNTRLR « [Node 008] ping successful 2023-09-06T13:07:57.881Z CNTRLR [Node 007] The node is alive. 2023-09-06T13:07:57.882Z CNTRLR [Node 007] The node is ready to be used 2023-09-06T13:07:57.884Z CNTRLR « [Node 007] ping successful 2023-09-06T13:07:57.920Z CNTRLR [Node 002] The node is alive. 2023-09-06T13:07:57.921Z CNTRLR [Node 002] The node is ready to be used 2023-09-06T13:07:57.924Z CNTRLR « [Node 002] ping successful 2023-09-06T13:07:58.000Z CNTRLR [Node 025] The node is alive. 2023-09-06T13:07:58.002Z CNTRLR [Node 025] The node is ready to be used 2023-09-06T13:07:58.003Z CNTRLR « [Node 025] ping successful 2023-09-06T13:07:58.034Z CNTRLR [Node 021] The node is alive. 2023-09-06T13:07:58.035Z CNTRLR [Node 021] The node is ready to be used 2023-09-06T13:07:58.036Z CNTRLR « [Node 021] ping successful 2023-09-06T13:07:58.068Z CNTRLR [Node 006] The node is alive. 2023-09-06T13:07:58.069Z CNTRLR [Node 006] The node is ready to be used 2023-09-06T13:07:58.071Z CNTRLR « [Node 006] ping successful 2023-09-06T13:07:58.105Z CNTRLR [Node 005] The node is alive. 2023-09-06T13:07:58.107Z CNTRLR [Node 005] The node is ready to be used 2023-09-06T13:07:58.109Z CNTRLR « [Node 005] ping successful New client Client disconnected Code 1000: New client 2023-09-06T13:08:05.947Z CNTRLR [Node 011] The node did not respond after 1 attempts, it is presumed dead 2023-09-06T13:08:05.949Z CNTRLR [Node 011] The node is dead. 2023-09-06T13:08:05.953Z CNTRLR [Node 011] ping failed: The node did not acknowledge the command (ZW0204) 2023-09-06T13:08:32.097Z CNTRLR [Node 023] The node did not respond after 1 attempts, it is presumed dead 2023-09-06T13:08:32.100Z CNTRLR [Node 023] The node is dead. 2023-09-06T13:08:32.105Z CNTRLR [Node 023] ping failed: The node did not acknowledge the command (ZW0204) ``` ### Additional information NA

Heute sollte noch ein Update reinflattern welches das Problem behebt.

Sollten bei euch Lichtschalter und Aktoren in Zwave nicht mehr auslösen…
Nicht verzweifeln…
Die Entwickler sind dran.

Update…

Release ist inzwischen raus.

Wenn ihr Treiber Version 11.14.0 würde ich ein Update empfhehlen…
Drunter sei nicht notwendig wenn keine Probleme auftauchen

burki-bb · 27. Oktober 2023 um 18:32

Ich habe jetzt auch das Problem, dass alles Z-Wave-Geräte in der Oberfläche weg sind. Im Z-Wave-JS sind sie noch alle da. Aber es klappt keine Automation etc.

Robert · 4. November 2023 um 06:58

Hallo burki, sollte mit der 3.0.1 nicht vorkommen.
Welche Version ist bei dir installiert?

guezli · 4. November 2023 um 11:59

Ah! Das ist mir überhaupt nicht aufgefallen. Alles lief problemlos.

Sammy51 · 30. Januar 2025 um 18:55

Hallo zusammen,

der Thread scheint wohl etws älter - aber vielleicht kann mir hier dennoch jemand helfen?

Hatte vorhin das problem, dass 1 zwave aktor nicht reagiert hat.
Da habe ich zwave js das addon mal testweise neugestartet.

Jetzt ist plötzlich gar kein zwave device mehr erreichbar.
Auch ein zweiter Neustart oder Neustart von HA hat nichts gebracht.

Folgendes findet sich im zwave js protokoll:


2025-01-30T18:50:50.758Z CNTRLR   The controller response indicated failure after 1/3 attempts. Scheduling next 
                                  try in 100 ms.
2025-01-30T18:50:50.863Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.
2025-01-30T18:50:51.967Z CNTRLR   [Node 003] ping failed: Failed to send the command after 1 attempts. Transmiss
                                  ion queue full (ZW0202)
2025-01-30T18:50:51.967Z CNTRLR   [Node 003] Failed all interview attempts, giving up.

EDIT: Jetzt ist allerdins 19:57 Uhr und es gibt keine neueren Log Einträge dort
EDIT2: Hab jetzt mal den zwave stick ab und angesteckt … jetzt geht es erstmal wieder.

Der Stick ist dieser:

DEVNAME: /dev/ttyACM0
DEVPATH: /devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-3/2-3:1.0/tty/ttyACM0
ID_BUS: usb
ID_MODEL: '0200'
ID_MODEL_ENC: '0200'
ID_MODEL_ID: '0200'
ID_PATH: pci-0000:01:1b.0-usb-0:3:1.0
ID_PATH_TAG: pci-0000_01_1b_0-usb-0_3_1_0
ID_PATH_WITH_USB_REVISION: pci-0000:01:1b.0-usbv2-0:3:1.0
ID_REVISION: '0000'

Beste Grüße
Sammy

Thema		Antworten	Aufrufe
HA: Z Wave JS geht nicht mehr Allgemein	6	277	2. April 2026
Probleme seit Verfügbarkeit eines Z-Wave Updates Add-ons z-wave	18	472	23. August 2025
Z-Wave error 202 Allgemein	19	270	4. Oktober 2025
Massive z-wave Probleme Installation, HW & HA-OS z-wave	9	272	16. November 2025
Problem nach Z-Wave JS UI Update 4.0.0 - KEIN Gerät wird mehr unterstützt Allgemein	6	208	28. März 2025

Aktueller Fehler in Zwave js und JSUi

Verwandte Themen