Warnings in log file: unable to find service and z-wave not ready / Errors and Warnings in OZW log

Every time I start Home Assistant I have the following warnings in my log, I’ve not bothered to look into it till now, because in general it seems to work. Z-wave loads very slowly, but I’m not sure that’s really a problem, the controller is just doing the initial poll of all the devices. And turning on switches seems to work.

Any ideas why this is happening and what I can do to solve the warning?

I am running the latest version of Home Assistant on my RPi3, which I installed through the hassbian image a couple of weeks ago.

17-03-09 15:39:41 WARNING (MainThread) [homeassistant.core] Unable to find service switch/turn_on
17-03-09 15:40:09 WARNING (Thread-1) [homeassistant.components.zwave] zwave not ready after 30 seconds, continuing anyway


When I check the OZW log I can see that the controller is still getting Initial read of value 7 minutes after starting. Some of my devices have 10 minute sleeps so that seems ok as well.

However, some other warnings and errors I don’t know what to do with:

2017-03-09 15:39:39.668 Info, Setting Up Provided Network Key for Secure Communications
2017-03-09 15:39:39.668 Warning, Failed - Network Key Not Set

I put a Network key in the options.xml file to add secure devices, it’s possible that I made a mistake with this. I changed the existing 16 2-byte hex-digits (0x00 - 0x10) to 16 random 2 byte hex-digits (0xD6, etc.). I’ve double checked this line, and cannot see any problems.


2017-03-09 15:39:39.672 Warning, Node004, WARNING: Checksum incorrect - sending NAK
2017-03-09 15:40:11.211 Info, Node012, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2017-03-09 15:40:11.211 Warning, Node012, WARNING: Device is not a sleeping node.
2017-03-09 15:40:25.778 Warning, Node005, WARNING: Received reply to FUNC_ID_ZW_ASSIGN_RETURN_ROUTE - command failed
2017-03-09 15:40:26.069 Info, Node005, WARNING: ZW_DELETE_RETURN_ROUTE failed. No ACK received - device may be asleep.
2017-03-09 15:40:26.069 Warning, Node005, WARNING: Device is not a sleeping node.
2017-03-09 15:40:26.082 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x15 received (expected 0x1f)
2017-03-09 15:40:26.082 Warning, Node005, WARNING: Unexpected Callback ID received
2017-03-09 15:40:59.994 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2017-03-09 15:40:59.994 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=0
2017-03-09 15:41:15.940 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x2d received (expected 0x00)
2017-03-09 15:41:15.940 Warning, Node005, WARNING: Unexpected Callback ID received

At some point the following warning repeats 6 times within about 10 seconds:

2017-03-09 15:42:52.614 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2017-03-09 15:42:52.614 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=0

Throughout, I also have the following error, affecting pretty much every node at some point. In some cases it seems to be immediately re-issuing a command to that node, in other cases not.

2017-03-09 15:42:15.146 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-03-09 15:42:15.147 Detail, Node008, Removing current message
2017-03-09 15:42:15.147 Detail, Node008, Notification: Notification - TimeOut

I also get this error 3 times within about 30 seconds, just affecting 2 nodes:

2017-03-09 15:41:11.824 Error, Node005, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack

Would be happy for a diagnosis on any of these points :slight_smile: