core: z-wave js fails to start after upgrading to 0.1.86
The problem
After upgrading Z-Wave JS from version 0.1.85 to 0.1.86 z-wave js add-on no longer starts. It shows “Failed setup, will retry” status in Z-Wave page.
I am using Aeotec Z-Wave Gen 7 USB stick. Device path seems to be corret: /dev/ttyUSB0 ID: /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_30e744e60555ed11b47c99131d62bc44-if00-port0
I tried to follow various suggestions (re-insterting the USB stick, restarting the plugin, rebooting hardware), nothing helped.
UPDATE: Downgrading to 0.1.85 and restarting the add-on made it work again.
I submitted the logs below.
What version of Home Assistant Core has the issue?
2023.8.1
What was the last working version of Home Assistant Core?
2023.8.1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Z-Wave JS
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
· SerialAPIStarted (0x0a)
· SerialAPISetup (0x0b)
· SetRFReceiveMode (0x10)
· FUNC_ID_ZW_SEND_NODE_INFORMATION (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)
· GetControllerVersion (0x15)
· SendDataAbort (0x16)
· 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)
· ExtNVMReadLongByte (0x2c)
· NVMOperations (0x2e)
· undefined (0x37)
· undefined (0x38)
· UNKNOWN_FUNC_ClearNetworkStats (0x39)
· UNKNOWN_FUNC_GetNetworkStats (0x3a)
· GetBackgroundRSSI (0x3b)
· undefined (0x3c)
· UNKNOWN_FUNC_RemoveNodeIdFromNetwork (0x3f)
· 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)
· FUNC_ID_ZW_CONTROLLER_CHANGE (0x4d)
· AssignPriorityReturnRoute (0x4f)
· FUNC_ID_ZW_SET_LEARN_MODE (0x50)
· AssignSUCReturnRoute (0x51)
· FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· UNKNOWN_FUNC_SEND_SUC_ID (0x57)
· AssignPrioritySUCReturnRoute (0x58)
· FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
· undefined (0x5f)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· GetPriorityRoute (0x92)
· SetPriorityRoute (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· FUNC_ID_SERIAL_API_SLAVE_NODE_INFO (0xa0)
· FUNC_ID_ZW_SEND_SLAVE_NODE_INFO (0xa2)
· FUNC_ID_ZW_SET_SLAVE_LEARN_MODE (0xa4)
· FUNC_ID_ZW_GET_VIRTUAL_NODES (0xa5)
· FUNC_ID_ZW_IS_VIRTUAL_NODE (0xa6)
· BridgeApplicationCommand (0xa8)
· SendDataBridge (0xa9)
· SendDataMulticastBridge (0xab)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· undefined (0xd6)
· Shutdown (0xd9)
· undefined (0xda)
· undefined (0xdb)
· undefined (0xdc)
· undefined (0xdd)
· undefined (0xde)
· undefined (0xdf)
· undefined (0xe7)
· undefined (0xe8)
2023-08-11T10:43:13.979Z DRIVER all queues idle
2023-08-11T10:43:13.994Z DRIVER Controller identification returned invalid node ID 0
2023-08-11T10:43:13.995Z DRIVER destroying driver instance...
2023-08-11T10:43:14.019Z DRIVER driver instance destroyed
[10:43:14] INFO: Service restart after closing
[12:43:15] INFO: Successfully send discovery information to Home Assistant.
2023-08-11T10:43:17.036Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2023-08-11T10:43:17.039Z DRIVER version 11.9.2
2023-08-11T10:43:17.039Z DRIVER
2023-08-11T10:43:17.040Z DRIVER starting driver...
2023-08-11T10:43:17.040Z DRIVER opening serial port /dev/ttyUSB0
2023-08-11T10:43:17.097Z DRIVER serial port opened
2023-08-11T10:43:17.099Z SERIAL » 0x15 (1 bytes)
### Additional information
_No response_
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 23 (1 by maintainers)
Will be fixed by
node-zwave-jsversion11.10.1(releasing now).Needless to say that downgrading to 0.1.85 solved the issue.
Thanks a lot! I’ll give it a try.