Two OpenZWave installations in HA Core?

Hi.
Is it possible to have two OpenZWave integrations in HA Core?
My scenario is this:
I have an “old” ZWave-integration, servicing 100+ devices, all kinds of stuff.
In addition to that, I have a ZWave2mqtt with 6 devices, sensors and switches.
2 different Aeotec zwave adapters, of course.
I’d like to replace zwave2mqtt with OpenZWave for a start (testing it by stopping zwave2mqtt, and then starting openzwave).
If that’s a success, I’ll migrate the rest. But it’s a huge amount of work moving all the devices to a single controller.
(Moving my main zwave to openzwave is quite risky, WAF-wise, so that’s not an option at the moment).
Any advice?

Helge
HA Core 0.113.1, Intel NUC, Debian

I’ve used the new OZW over mqtt integration alongside the old zwave integration (both using different controllers) with no (or minor issues).

the only thing was that there were some errors in the logs - that I can’t remember what they said - but I don’t remember them causing any issues. both worked fine together.

you can try it and see and in the unlikely event that it causes problems you can easily remove it.

I guess I’m not very good at explaining…
My “problem” is that I have two zwave installations that I want to replace with two openzwave installations. I would like both of my zwave installations to be controlled by separate openzwave installations on my NUC. I guess it can be managed with the help of a separate RPi, but I was hoping that I could do without that.

Yes, you can have more than one instance. You run two separate containers and set the OZW_INSTANCE environment variable on one of them so it isn’t 1.

Sounds simple…
How do I run openzwave in two separate containers?
Have you (or anyone) actually tried this?
I need to do this in a slow and safe way.

Just follow the instructions for one container, and create a second one with a different OZW_INSTANCE value. Config files for each container should go in their own directories. I have run two separate instances on different hosts before, and HA has no problem seeing both. Running on the same host should be no different, as long as each has access to the MQTT broker.

Ok. That seems like something I can do! I´ll give it a try.
What’ll happen to my existing devices in the “old” ha zwave?
Will the names be migrated? Setting 116 names and/or editing NodeRED flows is a lot of work.