Error fetching non-existent config params on startup of OZW

Configuration Z-Wave
1

I have HA 116.2 as a Hass.io image on RPi 3. I’m running ozw 0.5.2.

When I reboot, I notice that for about 2 or 3 minutes I get the following every 10s in the ozw log.

node 7 fail
node 7 fail1220×599 56 KB

Note that since this was repeating, the beginning of the cycle could be at the fourth message and the first three are the end of the previous cycle.

After about 2-3 minutes it stops doing this and goes on to node 8 and higher then everything operates properly (including the thermostat).

Although this does work fine after a few minutes, it is clearly wrong and it slows down my startups (which, admittedly, should be rare).

Any ideas what is going wrong and what workaround would be suggested?

Oh, also, where do I find the log file so I don’t have to use screen capture. I can get into the docker of ozw, I just can’t find the file.

Keith

2

OK, so I think I have found a couple of answers. I found this bit of advice on how to get the log file. Awsome and many thanks @ltilley. This is really critical to debugging, of course.

Now that I have had a chance to look at the log file, I could see that on startup ozw was attempting to fetch something (value?) for each config parameter in the .xml file. The 2-3 minute holdup (actually, just shy of 6 minutes) was attempting to fetch for config 161-199 with a 10s timeout on each.

So my question now is to those who really know, what are those messages saying? If they are reading a config parameter that doesn’t exist and that is why they are timing out, I will fix the .xml. My concern is that ozw sends a query message with the config number and DOES get a reply (the sixth line of my log) but seems to be waiting for more that never comes. Then it times out at 10s (the first line of my log). What is the expected transaction? 1. Query out, 2. some sort of ack back, 3. data back?

Please advise so I can fix the xml if appropriate.