ZWA-2 Migration Help

[echo tide]

My old adapter is really old, and I was getting more and more LR devices, I thought it was time to upgrade. I actually bought a different adapter the day before the new ZWA-2 announcement, but I still had time to cancel and get the ZWA-2 instead 🙂

Anyway, I have a AEOTEC Z-Stick Gen5 that I purchased in early 2017. The documentation mentions I should update the firmware, but that article says it won't work on stick made before 2018...

So I just skipped to the normal migration instructions, but it didn't seem to work...

There were no error, but I just have no other devices other than the ZWA-2:

[jovial edge]

The migration did not happen. There is a known bug in the current Z-Wave JS UI addon which causes the error not to be shown. I wasn't able to push the fix due to some build issues I don't understand.

Without updating the firmware, you won't be able to migrate. I think @devout surge had a trick up his sleeve with first migrating to a newer Z-Stick 5, which could be updated.

[echo tide]

Hmm... that's unfortunate. I have 60+ devices

and I don't really want to buy another stick just to migrate

[devout surge]

That’s exactly what I did

I migrated from the pre 2018 stick to a post 2018 stick and was able to migrate

The choice was that or spend hours reincluding devices to a new network

[echo tide]

is there any hope for a different solution? It feels dishonest, but could always order one from Amazon and return it after the migration...

Do they even sell any Gen5's anymore?

[devout surge]

I don’t know

[jovial edge]

I think they still do

[devout surge]

I got lucky, I had a spare in my office

[echo tide]

They don't sell it on Amazon anymore 🙁

not that I'm seeing (in the US)

[devout surge]

I bet you could do it to a new aeotec

Like, I don’t see how they wouldn’t support their old sticks to their new sticks

[echo tide]

when you say, "The migration did not happen," which part? The export or the import? I'm assuming it's an import issue? The old format is just not compatible...? or what's the issue?

[jovial edge]

500 series, 700 series and 800 series all have different memory layouts. In fact there are difference between SDK versions on all of them.

700 and 800 series are (mostly) forwards compatible, but 500 series is completely different. I have reverse-engineered the format until SDK 6.61 with the help of some documentation I should not have. I don't have anything on older versions though.

So what happens in your case is that Z-Wave JS reads the NVM of your target controller, realizes that is 800 series, and then nopes out because it doesn't know how to convert pre 6.61 to that format.

[echo tide]

I see

well, I could order a 700 series to arrive later today, so we'll see if that works...

[jovial edge]

Won't help

Z-Wave JS does not understand what's in the memory of your old controller.
And there is no other migration solution for moving from 500 to a later series, other than the trick with virtual nodes mentioned here: https://github.com/zwave-js/zwave-js-ui/issues/3828#issuecomment-2253070450

...which might actually be your best option - if you have access to a Windows PC

[echo tide]

not sure I fully follow. using this tool? https://aeotec.freshdesk.com/support/solutions/articles/6000108806-z-stick-gen5-backup-software

[jovial edge]

No, Z-Wave PC Controller. You "only" have to install a bloated 5 GB or so software package to get access:
https://community.silabs.com/s/question/0D58Y0000884He4SAE/where-can-i-download-zwave-pc-controller-for-zstick-gen5-?language=en_US

[inner hamlet]

You can "cheat" and get PC Controller from HomeSeer. https://docs.homeseer.com/products/smartstick-firmware-updates

[echo tide]

so an export from one of those should work...?

[inner hamlet]

No, you need to follow the guide linked, it's a tedious process.

[echo tide]

what guide linked? I am not following at all, I'm sorry. What's the goal here... update firmware?

[inner hamlet]

#1407077596696412210 message

[echo tide]

this guide? https://community.hubitat.com/t/guide-nortek-husbzb-1-nvm-backup-restore-and-updating-z-wave-firmware/48012

[inner hamlet]

Nope, the youtube video.

Which seems to be private now.

https://www.youtube.com/watch?v=71w0OLO6zxY

Oh no, that's not it

He took down the video

That one might be the same process, not sure.

[jovial edge]

Oh no the one linked there is for another stick

I was referring to that video 🥲

[echo tide]

this one? https://www.youtube.com/watch?v=71w0OLO6zxY or the one in the GitHub comment you linked (which has been removed)?

Here's a guide from a couple weeks ago that I think is relevant: https://community.home-assistant.io/t/how-to-best-migrate-from-aeotec-gen-5-to-aeotec-z-stick-7/637311/18

digging in to this

[inner hamlet]

Notice the first step is "Update Zwave Gen5 1.0 to 1.2(1.02) version - Aug 2025".

[echo tide]

yeah... I am seeing this. that won't work for my very old version of the Gen5 stick, right?

[inner hamlet]

Well, I've heard some say they were successful in upgrading. Either you try and it succeeds, it fails w/o breaking anything, or it kills the stick.

[echo tide]

the comment before that has the same de-listed video 🙁

[inner hamlet]

Unfortunately the post right above that one referred to the now private video.

[echo tide]

yeah, haha

[inner hamlet]

I'm not familiar with that other video. He has two controllers running using PC Controller. It might be the standard "controller shift" method, which leaves your new controller node as something besides node ID 1, which is probably why he goes through re-associating everything.

[echo tide]

Ok, it took a couple tries, but updating the firmware did work, and so then starting the migration over, it worked! I just controlled my office lights via Home Assistant using the ZWA-2

[inner hamlet]

"before 2018" seems to be kind of a guess on their part

[echo tide]

that's from the Aeotec support docs... lol

you think if anyone would know, they would

Do I need to re-pair LR devices to get them to use LR? I tried re-interviewing a device I know has (or at least should have) LR, but it still doesn't show as having LR support (I am also rebuilding routes, so maybe it's just queued)

[inner hamlet]

yes

but consider if those nodes are acting as repeaters before switching them

[kindred lintel]

I migrated an Aeotec Gen5 running 1.2 (I did not flash it recently) to ZWA-2 today. The migration didn’t throw any issues. However, when Zwave-JS starts it says that it can’t ping 3/4 of my 93 nodes. Tried rebuilding routes, but that also fails because it tries to ping the node first and fails. I did install the ZWA-2 update, FWIW. Core 2025.8.2, ZWave-JS 0.21.0.

[kindred lintel]

Issue resolved: turns out Z-Wave JS Radio Frequency Region defaults to EU. I’m in the USA, so that doesn’t work. Once I changed the region from “Automatic” to “USA (Long Range)” and restarted Z-Wave JS everything came back.

Comparing the Z-Wave JS logs at startup between my Aeotec Gen5 and the ZWA-2 they both indicate that they’re defaulting to EU frequency region. My assumption is since my Aeotec Gen5 only supports the USA region it didn’t matter what region Z-Wave JS thought it was using. With the ZWA-2, of course, this matters.

I don’t know how the region is determined on the “Automatic” setting but there appears to be room for improvement here.

[inner hamlet]

It's selected from your HA's configured location

https://github.com/home-assistant/addons/blob/master/zwave_js/DOCS.md#option-rf_region-optional

[jovial edge]

This works for me. Did you set your location/country correctly?

[kindred lintel]

When I started using HA years ago I don’t think this was configureable in the UI. I’d set some things such as name, elevation, and timezone in configuration.yaml. When I checked Settings -> General moments ago, Country was unset. Apparently never mattered until now, but that explains why Automatic region setting didn’t work. Thank you both — AlCalzone & freshcoast — for the assist.

[jovial edge]

Thanks for flagging. We'll see how to improve this

[echo tide]

I can confirm: my country was unset, but I tried to change something else in settings and it said I was missing required field: RF Region. So definitely a legacy issue.

@kindred lintel you said you had an option to set your regision to "USA (Long Range)"? Was there a separate "Long Range" entry? I don't see one.

[kindred lintel]

Yes. I'm using the Z-Wave JS Add-on and in its configuration tab I have this.

[echo tide]

interesting

[inner hamlet]

The core add-on defaults to automatic and sets the region for you. ZUI doesn't have that kind of capability, thus requires a manual setting.

Also ZUI auto sets LR

You just pick EU or US

sorry, in both addons that's the same

[echo tide]

yeah. I've been using Z-Wave JS UI for so long, I forget there's something different... the naming still confuses me, haha. I had it running in its own container forever, but moved it to an Add-on a couple years ago

[inner hamlet]

Not sure why the core-addon needs to expose the LR frequencies anymore, maybe they just missed it.

[jovial edge]

Good point, that's most likely an oversight

[raw valley]

I was thinking of moving my current stick to be managed by Z-Wave JS (official) and then set up my new 800 controller on Z-Wave JS UI so I could migrate devices one by one. Is this a bad idea?

The idea of having things be completely broken until I reset each device and re-add everything in its entirety is daunting

[inner hamlet]

That's a valid approach

Others have done that in the past.

As long as you are using only entity IDs in anything like automations, then the switchover won't even impact anything. If you use device IDs or node IDs you'll need to reconfigure those.

[raw valley]

I'm going to get foiled by stupid stuff though. How the heck do you put the default js integration into exclude mode lol

[inner hamlet]

"Remove device" from the integration configuration page.

Which controller do you have?

[raw valley]

I see it.

I have the ancient Nortek HUSBZB-1 still

Moving to the ZWA-2

I actually bought a Zooz 800 stick last year sometime and went through the fake node migration thing but it got all messed up and the stick itself was no longer id 1 lol

Ended up getting sidetracked and never migrated.

[inner hamlet]

Yeah, I wouldn't be able to stand that.

[raw valley]

Yeah I was Not Okay with it

Haha

OCD runs strong

So I'll just do it the suffering way but being able to do a few at a time without breaking the house would be awesome

[ember granite]

I hope you don't mind me jumping in on this post 🙂
I try to migrate from Zstick 7 and all I see after migration is everything to be unknown.
Does anyone have any advice what I did wrong or how to fix that? Luckily I could just plug the zstick back in and have everything running again.
Really like to get the ZWA-2 in production asap 😄

[ember granite]

OK, nevermind. I fixed it. Hint for everybody reading this: Update your zstick firmware beforehand! 7.11 is not working.

[jovial edge]

Any chance you still have the backup from 7.11? It should work. If not, I may need to look into that.

[ember granite]

Yes 🙂 I have it

[jovial edge]

Cool. Can you send it to me?

[jovial edge]

I don't seem to have issues migrating, but obviously I can't test without your devices.
Where are you located? US? Europe?

Can you also send me the NVM backup from the Z-Stick after the firmware update?

[ember granite]

Located in Europe. Sending you the nvm 🙂

[mild drift]

I am still using a Schlage z-wave lock from 2017. It is the only device setup with a Samsung hub. It was not added to HA because I no longer have the inclusion info. Will the smart feature allow this to now be added to ha?

[devout surge]

its unlikely. You'd need to have the QR code supplied by the manufacturer and that device was created before they were using QR codes

[jovial edge]

Typically there should be something on or IN the device (battery case usually)

2017 might mean it's S0 only in which case you don't need a PIN or QR code to join though

[raw valley]

@mild drift If it's the Schlage Connect it's S0 only. I am still using it as well.

This many years later I still feel like it's the best lock option 🙂

[fair bronze]

i just finished the job : aeotec gen5 upgrade to 1.2 (from 1.1 refusing to upgrade). then migrate to zwa2. WITHOUT restore to intermediate newer key.
Here is my explaination : https://discord.com/channels/330944238910963714/1409987708717105285

[buoyant isle]

I have a Nortek HUSBZB-1, is the path still: Assume it's old firmware, back it up, upgrade the firmware (https://community.hubitat.com/t/guide-nortek-husbzb-1-nvm-backup-restore-and-updating-z-wave-firmware/48012), and then follow the normal migration steps here: https://support.nabucasa.com/hc/en-us/articles/29529265751965-Migrating-an-existing-Z-Wave-network-to-Home-Assistant-Connect-ZWA-2 ?

(Should I try just migrating following the normal steps first on the off chance that it just works? The HUSBZB-1 was not my first z-wave controller, needed pieces may already be in place)

[inner hamlet]

Linked on that page is a dedicated support article for that controller. https://support.nabucasa.com/hc/en-us/articles/29688968436765-Migrating-from-a-Nortek-HUSBZB-1-adapter-to-Home-Assistant-Connect-ZWA-2

No, it won't migrate w/o the firmware upgrade.

Unless you have a unicorn that has a SDK version >=6.61

[buoyant isle]

Ooops, I meant that to be the link for the 'normal migration steps here'. Okay. I'll give it a try. Having to re-do my entire network would suck, but maybe a "nuke the site from orbit" approach is what's needed. This installation has been going for a long time and who knows how much migration cruft is there.

[inner hamlet]

If you're adapt at soldering the f/w upgrade might be the way to go. If it fails, well you start over anyways, not much loss (except for a bricked controller).

Another option is to run two networks at the same time and slowly migrate one device at a time.

[buoyant isle]

Hmmm... That involves putting the devices in pairing mode though, right (IE - running around and flipping switches)

[inner hamlet]

that's what starting over is

exclude or factory reset every device, re-include on the new controller

[buoyant isle]

Seems like pretty much the same amount of work either way 🙂

I'll try the upgrade path first - I'm fine with the hardware side of the firmware flashing. Getting all the software bits is there I get a bit hazy. I guess I have to download the SDK from within Simplicity Studio now rather than as a standalone download?

[inner hamlet]

If you're decent a soldering that would be much easier, depending on the number of nodes you have.

No, don't need simplicity studio, that's for 700/800

https://www.silabs.com/software-and-tools/z-wave-500-series?tab=download

[buoyant isle]

Ohh.... I followed the wrong links

[inner hamlet]

You do need to create an SiLabs account and accept their EULA.

Eh, SiLabs changes things arounde

[buoyant isle]

No wonder it wasnt making sense! 🙂

[inner hamlet]

Back when the post was written the links were working

[buoyant isle]

And now, I am in driver hell 🙂

Working through this page - https://community.hubitat.com/t/nortec-husbzb-usb-stick-windows-drivers/6902/3

[buoyant isle]

I am currently unable to get a working driver installed for the HUSBZB-1. I've tried 4 or 5 different downloads (including the one in the Axial server) and (I think) scrubbed them out properly. I disabled driver integrity checks. When I plug the stick in, I get two HUB devices (zigBee and zwave) with the little exclamation mark. No matter what method I try, I get "No drivers were found" (IE - running the install_x64.exe, pointing to the disk, selecting Silicon Labs in select from list). What key step am I missing?

[buoyant isle]

To answer myself - Do not try to install the device as a Silicon Labs device - you need to drill down and install it from "Ports (COM & LPT)" and select the "Silicon Labs" entry under that.

[buoyant isle]

Urr.... In looking at the flashing docs, the author is shorting out pin 15 (or TP28) to the USB Shield... That's not grounded?

[buoyant isle]

Woohoo! Firmware upgrade complete. That was a bit of a journey. Still (so far) easier than re-pairing everything though.

[buoyant isle]

And after all that, the migration was easy peasy. Except for the part where they say to unplug the HUSBZB stick so it doesnt interfere.. Except that it's also my Zigbee controller, so I can't unplug it.

Thanks a ton for the help, @inner hamlet !

[inner hamlet]

I would do a hard reset on the Nortek for the Z-Wave part

The old controller will interfere with the new one if they are the same network

Or, upgrade your Zigbee too 😆