Purchased mine a few days ago and it arrived last night. Tried to set it up but I’m using LinknLink iSG Max and it is not recognized. Speaking with LinknLink support, they would need to provide a driver. I thought the driver would be in wave js ui.
Anyone else running iSG with the new ZWA-2?
I ordered one last week. Plan on using it with my Zooz 800 USB controller.
If it works as designed it will make flipping from one Proxmox node to another simpler. No need to move the USB plug. Yes, I seem to be lazy. LOL.
No, really, I can bring it all back up remotely in case of a server failure. I already have a POE Zigbee controller.
Whats the best way to reset the old stick? Is that been done by the migration tool? Or will it start sending out the network again on power on?
Not exactly true.
Most Z-WAVE dongles allow NVMe Backups to be made, even 500 series on later firmware (if available) Do an NVMe backup of your stick. Restore this backup to the ZWA-2. Done. Z-WAVE does not use a software store of nodes. All nodes are stored on NVMe on the stick. You do not need to exclude and reinclude, providing your old stick can up grade firmware (if 500 series), or migrating from a newer series stick. Worst case, you may need to rename your home assistant entities, though often HA will pick them up.
Doing it this way also allows a backup controller to be available, as your old controller still retains your Z-Wave network as of the time it was unplugged. To go back to it, you just plug it back in and the nodes will all be there. Again, HA Entities may need to be renamed, but all the nodes would be present on the stick.
This is how I have maintained a backup controller for my 25 Z-Wave devices for a few years now.
Of course, if using newer devices and wanting to migrate from mesh to long range, this won’t work. to migrate from mesh to long range will require excluding from the mesh and re-include as a long range device. Same is true if your current Z-Wave controller is an older than 500 series device. The 200,300,400 do not support a migration of NVM to 800 series. This is why no migration is not exactly true, there is migration in some (maybe a lot) of cases. It is just not a simple point and click inside a single UI. It may be a few steps to do it, depending how the current hub does the backup of the current controller.
Now, even the best made migration can have failure. I have not yet experienced it with backing up of the NVM, but you may do. If you get a “dead node” you can factory reset it without the original controller. Just follow the instructions that came with the device to hardware factory reset it, and in Home Assistant, Z-Wave JS has a pretty reliable mechanism for removing dead nodes. I have used this with genuine dead nodes before.
@brendan Did you see that my reply was in answer to a question with a specific scenario in which he did not have a Z-Wave dongle but asking Z-Wave device about migrations from a propriatory Z-Wave smart hub appliance from Fibaro. So question I answered was if there is a straightforward migration path to migrate Z-Wave devices from the commercial ”Fibaro Home Center Lite” appilance to the ZWA-2 and Z-Wave JS without having to exclude and re-include each device manually. Anyway, I am pretty sure that Fibaro hubs use vendor lock-in on purpose so even if they have backups then it will probably be in a propriatary format that can only be restored to other compatible Fibaro hubs.
I haven’t got experience directly with Fibaro, I admit that.
Some hub/appliance do have a backup option, but you are 100% correct and now you mention it I have heard this complaint from ex Fibaro home centre users before.
I think that might be why I never tried it, because of the limitations as I do rely on using z- wave for some of my aquarium automations
Petro, was this an Aeotec gen 5+ usb stick you are talking about? If there truly is a simple upgrade path, without having to rebuild the network from scratch, this is something I’d be very interested in. Did you lose anything, like custom renamed entities. I know many people don’t rename things, but I rename everything for consistency.
Network migration preserves everything. At this point the process is thoroughly documented (and discussed here in various posts).
Generic instructions:
ZWA-2 specific (process is the same):
A Gen5+ (not plain Gen5) should already have the required v1.2 firmware, but if not upgrading the firmware is the hardest (and riskiest) part of the migration. Some tips were reported for that at Tips wanted for upgrading an Aeotec Gen5 ZW090-C stick - #10 by mty17.
@GrizzlyAK
Update the firmware to latest firmware. Backup the NVMe then you can import it to the new 800 series devices. You have to update to latest firmware though
I actually moved from a Aeotec gen5 to a gen5+ to the ZWA-2. I had to do this because there was no way to go from the gen5 straight to the ZWA-2. I had a spare 5+ hanging around which was just dumb luck.
Upgrading the firmware on the 5+ did take a few attempts and has to be done through Aeotec’s service on their website. Once you do that and get your get 5+ from firmware 1.1 to 1.2, it can be done through Zwave JS UI. And just for clarification, 1.01 and 1.02 firmwares for aeotec are equivalent to 1.1 and 1.2. Depending on which site/guide you use, they all use different terminology.
It took 5 minutes and held all customization in Zwave JS and HA.
This is great news. My Gen 5+ is at FW v1.2 and SDK: V6.81.6. Is there a fallback path in case things don’t work out to recover previous state? Or maybe it would be a chance to upgrade my Pi4/SD card to one of the HA products. Is there an easy path to that migration with the new controller?
Are you seeing better ranges on your existing short range devices across floors with the new ZWA-2?
Thanks @freshcoast for all the links! Thanks @brendan!
I went from gen5 (not plus) to zwa-2
No issues experienced
Interesting, I couldn’t get the gen5 to upgrade to 1.2 firmware using their utility.
I purchased the ZWA2 shortly after its release, but only got to install it tonight as I was out of the country.
The upgrade from the Zooz ZST39 was painless - just an NVM backup and restore in Z-Wave JS UI.
I also updated the firmware to the latest version 1.1
I have a 130 node network. 91 of them are Zooz ZEN76 800LR switches, setup in LR mode.
Most of the nodes came up green when the add-on started. But there was an exception - one of the most distant ZEN76 LR switches, several floors away, and in the back of the house, showed up as red, ie. as a dead node. I manually clicked “ping” in ZUI and it failed until the 3rd try.
I restarted ZUI, and a different switch in the same room showed up as dead. Similarly, I was able to revive it after a couple of manual pings.
This is not brand new behavior. I have seen this type of problem with the ZST39 before, usually with more than one node.
I was really looking forward to “Z-wave is not dead”, but I think I still need to find a better location for the ZWA2. My ZST39 was a bit higher up on a wall, about 5ft high. The ZWA2 is not designed to be wall-mounted, and I had to set it up lower, on an A/V shelf. about 3ft high. There is a tall bookshelf in the back of the room, which could provide a better flat spot. I would need a much longer USB extension cable to reach it, though, at least 25ft.
My tip is to use a super long USB extension cable by bying inexpensive dumb “USB to RJ45” converter-adapters to reuse a Ethernet cable, so see details and link in earlier reply in this thread here:
I believe recommendation is to Re-pair LR devices after install zwa-2
In your set-up with ZWA-2, Zigbee and Matter:
Do you run your 2 Matter devices as Matter-over-Thread directly via MR1U or Matter-over-Wi-Fi?
That’s a great question and one I that I hadn’t thought about when I made that post. 
The devices are in fact using WiFi at this time, as they’re through the Aqara hub 2. So it’s also the hub that is Matter and the devices are BT/Zigbee (door locks) - though they’re listed in HA as “Matter”
So at this time all my (10) Thread devices are actually border routers. The MR1U, multiple HomePods mini, 3 eero access points, and AppleTV.
Is this documented somewhere ?