SkyConnect needs to migrate after each reboot (after migrating from HUSBZB-1)

[Jasper8472]

I have migrated my ZHA network from a HUSBZB-1 to a SkyConnect. I’m still using the HUSBZB-1 because I have a few Z-Wave devices.

I have used this guide: Home Assistant SkyConnect
Because I still needed the Z-Wave part of the HUSBZB-1 I did not do step 5, remove the device.

All was well and Home Assistant told me my Zigbee network was now controlled through the SkyConnect according to the ZHA integration.

It works fine. As long as I do not reboot. When I reboot the ZHA integration keeps trying to initialize. I have to press migrate again, select the SkyConnect and restore from backup or leave radio settings alone to make it work again.

I do not know how to solve this. It clearly works but forgets it needs to use the SkyConnect on reboot. Any idea what I could do?

[francisp (Francis)]

See

Skyconnect Migration from Nortek HUSbzb-1

I ordered a Skyconnect and was preparing to migrate my ZHA network this afternoon. I do have a separate Z2MQTT Network as well on a different Sonoff coordinator. When I went to the web address referenced on paper card that came with the device I noted in the instructions that the new radio would inherit the IEEE address from the old coordinator and later in the instructions it stated that I would need to remove my old device. This is a problem for me since my Nortek device also handles my Z-W…

[Jasper8472]

I read that topic. I can see that it’s related but I cannot find a solution there. And I’m not quite sure what is happening.

Why is it working when I assign the radio? Are they both being detected as viable and therefore nothing is selected on boot? I’m clearly using the SkyConnect after migrating as it states at step 5 that the old radio has been reset. Has it secretly not done that?

I don’t know how to exclude the HUSBZB-1 if that is what needs to be done. I’ll test if it works when I disconnect the HUSBZB-1 and reboot when I’m home. That’ll narrow it down a bit.

[francisp (Francis)]

@Jasper8472

I can see that it’s related but I cannot find a solution there.

This part:

@jerrm

If it hasn’t been changed in the past, you should be able to change the Nortek zigbee ieee address after migration using the SI Labs Flasher . In theory you could migrate, and then change the Nortek ieee, and everything should work.

[Jasper8472]

Yeah, that clearly states should. It’s also not really an easy method, I understand little of that repository.

Can I do this from HA?
Do I need another device, besides my windows machine, to execute this code?
What IEEE should I change it to?
There’s warnings all over the place.

I just need a solution where HA selects the correct radio on boot. It clearly sees the SkyConnect, so why doesn’t it remember the preferred radio? Or the radio that was last configured. What does the selected device have to do with the IEEE of the obsolete one? What would changing the IEEE do to that setting?

[francisp (Francis)]

Your 2 radios have the same IEEE at the moment, so ZHA gets confused.

[Jasper8472]

All right, I went ahead and saw that it runs fine when I remove the HUSBZB-1 from the system.

I spun up an old RPi running DietPi and connected the Nortek HUSBZB-1 to the Pi. I installed universal-silabs-flasher. I ran the following commands and received the output below, it seems it cannot find the Zigbee part.

root@DietPi:~# universal-silabs-flasher --device /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_41500CC4-if00-port0 write-ieee --ieee 003c84fffe92bb2c
2024-03-13 18:39:01.207 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-03-13 18:39:03.217 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-03-13 18:39:07.537 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud
2024-03-13 18:39:11.853 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud
2024-03-13 18:39:16.168 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2024-03-13 18:39:21.181 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
root@DietPi:~# universal-silabs-flasher --device /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_41500CC4-if01-port0 write-ieee --ieee 003c84fffe92bb2c
2024-03-13 18:41:23.767 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-03-13 18:41:25.776 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-03-13 18:41:30.091 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud
2024-03-13 18:41:34.406 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud
2024-03-13 18:41:38.721 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2024-03-13 18:41:43.733 DietPi universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type

So, I’ve tried but running out of options again.

I still don’t understand why it doesn’t remember the last used radio.