Because IMO the user interface of the Vera isn’t very good. And the device support is much deeper in Home Assistant over Vera, so if all of my devices are in HA I can have them automate together.
1 Like
You are definitely not wrong. I do try and read the breaking changes. In fact, I will have several issues to face. My Python version is deprecated, pretty sure the virtenv is no longer supported, and the Z-wave stuff we talked about. I try and stay a few versions behind on purpose, but yeah i need to upgrade soon as well.
Hmm I hadn’t heard anything about virtenv not being supported soon. Where did you hear this? Did a few searches but nothing turned up. I hope it’s not killed, I use it and like it. Tried hassio and felt limited.
python 3.4.x is no longer supported you need to be on python 3.5.3 or higher
check the blog for this stuff 
I could be wrong on the virtenv. (Looking at blogs now), but Python 3.4.x is definitively gone
It was the all in one that is deprecated
- Home Assistant is using a python implementation of OpenZwave. Neither of which are official and/or current. They work fine for some and not so much for others.
I’ve ran Home Assistant for a while and with different controllers (usb stick) and the best for Home Assistant has been using a Vera Plus as the z-wave and zigbee controller and using the Vera component to integrate the devices. Leave the Z-wave and Zigbee hardware level interactions to the systems that know it best.
Vera is a great z-wave/zigbee controller. But you will kill vera very very fast by adding plugins and trying to really do much with it. Leave it be to do the hardware and use Home Assistant to do the automations and media interactions etc etc.
Today I’m using a combination of 3 systems (1 because I’m cheap) and 2 because the vera zigbee ZHA support is better than Home Assistant.
1 Like
That is all good. Different strokes, right? Not sure how Vera Plus helps you with being “cheap” since it costs 2-2.5 times a Z-Wave USB controller though (Like the Aeotec Z-Stick)
Well in some ways I’m cheap and in others, well I’m not. As I said I run a combination of 3 systems and the vera isn’t the cheap part, but the plugins are.
HomeSeer 3 - Not cheap!!! and the plugins are expensive. But SOLID LOCAL system
Vera Plus - Had it and makes for a good Zigbee controller as HomeSeer doesn’t have good Zigbee yet. Plus I use the plugins on Vera for certain things like Lutron Caseta and Philips Hue ($40) etc which for HomeSeer are expensive (Lutron plugin is $60). So this is me being cheap 
Home Assistant - Runs on a rPi or a VM or Docker depending on what I have it loaded on at that point in time as my configuration is movable. I use HA for media and TTS through the Google Home Mini’s. I can do that same with HomeSeer but that just the Casting would cost me $40 bucks. Then there’s Harmony plugin that’s $30 and I could run that on HA or Vera either for free.
So I guess I’m cheap in regards to buying the different plugins 
I eventually will and then I’ll move 98% of everything into HomeSeer. But until there’s good Zigbee for HomeSeer it looks like I’ll be keeping a vera hub connected.
I use the 3 systems each for their own strengths and to augment the others. HomeSeer is by far the leader in the home automation world among consumer systems. If you want something better you pony up for Control4, Crestron, Leviton, Etc etc. Using the 3 I have direct interaction through their HTTP API’s to keep all systems in sync.
So far I’ve found this combination to be the best situation. And if you’re wondering, in my current “pile of stuff” I also have a SmartThings v2 hub and a Wink Hub 2 and another Vera Plus hub and I’ve tried numerous other software solutions.
For my “needs” more wants really, I like my setup for now. But I also change it up quite a bit.
1 Like
Yes, it does. Wink does require internet but so far it was great with HA, Google Assistant, Homeridge
Got the VeraPlus and rebuilt the entire mesh network by excluding everything and then including. Some things are a little slower than before but overall the include process was very reliable and I didn’t need to spend a lot of time troubleshooting. The last time I rebuilt the mesh network it took several days. This time I managed in a few hours. Overall I’m very happy.
I have device running in central location in house, connected to a very reliable wi-fi network.
Very pleased, should have done this a long time ago.
Anyone want a cheap USB zwave stick 
1 Like
Give it a some time for the mesh to clear up the routing table and settle and that will improve the speed. There’s always going to be some degree of latency as HA is talking to the Vera through the HTTP API on the Vera. This will always introduce some latency, but usually very small in the millisecond range of things. If the latency gets too bad it’s probably a Wifi latency issue. Then I would suggest use a hardwire ethernet connection. If you have plenty of devices that are routing (powered devices) then the placement of the vera doesn’t always have to be “central location”. I have mine in my “family room / office” area which is on one side of the house and all the devices are spread out through the house and I don’t have z-wave latency unless I’ve changed the routing by adding/removing devices.
I also agree about the entity names and had a similar problem. I borked my whole z-wave system by using the HA editor to change the entity name of a couple of my z-wave modules. I forgot the “little” warning and used a dash in the new entity name. Can’t remember exactly how I got it fixed, but I think it had to do with some under-the-hood editing of the zwave xml file.
Don’t give up on zwave for the hardware layer. I have been using automation since my first X10 unit in 1983 and have found zwave to be the best so far; nowhere near great, but best so far.
The Aeotec Z-Stick seems to work ok for me, but it is so limited on its interfacing that it makes troubleshooting a royal pain.
Z-wave needs work, open-zwave seems to work just fine but some features can use a tweak. If you add a device and then rename it, the first part of the device is still the old name in the registry file. There are some threads abou that too. At some point i needed to make it work, since i have 70+ devices. Just 1 bad node in your network and it is screwed. Actually greated a complete post about my issues which perhaps can help others.
That said, it takes a long time to boot up (which is normal) but even with a lot of devices you should still be able to ‘switch’ a device although with longer wait times. If that is not the case then something is bad too.
As some suggested, the whole entity things changed and a good chance thats the case too. Adding a Vera only moves your problem somewhere else, and by problem i mean having another device. I use automation to also safe money on electricity by turning off the subwoofer when the stereo goes off. Adding another device consumes power too.
Room for improvement, sure! Does it work? Yup! Does it drive you crazy to the point you want to get a Vera too? Jup. But i just didn’t want to give in and it works just fine now.
I found moving from a rPI to a NUC has drastically helped startup times for zwave as well. I don’t understand how as in theory it’s radio speed limited to enumerate all the nodes but it made a huge difference.
Also setting logging levels to a reasonable level in OZW helps.
A couple dead nodes on the network can be handled by ignoring them; I do this for all my holiday outdoor zwave switches for lights. I just uncomment them when I set the lights back up.
I did move to a NUC too actually, RPI was at 100% when starting with z-wave. It saves some time but in the end it would only save a minute or 2 and then work as normal. (but now i can run more stuff on it)
Personally, similar story; currently have about 70 Zwave devices (mainly Evotronic Spirit TRVs, Greenwave Powernode 1s and three or four Fabiro devices)
I had a Vera Plus and was happy to remove it, due a lot of compatibility issues, and a total pain to resolve. Earlier comments about installing apps on the Vera as spot on, do not do it! The best things it had to offer was the extended UI to see the Network Map but in the end it was slow (many seconds) to simply toggle a socket power.
I tested moving first to open Zwave on a PI with Domoticz (as it also supported Evohome without cloud) and using a Zwave.me module This was a major improvement in a stable and usable system.
After a number of months with Evohome that had to go as it has no mesh support and it’s range was not suitable for the house (6000 sq ft), so after some more testing of TRVs I have replaced over 30 heads with spirits.
Not needing the Domoticz software I moved the core on the pi to Home Assistant, and quickly saw the pi was under strain, so moved production to a NUC and at this point I am experiencing the most reliable Zwave solution so far.
I run the front end experience with IRidium as I Do professional installations with this platform but at home I use MQTT to bridge the worlds.
Home assistant is an amazing solution and kudos to was is one of the most vibrant communities I have experienced in 20 years of Home Automation.
Cheers
Have that installed. But just yesterday wrote a macro that gets the neighbors from the Zwave states as exposed in Home assistant and this week I am hopefully to figure out how to create a custom card to illustrate the results.
A lot of valid reasons here, that’s why I went the opposite way: I split my zwave network in 3 pieces (now moving to 4). Handling 15-20 devices per network is very fast and startup is around 20-40 seconds (except battery devices). It costs a bit more but its so much easier to manage… Maybe I’ll have 5 networks in the future :). Also… I have no hops in the network, everything is direct communication