Migration advice....

[Vinisz]

Ok, so, I tested this on an RPI with and UZB zwave controller and that all looked ok....
But, Now I want to migrate from Zwave.me (ZWAY) , to this....
Question is, what is the best way to do this and, even better, is there a "soft" way to do it (that would require node-red and zway to run in parralel, which seems not so be working cause both try to claim the controller)
I can of course just let the controller query and inventory, so no need to do anything on the "zwave" part (at least not on the devices) but I have over 150 zwave devices connected here, so it's not like I will be able to do it all in just couple of hours, it will take days, and functionality needs still to be there....

[marcus-j-davies]

Hey

Sadly,

There is a no way to 're-format' the devices database from one application to another.
Every application will have its own way for storing device data.

zwave-js stores its data in a different format to zwave.me - I don't think there is a way.
if the devices are mains powered, and in good range - it might not actually take that long.

As you said, you don't need to disconnect the devices from the controller itself, but the interviews still need to happen initially so, zwave-js knows about there abilities.

[marcus-j-davies]

This will still require the interview on the zwave-js side.
zwave-js (I think) will act as the primary controller.

@AlCalzone,
Whats your take on migrating 150 devices from one software solution (zwave.me) to zwave-js (node-red)
There is a spare USB controller at hand, that may help?

(and a spare PI)

[AlCalzone]

Z-Wave JS expects to be the primary controller, so "joining" it into an existing network won't be possible.
IMO it depends what causes less pain. Either exclude devices one by one and re-include them in Z-Wave JS. Or update all automations at once.

[marcus-j-davies]

I was just betting on just allow the interviews to do their thing, when the controller is attached to the 'new software'?

[Vinisz]

@marcus-j-davies , yes, if secondary controller is not possible this is the best... but... we can also turn it around of course, I can make zwave-js the primary controller and z-way the secondary... If that works, then commands (so normal "house" operations) can just go to the secondary and the "new" primary can be used to do all the interview stuff and after that, adjust my flows one-by-one in node-red (adjusting all those flows is where all the work is....)

[Vinisz]

Z-Wave JS expects to be the primary controller, so "joining" it into an existing network won't be possible. IMO it depends what causes less pain. Either exclude devices one by one and re-include them in Z-Wave JS. Or update all automations at once.

Excluding and including is a total nightmare.... I have been to that process once and will never, ever do it again.... Works with 10 devices maybe, but not with this amount

[marcus-j-davies]

If you do embark on this journey, you will have to keep us updated.
150 devices being interviewed (albeit in an orderly fashion) will certainly be of interest to us 😆

[AlCalzone]

FYI, 150 devices would be the largest network so far, but not by far. There's one in the 120-125 range already.

[Vinisz]

Just checked, it's 119 "real" z-wave devices actually, (some others are wifi/homekit based) and there's a view virtual ones... so that makes the +/- 150 in total... but 119 zwave only is already a lot I think...

[Vinisz]

And a spare Rpi ;-)

…

Op 14 okt. 2021 om 15:55 heeft Marcus Davies ***@***.***> het volgende geschreven:  This will still require the interview on the zwave-js side. zwave-js (I think) will act as the primary controller. @AlCalzone, Whats your take on migrating 150 devices from one software solution (zwave.me) to zwave-js (node-red) There is a spare USB controller at hand, that may help? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.