ZBT-1 (thread) to ZBT-2 (thread) problematic (caution)

Configuration Matter/Thread
,
1

The new ZBT-2 is very nice hardware.
There is little instruction on how to migrate from ZBT-1 to ZBT-2 for thread (in the box or on the website that I could find)

When plugging the device into a native HA NUC for the first time the firmware change/update to thread failed. This seems to be common, as shown in this github thread:
https://github.com/home-assistant/core/issues/156966

I rebooted and the firmware seemed to take, but it did not migrate cleanly from ZBT-1 to ZBT-2 in the config.

The caution is that it might be advisable to wait until this update and migration process is ironed out a bit as its new.

I’ve disabled the ZBT-1 add-on, and disconnected the ZBT-1 and everything appears to work but I won’t be deleting it yet until the following issue is resolved as I really don’t want to re-pair all my kit.

otbr addon
otbr addon988Ă—453 27.6 KB

OTBR “add on” shows ZBT-2

OTBR “service” shows ZBT-1 (even though its disabled and not even connected) I am unable to add the second screenshot as I am a “new user” :frowning:

2

otbr services
otbr services894Ă—451 21.2 KB

OTBR “service” shows ZBT-1

How? :slight_smile:

3

I think that is just a name string that HA gave the OTBR Integration entry when the entry was created. You can click on the 3-dots and rename it if you like, but it should still work as is. This integration is communicating with your existing OTBR AddOn, and it will continue to communicate with your OTBR.

I am not aware of a ZBT-1 AddOn, so not sure what you mean by disconnecting the ZBT-1 and things are working.

Assuming the firmware flashing worked OK, all you need to do is stop OTBR AddOn, unplug the ZBT-1 and then plug in the ZBT-2 and configure the OTBR AddOn to use the ZBT-2 as you have shown in the screenshot, startup the OTBR AddOn and everything should work.

Pairing should not be an issue, as the current OTBR AddOn and Matter Server AddOn will still retain all the information needed.

4

I just connected my ZBT-2, so I had both connected.
Then I opened up my Thread integration (or maybe it was the OTBR addon) and changed the USB binding from ZBT-1 to ZBT-2.
Then I restarted and removed ZBT-1.

It was extremely easy.

5

Thanks Tommy, will try that. This is what I mean about “add-on” (its of course the integration - my poor terminology)

addon
addon1658Ă—730 49.2 KB

6

Thanks Wally. Can you tell me where I change the USB binding? (My “service” seems OK and its pointing at ZBT-2. Its the OBTR integration showing the previous ZBT-1 even though the ZBT-1 add-on is disabled and the device itself ZBT-1 is physically removed)

7

What Wally means is to change the OTBR AddOn’s config to use the ZBT-2 which you show with the above screen shot (/dev/serial/by-id/blah blah).

Its just a name that HA came up with when it first created that entry for the OTBR Integration. You need not worry that it has ZBT-1 in the name. The OTBR Integration doesn’t care about which USB device is being used, it only cares about which OTBR AddOn it needs to talk to.

1 Like
8

Remember that addons are separate containers, so a restart means restarting the addon, not the HA core.

1 Like