The only thing I can figure out from that tip is that it allows one to manually Exclude a device from one controller and Include to the other controller one-by-one in a slow roll fashion.
As long as they are using different Z-Wave add-ons. ie: one add-on cannot operate with two controllers and you can’t run 2 instances of the same add-on.
right, but you still have two separate ZWave networks.
almost ready for the procedure…
what makes me insecure in the Aeotec documentation, is whether that firmware update overwrites the existing network configuration?
1 download drivers
2 install drivers
3 perform update
seems obvious, but the Warning paragraph above all that mentions
- If you are firmware updating, please make sure that you create a backup using the backup tool we have so that you can restore it to a new Z-Stick
Ideally I shouldn’t need this should I…?
I am updating the Aeotec gen 5 stick before I migrate to the new ZWA-2, so not to any other stick like the warning states.
I need help… Badly.
Ive done all of the options in the Aeotec documentation, and still cant update.
My new Windows box (admin, so all authority) did even confirm the successful installation of the drivers (both 1st and 3d install method)
However, the executable to update the firmware keeps erroring on the button not being pushed / released, which is indication the drivers are Not installed correctly after all.
Now how to proceed?
I had the same thing. From memory it is because the existing firmware on the Aeotec stick is too old. There is no solution for it.
o dear, that doesnt sound good… So that means we need to manually build the mesh on the new Zwa-2 then?
my hopes were up watching this vid https://www.youtube.com/watch?v=YB6cgW7bVts where he has the exact same firmware to start with
Did you have any luck? My Gen 5 is only on firmware version 1.0 and I’m pretty sure it’s pre-2018 so I wasn’t able to update it.
no not yet.
I still need to try the final if anything else fails method…
what scares me there, is that a factory reset is mentioned, but no method to do so.
And after that we should try updating again. But, why would that work, if it is reset to the same version I now have…? seems moot if you ask me.
I do have the backup of the current stick made with the Aeotec software (so not the built in HA method)
It is silly we cant see which hardware version we have… all the guessing. I mean, my stick was bought after 2018 for sure, but I cant remember exactly, so that isnt going to help
If all fails, I suppose I have to add each device manually.
tbh, I would hope to be able to do so with both the Aeotec and the new ZW-2 alongside each other, so I wont be left with 60+ unavailable but essential devices for some time…
I think it’s possible to run one z-wave radio on Z-Wave JS and the other on Z-Wave JS UI which could be a way to slowly migrate devices across but it means changing your Z-Wave Integration from what you are currently running to the other option.
…or maybe that was possible with Zigbee (ZHA & Zigbee2MQTT) rather that Z-Wave, I would need to confirm.
Afaik the OTBR add-on knows the topology. In my case HA joined the Nest thread network from Google after I added the devices and still shows it. Now that protocols have gotten their separate place in the system menu it feels even weirder HA does not enable and use the rest api in the add-on to retrieve and show the topology. It should not matter (or should I say thread 
) who provides the info.
I think you are confusing Z-Wave and Thread. Z-Wave has nothing to do with Thread or the use of OTBR.
Ah, not confused, just switched what I wanted to say mid sentence and did not remove all of it. From what I understand with zigbee the software owns the toplogy, for z-wave the adapter owns the topology but HA still shows it. For Bluetooth there isn’t one but the bluetooth integration shows it that way. The graph is just a tool, but it has its uses to be valuable in HA.
well I tried it all, and indeed was able to update the stick to use the latest drivers. Unfortunately not to update its firmware.
Turns out I dont have the + stick.
Its not at all simple to run both zwave servers and migrate the existing zwave js to zwave js ui.
Mayby I can fireup one of my dust gathering RPi’s and connect the aeotec to that, running zwave js.
And install the new ZWA2 on the host and 1 by 1 migrate the devices.
No idea if the total kWh’s will be correctly written like that.
otherwise I will just have to forget about history, and start from scratch (have to reset the Aeotec stick for that, because devices are all on that still of course)
Or, keep using the Aeotec, and use the ZWA2 for something else…
its a real set back we can not use the backup for the new install, seems almost unbelievable’there is not some kind of tool to update only the .bin file
If you can find a + online, you can use aeotec’s utility to update that with your network, then migrate from there. That’s what I did with my non+ stick.
You mean buy a new intermediary stick?
So backup current old stick, setup new stick and write that backup to it, and next migrate that new stick to the new Zwa-2?
Found one 
Yep, probably a waste of money but I luckily had a spare lying around. I’d ship it to you but I’m pretty sure it’s a different frequency from the EU
Well, sometimes we waste money to use the latest …
Let’s just hope it works, and works better….
I’ll have a spare if something goes awol
Yep, that’s what I use mine for. I used it to do the migration from the old stick whch had 1.0 firmware. I used their “Help me migrate page” to move to the stick with the 1.1 firmware. I fumbled a bunch and had to redo this process a few times (The old stick will still work, so no problems there). Once I got it working on the 1.2 firmware stick, everything was upgradeable through HA/ZwaveJSUI
That’s what has me worried. Use the backup tool to write the current (old firmware) .bin file to the new stick as is. I hope the new stick has latest firmware.
Its hardware has in fact changed so maybe that is prerequisite enough for the migration to succeed
I’ve been playing with Aeotec tools so much now , the migration shouldn’t take longer than 3 minutes now.
Compared to manually excluding here and re-including there for over 70 devices, the investment for the new stick seems defendable (forget to mention I also had to buy a Windows box for it…)
Thanks for saving me 2 extra days of trouble…