Utilize the same entity names and you don’t have to update scripts/automations.
I had stated that already, but if the old ones aren’t renamed first then that won’t work.
That’s where the migration tools are supposed to assist
Hi…
So I have to rebuild my Zwave network this weekend, was debating on going openzwave then started to read this thread. I am still newbie with HA, should I go openzwave? I only have maybe 20 devices or so…
I wouldn’t.
it looks like (maybe…?) the new direction is going to be zwave js. But it’s not ready yet.
I would just use the built-in zwave integration for now then switch over to whatever the “new official” integration is going to be once all of the dust settles.
Anyway you go there is going to be at least some pain in migrating if you want to stick with whatever the official integration will be. Hopefully a migration tool mitigates some of that when zwave js becomes more mature.
But who knows? maybe OZW development will resume again now and it will be OK going forward. But I don’t know that I would count on that reading some of the posts in this thread.
I will provide you with anything you need while I still have my HA running and before I blow it away to go back to SmartThings, just tell me what you need and how and I’ll get whatever you ask.
I have always been prepared to help wherever I can and provide money where I can’t, I gave actual cold hard cash to several developers on the SmartThings platform who weren’t even asking for it but to be honest, the reception I and several others have received here from developers over simple criticism has very quickly made me look the other way.
I have 74 Z-Wave devices paired of varying sorts, I have over 90 in total but I stopped pairing them the more things got unstable because there’s no point since as it’s stands Z-Wave and thus HA is completely unusable to me. I chose the most supported method using the most supported hardware possible thinking it would give me the best experience but it has been the total opposite.
Tell me what will help you the most and how and I will do my best.
Just an update for everyone. I’m in the process of importing every single certified zwave device into Zwavejs2mqtt and node-zwave-js (the new server backend). I’m about 98% finished and working on bugs now so confident it’ll work. It’s a few hundred additions and revisions to around 1,000 device files representing devices from all over the world (after accounting for model changes…its 4,700 entries total). In talking with the maintainer, our goal is to have it auto-PR newly added devices each week or so. At the moment the database even includes pre-release devices so hopefully device file issues become a thing of the past.
From switches to bulbs to thermostats to mousers and graters (whatever the hell they are…the Russians have some interesting devices), we’ll have device files for it all.
Thanks so much! Very nice to see how you have on the one hand been passionately advocating for the need to do something about the deadlock position Z-wave for home assistant was in (with qt-openzwave not moving forward), and on the other hand are now with an equal amount of passion contributing to implementing to the newly defined roadmap.
Given the flurry of activity I’m seeing and the speed of development, I wonder whether my choice of starting off with the current (outdated) native integration is the right one. Perhaps in a few months zwavejs will already outperform the native integration on almost all fronts. In that case I would simply wait a bit longer with migrating my z-wave devices to Home Assistant.
Perhaps in a few months zwavejs will already outperform the native integration on almost all fronts. In that case I would simply wait a bit longer with migrating my z-wave devices to Home Assistant.
Definitely a possibility, though we’ll see how many bug reports we get after the 2021.2 release
In this light :-)… is there already a positive advise to “easily move from QT-Openzwave to JSOpenzwave”?
There’s no such thing as JSOpenzwave
Right now migration between the integrations would be completely manual. Depending on how many devices you have (and what kind of devices) it may or may not be worth it yet. I’m not sure if anyone is running the new integration on a large “production” network yet, most of us have been using smaller test Z-Wave networks.
are there instructions for updating the device database located anywhere?
I’m not even sure where I would submit updates. I submitted a PR for a couple of devices to OZW so I could do the same for zwavejs.
Also it might be better to continue zwavejs discussions in it’s own thread.
I started one already but if you want to start another that would be OK too.
there’s no reason to start out a discussion oin the new stuff in a thread that already has over 200 posts about the old stuff to wade thru.
I’d hold off on manually submitting them. I’m about to import a ton of devices so it’s likely wasted work and a fair chance it adds more work to me to reconcile conflicts.
FWIW I have 31 devices, 10 different device models (switches, dimmers, motion sense lights, energy monitor plugs, motorized blinds, door sensors) and it’s running smoothly. There’s devices that are not OZW 1.4 compatible which is why I tried out the alternatives (ozw, zwave2mqtt, zwavejs2mqtt). Currently deployed with docker on one host and hassio on an Rpi. Zwavejs works for me right now, and I see lots of activity on bug and feature requests. I like blwhoward2’s work on importing from the compliance source, I think that’s going to be a material benefit compared to OZW.
I like blwhoward2’s work on importing from the compliance source, I think that’s going to be a material benefit compared to OZW.
FWIW, OZW also did a big import of configuration info/metadata from the Z-Wave compliance docs, but I’m not sure how often they’ve been refreshed (if any) since the initial pull a year or two ago.
@cgarwood Yeah, I can tell when the labels line up exactly. It had to have been a while ago and they don’t appear to have used them to error correct what they already had in place from users creating them manually from other files.
Right now we’re using openHAB files which are more out of date. Fishwaldo hasn’t responded about requests to use ozw’s files. We may run those through too but this way doesn’t require worrying about whether the license protects them at all or arguably incompatible licenses so I started with this.
Let me know what you need, let me know what you want me to do, I will start with a fresh copy of HAOS and do (almost) anything you want.
The faster we can get this going the better and I am happy to do what I can to make this happen. I will feedback any issue I come across if I can.
You have personally helped me get things working throughout your project. I want to thank you for everything you have been doing and thank you for the work that has made home automation really work well.
I wholeheartedly understand where you are coming from and, frankly, have handled it better than I ever could have. I hope that maybe some people will see this and take the time to consider the people behind libraries and services.
So, again, thank you so much for your work; you deserve to feel as if you’ve accomplished something great.
Fishwaldo,
You have contributed massively to HA, you have helped many many many people here on the forum, including me You owe us nothing.
We owe you a huge debt of thanks
I don’t really care what is happening in your personal life other than to wish you well, both now and in the future. (though I’m sorry about your gear, I weep for their little silicon souls)
You have a right to both a career and a personal life and anyone who criticises you is saying more about ‘them’ than about you.
Good Luck in your endevours.
@Fishwaldo Thank you Justin for all your hard work and contributions. It was through your unsung efforts that I was able to migrate my Z-wave NW from a Vera Hub (which is a paid product being dead-ended) to Home Assistant.
Overall I would say my z-wave is definitely faster and more devices are supported thanks to your hard work than Vera did. Are there occasional stability hiccups… sure… but no worse than I had before and I know much more about what is going on now than I previously did.
Thanks again for everything.