Home Assistant Connect ZBT-1 migration error

Since the latest update of Home Assistant Core, I’m seeing the following message for the Home Assistant Connect ZBT-1 integration:

“Migration error”.

I can’t find anything related to this in the logs.
The SkyConnect is still functioning correctly as the radio antenna for my Thread network with (only) 7 devices.

When I click on the integration, I see a “needs attention” message.
If I then select the “Home Assistant SkyConnect” device within the integration, I see the same “Home Assistant Connect ZBT-1” entry listed twice under Device Info.

Does anyone know the easiest way to get rid of this issue?

I have this issue also. Using it as a thread device everything works fine otherwise and nothing in the logs.

1 Like

I think my skyConnect flagged and accepted an update a day or 2 ago.
Is there a pending update for yours?
OR did you click the update?
Mine is hanging out with nothing attached if I get brave enough to install a matter annoyance. (I haven't yet)

1 Like

Nope, no pending update for mine.

I have exactly the same "problem".
I think it has something to do with the latest Home Assistant Core Update.
But its still working atm, must be a bug.

Today, I decided to make a full backup and then delete the "Home Assistant SkyConnect" integration (the one causing the migration error). After that, everything seems to be working normally. The other entry with the same name in the integration remained fully functional.
As a result, I no longer have any migration errors.

Thanks VictorvandenHoven


for the tip. I hadn't dared to simply delete the highlighted device, since it is identical to the one currently in production use. But it worked — only the entry containing the error is gone now, and Thread on ZBT-1 is running just as it did before.
The only minor issue is that two entities are now being counted, even though there is actually only one. However, this is likely just a display issue.

Correct: There are two entities:

One device (the USB stick) with two entities:

  • One for the firmware
  • One for beta firmware updates

You are right. Before the release, there was only one entity. That is why I thought the display was incorrect. But the "Beta Firmware" entity likely appeared with the release.

Went and did the delete of the messed up one like you suggested and everything is fine.