Hello fellow Home Assistant enthusiasts! I’ve been experiencing some issues with my Matter/Thread devices, and I wanted to share my troubleshooting journey in case others might find it helpful or relate to the challenges I’ve faced.
The Setup:
I’ve been using Home Assistant OS with Matter/Thread devices for about a year now. My setup includes three Nanoleaf NL67 lights, two Eve Energy smart switches, and a Home Assistant Connect ZBT-1. It’s been a smooth experience until recently when all my devices became unavailable.
The Problem:
At first, restarting add-ons and reloading integrations fixed the issue, but this time, it didn’t work. The OpenThread Border Router add-on had some failure messages, and the Matter Server add-on was flooded with serious errors. I started digging into the logs to understand what was going on.
The Logs:
Here’s a snippet from the OpenThread Border Router add-on log:
text
[16:53:46] INFO: Checking /dev/ttyUSB0 identifying Home Assistant Connect ZBT-1 from Nabu Casa.
[16:53:46] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2025-05-26 16:53:46.545 homeassistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=2, sdk_version=‘4.4.4’, ezsp_version=None, ot_rcp_version=‘SL-OPENTHREAD/2.4.4.0_GitHub-7074a43e4’ (2.4.4.0), cpc_version=None, fw_type=<FirmwareImageType.OPENTHREAD_RCP: ‘openthread_rcp’>, fw_variant=None, baudrate=460800)
It seemed like the add-on was accessing the Home Assistant Connect ZBT-1 correctly, but there were still errors popping up.
The Journey:
I decided to go through the logs meticulously. The OpenThread Border Router was showing some warnings about radio tx timeouts and RCP recovery attempts. This made me think there might be an issue with the communication between the Border Router and the devices. I also noticed some kernel-level messages about external routes, which piqued my interest.
I reached out to the community for advice and found that others had experienced similar issues. Some suggested checking the firmware versions of the devices and the Border Router. Others recommended ensuring that the network settings were optimized for Thread.
The Fix:
After some research, I discovered that updating the firmware on the Home Assistant Connect ZBT-1 might resolve the communication issues. I followed the steps to flash the latest firmware using the universal-silabs-flasher tool. The process went smoothly, and after a reboot, my devices started coming back online one by one.
The Reflection:
This experience taught me the importance of keeping firmware up to date and thoroughly checking logs when troubleshooting. It also highlighted the value of community support—without the insights from others, I might have been stuck for much longer.
If anyone else is facing similar issues, here are a few tips:
- Check Logs: Always start by reviewing the add-on logs for any clues.
- Update Firmware: Ensure all devices and add-ons are running the latest firmware.
- Community Support: Don’t hesitate to reach out to forums or Discord for help.
I’m relieved to have my devices back up and running, and I hope this story helps someone else navigate a similar situation!
Best regards,
[Your Name]