ozwdaemon currently shuts down when it gets disconnected from the MQTT broker. Unknown if it will be changed in the future, but I sure hope so (see Github issue).
If you are using the latest container image, it will automatically restart and wait for the MQTT broker for a short timeout. I can’t remember if there’s a limit on the number of retries. Older versions (e.g. the fabled build-150) don’t do this.
If you don’t have a docker restart policy configured, which is sounds like you don’t (?) you probably want to.
I have the restart policy set to unless-stopped. I know the container was running when I finally manually restarted it. Hope this gets addressed somehow.
I’m now using the polling workaround on 5 of my switches. It seems that it polls a device every 6 seconds, and therefore all 5 devices every 30. Unfortunately 30 seconds is a very long time here. I see the ability to change intensity, but there must be somewhere to set the polling interval? Any ideas?
However, I have not seen these settings have any effect, so I don’t know if it’s really possible at this time. Alternatively, create an automation that published an mqtt refreshvalue command on a timer, and use any interval you like.
Polling too often can have a negative effect on the performance of your network.
Excellent! I was unaware of the “refreshvalue” MQTT command. That allowed me to move my 2 dimmer modules off of polling and just refreshing them 4 seconds after any command to them. For the remaining 3 switches that don’t report manually, I think I’m going to have to aggressively refresh them. I don’t like it, but I don’t have a better option right now. 3 refreshvalues (1 per switch) every 5 seconds is quite sufficient, and I doubt will have too much of a performance hit on the network.
I have begun my migration to the new QT-OpenZWave. I am trying to rename the device and auto update the entity id’s (like the popup mentions) and sometimes it doesn’t work. Only the device name is updated. Any ideas why? Any easy way to “manually” update a few items that doesn’t involve multi clicks per device? Screenshot of mentioned popup below.
If you click Ok on that dialog it should rename the entitiy_ids as well, if it’s not occuring it’s usually due to the entities having been renamed already.
Is this still the future path? It’s difficult for me to follow updates or progress since there’s been no movement in the public repo for over 2 months and no response to critical issues like the one I filed several weeks ago. Right now I’m completely blocked and not sure what to do.
I’m contemplating moving to Zwave2Mqtt as a possible resolution, which seems to continue to see active development. Has anyone made a move in that direction?
I dont have an answer for you but am curious as well as to why there have been no updates lately. I can’t complain much as my setup seems to just work right now. I had a crash a couple of weeks ago from the OZWD container that required a restart, but other than that, been rock solid since. It is nice to restart Home Assistant as much as you want and not have to wait for the network to reload.
Well, his last activity on GitHub was in August, so maybe he is just taking a vacation
If he would be unable to work on ozw anymore, this would have an impact on zwave2mqtt as well, as it is also based on open zwave, where fishwaldo is (one of the) the main contributor(s).
