I’m a little bit afraid to put "restart: always" in my docker-compose file, what if ozwdaemon is restarted before my mqtt broker is available again? Will it crash immediately again or in that case, wait for connection and continue starting up just fine?
It is coded so that if the MQTT broker isn’t available it exits.
That’s not a very resilient implementation.
Configurable retries delays and timeouts would be nice.
It’s not crashing. It’s exiting orderly. If the ozwdaemon tries to start and cant contact the broker, it will exit. If you have restart: always or restart: unless-stopped then it will just keep trying until the broker comes back. It’s not like it will “wear out” 
Yes, it would be better if it was robust to mqtt outages, but for now it isn’t. What you could do is run the broker on the same pi as ozwdaemon. Then you can reboot your mac/HA all day, no issues. MQTT broker is super lightweight.
1 Like
I’d suggest running a seperate MQTT broker on the qt-openzwave host and bridge it to your main broker. My bridging config looks something like this:
connection main-broker
address main-broker.example.com
remote_username pi-username
remote_password pi-password
cleansession false
topic # both 2
You should be able to change the # to be OpenZWave/# if this additional broker is only used for proxying qt-openzwave.
2 Likes
Let’s see if I have some time next week, I may have a look at it. My profession is enterprise application integration, so why not at least give it a shot 
That’s actually a really good idea! Thanks! I think I will try this out.
I have to say, I’m relatively new to HA and started with the normal z-wave integration. I finally got everything setup and then saw the news of the new component and wasn’t looking forward to migrating in the future if I wanted OZW 1.6. I bit the bullet this weekend due to various things not working in regards to devices not being in 1.4 and my new locks having issues. I have to say, I’m impressed even with this being a beta. It works so much better with my locks and with the various devices. I knew nothing about mqtt and with some research and tinkering, I was able to figure it out. Just wanted to say I’m excited for what the future of this integration will bring and wanted to thank the developers for the hard work they have put in so far. Thank you.
3 Likes
I have a quick question. I have two instances of HA, my primary usage instance, and a testing instance. I have the older 1.4 ozw running on my primary, because it works fully for me at the moment. I am definitely interested in checking out the ozw beta. If I plug my zwave controller (using same network key) into another computer (my testing instance), and dont add/remove any devices, just do some testing, will it make changes on my controller that will cause issues when I put it back into my primary instance.
I was thinking I could see what works/does not work, learn a few things for a few hours at a time, and then put it back when done until I was ready to dedicate the time to making the official plunge.
Anyone else done this?
Nothing gets changed.
Nope I went full beta after cover support was announced, but found it was only for blinds/roller shutters 
Garage door support is merged in the latest dev version.
I will tell you what doesn’t work off the top of my head, no light RGBW color support as of yet, no usercode support for locks yet (PR pending), no set_config_parameters support yet for changing LED indicators (PR pending).
Ok, since a while (I think since update to 0.112 I have this weird issue I never had before.
zwave stops responding. In home assistant I do not see anything happen. via VNC I do not see any zwave logging.
I have:
it might also possibly have to do with an update of hassos (4.10 --> 4.11).
I see in logging:
And when I restart the openzwave addon it starts working instantly. I have had this now for the 3rd day in a row at the end of the day/begin of the evening…
Help!?
I’ve been experiencing similar issues, but I just went from “old” v1.4 to this beta 3 or 4 days ago. So I’ve just been chalking it up to the beta tag. I’m approaching 80 nodes and was also thinking that perhaps my network was far too congested.
I believe you can configure docker with some restart policies. (retry timeouts etc).
If you want something more - Patches welcome 
1 Like
Unfortuantly - Not enough logging is enabled to see whats going on there and why it stops working. I believe the addon configures a very minimal logging rules so I can’t deduce much of anything.
Hi, this is starting to become “a thing” I think. My gut feeling tells me “most” people use the addon via home assistant, now and in the future also will.
I have seen it over and over again in this topic that the one is pointing to the other with regards to “I don’t do the addon, I do only QT openzwave” etc.
Don’t get me wrong! i do very much appreciate all the free time and hard work that’s being put into this and where possible I do want to add to that, but I am not a programmer - at all -, just an enthousiastic users that is trying to find it’s way in the wood of opensource - people - product - addon - etc. And the only thing I would kike to see is: it works and it’s kept up to date.
for me it is VERY hard to get a grip of “I have updates this”, “I believe the addon configures a very minimal logging rules”, etc. to even know where I can start to make this work better for me (and others)…
EDIT: having said above.
where in the addon can I see more logging? I can only see in:
- Supervisor --> Openzwave --> log (but this gets purged when restarting and is not very “complete” I think.
- When I use VNC and click here:
But that is not very hand to scroll through and not possible to search.
Any better way?
Only in swarm mode, I believe
No, unfortunately you have to wait for it to get fixed with the addon. Logging by default is captured and placed inside the addon logs.
I have written an issue against the addon and we are waiting for the fixes to come through to add better logging & configuration.
You’re welcome to comment on the issue about the logs
Once everything stabilizes - Of course there will not be a need to “update” the add on as often. But as we are living bleeding edge right now, with Beta, of course I’m going to be fixing bugs often. If the addon works for you (and I believe it does for 90% of the testers) then its fine. For the 10% that don’t, well I take two things away from this:
- Something needs to be considered about how to handle logging in the addon when things dont work. (see below for at least my long term goal)
- maybe you should hang out in the discord channel - There are a lot of “veterans” in there that help out with complex issues (and often solve them!).
As far as the long term solution from me - That log window will eventually allow you to download/save log files etc. (with a few wizards to help with troubleshooting) - But its a long term goal. Btw, you know you can drag that “OZW Logs” window out to resize it, create new windows etc right? - Its not perfect but its a baby step towards helping?
The thing is the addon is NOT updated that often! 