Enduro
24. März 2025 um 08:49
1
Moin Zusammen,Z-Wave JS UI Update 4.0.0 heute morgen ging bei mir nichts mehr - kein Z-Wave Gerät mehr erreichbar - konnten auch nicht erneut interviewed werden - der Fehlerhinweis besagt, dass sie nicht mehr von Z-Wave JS UI unterstützt werden.
Ich hatte auf meinem Green bislang nie Problem nach Updates - das ist das erste mal.Hat evtl. noch jemand das gleiche Problem?
Habe zwischenzeitlich das Backup von Version 3.24.0 wieder eingespielt und jetzt funktioniert alles wieder wie vorher.
Gruß
### Update 2025-03-25: Bin offensichtlich „noch“ der einzige mit diesem Z-Wave Problem. In der EN-Community wurde aber bereits darauf reagiert. Zur info:
opened 05:52AM - 25 Mar 25 UTC
this loops after upgrade to 4.0.0. Other users seem to have similar problems. … had to go back to previous version and reboot. then it works again. https://community.home-assistant.io/t/problem-after-installing-z-wave-js-ui-update-4-0-0-no-device-is-supported-anymore/868545
```
2025-03-25 06:27:22.732 INFO APP: GET /health/zwave 301 0.691 ms - 162
2025-03-25 06:27:26.379 INFO Z-WAVE-SERVER: Server closed
2025-03-25 06:27:26.380 INFO Z-WAVE: Client closed
2025-03-25 06:27:26.381 INFO Z-WAVE: Connecting to /dev/ttyAML1
2025-03-25 06:27:26.382 INFO Z-WAVE: Setting user callbacks
2025-03-25T05:27:26.384Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2025-03-25T05:27:26.384Z DRIVER version 15.0.2
2025-03-25T05:27:26.385Z DRIVER
2025-03-25T05:27:27.390Z CONFIG version 15.0.1
2025-03-25T05:27:27.972Z CNTRLR querying Serial API capabilities...
2025-03-25T05:27:27.980Z CNTRLR received API capabilities:
firmware version: 5.0
manufacturer ID: 0x0147
product type: 0x0400
product ID: 0x01
supported functions:
· GetSerialApiInitData (0x02)
· SetApplicationNodeInformation (0x03)
· ApplicationCommand (0x04)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· SoftReset (0x08)
· GetProtocolVersion (0x09)
· SerialAPIStarted (0x0a)
· SetRFReceiveMode (0x10)
· UNKNOWN_FUNC_SET_SLEEP_MODE (0x11)
· SendNodeInformation (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)
· GetControllerVersion (0x15)
· SendDataAbort (0x16)
· FUNC_ID_ZW_R_F_POWER_LEVEL_SET (0x17)
· UNKNOWN_FUNC_SEND_DATA_META (0x18)
· FUNC_ID_ZW_GET_RANDOM (0x1c)
· GetControllerId (0x20)
· UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
· UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
· UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
· UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
· EnterBootloader (0x27)
· UNKNOWN_FUNC_UNKNOWN_0x28 (0x28)
· GetNVMId (0x29)
· ExtNVMReadLongBuffer (0x2a)
· ExtNVMWriteLongBuffer (0x2b)
· ExtNVMReadLongByte (0x2c)
· ExtExtWriteLongByte (0x2d)
· GetNodeProtocolInfo (0x41)
· HardReset (0x42)
· FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
· FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
· AssignReturnRoute (0x46)
· DeleteReturnRoute (0x47)
· RequestNodeNeighborUpdate (0x48)
· ApplicationUpdateRequest (0x49)
· AddNodeToNetwork (0x4a)
· RemoveNodeFromNetwork (0x4b)
· AddControllerAndAssignPrimary (0x4c)
· AddPrimaryController (0x4d)
· SetLearnMode (0x50)
· AssignSUCReturnRoute (0x51)
· RequestNetworkUpdate (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· SendSUCNodeId (0x57)
· ExploreRequestInclusion (0x5e)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
· UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
· FirmwareUpdateNVM (0x78)
· GetRoutingInfo (0x80)
· LockUnlockLastRoute (0x90)
· GetPriorityRoute (0x92)
· SetPriorityRoute (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· undefined (0xb4)
· EnableWatchdog500 (0xb6)
· DisableWatchdog500 (0xb7)
· KickWatchdog500 (0xb8)
· UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
· UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
· GetLibrary (0xbd)
· SendTestFrame (0xbe)
· GetProtocolStatus (0xbf)
· StartWatchdog (0xd2)
· StopWatchdog (0xd3)
· SetMaximumRoutingAttempts (0xd4)
· undefined (0xef)
· Proprietary_F2 (0xf2)
· Proprietary_F4 (0xf4)
· Proprietary_F5 (0xf5)
2025-03-25T05:27:27.981Z CNTRLR querying additional controller information...
2025-03-25T05:27:28.044Z CNTRLR received additional controller information:
Z-Wave API version: 5 (legacy)
Z-Wave chip type: ZW050x
node type Controller
controller role: primary
controller is the SIS: true
controller supports timers: false
Z-Wave Classic nodes: 1, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 3
4, 35, 36, 37, 38
2025-03-25T05:27:28.045Z CNTRLR querying version info...
2025-03-25T05:27:28.051Z CNTRLR received version info:
controller type: Static Controller
library version: Z-Wave 3.99
2025-03-25T05:27:28.051Z CNTRLR querying protocol version info...
2025-03-25T05:27:28.056Z CNTRLR received protocol version info:
protocol type: Z-Wave
protocol version: 3.99.0
2025-03-25T05:27:28.057Z CNTRLR querying controller capabilities...
2025-03-25T05:27:28.061Z CNTRLR received controller capabilities:
controller role: Primary
is the SUC: true
started this network: true
SIS is present: true
was real primary: true
2025-03-25T05:27:28.062Z CNTRLR supported Z-Wave features:
2025-03-25T05:27:28.063Z CNTRLR Performing soft reset...
2025-03-25T05:27:28.067Z CNTRLR Waiting for the controller to reconnect...
2025-03-25T05:27:29.569Z CNTRLR Waiting for the Serial API to start...
2025-03-25T05:27:34.575Z CNTRLR Did not receive notification that Serial API has started, checking if it respo
nds...
2025-03-25T05:27:34.580Z CNTRLR Serial API responded
2025-03-25T05:27:34.581Z CNTRLR querying controller IDs...
2025-03-25T05:27:34.585Z DRIVER Dropping message with invalid payload:
0x010a000a030103020101ff03
2025-03-25T05:27:34.587Z DRIVER Failed to initialize the driver, no response from the controller. Are you sure
this is a Z-Wave controller?
2025-03-25 06:27:34.589 INFO Z-WAVE: Restarting client in 15 seconds, retry 1865
```
ppaulh
26. März 2025 um 23:37
2
Es scheint wohl ein Razberry-spezifisches Thema zu sein.
Enduro
27. März 2025 um 06:20
3
Moin,Update auf 4.0.2 ,nicht speziell für das genannte Problem, führt aber zu dem gleichen negativen Ergebnis.
Gruß
Moin,
Enduro:
HA green …
soweit mir bekannt, entspricht der Green dem RasPI 4 was CPU und periphere angeht, ist nur ein eigenes Boarddesign und hat anstelle einer SD-Karte halt gleich 32 GB eMMC speicher, aber alle dieser kleinen Wundertüten, nutzen ARM Architektur für die CPU, daher kann das schon sein, dass mit einem Update da etwas kaputtgegangen ist
VG
P.S.: ich habe auch keine Probleme, läuft aber auch auf AMD X86_64.
1 „Gefällt mir“
Enduro
27. März 2025 um 06:48
5
Moin,
Enduro
27. März 2025 um 14:02
6
Hi, es sieht so aus, dass - zumindest für mich und meinen HA green - das Problem gelöst ist. Einzelheiten können einem Eintrag (issue) unter github.com eingesehen werden:
opened 09:55AM - 25 Mar 25 UTC
Hello!
After updating Z-Wave JS UI from 3.23.0 to 4.0.0 (and then 4.0.1), my wh… ole Z-Wave network doesn't work anymore. It seems like my Z-Wave Controller (Aeotec AEON Labs | Z‐Stick Gen5 USB Controller | ZW090) it's not being detected anymore.
I have tried to disconnect/reconnect the Z-Wave Controller. Did not helped. I have rebooted the machine. Same problem.
Reverted back to 3.23.0 and everything worked again.
Here are some logs:
`2025-03-25T09:40:25.459Z DRIVER Dropping message because the driver is not ready to handle it yet.
2025-03-25T09:40:25.459Z DRIVER TypeError: Invalid state: WritableStream is locked
at setupWritableStreamDefaultWriter (node:internal/webstreams/writablestre
am:612:11)
at new WritableStreamDefaultWriter (node:internal/webstreams/writablestrea
m:346:5)
at InternalWritableStream.getWriter (node:internal/webstreams/writablestre
am:234:12)
at ZWaveSerialStream.writeAsync (/opt/node_modules/@zwave-js/serial/src/se
rialport/ZWaveSerialStream.ts:163:32)
at Driver.writeSerial (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts
:7150:23)
at Driver.writeHeader (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts
:7145:15)
at Driver.serialport_onData (/opt/node_modules/zwave-js/src/lib/driver/Dri
ver.ts:3798:31)
2025-03-25T09:40:25.476Z DRIVER Dropping message because the driver is not ready to handle it yet.
2025-03-25T09:40:26.446Z CONFIG version 15.0.1
2025-03-25T09:40:26.728Z CNTRLR querying Serial API capabilities...
2025-03-25T09:40:27.731Z DRIVER Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
from the controller (ZW0200)
at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts
:6765:23)
at ZWaveController2.queryCapabilities (/opt/node_modules/zwave-js/src/lib/
controller/Controller.ts:1130:37)
at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib
/driver/Driver.ts:1830:46)
at Immediate.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver
.ts:1582:16)
2025-03-25 11:40:27.731 INFO Z-WAVE: Controller status: Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6765:23)
at ZWaveController2.queryCapabilities (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:1130:37)
at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1830:46)
at Immediate.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1582:16) (ZW0100)
2025-03-25 11:40:27.731 INFO Z-WAVE: Restarting client in 15 seconds, retry 9`
And here are some screenshots:
P.S. This worked flawlessly for years... what's happening now with 4.x.x?
Gruß
ppaulh
28. März 2025 um 07:33
7
Vielleicht wäre das Problem bei mir auch aufgetreten, wenn ich auf die V4.0.0 aktualisiert hätte. Habe mir jedoch angewöhnt, bei 0er Versionen erstmal abzuwarten und Foreneinträge zu beobachten.
