sirfooey
sirfooey
I am also experiencing this issue, occurring when the ozw container is starting up. Resulting in a client timeout and disconnection. In the previous zw1.4, ozwlog shows I have a...
As with OP, the only way for the ozwd to remain connected to mqtt (not getting timeout) is to trash the ozwcache file.
@jlengq Check your OZW container volume location, it should be right there.
@jlengq yes, trashing the file starts the whole discovery process again (no loss of any node data); but sometimes that's what is needed to get it fully operational. Some people...
So far with limited testing, I can confirm with @kpine's suggestion, ozw is able to start up with a pre-existing ozwcache file, whereas in the past, I would 100% of...