#Z Stick Gen 5 plus --> Zooz 800 Series?

1 messages · Page 1 of 1 (latest)

sharp ore
#

Is there a migration path from Z Stick Gen 5 plus to Zooz 800 Series?

#

If there is not, is there some way to remove all my zwave devices and add them back while retaining their HA name do i dont need to update dashboards and automations?

grizzled sapphire
#

Make sure the stick is on firmware 1.2.
Use Z-Wave JS UI.
NVM backup, switch to new stick, NVM restore

grizzled sapphire
#

Yeah looks like you're already good to go

sharp ore
#

amazing thanks!

grizzled sapphire
#

There's a small bug where Z-Wave JS UI displays the wrong name for the controller after migration.
If that bothers you, just restart.

sharp ore
#

thank you! i read this on the amazon listing and got real nervous :

grizzled sapphire
#

That refers to doing the backup with PC controller or other software. Those don't convert the NVM contents to the target format and will brick the stick

#

Z-Wave JS (ui) does.

sharp ore
#

ah bummer. backup is throwing errors. google didnt seem to have an answer. maybe youve seen this before?: 2024-12-10 11:32:41.635 INFO Z-WAVE: Controller status: Backup NVM progress: 16% 2024-12-10T16:32:42.713Z DRIVER unexpected response, discarding... 2024-12-10 11:32:46.220 INFO APP: GET /health/zwave 301 0.360 ms - 162 2024-12-10T16:32:52.718Z CNTRLR Turning RF on... 2024-12-10T16:32:52.725Z DRIVER unexpected response, discarding... 2024-12-10 11:32:52.730 INFO Z-WAVE: Timeout while waiting for a response from the controller (ZW0200) backupNVMRaw undefined

#

tried rebooting zwavejs but happened a second time as well

#

suspect i may just need to start from scratch when the new zooz 800 stick arrives.

#

do you know if there is a prefered method starting from scratch to try and keep the names./or reuse the names of the devices so i dont need to update automations or front end

grizzled sapphire
#

Need to look at driver logs on level debug. Those you shared don't tell the full story.

sharp ore
fallow briar
#

wrong logs

#

n/m, it's a mix

#

Fails earlier than that, around line 1953. Somehow it's logging a Meter report even while RF is off.

sharp ore
#

can this be linked to a problematic device that should be removed?

fallow briar
#

RF is turned off during NVM backup/restore

sharp ore
#

is there a manual method to turn off RF first then start the NVM backup?

fallow briar
#

it's all automated, you don't need to

sharp ore
#

doesnt it look like device 126 is the one still talking...should i just remove that?

#

its a long range 800 series device and the gen5 stick seems to disslike 800 LR devices

fallow briar
#

Node 15 also reports a meter value prior to RF being turned back on.

sharp ore
#

ok i will remove 126 try again. if that doesnt work. remove 15. and see from there

fallow briar
#

Sort of defeats the purpose of the process. Seems like a bug at least.

sharp ore
#

true. but remving two nodes is easier than perhaps waiting for a big fix

fallow briar
#

Yeah, hopefully other nodes don't decide to start talking.

#

You could also try turning of meter reporting temporarily.

sharp ore
#

oh on the device? ok yeah ill try that

#

i could also unplug it...right then it would not be sending data

fallow briar
#

actually seems to be notifications as well

#

I see Node 10 as well

grizzled sapphire
#

Is anything (automations, etc) sending commands during the NVM backup? That might explain the problem.

fallow briar
#

how can the nodes communicate with RF off though?

sharp ore
#

not sure. I will disable those and node-red

grizzled sapphire
#

or maybe the stick crashes and restarts

grizzled sapphire
fallow briar
#

there's no log to indicate it's doing that, at least

#

Oh, SetRFReceiveMode ?

grizzled sapphire
#

Eh, the NVM backup is being started in the middle of a failed transmission. I'm not 100% sure that edge case is handled

fallow briar
#

Yeah, interesting

grizzled sapphire
#

Ideally make sure there are some seconds of silence before starting the backup to avoid that.

fallow briar
#

Could proactively disable RF via driver code prior to backup?

grizzled sapphire
#

I have made some progress at making these command sequences more predictable, but it's not there yet

grizzled sapphire
#
await driver.controller.toggleRF(false);
#

Then wait a minute and watch the log for commands from and to nodes

#

if nothing happens, start the backup

fallow briar
#

from ZUI control panl,dotsvertical -> 🪄 -> Driver function -> Write

sharp ore
fallow briar
#

ZUI = Z-Wave JS UI

#

the 🪄 is literally above your circle

sharp ore
#

sorry i see that now

#
2024-12-10T18:30:37.997Z CNTRLR   Turning RF off...
2024-12-10 13:30:38.012 INFO Z-WAVE: Success zwave api call driverFunction undefined
2024-12-10 13:31:00.220 INFO APP: GET /health/zwave 301 0.443 ms - 162
2024-12-10 13:31:14.617 INFO Z-WAVE: Calling api backupNVMRaw with args: [ [length]: 0 ]
2024-12-10T18:31:14.619Z CNTRLR   Backing up NVM...
2024-12-10T18:31:14.622Z CNTRLR   Turning RF off...
2024-12-10T18:31:14.634Z CNTRLR   Stopping hardware watchdog...
2024-12-10 13:31:15.686 INFO Z-WAVE: Controller status: Backup NVM progress: 0%
2024-12-10T18:31:15.711Z DRIVER   unexpected response, discarding...

....

2024-12-10T18:31:28.014Z DRIVER   unexpected response, discarding...
2024-12-10 13:31:29.170 INFO Z-WAVE: Controller status: Backup NVM progress: 8%
2024-12-10T18:31:29.199Z DRIVER   unexpected response, discarding...
2024-12-10 13:31:30.284 INFO APP: GET /health/zwave 301 0.477 ms - 162
2024-12-10T18:31:30.467Z DRIVER   unexpected response, discarding...
2024-12-10T18:31:40.472Z CNTRLR   Turning RF on...
2024-12-10T18:31:40.480Z DRIVER   unexpected response, discarding...
2024-12-10 13:31:40.484 INFO Z-WAVE: Timeout while waiting for a response from the controller (ZW0200) backupNVMRaw undefined``` i think a device is still butting in
grizzled sapphire
#

ok share another driver log of trying that

#

(loglevel debug, so we see what's happening)

fallow briar
#

not seeing toggleRF in that last log?

sharp ore
fallow briar
#

Background RSSI is quite poor BTW. Are you using a USB extension cable?

sharp ore
#

yes im using a USB extension

#

should i not be?

fallow briar
#

you should be

sharp ore
#

ok perhaps I should replace it with a new one.

fallow briar
#

That would be an odd thing to fail. Background RSSI should ideally be < -90 dBm for a Z-Stick Gen5.

sharp ore
#

should i try plugging direct to port just for backup purposes?

sharp ore
#

ok no difference with stick plugged directly in to USB rather than through extension

grizzled sapphire
#

Do you have a Windows PC?

#

If so doing the backup in PC controller could help. I can verify if the backup file is okay

sharp ore
sharp ore
grizzled sapphire
#

Looks like Z-Wave JS parses this just fine, so you should be able to restore that on the new stick (with Z-Wave JS UI)

sharp ore
#

oh wow

#

so just here but selet the 'zwaveBackup.bin' file from my local computer?

grizzled sapphire
#

assuming you've plugged in the new stick, yes

sharp ore
grizzled sapphire
#

Just plug the new one in and configure Z-Wave JS to use that before starting the restore.

sharp ore
#

got it. so now that I am here, i would restore?

#

also seems i should update the firmware first

#

ok i think it all worked! thank you so much for your assitance.

#

should i heal or reinterview any of the network? any maintinace i should do now?

grizzled sapphire
gaunt oxide
#

What a coincidence...I'm about to do this exact migration.

sharp ore
grizzled sapphire
#

shouldn't be necessary

devout steppe
#

Watching closely as I have this same 500 aeotec to zooz 800LR task to complete in my pile.

#

I think Friday looks like. The green and black boxes on my desk here are haunting me.

gaunt oxide
sharp ore
#

I tested an NVM backup using the new 800 series stick and it worked, fast, no issues

devout steppe
#

I booted windows, after 3 restarts for updated and a failed installation of something... Windows is annoying. I'm about to try the backup thingie. (After is loads the .net crap...)

sharp ore
#

sorry i had a working windows box ready to go

devout steppe
#

Just venting. This is the other nvme on my main laptop. The one I deleted everything I could from and ignored until tax time when I needed it to run tax software.
Nice. Couldn't update BC being used. Awesome...

#

It's probably disccord...

devout steppe
#

Windows updates done so the .,net could load, and backup done. Did I mention I hate windows? This is a 12th gen I9 and an nvme, no slouch and still hours to get windows running again after sitting a couple of months.

devout steppe
#

So I am currently booted and running zwave on my 500 stick. I have the backup file. What do I do next?
I tried a bunch of stuff played for a couple of hours and got nowhere.
Zwavejs is still installed, and HA tries and is successful in finding it and getting that running. zwavejsui doesn't find it.
Normally right noiw ui is running and is populated.
Guessing just delete the old one as I don't need it.

#

Anyway I restored the addons and stuck the 500 back in and it just ran again, how to continue here.

fallow briar
#

You should only ever have one of the add-ons installed, and to perform an NVM restore you need Z-Wave JS UI. Also, no reason to use Windows unless you had run into the above problem reading the NVM.

devout steppe
#

I had the same stick, so I got the backup.

#

Are the next steps written somewhere? Like if I pull the old stick, plug the new stick, go into integrations and change path so it sees it, go into the ui addon. load restore?

#

My problem is It was auto connecting using the old add-on, now that's gone, I know the serial string if I need it, the web socket should be the same.

fallow briar
#

The integration doesn't have any settings to change. Everything is in ZUI. Yes, you just swap the device path in the add-on and restore the NVM.

#

You can disable the integration for the time if you want to avoid connection failures

devout steppe
#

I looked and looks half dozen times, just found that. I thought it had to be somewhere... OK. Thanks.