#Migrating from Yellow w/ plug in Zooz controller to x86 w/ USB Z-station

1 messages · Page 1 of 1 (latest)

unreal blaze
#

Migrating from Yellow with Zooz Z-wave controller to x86 with Z-station. Zigbee migrated but Z-Wave is failing. The driver won't start. I get

version 15.3.1
2025-05-12T20:54:50.518Z DRIVER   
2025-05-12T20:54:50.518Z DRIVER   starting driver...
2025-05-12T20:54:50.518Z DRIVER   opening serial port /dev/ttyAMA0
2025-05-12T20:54:59.538Z DRIVER   Failed to open the serial port: Error: No such file or directory, cannot open 
                                  /dev/ttyAMA0
2025-05-12T20:54:59.539Z DRIVER   destroying driver instance...
2025-05-12T20:54:59.540Z DRIVER   driver instance destroyed
sterile thorn
#

/dev/ttyAMA0 is the GPIO, not any USB port.

unreal blaze
#

Hmmm I select this in config so why does the system try to use an I/O... it seems to be stuck on the Zooz plug in board

image.png
#

From the Yellow

sterile thorn
#

is the Zooz the GPIO board?

#

ZAC93

unreal blaze
#

yes

sterile thorn
#

Did you remove it?

unreal blaze
#

Its in the old box .... I having the issue on the X86 with the Z-Station

sterile thorn
#

How exactly are you migrating? Whatever has been done, the config is not applying.

unreal blaze
#

I did a system backup and restore

sterile thorn
#

A migration would need to include an NVM backup and restore, if you are choosing to preserve the network, and then re-configuring the add-on with the new path.

unreal blaze
#

I have the NVM backup but can't apply it because the driver won't start

sterile thorn
#

Well then configure the correct path.

unreal blaze
#

How where?

sterile thorn
#

In the add-on.

unreal blaze
#

Do I need load up the ZW JS addon ? I'm using ZWJS UI?

sterile thorn
#

You can only use one add-on per-controller.

jagged oyster
#

Don't use /dev/tty* but /dev/serial/by-id/...paths if possible.
What does ls -l /dev/serial/by-id/ via terminal say?

sterile thorn
#

So go to the ZUI settings if that's the one in use.

#

The add-on's settings auto-populate the by-id paths.

#

Just click on the pull down menu and choose the correct one.

unreal blaze
#

Wehre do i find that?

sterile thorn
#

In the ZUI settings

unreal blaze
#

OK ... they are coming to life .... waiting on the battery devices... Thanks

#

My HA device Ids are all fvcked up now

sterile thorn
#

I think there's a bug in HA that resets them.

unreal blaze
#

Nice ...

sterile thorn
#

A backup would fix it.

#

Probably next release of HA supports it.

unreal blaze
#

OK .. I was about to try that, Should I skip restoring JS UI?

sterile thorn
#

Yeah, just HA core backup. Sorry, forgot about the bug. The workaround is to disable the integration during the migration.

unreal blaze
#

Also weird ... none the active controls like switches are present in HA UI. Is that also part of the bug?

sterile thorn
#

no

unreal blaze
#

So what's that due to?

sterile thorn
#

Dunno

unreal blaze
#

Restore brought back controls but some don't work ???

unreal blaze
#

Migrate doesn't really work that well some of Z-wave devices migrated without intervention, some needed to be re-interviewed. Some of my Zigbee devices migrated, some needed to be repaired. Battery or line powered didn't seem to matter. All of my old (10 years old) GE and Enbrighten Z-Wave switches worked. Of course, I had to activate battery devices to check that they worked

sterile thorn
#

Sounds like some kind of hiccup in your specific migration

#

generally re-interviews are not necessary as that information is cached

unreal blaze
#

Maybe, it was pretty rough. But the fact that the controllers found all the EPs and some worked and some didn't argues against that. I'm not going to try it again anytime soon 🤣 I think everything is working and the N100 is noticebly peppy compared to the yellow and both Z-Wave and Zigbee have nice antennas on the end of USB cable on the hockey puck is nice. The Z-Station is sweet. I tested it long time before migrating. Looks better than USB dongles hanging off the device too.