Easiest way to migrate Openzwave to ZWave-JS-UI

[lost]

Same question here. It is not clear or obvious to me what is meant by security key and where to find it.

That's supposed to be where you (should?) have set it in the 1st place: Config->Hardware, then go to your wave controller line & click configuration, then select your zwave controller node (should be 1st) and you should see security network key in item nb 4.

If you did not changed it before 1st secure node inclusion, you must still have default one... Thus no (real) security in fact!

[jvdz]

@waltervl, Are you sure you want to publish your Security Network Key here in public forum?

[waltervl]

It is not mine, I dont use Zwave. I found it on the net.

[BartSr]

I also still don't have the courage to do this job. Tried several times but mostly got stuck early this year so left it for the time being...
I never used a security key. Required now?
-Bart

[uschuga]

Before I come to my next question, I would like to put the basic problem into a vision of a train journey.

Basically, I want to know whether I'm on the right train at all. The journey is clear: my ZWave installation should still work even after OZW has been switched off. To ensure that the journey is not an adventure, I need a clear travel plan. Unfortunately, I can only find travel recommendations in the forum and Wiki and have to make everything up as I go along. There are many stops with changes, timetable changes (release version, updates) etc. The preparations (released OS version) and the luggage also have to be right: NodeList, network key etc. If the train is travelling in the wrong direction (destination incorrectly formulated) or stops (Rasp not reachable), the helicopter (SD backup) fortunately comes to the rescue. Later, in the case you think you've reached your destination, you realise that something went wrong and you can start your journey again. This is attractive for backpackers, but not for smart home implementors who want to realize their ideas.

Back to the actual problem:
I have chosen @d3smo's tutorial as my travel plan, as it seems to me to be the most mature and it heads for my destination. However, I cannot expect that his plan will be updated regularly.
In the course, I can't find any indication of which Raspberry PI OS to use for the whole process and what a clever Pi OS strategy could be. This is one part of the travel preparation.
Since Buster is still installed on my system and Buster no longer seems to be up-to-date, I started with an update to Bullseye – and I failed. No idea why.

Before I think about starting with a fresh Bullseye image, the question arises as to whether an update is necessary at all. Perhaps it makes more sense to wait for Domo V 2024.1 and carry out an OZW -> MQTT migration together with Bookworm. What does the road map look like and what is the recommendation of the release makers?
Perhaps there are already published answers to this, but I have not found them in this context so far. Please correct me if I am wrong.

I guess that there are a lot of Domo/Zwave installations out there and the admins have no glue what happens when pressing the update button and all zwave devices lost contact…

[MikeyMan]

In case there are people here with issues using snap icw Zwave-Js-Ui.

There is an issue with the latest version.
You can revert back.

https://github.com/zwave-js/zwave-js-ui/issues/3487

[nitpicker]

In case there are people here with issues using snap icw Zwave-Js-Ui.

There is an issue with the latest version.
You can revert back.

https://github.com/zwave-js/zwave-js-ui/issues/3487

Thanks!!!

[forumdomo]

Sometimes I hate open source. If one developer has no longer fun, the project is dead. Software communism not always works.

[rfvdboom]

I made the switch to ZWAVE-JS-UI. It works and it works way better than OpenZwave. My Domoticz was crashing everytime when i enabled/disabled the plugin. Even after completly rebuild the zwave stick. I think the reason were the Fibaro motion sensors.

When i started with Zwave JS UI. I exclude and then include the nodes one by one. Zwave works very stable now. The UI is very user friendly.
Als the MQTT connect works fine.

[tjabas]

i run a rpi 3b+, domoticz v2022.2, rasbian buster, today i tried to install z-wave js ui, but the installation didnt work, i dont run docker, which installation metod should i use?

[MikeyMan]

i run a rpi 3b+, domoticz v2022.2, rasbian buster, today i tried to install z-wave js ui, but the installation didnt work, i dont run docker, which installation metod should i use?

How did you try to install then?

Snap or docker are the way to go. Enough posts in this topic on that.

[lost]

Snap or docker are the way to go.

That should not be the way to go if this thing was not designed with too many avoidable dependencies. Really hope there is indeed a way to avoid this containerization stuff, but did not tried myself and not willing to for now: Being compelled to this to drive some simple serial HW, that's really good sign of bad design choices & some users have unforeseeable issues over time quite far from the move to this accidentally working sw pile... Just cannot afford this on my system.
In the end, this dependency nightmare already difficult to install for users will also be difficult to maintain & really hope some zwave controllers will embed MQTT layer before I need some more hardware unsupported by OZW so I could avoid zwavejs at all.

[MikeyMan]

Snap or docker are the way to go.

That should not be the way to go if this thing was not designed with too many avoidable dependencies. Really hope there is indeed a way to avoid this containerization stuff, but did not tried myself and not willing to for now: Being compelled to this to drive some simple serial HW, that's really good sign of bad design choices & some users have unforeseeable issues over time quite far from the move to this accidentally working sw pile... Just cannot afford this on my system.
In the end, this dependency nightmare already difficult to install for users will also be difficult to maintain & really hope some zwave controllers will embed MQTT layer before I need some more hardware unsupported by OZW so I could avoid zwavejs at all.

Oh that i fully agree with.
Home automation software should really be a one stop shop. And Domoticz is getting further and further from this.

Both zwave and Shelly are now much more difficult to implement than before.

I've mostly stopped using domoticz recently, and moved to Home Assistant. And although there are many drawbacks to that as well, it is starting to win the battle hugely.

[jake]

Sometimes I hate open source. If one developer has no longer fun, the project is dead. Software communism not always works.

Did you sponsor the original developer by any means?
Even in communism era everybody had to work and that with only a mediocre outcome. IMO there are 3 options for you:
- Add to the community with coding
- (financially) sponsor the coder
- buy commercial software

O, and the last one: use what it is supplied as is and be thankful for the creativity and effort that someone else put in.

Verstuurd vanaf mijn SM-S911B met Tapatalk

[AimoPaukku]

Shit hit the fan... Now what?
My automation is now useless, and this came to me TODAY AFTER "normal update"
I have using since 2017.

If i have to do some tricky stuff and add every z-wave again, it is not domoticz any more

[HansF]

Do you have a backup or image of your last working setup? Hopefully you can put it back.

[AimoPaukku]

it wont bring my z-wave stick back, so i can see all devices but those are dead

[lost]

I've mostly stopped using domoticz recently, and moved to Home Assistant. And although there are many drawbacks to that as well, it is starting to win the battle hugely.

I'm not on this path (maybe Debian founder should also not have, 8 years ago)... Too many personal investment in my system & HA is on the same dirty containerization/docker path, even if probably better hidden to users.

[AimoPaukku]

Im thinking to switch homey now and quick.

im really sad how this went...

[jbaragon]

As soon as they do not release a version of Domoticz where Zwave is not simply implemented as before, I am switching to another system. Things have to be simpler and for a program to be used by the majority it must be made easy and friendly.