Great work!
I’m sure this thread will help a lot of people.
I’ll definitely need to look into some of these things as I’ve had my share of Z wave issues. I thought it was hardware related (Aeotec G2 micro switches & Aeotec in wall dimmers - some I have returned/replaced). Maybe it was software all along.
Right now I have one more Aeotec G2 randomly not updating it’s status consistently and now occasionally showing as “dead” until I heal the network.
you did yoeman’s work for sure on this… thanks for posting these “deep dive” details, extremely helpful. I’m in the process of deciding which technology to invest in and was considering z-wave. Initially will deploy two thermostats and a small number of lighting controls to a vacation home and desire remote control to preheat and turn on the lights before arrival.
The logging issue is one to get an answer on, I would think.
So exactly one of your issues somewhat indirectly has anything to do with home assistant, point number one. And I say indirectly since its still and ozw issue renaming entities.
In the latest release HA now creates unique eneity ids so this issue with zwave changing names should go away.
Debug in HA is for the HA component, not ozw
Not sure about that, but maybe ask the openzwave guys why we have to put specific workarounds in?
That’s really unfortunate that you’ve had a bad experience.
My experience is the complete opposite. It’s been great and smooth with 12 zwave devices and counting.
So the workarounds, it looks like this was because of zwave config files not being updated, so someone hacked it to map devices to working devices. We recently updated open zwave so I bet these are no longer necessary.
And yeah, zwave has always worked great for me (besides the entitiy renaming) but ZigBee on the other hand…
I have had my frustrations as well. After switching out most of my 433 MHz network from Telldus to HA and Z-wave, I almost have nightmares from debugging and staring at the OZW log the last weeks 
Currently I have problems with Aontec dimmers and NorthQ power reader. Aeotec dimmers worked fine for a couple of months, but then it was just random (Z-wave issue - HA sending value 0). There is a thread about the NorthQ Power Reader, but I haven’t had the time to debug it yet (NorthQ NQ-92021 Power Reader).
I currently have 36 Z-wave devices. I have not yet noticed any large delays in my network. Looking at the log, It can be 10-20 seconds between a device-update on idle, so there is some breathing-room - but when I try to dim my Nexa dimmer it generates 713 lines in the OZW log, so I think there is something weird going on.
My conclusion is that using HA and Z-wave without the OZW log, is like using a rock instead of an hammer when building a house at this moment This is mostly because missing feedback in the GUI and a lot of restarts.
Im reassured to read that more people face problems with zwave . I’m partially thinking to stop home assistant entirely but then I think after spending 100 of hours and more than 1000€ for all my stuff I think no…I must continue.
I have those remotec zwave ac ir device and even after using always listening mode they appear dead or just don’t react.nice at this period of the year.
I recently bought Intel nuc and I’ll setup home assistant with all automation and components from scratch.also zwave.
I hope after restarting with reset devices.empty files and fresh system it will work. I hope so as I also built my home security with zwave.
Problems with mixed non secured and secured (zwave plus) network should really not be a problem but I read those often here.
Well. I’ll come back here with a 100% fresh installed home assistant and reset zwave network/devices and will report back.
Till then I have to accept that my sh**** remotec devices won’t work as needed.pity for those extraordinary prices for zwave.80€ for one device. Sometimes I think zwave is more like for devs and play kids than serious devices.even those Chinese Xiaomi stuff works better costs 10% of the zwave price and even looks better.
We will see the future for my zwave network here.if not u can buy all my stuff on eBay the next upcoming weeks 
Point 6 (and Ad6) needs to be addressed. It’s what causes timeouts in my network. Almost everytime I see the controller waiting for something it’s those checks that have piled up.
Thanks for writing this article.
Well, I finally gave up.
Zwave on Home Assistant is just horribly unreliable, and impossible to troubleshoot in any meaningful way.
I’m still using home assistant, but I’ve offloaded my zwave network to a Vera controller that connects in to Home Assistant. Immediate impressions:
As I go on, I’m finding that Home Assistant has amazing core functionality, unrivalled by any other product I’ve seen. But there is a lot of focus on “new and shiny” and not so much on fast and reliable. For my next task I’m looking at moving my GPIOs off of home assistant to something that registers the correct state every time and can handle debounce properly without getting stuck on the wrong state.
Thanks for replying so quickly to my comment. I almost thought as much, because the unstable nature of Z-Wave in HA couldn’t be representative of z-wave as a whole. If it were, no one would buy it.
I’m placing my hopes on the latest blog article.
I will pay for HA cloud if they fix the z-wave issues because my whole house relies on z-wave.
I’m a bit surprised. Stumbled on this post and have z-wave via Home Assistant running for more than a year now. Best combo ever. I have about 29 devices and although somethings feel spartan… I wouldn’t say unreliable.
I’m using the aeotec z-stick gen 5.
Perhaps there is something different with types of controllers?
I’m using an Aeotec Z-Wave Gen5.
These are helpful observations and will hopefully help some others debig what’s going on with their networks.
However, do you remember what you paid for HomeAssistant and for OpenZWave? Probably nothing. I’m not knocking the amazing contributions of the people who volunteer to commit to projects like OpenZWave, but they are volunteers. If you want something that’s much more stable, why not purchase a solution like HomeSeer.
I started with OpenZWave, got frustrated and went to HomeSeer. I went back to OpenZWave because I thought there were improvements and I’m a developer at heart. OpenZWave gave me the ability to have much more control over the application. But now I’m back to HomeSeer I think once and for all because I value stability more than flexibility.
Like many other decisions, you do a cost/benefit analysis and decide what’s more important to you.
I have only recently started with Z-Wave on Home Assistant and have also had issues with it being flakey or unreliable.
The entity renaming issue hasn’t hit me, but issues with randomly freezing and slow responses due to the way Z-wave is handled definitely have.
I migrated from Openhab (also free and opensource) because the Java scripting used in that was a little technical for me, but I have found I have had to put a lot more time into ZWave trouble shooting with OZW and HA.
Issues, such as some devices (ZXT-120 in particular) not responding in OZW, yet respond perfectly in OpenHab have made this a bit frustrating.
I am going to take the Vera route to control ZWave until OZW in HA is more reliable. I don’t like extra hubs, but reliability is stability is key in anything to do with home automation.
With that said, I love Home Assistant so far and appreciate all the work that is put into it.
I also understand, as @swmcdonnell pointed out, it is free. Don’t take anything said as an attack, more observations, and a little frustration. I am not looking for instant fixes. These are just accounts of my frustrations with some bugs that currently exist.
Consider this a +1 for the OP’s issues… I opened a different thread hoping to start fresh, but no replies yet:
https://community.home-assistant.io/t/status-not-updating-seems-to-be-getting-worse/85790/5
It’s frustrating to hear all the people chime in and say they have no issues and most of them use the Aeotec Z-Stick as well. That was the reason I bought that device, it seemed to be the best supported and best reviewed by HA users. In addition to everything outlined in the OP I also have an issue where every time HA is restarted a different mix of Z-Wave devices are “Entity Not Available.” After a few more restarts eventually I can get it where all devices show up, but not much else has changed besides the # of reboots. The OZW Log shows the same type of chatter each time it boots up. Occasionally I do see “Z-Wave not ready after 300 seconds, continuing anyway” in the HA logs itself, but again OZW Log shows normal Network chatter. I’m not sure what makes it ready versus not ready… just a few more restarts of HA and it’ll eventually consider itself ready.
It’s nice to hear that there’s the possibility of starting from scratch with a different Z-Wave implementation (in lieu of OZW) but in my laymen’s perspective, the issue is not with OZW. When I fire up OZWCP, all of the devices are always ready and happy, respond instantly to commands, and instantly become aware of manual device changes.
I believe the issue is likely related to the OZW Python Wrapper. It seems to be a little less than ideal.
It will be good to have a ZWave revamp using the new public SDK.
There is talk behind the scenes in how to best move forward.
Hi, which Vera controller are you using?