Lost Zigbee configuration | Home Assistant | Page 1

mild portal Jan 31, 2026, 8:14 PM

#

I came inside from shoveling snow to find my entire server locked up - CPU pegged at 100%, RAM at 94% - mostly assigned to docker.
After about 15 minutes, I got the server to respond to a "shut down all containers" command.

I started containers up 1 by 1 and everything seems to have come up just fine except HA. It's telling me that my ConBee II coordinator has failed setup. Well, that's not totally shocking since I replaced it about a month ago with a ZTB-2. There's no reason for it to be attempting to initialize the CBII.

I tried restoring a complete backup of my HA config (from yesterday when it was happily running on the ZBT-2), but that doesn't seem to have helped - it's still trying to load the CBII as my ZigBee coordinator.

Where do I go from here?

mild portal Feb 1, 2026, 7:19 PM

#

OK, minor lie in that previous post. I do still have the CBII stick plugged into the server and passed into the container. Planned on removing it from the pass through, then physically removing it, but forgot about doing so.

Just had another server CPU max out (an issue I'm pursuing elsewhere). This time, I've rebooted the whole server. HA has come back up and my ZB network is now running successfully on the CB!

Do I migrate from the CB to the ZBT-2 again? Is there a possibility of restoring the backup from earlier in the week and getting it to recognize that it should be running on the ZBT-2?

I promise I'll get the CB physically removed as soon as I'm back on the ZBT again!

Still, confounded on how it would have fallen back. I can confirm that the ZBT-2 is passed through to HA, however, it's not detecting it as a new device, and I don't see it showing anywhere on the list of devices.

bright quest Feb 2, 2026, 2:47 PM

#

You're still using ZHA, right? (Home Assistant's built-in Zigbee integration)

#

Is there anything in the logs?

#

but that doesn't seem to have helped - it's still trying to load the CBII as my ZigBee coordinator.
Like, how did you determine this?

mild portal Feb 2, 2026, 9:25 PM

#

bright quest > but that doesn't seem to have helped - it's still trying to load the CBII as m...

in answer to both your questions:

#

When it wasn't actually loading, it said that there was an error connecting to it.

bright quest Feb 2, 2026, 9:38 PM

#

That’s just the config entry name. You can rename it with the three dots

#

Click on the cog wheel and it’ll mention the actual serial path it’s trying to connect to

bright quest Feb 2, 2026, 9:39 PM

#

bright quest That’s just the config entry name. You can rename it with the three dots

We should probably rename it automatically during migrations..

mild portal Feb 2, 2026, 9:49 PM

#

/dev/ttyACM0 which is being passed into the container: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2411473-if00:/dev/ttyACM0

it should be using the ZBT-2, being passed into the container as /dev/serial/by-id/usb-Nabu_Casa_ZBT-2_DCB4D90F9500-if00:/dev/ttyACM1

#

For completeness, I also have /dev/serial/by-id/usb-Zooz_800_Z-Wave_Stick_533D004242-if00:/dev/ttyACM2 which has been unaffected by this recent issue.

mild portal Feb 2, 2026, 10:13 PM

#

dunno if those numbers should be private, so blocked them out...

bright quest Feb 3, 2026, 10:30 AM

#

Did you already restore a backup where the Conbee was still the main coordinator? Or migrated again? ZHA won’t change that automatically.

#

Or maybe something with your Docker paths changed?

#

If you migrated to the ZBT-2 already, you should be able to Migrate adapter -> ZBT-2 -> Manual -> Advanced -> Keep network settings (something like that)

mild portal Feb 4, 2026, 3:40 PM

#

bright quest Did you already restore a backup where the Conbee was still the main coordinator...

When it first failed, I restored the newest backup (which was 2 days old and had me running on my ZBT-2), and that didn't change anything.

#

Made zero changes to the docker setup.

#

Will attempt to manually migrate this evening.

bright quest Feb 4, 2026, 4:12 PM

#

As a side note, I'd recommend looking into using Home Assistant OS instead 😅
It avoids a lot of the issues you have with Docker passthrough and auto add-on installs and so on.

mild portal Feb 4, 2026, 10:01 PM

#

bright quest As a side note, I'd recommend looking into using Home Assistant OS instead 😅 I...

I've just purchased parts for a much needed server upgrade to happen over the weekend. Once that's done, I might just run HAOS in a VM on said server.
I'm also strongly considering stand-alone hardware for it so server issues don't touch HA...

#

I think I've figured it out.
Here's how I've configured the container to run:

#

Here is how HA is seeing the 3 controllers:

#

I'm telling it that the ZBT-2 is on ttyACM1, but HA thinks that the ConBeeII is on ttyACM1.
So, it appears that it thinks it's using the ZBT-2 as I told it, but, in fact, it's using the CBII.
Now... how to fix this? 🤷‍♂️

bright quest Feb 4, 2026, 10:19 PM

#

You‘re using the latest UNRAID version? Can you try to restart the container again and see what happens?

mild portal Feb 4, 2026, 10:19 PM

#

I'm on UR 7.2.3.
The screen shot above was from a fresh restart of the container

#

it was the same before the reboot - I restarted after checking that the config was correct (then grabbed the screen shot of the container restart for the configuration)

#

Also, dinner's ready, so I'll be back in a few. I'll carry out any instructions you might leave. 😄

bright quest Feb 4, 2026, 10:22 PM

#

What happens if you don’t specify a path to map to? So just pass in --device=/dev/serial/… (but not the : part)

#

Like, I’m really not sure why this happens here.

#

Are only the USB device names incorrect? And the actual devices are where they‘re expected?

#

Or are the ports just swapped completely?

mild portal Feb 4, 2026, 10:50 PM

#

When I select ZHA, then the gear for the CB II, it shows serial port /dev/ttyACM0, so that, to me, looks to be swapped.

I do not see the ZBT-2 listed anywhere in HA except in the Migrate dialog shown above.

The z-wave stick is on ACM2 as it's supposed to be.

#

removing the path from the mapping

#

seems to be a no go:

#

It's still looking for it on ACM0

#

I wonder what would happen if I tell it that the devices are at the path it thinks they are: #1467251687994429660 message

#

Nope definitely did NOT like me trying to swap them around like it thought they were!

#

#

I presume adding a hub wouldn't be helpful: I'd end up having to add all the devices to the new hub instead of everything running correctly from it, right?

#

Might a reconfigure to change the serial port to get it to recognize the CB where it thinks it is, then try migrating?

mild portal Feb 6, 2026, 2:53 PM

#

@bright quest any additional thoughts? I'm about to do a server hardware upgrade this weekend and would prefer to have this sorted out beforehand.
(Again, going to stick with a container for now, but if I can get this sorted, I'm happy to consider moving to a VM on the new hardware which should be robust enough to support HAOS in addition to everything else, before finally moving to dedicated hardware at some point in the future...)

mild portal Feb 10, 2026, 3:15 PM

#

Now that my server is functional again, I'm going to try not passing the CB II into the container at all and see if the system still runs. If so, then it is using the ZBT-2 and just has it named wrong. If not, well, I'm still stuck with something being really screwy.

mild portal Feb 10, 2026, 11:21 PM

#

@bright quest Does this ^ seem like a reasonable idea? How can I tell which of the two it's actually using without removing one and seeing what happens?

bright quest Feb 10, 2026, 11:41 PM

#

mild portal seems to be a no go:

Looking at this picture, your ZHA config entry sees to be named "ConBeee II" still. Just click the three dots and rename it to "ZHA" for now, so that the confusion from that stops at least.

bright quest Feb 10, 2026, 11:42 PM

#

mild portal Now that my server is functional again, I'm going to try not passing the CB II i...

This makes sense to me.

#

But there's still something very weird with your setup and passthrough. I'm not sure if it's UNRAID or something else..

bright quest Feb 10, 2026, 11:43 PM

#

mild portal <@773609067264344105> Does this ^ seem like a reasonable idea? How can I tell wh...

ZHA erroring out when it doesn't find the adapter is fine. You can just restart the container with the adapter passed through and it should reconect.

#

(I'd still recommend you to move to HAOS. You should be able to set up a lightweight VM on the same system you're currently running your containers on and just pass through the USB devices via the UI. HAOS should handle everything properly.)

mild portal Feb 12, 2026, 3:57 PM

#

bright quest This makes sense to me.

I'll give this a shot later today.
Thanks again for all your help! We seem to be totally out of sync on our communication right now, but so long as this gets worked out eventually, I'm just fine with it! 😉

mild portal Feb 12, 2026, 3:59 PM

#

bright quest (I'd still recommend you to move to HAOS. You should be able to set up a lightwe...

I'd like to get this issue resolved so that I've got a clean backup to restore to a HAOS installation. However, once I do, I may well set up a VM and install HAOS on it and shut down the docker.
My ideal would be to get standalone hardware so nothing on the server will impact HA and I don't have to worry about pass through at all anymore, but the VM might be a cleaner intermediate step.

bright quest Feb 13, 2026, 3:59 AM

#

It should be fine to (take a backup and) fix the issue on the HAOS instance. At most, it should require a reconfiguration in the "Migrate adapter" dialog. Something like: Migrate adapter -> select ZBT-2 -> Manual -> Advanced -> Keep network settings.

#

But on what coordinator is your network running now, if any?

mild portal Feb 14, 2026, 3:45 PM

#

bright quest But on what coordinator is your network running now, if any?

it is currently running, but I don't know if it's on the CB II as is named, or on /dev/ttyACM0 which I told the container is the ZBT-2.

I'm going to test by restarting the container passing only one device in to see which one retains function and which one leaves me broken.
I'm hoping it's actually running on ACM0/ZBT-2 and it's just named wrong...

bright quest Feb 14, 2026, 5:32 PM

#

mild portal dunno if those numbers should be private, so blocked them out...

Post a screenshot of that ZHA config panel again ^

#

The radio type and serial port there are accurate.

bright quest Feb 14, 2026, 5:33 PM

#

mild portal seems to be a no go:

Also here ^, make sure to just rename that config entry to "ZHA" to avoid confusion.

mild portal Feb 14, 2026, 5:33 PM

#

bright quest Post a screenshot of that ZHA config panel again ^

#

since radio type is deconz, does that mean it's actually running on the CB II?

mild portal Feb 14, 2026, 6:00 PM

#

bright quest Are only the USB device names incorrect? And the actual devices are where they‘r...

reading back through, I caught this. Not sure what the c in the first column of the permissions means, but this is from a shell within the HA container.

/dev # ls -la ttyACM*
crw-rw----    1 root     cron      166,   2 Feb 14 12:59 ttyACM0
crw-rw----    1 root     cron      166,   0 Feb 14 00:41 ttyACM1
crw-rw----    1 root     cron      166,   1 Feb 14 00:41 ttyACM2

Don't know if that's helpful info

bright quest Feb 14, 2026, 6:22 PM

#

mild portal since radio type is deconz, does that mean it's actually running on the CB II?

Probably. Try unplugging the ZBT-2 and see if it still works

mild portal Feb 14, 2026, 6:24 PM

#

Yup. Sure 'nuf is. Pulled the plug on the ZBT-2 and can still turn lights on/off.
😢

mild portal Feb 14, 2026, 6:24 PM

#

bright quest It should be fine to (take a backup and) fix the issue on the HAOS instance. At ...

Back to this, then?

bright quest Feb 14, 2026, 6:25 PM

#

Since it's been running on the Conbee the entire time now, a proper migration should be done, so just "Migrate adapter" -> ZBT-2 -> Automatic should work

#

.. but I'd still recommend first setting up HAOS because there are clearly some issues with your Docker passthrough.

mild portal Feb 14, 2026, 6:26 PM

#

bright quest .. but I'd still recommend first setting up HAOS because there are clearly some ...

I fully understand this, but I've got so many projects going on right now, that I don't want to dive into another one.

#

If When I get it successfully migrated to the ZBT (again). I'll shut down the container, edit to remove the CB II from the config and physically unplug it, then start things up. That should help.

bright quest Feb 14, 2026, 6:29 PM

#

It's possible you never migrated at all. The ZHA migration wipes the old coordinator during the migration (if both old + new coordinator are plugged in), so a repair informing about missing network settings would have showed up in HA if it suddenly was reset to the Conbee again.

mild portal Feb 14, 2026, 6:29 PM

#

hmmm...

#

This is still a bit concerning and confusing:

bright quest Feb 14, 2026, 6:30 PM

#

Indeed

mild portal Feb 14, 2026, 6:31 PM

#

Just forge ahead with the ZBT-2 migration as is?

bright quest Feb 14, 2026, 6:31 PM

#

What if you remove the :/dev/ttyACMX part from the UNRAID passthrough for all passed through (serial) devices?

#

.. if that's even possible. Let me check

mild portal Feb 14, 2026, 6:32 PM

#

bright quest What if you remove the `:/dev/ttyACMX` part from the UNRAID passthrough for **al...

#1467251687994429660 message

#

It didn't like it when I tried.

bright quest Feb 14, 2026, 6:33 PM

#

Well, ZHA just didn't find it at the /dev/ttyACM0 path. It would be at the /dev/serial/by-id/... path

#

You could try to remove that again (for all serial devices) and then use the "Migrate adapter" option -> "Reconfigure current adapter" -> select Conbee (if found) -> "Advanced" -> "Keep network settings".

#

That updates ZHA's path to look for the coordinator, without changing any network settings on any coordinator.

mild portal Feb 14, 2026, 6:36 PM

#

bright quest You could try to remove that again (for all serial devices) and then use the "Mi...

Just to be clear, remove the :/dev/ttyACMx part?

bright quest Feb 14, 2026, 6:36 PM

#

Yup, for all serial devices you passed through

#

Maybe don't even passthrough the ZBT-2 at all, for now.

#

ZHA will fail to find the Conbee then, so you need to Migrate -> Reconfigure and point it at the updated path of the Conbee

mild portal Feb 14, 2026, 6:37 PM

#

I'll give that a go, ignore the complaints, and try the migrate/reconfig

#

will pull zbt-2 from the config as well.

#

will copy/paste all the paths into a text doc so I can easily put them back, too. 😄

#

I presume this is to be expected and to just carry on as is?

#

I note it found the CB II at acm0

bright quest Feb 14, 2026, 6:44 PM

#

Hmm, that's not great. You'll need to enter the full /dev/serial/by-id path frfom your host system then

bright quest Feb 14, 2026, 6:44 PM

#

mild portal I note it found the CB II at acm0

really?

mild portal Feb 14, 2026, 6:44 PM

#

well, it seems to think so...

#

use this for the device path, instead:
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2411473-if00

#

I presume 115200 is the proper speed and None for flow control?

#

(I dunno this stuff...)

bright quest Feb 14, 2026, 6:45 PM

#

mild portal I presume this is to be expected and to just carry on as is?

You're still in this dialog? Can you close it again, wait a few seconds, do Migrate adapter again. Instead of selecting the auto-detected Conbee, click "Manually enter serial path" and enter the dev serial by id path there

#

I think it should auto-detect then, but I'll check

mild portal Feb 14, 2026, 6:46 PM

#

will do

bright quest Feb 14, 2026, 6:46 PM

#

But there's something very weird still..

#

Eh, it won't auto-detect if you enter manually anyway.

mild portal Feb 14, 2026, 6:47 PM

#

Don't seem to have an option to manually enter a path

bright quest Feb 14, 2026, 6:47 PM

#

Yeah, try deCONZ then

#

and then just what's set there (115200 + none flow control)

mild portal Feb 14, 2026, 6:47 PM

#

takes me back to the screen shot above. specifically

bright quest Feb 14, 2026, 6:47 PM

#

Try entering the full serial by id path there

mild portal Feb 14, 2026, 6:48 PM

#

it seems OK with that and asks

bright quest Feb 14, 2026, 6:48 PM

#

Ok, if this is the Conbee, do Advanced -> Keep network settings. It won't migrate anything then, just change the path ZHA uses.

mild portal Feb 14, 2026, 6:49 PM

#

here we go!

#

#

drums fingers on desk...

bright quest Feb 14, 2026, 6:49 PM

#

(the old adapter being mentioned there is a cosmetic issue 😅)

#

So, try checking if the lights work. If they are, try also passing the ZBT-2 adapter into the container, I guess

#

Then see if Conbee still works. If so, we can try the actual migration to ZBT-2

mild portal Feb 14, 2026, 6:50 PM

#

Yup. seems to work.

#

going to take a deep breath and let sit for a bit.
Need to spend a bit of time with the wife today. 😉

#

Will try adding the zbt2 in and migrating to it in a little while.

#

Thank you again for all your help!!!! Greatly appreciated!

#

should I try adding the ttyACMx back in later, or just stick with serial/by-id?

bright quest Feb 14, 2026, 6:53 PM

#

Definitely just stick with /dev/serial/by-id 😄

#

When you try to migrate to ZBT-2 later. The process should be as follow: Pass ZBT-2 into container, check that ZHA still works with the Conbee, Migrate adapter -> Migrate -> Enter path -> EZSP -> Enter /dev/serial/by-id path for ZBT-2. As the baudrate, use 460800 and it should be hardware flow control.

mild portal Feb 14, 2026, 8:26 PM

#

Hey...
IT WORKED!!!!!!!

And, the somewhat annoying flashing blue LED in the top of the antenna has stopped flashing!!

If that's the indication that it's running on the ZBT-2, then I guess I never actually migrated to it in the first place. 🙁

#

#

and yet...

#

Guess I'd best rename it. 🙂

#

I feel better now

#

and this is running w/o the CB II even being passed into the container.

#

Thank you, once again, @bright quest, for saving my bacon!!!

bright quest Feb 14, 2026, 8:31 PM

#

Awesome!!

#

and yes, the blinking LED indicates that no network settings are stored on it yet

#Lost Zigbee configuration