I want to get started with Thread, so naturally, I am evaluating which is the best (most reliable?) option for a Thread Border Router. My tendency goes strongly into using my HAOS machine as an Open Thread Border Router, and thus I need a Thread radio. But, as I see it, there are mainly four options overall:
OTBR on HAOS machine by using the official HA Connect ZBT-1 (formerly SkyConnect) radio. My expectation would be that this runs relatively stable and is a solid solution.
OTBR on HAOS machine with a third-party radio (e.g., Smlight SLZB-06M). Those offer advanced features (bigger antennas, easier placing through PoE, etc.), but I wonder whether the firmware interacts nicely with HA and I fear lacking support.
A third-party device that includes a Thread Border Router (e.g., something like an Apple Homepod, Alexa hardware, etc.). As I would purchase such a product just for the Thread Border Router functionality, I would not expect any real advantages, but feel free to prove me wrong.
A dedicated third-party Thread Border Router (e.g., GL.iNet GL-S20), seems like a mixture of solutions 2 (but more independent) & solution 3 (but no unnecessary features).
All Thread devices to be used will be Matter-over-Thread. I do not plan to use ZigBee, Z-Wave, or any other wireless protocols (despite Wi-Fi, of course )
IMHO: #1 is the setup I use. It works for me, but for others, it is very problematic with Thread dataset/credentials management, but if you are starting from scratch its more manageable. #2 that particular device in PoE mode is not recommended by the HA Matter/Thread developers #3 Apple/Google (not Alexa and maybe not others) would be the easiest #4 I don’t have experience with.
I already had a few HomePods mini, so I just use them. The main perk is that they make commissioning easy with Apple Home, but like others (e.g. Google, Alexa) they hide the credentials so make it complex to use other apps (e.g. HA) for commissioning.
My parents needed to upgrade their WiFi so I got them Eero 6 mesh routers, which also have TBR built-in. Kudos to Eero for making the Thread credentials easy to pull from their management app to facilitate commissioning with the HA companion app. A good solution if you don’t already have WiFi 6 or better (which I highly recommend).
I considered the GL.iNet to better learn OTBR, but found it somewhat expensive. So instead I flashed a $5 esp32-h2 with RCP firmware, and setup OTBR docker container (an esp32-s3 also works). I find that it works fine for a cheap config, no “firmware interaction” issues with HA. But mixing TBR types/vendors is still a mess because of credential sharing/syncing issues so I only use it for testing.
Keep in mind that one TBR is adequate, and line-powered Thread devices will extend the reach of your mesh, compensating for antenna/range limitations.
#2 that particular device in PoE mode is not recommended by the HA Matter/Thread developers
Hm, do you have more information where these recommendations can be found, @wmaker ?
Eero 6 mesh routers, which also have TBR built-in
Thats a good hint. I already have a powerful router that I do not want to replace. But it totally makes sense to combine WiFi and Thread routers.
I flashed a $5 esp32-h2 with RCP firmware, and setup OTBR docker container (an esp32-s3 also works)
Thanks for pointing that out, I did not have this in mind. I think serious everyday usage will be off the table for most users.
Keep in mind that one TBR is adequate, and line-powered Thread devices will extend the reach of your mesh, compensating for antenna/range limitations.
Yes, a full thread device (FTD) works as a repeater and makes the mesh more robust, but the TBR still is a single point of failure - or how does it work when you have multiple HomePods or the like (solution #3)?
)