Why Migrate to Z-way from vera and how?
-
You can make the reactor device IDs the same by manipulating them the same way you would on a vera (it is an attribute). What will be different will be the device IDs of the zwave devices.... When moving to openLuup, the zwave devices will be come bridged and will have an added “prefix” of 10 sending them in the 10000+ range.
You could alternatively try to add z-way as a secondary controller first which would make the same zwave device show up twice on openLuup: one through the vera path and the other through the z-way path.
-
Yeah sorry, I meant the zwave devices, not the Reactor device ids.
Not possible to move one device at a time?
C
-
Not without breaking your network... remember? it's a mesh. So they all talk to one another. The whole point of this migration is so that you don't need to do it one device at a time. Trust me it is much better to move the whole thing all at once but you do need to reserve the time to change all the IDs in the scenes.
-
That's a lot of time is my point I don't mind a lot of time per se, but a lot of time without HA working (If I'm reading it right every instance of every device in every Reactor / scene will need updating)
Prophead's experience seems that it's even more a lot of time getting Z-way running due to the libcurl 3/4 issue?
Personally I'd probably compile from source, but.....
C
-
@rafale77 said in Why Migrate to Z-way from vera and how?:
- Install openLuup somewhere on any machine (again does not need to be a rPi but it can be) with verabridge.
- Move all your plugins and scenes to openLuup with using the helper features of the bridge. See how you like this. It should stabilize the vera to some degree. (I ran like this for a couple of years)
Then if reliability is still an issue, - get a uzb plug it to a machine, can be the same one, and install z-way-server.
- plug the uzb on the vera to migrate your zwave network on the uzb and then plug it back to where the z-way-server is
- Install the z-way bridge on openluup and connect them together. Migrate scenes.
OK I think I'm up to step 2.
But I have no plug ins.
I have no scenes either but that's deliberate. All my automation is now done on Reactor (the 4 house scenes are there, of course)So what do I need to do to further to stabilize the Vera?
Cheers
C
-
Move reactors to openLuup along with all the plugins.
-
Move Reactors =
Install Reactor from AltMarketplace
Backup Reactors on Vera
Restore Reactors on OpenLuup
Edit Reactors on OpenLuup with regard to device numbers
Delete Reactors on Vera
?Move plugins = Just install them all from Alt Market place?
Cheers!
C
-
This all sounds about right for those which are on the alt market place. Technically though the files should have been transferred over from from the download verafiles action so all you have to do is to create the devices to get the plugins appear and then copy over the parameters for these plugins from the vera.
-
Your point 5 here:
<quote>
Go into the vera UI and go under Settings/Z-wave settings/Options Tab and change the port field to "/dev/ttyACM0" and let the luup engine reload. This will wipe out all the zwave devices from your vera configuration (Another wonderful feature of the luup reload...) and switch you to the uzb as your zwave chip.
</quote>Can I assume the NVM of the Vera dongle is not impacted? And if you change the port back everything will be restored? Just wondering what my roll back / fix forward options might be.
Cheers
C
-
The vera dongle is indeed unimpacted. If is just swaps what dongle the luup engine's communicates with.
-
@rafale77 said in Why Migrate to Z-way from vera and how?:
The vera dongle is indeed unimpacted. If is just swaps what dongle the luup engine's communicates with.
OK, that's cool. Need to try and find some time this week. Been too busy this weekend working on the new kwoon for those into that kind of thing
C
-
Hi guys,
Do I need a Zway license for this?
-
To use z-way-server for anything more than upgrading the uzb firmware, yes.
If you use a razberry instead, no but you can't transfer over the vera's zwave network with a razberry alone.
What you can do, which is what @DesT has done if I remember correctly, is to follow this procedure to transfer your vera network to a uzb, back it up on z-way and restore it on a razberry. -
yes because you will need to use the z-way software to be the zwave network manager layer.
-
Yes, it will basically the vera. add/remove device, report battery etc... openLuup communicates with z-way, not with the uzb directly.
-
Ah ok, now it's clear! Thnx
-
Can I just say "do it"
I cannot believe how much better OpenLuup / z-way is than Vera. OK it's a learning curve. But it's rock solid. Fast and so much better in every way
C
-
@rafale77 said in Why Migrate to Z-way from vera and how?:
You can make the reactor device IDs the same by manipulating them the same way you would on a vera (it is an attribute). What will be different will be the device IDs of the zwave devices.... When moving to openLuup, the zwave devices will be come bridged and will have an added “prefix” of 10 sending them in the 10000+ range.
You could alternatively try to add z-way as a secondary controller first which would make the same zwave device show up twice on openLuup: one through the vera path and the other through the z-way path.
I have openLuup connected via VeraBridge to 3 x veras. The vera that has just gone to orange light hell has its devices in the 30000 range on openLuup. If I have any success copying vera on to uzb is it possible to keep those device numbers via Z-way Bridge in openLuup? My Reactors are all on openLuup already so would be mighty useful.