tight turtle
Update below:
After a restart of HAOS, I cannot start the OpenThread Border Router add-on due to a ZBT-2 failure. The setup was previously working. I have about 50 matter-over-thread bulbs (Nanoleaf Essentials) controlled by the ZBT-2, and I presently cannot control them. To troubleshoot, I tried:
- installing the zigbee firmware and reinstalling the thread firmware (on a separate computer from here: https://toolbox.openhomefoundation.org/home-assistant-connect-zbt-2/install/), and
- turning off all other thread devices to allow the ZBT-2 to start in a “silent” environment.
Neither of these steps worked.
Attached are the logs for when I attempt to start the OpenThread Border Router Add-on.
This is my first post and I sincerely appreciate any assistance!
UPDATE:
I deleted the OpenThread Border Router Add-On (and its data) and I deleted the ZBT-2 integration. Then I restarted HAOS and reconnected the ZBT-2 and it started again, seemingly resolving the issue.
In case it helps anyone else:
For my thread network, the ZBT-2 never seems to become the thread leader and the network is unstable unless I force a leaderweight of 255 as follows:
ssh into homeassistant
docker exec -it addon_core_openthread_border_router /bin/bash to run shell in the OpenThread Border Router Add-on
ot-ctl thread stop stop the thread network to make changes
ot-ctl dataset init active load current settings in memory
ot-ctl dataset activetimestamp view current timestamp
ot-ctl dataset activetimestamp <CURRENT_TIME> update the data set to take precedence with newest time
ot-ctl dataset commit active save change
ot-ctl leaderweight 255 set the ZBT-2 leaderweight to the max so that it attains leadership status in the thread network
ot-ctl thread start restart thread
ot-ctl state view ZBT-2 role in network to check if it establishes as leader (I gradually turn on other thread devices)
I wish there was another way to achieve a stable thread network, but this works for me.
rocky marsh