What is the distance between the stick (controller) and the node? Does it help bringing them closer? How certain are you this is the Gen5+ and not the regular Gen5?
Thank you for your reply.
Well, since this is an initial test set up they are pretty close to each other, I would say between 1-2 meters. As for the Aeotec stick, well it’s pretty new (1 month old) and I just got it directly from the https://popp.to/ store and both the box and the description in the order do have the “5+” tag - but I do agree it’s not easy to see the difference on the actual device since they both have the same model number.
Just wanted to give some feedback on the equipment I do use:
- RaspberryPi 4 4GB
- External 120GB USB SSD
- Aeotec Z-Stick Gen5+
- Single Relay Module model TZ78 Plus
In my initial post I said that I did test with other software, however since it was only done as an limited test the installation of both openHAB and Domoticz was done to an SD card, i.e. in this case I did not use the external SSD disk. However in both cases when testing the other applications I could control the Z switch and issue commands to it just minutes after the software was up and running.
Also since I never managed to get the Z-wave protocol working in HA the pairing of the Z stick and the Z relay was done using the Zensys Tool, when trying to pair in HA it never succeeded. Also note initially I did have 3 external Z-wave devices which also where just next to the Rpi, two of them was battery powered. All devices where “visible” in HA, i.e. I could see them in the 1.4 Z-wave config file but for some reason only the first one (i.e. with lowest ID) was visible - and by visible I mean that you could see it as an device but it would state it as “unknown” and no mean to control it or get info from it.
Two of the devices used where battery powered temperature sensors but the battery would drain within one day…
Just found the “Advanced” option so I do have some logs from Open Z-wave now:
[20210205 10:09:11.542 CET] [ozwadmin] [info]: OZWCore Initilized QTOpenZwave(0x7f90091c20) QTOZWManager(0x555e7fca40)
[20210205 10:09:11.619 CET] [default] [warning]: QVncServer created on port 5900
[20210205 10:09:12.300 CET] [ozw.library] [info]: Info - Node: 0 Queuing download for http://download.db.openzwave.com/images/shenzen_neo/nas-sc03ze.jpg (Node 0)
[20210205 10:09:12.300 CET] [ozw.library] [info]: Info - Node: 0 Missing Picture /data/ozw/config/images/shenzen_neo/nas-sc03ze.jpg - Starting Download
[20210205 10:09:12.301 CET] [ozw.library] [debug]: Debug - Node: 0 Download Starting for http://download.db.openzwave.com/images/shenzen_neo/nas-sc03ze.jpg (/data/ozw/config/images/shenzen_neo/nas-sc03ze.jpg)
[20210205 10:09:12.523 CET] [ozw.library] [info]: Info - Node: 0 Queuing download for http://download.db.openzwave.com/images/namron/4512714.jpg (Node 0)
[20210205 10:09:12.523 CET] [ozw.library] [info]: Info - Node: 0 Missing Picture /data/ozw/config/images/namron/4512714.jpg - Starting Download
[20210205 10:09:12.558 CET] [ozw.library] [debug]: Debug - Node: 0 Downloads Remaining: 2
[20210205 10:09:12.692 CET] [ozw.library] [debug]: Debug - Node: 0 Download Starting for http://download.db.openzwave.com/images/namron/4512714.jpg (/data/ozw/config/images/namron/4512714.jpg)
[20210205 10:09:12.692 CET] [ozw.library] [warning]: Warning - Node: 0 Download of http://download.db.openzwave.com/images/shenzen_neo/nas-sc03ze.jpg Failed (Node: 0)
[20210205 10:09:12.692 CET] [ozw.library] [debug]: Debug - Node: 0 Downloads Remaining: 1
[20210205 10:09:12.693 CET] [ozw.library] [debug]: Detail - Node: 0 Notification: A Config File Failed to download
[20210205 10:09:12.693 CET] [ozw.notifications] [debug]: Notification pvt_ozwUserAlert NotificationTypes::Notification_User_ConfigFileDownloadFailed Thread: 0x7f9c50ce38
[20210205 10:09:12.693 CET] [ozw.mqtt.publisher] [debug]: Publishing Event ozwUserAlert
[20210205 10:09:12.836 CET] [ozw.library] [warning]: Warning - Node: 0 Download of http://download.db.openzwave.com/images/namron/4512714.jpg Failed (Node: 0)
[20210205 10:09:12.836 CET] [ozw.library] [debug]: Debug - Node: 0 Downloads Remaining: 0
[20210205 10:09:12.836 CET] [ozw.library] [info]: Info - Node: 0 ManufacturerSpecificDB Initialized
[20210205 10:09:12.837 CET] [ozw.library] [debug]: Detail - Node: 0 Notification: A Config File Failed to download
[20210205 10:09:12.837 CET] [ozw.library] [debug]: Detail - Node: 0 Notification: ManufacturerSpecificDB Ready
[20210205 10:09:12.837 CET] [ozw.library] [info]: Info - Node: 255 Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
[20210205 10:09:12.837 CET] [ozw.library] [info]: Info - Node: 255 Encrypted Flag is 0
[20210205 10:09:12.837 CET] [ozw.notifications] [debug]: Notification pvt_ozwUserAlert NotificationTypes::Notification_User_ConfigFileDownloadFailed Thread: 0x7f9c50ce38
[20210205 10:09:12.838 CET] [ozw.mqtt.publisher] [debug]: Publishing Event ozwUserAlert
[20210205 10:09:12.838 CET] [ozw.notifications] [debug]: Notification pvt_manufacturerSpecificDBReady Thread: 0x7f9c50ce38
[20210205 10:09:12.838 CET] [ozw.mqtt.publisher] [debug]: Publishing Event manufacturerSpecificDBReady
[20210205 10:09:12.839 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x37). Sending NAK.
[20210205 10:09:12.840 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x10). Sending NAK.
[20210205 10:09:12.841 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x2d). Sending NAK.
[20210205 10:09:12.841 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x97). Sending NAK.
[20210205 10:09:12.842 CET] [ozw.library] [debug]: Detail - Node: 0 Unsolicited message received while waiting for ACK.
[20210205 10:09:12.844 CET] [ozw.library] [debug]: Detail - Node: 255 Received: 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x36, 0x2e, 0x30, 0x37, 0x00, 0x01, 0x97, 0x01, 0x10, 0x57, 0x61, 0x65, 0x36, 0x30
[20210205 10:09:12.844 CET] [ozw.library] [warning]: Warning - Node: 255 WARNING: Checksum incorrect - sending NAK
WebSocket server settings:
- Listen on :8099
- Web server. Web root: /usr/share/novnc
- No SSL/TLS support (no cert file)
- proxying from :8099 to 127.0.0.1:5900
[20210205 10:09:13.844 CET] [ozw.library] [critical]: Error - Node: 255 ERROR: Dropping command, expected response not received after 1 attempt(s). Command: "FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9"
[20210205 10:09:13.845 CET] [ozw.library] [debug]: Detail - Node: 255 Removing current message
[20210205 10:09:13.845 CET] [ozw.library] [debug]: Detail - Node: 255 Notification: Notification - TimeOut
[20210205 10:09:13.845 CET] [ozw.notifications] [debug]: Notification pvt_ozwNotification NotificationTypes::Notification_Code_MsgTimeout Thread: 0x7f9c50ce38
[20210205 10:09:13.846 CET] [ozw.mqtt.publisher] [debug]: Publishing Event ozwNotification
[20210205 10:09:14.165 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x00). Sending NAK.
[20210205 10:09:14.165 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x7f). Sending NAK.
[20210205 10:09:14.166 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x00). Sending NAK.
[20210205 10:09:14.167 CET] [ozw.library] [debug]: Detail - Node: 0 CAN received...triggering resend
[20210205 10:09:14.168 CET] [ozw.library] [warning]: Warning - Node: 0 m_currentMsg was NULL when trying to set MaxSendAttempts
[20210205 10:09:14.169 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x0b). Sending NAK.
[20210205 10:09:14.171 CET] [ozw.library] [debug]: Detail - Node: 0 CAN received...triggering resend
[20210205 10:09:14.172 CET] [ozw.library] [warning]: Warning - Node: 0 m_currentMsg was NULL when trying to set MaxSendAttempts
[20210205 10:09:14.173 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x13). Sending NAK.
[20210205 10:09:18.149 CET] [ozw.library] [debug]: Detail - Node: 0 Received: 0x01, 0x20, 0x01, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x5f, 0x01, 0x20, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
[20210205 10:09:18.151 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Checksum incorrect - sending NAK
[20210205 10:09:18.152 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x00). Sending NAK.
[20210205 10:09:18.153 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Out of frame flow! (0x00). Sending NAK.
[20210205 10:09:22.836 CET] [ozw.library] [info]: Info - Node: 0 HttpThread Exiting. No Transfers in timeout period
1612516164: New connection from 172.30.32.1 on port 1883.
1612516164: New client connected from 172.30.32.1 as 3PyIK2Oev3E3HFktVzDDMj (p2, c1, k60, u'homeassistant').
[20210205 10:10:10.796 CET] [ozw.mqtt.publisher] [debug]: "Fri Feb 5 10:10:10 2021 PingResponse\n"
I can also add some info from Z-Wave for MTTQ which I installed in an attempt to solve the issue. In this log Node#1 is the Z-stick and #9 is the Z-wave switch.
2021-02-05T09:09:02.421Z z2m:Zwave Scanning network with homeid: 0xdd9b4469
2021-02-05T09:09:03.225Z z2m:Mqtt MQTT client connected
2021-02-05 10:09:08.124 Detail, Node009, Received: 0x01, 0x18, 0x00, 0x13, 0x0a, 0x01, 0x02, 0x5b, 0x00, 0x7f, 0x7f, 0x7f, 0x7f, 0x7f, 0x00, 0x00, 0x07, 0x00, 0x00, 0x00, 0x00, 0x02, 0x03, 0x00, 0x00, 0xdf
2021-02-05 10:09:08.124 Detail, Node009, ZW_SEND_DATA Request with callback ID 0x0a received (expected 0x0a)
2021-02-05 10:09:08.124 Detail, Node009, Extended TxStatus: Time: 6030, Hops: 0, Rssi: --- --- --- --- ---, AckChannel: 0, TxChannel: 0, RouteScheme: Explorer Route, Route: 0 0 0 0, RouteSpeed: 40K, RouteTries: 3, FailedLinkFrom: 0, FailedLinkTo: 0
2021-02-05 10:09:08.124 Info, Node009, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2021-02-05 10:09:08.124 Warning, Node009, WARNING: Device is not a sleeping node.
2021-02-05 10:09:08.124 Info, Node009, QueryStageRetry stage CacheLoad requested stage CacheLoad max 3 retries 0 pending 1
2021-02-05 10:09:08.125 Detail, Node009, Expected callbackId was received
2021-02-05 10:09:08.125 Detail, Node009, Expected reply was received
2021-02-05 10:09:08.125 Detail, Node009, Message transaction complete
2021-02-05 10:09:08.125 Detail,
2021-02-05 10:09:08.125 Detail, Node009, Removing current message
2021-02-05 10:09:08.125 Detail, Node009, Notification: Notification - NoOperation
2021-02-05 10:09:08.125 Detail, Node001, Query Stage Complete (Neighbors)
2021-02-05 10:09:08.125 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2021-02-05 10:09:08.126 Detail, Node001, QueryStage_Session
2021-02-05 10:09:08.126 Detail, Node001, QueryStage_Dynamic
2021-02-05 10:09:08.126 Detail, Node001, QueryStage_Configuration
2021-02-05 10:09:08.126 Detail, Node001, QueryStage_Complete
2021-02-05 10:09:08.126 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2021-02-05 10:09:08.126 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=0
2021-02-05 10:09:08.126 Info, Saving Cache
2021-02-05 10:09:08.126 Info, Node001, Cache Save for Node 1 as its QueryStage_CacheLoad
2021-02-05 10:09:08.127 Info, Node009, Cache Save for Node 9 as its QueryStage_CacheLoad
2021-02-05 10:09:08.129 Detail, Node001, Notification: NodeQueriesComplete
2021-02-05 10:09:08.129 Detail, Node009, Query Stage Complete (CacheLoad)
2021-02-05T09:09:08.128Z z2m:Zwave Notification from node 9: Notification - NoOperation (2)
2021-02-05 10:09:08.129 Detail, Node009, AdvanceQueries queryPending=0 queryRetries=1 queryStage=CacheLoad live=1
2021-02-05 10:09:08.129 Detail, Node009, QueryStage_CacheLoad
2021-02-05 10:09:08.129 Info, Node009, Loading Cache for node 9: Manufacturer=Unknown: id=0000, Product=Unknown: type=0000, id=0000
2021-02-05 10:09:08.129 Info, Node009, Node Identity Codes: 0000:0000:0000
2021-02-05 10:09:08.129 Info, Node009, NoOperation::Set - Routing=true
2021-02-05 10:09:08.129 Detail, Node009, Queuing (NoOp) NoOperation_Set (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x00, 0x00, 0x25, 0x0b, 0xc0
2021-02-05 10:09:08.129 Detail, Node009, Queuing (Query) Query Stage Complete (CacheLoad)
2021-02-05 10:09:08.129 Detail,
2021-02-05 10:09:08.130 Info, Node009, Sending (NoOp) message (Callback ID=0x0b, Expected Reply=0x13) - NoOperation_Set (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x00, 0x00, 0x25, 0x0b, 0xc0
2021-02-05 10:09:08.130 Info, Node009, Encrypted Flag is 0
2021-02-05 10:09:08.156 Detail, Node009, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2021-02-05 10:09:08.157 Detail, Node009, ZW_SEND_DATA delivered to Z-Wave stack
2021-02-05T09:09:08.160Z z2m:Zwave node 1 ready: Unknown: id=0086 - Unknown: type=0001, id=005a (Unknown)
2021-02-05 10:09:12.841 Detail, Node009, Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x36, 0x2e, 0x30, 0x01, 0x65, 0x2e, 0x30
2021-02-05 10:09:12.841 Warning, Node009, WARNING: Checksum incorrect - sending NAK
2021-02-05 10:09:12.844 Warning, WARNING: Out of frame flow! (0x97). Sending NAK.
2021-02-05 10:09:14.168 Detail, Node009, Received: 0x01, 0x18, 0x13, 0x0b, 0x01, 0x02, 0x5b, 0x00, 0x7f, 0x7f, 0x7f, 0x00, 0x00, 0x07, 0x00, 0x00, 0x02, 0x03, 0x00, 0x00, 0xde, 0x01, 0x00, 0x13, 0x00, 0x00
2021-02-05 10:09:14.169 Warning, Node009, WARNING: Checksum incorrect - sending NAK
2021-02-05 10:09:14.170 Detail, Node009, Received: 0x01, 0x00
2021-02-05 10:09:14.171 Warning, Node009, WARNING: Checksum incorrect - sending NAK
2021-02-05 10:09:14.172 Warning, WARNING: Out of frame flow! (0x02). Sending NAK.
2021-02-05 10:09:18.131 Error, Node009, ERROR: Dropping command, expected response not received after 1 attempt(s). Command: "NoOperation_Set (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x00, 0x00, 0x25, 0x0b, 0xc0"
2021-02-05 10:09:18.131 Detail, Node009, Removing current message
2021-02-05 10:09:18.133 Detail, Node009, Notification: Notification - TimeOut
2021-02-05 10:09:18.134 Detail, Node009, Query Stage Complete (CacheLoad)
2021-02-05 10:09:18.135 Detail, Node009, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Associations live=1
2021-02-05 10:09:18.135 Detail, Node009, QueryStage_Associations
2021-02-05 10:09:18.136 Detail, Node009, QueryStage_Neighbors
2021-02-05T09:09:18.136Z z2m:Zwave Notification from node 9: Notification - TimeOut (1)
2021-02-05 10:09:18.136 Detail, Requesting routing info (neighbor list) for Node 9
2021-02-05 10:09:18.138 Detail, Node009, Queuing (Command) Get Routing Info (Node=9): 0x01, 0x07, 0x00, 0x80, 0x09, 0x00, 0x00, 0x03, 0x72
2021-02-05 10:09:18.139 Detail, Node009, Queuing (Query) Query Stage Complete (Neighbors)
2021-02-05 10:09:18.139 Detail,
2021-02-05 10:09:18.140 Info, Node009, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=9): 0x01, 0x07, 0x00, 0x80, 0x09, 0x00, 0x00, 0x03, 0x72
2021-02-05 10:09:18.141 Info, Node009, Encrypted Flag is 0
2021-02-05 10:09:18.144 Warning, WARNING: Out of frame flow! (0x80). Sending NAK.
2021-02-05 10:09:18.145 Warning, WARNING: Out of frame flow! (0x00). Sending NAK.
2021-02-05 10:09:18.147 Detail, Node009, Received: 0x01, 0x01, 0x00
2021-02-05 10:09:18.147 Warning, Node009, WARNING: Checksum incorrect - sending NAK
2021-02-05 10:09:18.148 Warning, WARNING: Out of frame flow! (0x00). Sending NAK.
2021-02-05 10:09:18.650 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2021-02-05 10:09:18.651 Detail, Node009, Received: 0x01, 0x00
2021-02-05 10:09:18.651 Warning, Node009, WARNING: Checksum incorrect - sending NAK
2021-02-05T09:09:26.871Z z2m:Mqtt Message received on homeassistant/status
2021-02-05T09:09:26.873Z z2m:Gateway Home Assistant is ONLINE
2021-02-05 10:09:28.142 Error, Node009, ERROR: Dropping command, expected response not received after 1 attempt(s). Command: "Get Routing Info (Node=9): 0x01, 0x07, 0x00, 0x80, 0x09, 0x00, 0x00, 0x03, 0x72"
2021-02-05 10:09:28.143 Detail, Node009, Removing current message
2021-02-05 10:09:28.144 Detail, Node009, Notification: Notification - TimeOut
2021-02-05 10:09:28.145 Detail, Node009, Query Stage Complete (Neighbors)
2021-02-05 10:09:28.146 Detail, Node009, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2021-02-05 10:09:28.146 Detail, Node009, QueryStage_Session
2021-02-05 10:09:28.147 Detail, Node009, QueryStage_Dynamic
2021-02-05 10:09:28.148 Detail, Node009, QueryStage_Configuration
2021-02-05 10:09:28.149 Detail, Node009, QueryStage_Complete
2021-02-05 10:09:28.150 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2021-02-05 10:09:28.150 Warning, CheckCompletedNodeQueries all=1, deadFound=0 sleepingOnly=1
2021-02-05 10:09:28.151 Info, Node query processing complete.
2021-02-05 10:09:28.151 Info, Saving Cache
2021-02-05 10:09:28.152 Info, Node001, Cache Save for Node 1 as its QueryStage_CacheLoad
2021-02-05 10:09:28.153 Info, Node009, Cache Save for Node 9 as its QueryStage_CacheLoad
2021-02-05 10:09:28.156 Detail, Node009, Notification: NodeQueriesComplete
2021-02-05T09:09:28.156Z z2m:Zwave Notification from node 9: Notification - TimeOut (1)
2021-02-05 10:09:28.157 Detail, contrlr, Notification: AllNodesQueried
2021-02-05T09:09:28.163Z z2m:Zwave node 9 ready: Unknown: id=0000 - Unknown: type=0000, id=0000 (Unknown)
2021-02-05T09:09:28.166Z z2m:Zwave Network scan complete. Found: 2 nodes
Regarding the OZW Beta these errors indicate the addon crashing. There’s some reports it will fix itself after some tries and others have to either remove nodes or reinstall the addon.
You mention adding the node through the Zensys tool, which isn’t what you should be doing. Can you unpair it from the stick and add it through HA using any of the addons? (ZwaveJS is the best moving forward)
Thank you for your help here Rick
What I did now is as follows, just to be sure I do not have any conflicting configuration:
- Wiped the current installation by dumping the image hassos_rpi4-64-5.10.img.xz using the Raspberry Pi imager to the SSD
- Removed the single Z-wave switch using the Zensys tool so now it reports no pairings
- Started HA and did the initial configuration
- Installed the Z-Wave JS Integration (the service add checkmark checked)
- Rebooted the system
When the system was up again the status of the Z-wave integration was as follows:
Then I clicked the “Add Node” and then “Start Inclusion”, entered pairing mode on the Z-wave switch but no success. The “Add a Z-wave node” wave went back to the “Start inclusion” state but the switch did not indicate that pairing was successful.
Just to test if there is any issue with either the Z-wave stick, the Z-wave switch or something else I did start up, on the same Rpi4, OpenHAB and tried to add the same switch from there. And that actually did work right away, z switch is now added to the Z stick. As noted earlier only difference when running OpenHAB from when running HA is that the OpenHAB do run from an SD card and HA run from an USB attatched SSD drive.
The log from the Z-wave JS add-on is as follows:
· FUNC_ID_ZW_CREATE_NEW_PRIMARY (0x4c)
· FUNC_ID_ZW_CONTROLLER_CHANGE (0x4d)
· undefined (0x4f)
· FUNC_ID_ZW_SET_LEARN_MODE (0x50)
· FUNC_ID_ZW_ASSIGN_SUC_RETURN_ROUTE (0x51)
· FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
· FUNC_ID_ZW_SET_SUC_NODE_ID (0x54)
· FUNC_ID_ZW_DELETE_SUC_RETURN_ROUTE (0x55)
· GetSUCNodeId (0x56)
· UNKNOWN_FUNC_SEND_SUC_ID (0x57)
· UNKNOWN_FUNC_AssignPrioritySUCReturnRoute (0x58)
· FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
· undefined (0x5f)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
· UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
· UNKNOWN_FUNC_UNKNOWN_0x78 (0x78)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· UNKNOWN_FUNC_GET_PRIORITY_ROUTE (0x92)
· UNKNOWN_FUNC_SET_PRIORITY_ROUTE (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· FUNC_ID_APPLICATION_SLAVE_COMMAND_HANDLER (0xa1)
· UNKNOWN_FUNC_UNKNOWN_0xB4 (0xb4)
· UNKNOWN_FUNC_WATCH_DOG_ENABLE (0xb6)
· UNKNOWN_FUNC_WATCH_DOG_DISABLE (0xb7)
· UNKNOWN_FUNC_WATCH_DOG_KICK (0xb8)
· UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
· UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· FUNC_ID_ZW_SET_PROMISCUOUS_MODE (0xd0)
· FUNC_ID_PROMISCUOUS_APPLICATION_COMMAND_HANDLER (0xd1)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· undefined (0xee)
· UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)
19:14:00.194 CNTRLR finding SUC...
19:14:00.238 CNTRLR SUC has node ID 1
19:14:00.295 CNTRLR querying node information...
19:14:00.435 CNTRLR received node information:
controller role: primary
controller is a SUC: true
controller is a slave: false
controller supports timers: false
nodes in the network: 1
19:14:00.461 CNTRLR [Node 001] trying to load device config
19:14:00.477 CNTRLR [Node 001] device config loaded
19:14:00.494 CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms
19:14:00.521 CNTRLR serial API timeouts overwritten. The old values were: ack = 1500 ms, byte = 15
0 ms
19:14:00.522 CNTRLR Interview completed
Starting server on port 3000
19:14:00.551 CNTRLR [Node 001] Beginning interview - last completed stage: RestartFromCache
19:14:00.554 CNTRLR [Node 001] not pinging the controller
ZwaveJS server listening on port 3000
Server listening on port 3000
19:14:00.570 CNTRLR [Node 001] Interview stage completed: CommandClasses
19:14:00.573 CNTRLR [Node 001] trying to load device config
19:14:00.579 CNTRLR [Node 001] device config loaded
19:14:00.581 CNTRLR [Node 001] Interview stage completed: OverwriteConfig
19:14:00.583 CNTRLR » [Node 001] requesting node neighbors...
19:14:00.656 CNTRLR [Node 001] The node is alive.
19:14:00.658 CNTRLR [Node 001] The node is ready to be used
19:14:00.660 CNTRLR All nodes are ready to be used
19:14:00.662 CNTRLR « [Node 001] node neighbors received:
19:14:00.663 CNTRLR [Node 001] Interview stage completed: Neighbors
19:14:00.664 CNTRLR [Node 001] Interview completed
New client
New client
Client disconnected
Code 1000:
Client disconnected
Code 1000:
New client
New client
Client disconnected
Code 1000:
19:17:40.358 CNTRLR starting inclusion process...
19:17:40.410 CNTRLR handling add node request (status = Ready)
19:17:40.411 CNTRLR the controller is now ready to add nodes
19:17:43.742 CNTRLR handling add node request (status = NodeFound)
19:17:50.915 CNTRLR handling add node request (status = Failed)
19:17:50.916 CNTRLR starting the inclusion failed
19:17:50.920 CNTRLR stopping inclusion process...
19:17:51.077 CNTRLR handling add node request (status = Done)
19:17:51.079 CNTRLR done called for 0
19:17:51.080 CNTRLR the inclusion process was stopped
19:28:09.562 CNTRLR starting inclusion process...
19:28:09.593 CNTRLR handling add node request (status = Ready)
19:28:09.593 CNTRLR the controller is now ready to add nodes
19:28:41.617 CNTRLR stopping inclusion process...
19:28:41.693 CNTRLR handling add node request (status = Done)
19:28:41.695 CNTRLR done called for 0
19:28:41.696 CNTRLR the inclusion process was stopped
Thanks all for looking into this, I would really like to be able to use HA for my little setup…
Have you actually excluded the node or just removed it forcefully from the stick?
I did remove the node using the Zensys Tool and performed the “Remove node” action, i.e. click on the remove button in the tool and then click on the button on the z-wave node. When complete the node was gone from the list of devices in Zensys.
Just an update regarding this issue I have with my Z-wave “network”, might be useful for others in the same situation.
As mentioned I was successful in setting up Z-wave in both OpenHAB and Domoticz but I was aware that in certain degree I was comparing “apples with pears” since those systems did run using an internal SD card while the HA installation was done to an USB attached SSD drive, however it never crossed my mind that there would be any connections here. But today I did try to instead do as I have done with those other systems, i.e. install HA on the SD card and with the result that the Z-Wave net works straight out of the box!
So either there is some compability issues between using an USB SSD drive and an USB attached Z-Wave stick - from the outset all seems fine since HA do not complains at all and things seemingly boot up as it should - or (another note) there might be an change done in the latest HA version (did get an update note to something …2.1 when I started from fresh).
UPDATE: Seems it was the new HA OS 5.11 version that fixed the issue, I do now have HA installed on an SSD and can contact to my Z-wave node.
1 Like
Hi @bjornskj
I have the same problem as you, it seems.
Rpi with HassOS 2021.2.3 installed on SSD.
Zwave controller : Aeotec Z-Stick Gen5+
Module Fibaro roller shuttler 3.
More details here : Add Fibaro Roller Shutter 3 node to Zwave JS
ZwaveJS works, 2 nodes (z-stick and fibaro).
But, fibaro has a status : dead
How did you solved it please ?
Hi Darslan
You can check out my other post here: https://community.home-assistant.io/t/lesson-learned-z-wave-and-usb-ssd-boot-from-usb3/280442
Maybe the solution I found, i.e. use an USB extention cable between the Rpi and the Z-Wave stick, might help you? At least now with the cable my Z-Wave network works without issues.
1 Like
Ty Bjorn.
Wait, WHAT !
Is it that simple ? Hardware problem with HassOS on SSD plugged on USB…
It’s sounds crazy.
You plugged your Z-Wave stick (with ou without USB extension) on USB 2.0 or USB 3.0 ?
How long is a usb extension?
Hi
I have my USB SSD plugged to the an Rpi USB3 port and the Z-Wave stick to an USB2 port using an extention cable. When I did have the issues with Z-Wave the stick was connected directly to the USB2 port.
To be sure, you bought USB2 extender or USB3 extender ?
Anw, USB3 must be compatible with 2.0.
Well, i just bought USB 3.0 extension 1 meter.
Hope it will solve my problem.
But, Zwave stick is well recognized on Hass and it status is Ready.
It’s just the Fibaro roller shutter that has a status Dead.
It was the same for you ? Zwave controller was OK and module was Dead ?
Hi
Main purpose with the USB extention cable (note, it’s not an extender but an extention cable) is to get some distance between the USB3 port on the Rpi and the Z-Wave stick and since the stick do not really need USB3 speed it’s just as well to use the USB2 port.
And yes, what you describe is exactly what I did see, the stick was ok in HA but the Z-wave devices was not. The reason is simple, HA communicate with the stick directly but the communication with the Z-wave devices is through the Z-wave band. And the issue is that the USB3 port is interfering with the Z-wave signal frequencies thus communication between the Z-wave stick and the Z-wave devices is affected.
I can contest to this improving signal strength for the radio on the computer. TBH, I think I recall seeing it in my sticks instruction manual…
I really hope this solves my problem or I’m gonna give up.
I had this issue with z-stick 7. I thought that the problem was in the signal strength because I could see timeouts in logs. Added two range extenders - no luck. Then bought z-stick gen5+ - still unstable.
Thankfully I found this thread. I took USB 2.0 extension cable and the network become finally stable.
Aparently the anthena is very sensitive to surrounding electronics - mine rpi4 (also with ssd over usb) lives in a server rack next to the UPS.
Guys, you made my day!
I have a z-wave network with 26 nodes (Fibaro switches, plugs, smoke detectors, motion sensors… on a Aeotec gen 5 stick.
Every now and then it became unstable and two range extender (I bought to improve the signal strength) went dead.
Healing, pinging restarting did not help.
So i thought I need to re-include them (?).
Then I tried your usb cable truck with a cable laying around and voilà!
After a restart of the Zwave integration both dead notes came back to life.
I hope that this will have fixed the issue.
Thank you so much for this thread 