Have you bought it and set it up yet? Im interested in the results. I currently use the SLZB-06 for my zigbee network and connect using the ethernet but powered by USB as my switch isnt PoE so i could have the coordinator in the centre of the house as my mini OC running HA is in the lounge. Im wanting to get a boarder router for thread that can also connect via ethernet to place it in the centre of the house. Im not too fused about PoE as i have power in the location to power via USB so its mainly the Ethernet for connection only.
Make sure that you don’t have mDNS issues as matter needs it to work properly.
I haven’t yet, but likely will be ordering it at the end of the month - tbh, to get it all set up I’ll very likely be powering it from USB as well (just plug it into a power bank while I get it working) so I’ll update this thread with how difficult or not the process is.
I’m hoping the biggest challenge will be convincing the devices to swap over to the new Thread network and reject the Google Nest Hub as TBR.
Having found the Thread Mesh map under the Matter server options (enable the beta version under config, then Open Web UI), I can see that even with the IKEA ALPSTUGA AQ sensors acting as routers network quality is not at all great because of the location of the TBR (stuck in a corner). Having a TBR in a more central location will improve things greatly.
Not really sure about that. The alpstugas are not-so-good routers due to their low output power (3dbm, it’s in the manual). Kajplats bulbs are better for that purpose (10dbm). In the grand scheme of things, it doesn’t really matter as the mesh is self-forming, self-healing, self-maintaining. You just need to have enough mains powered devices, the mesh will work it out.
In this instance it should - agreed the ALPSTUGAs aren’t great, but that’s compounded by the current TBR being in one corner, and then all 3 of them being in rooms quite a distance from said TBR. Moving the TBR somewhere they can all “see” it more clearly will definitely help.
The beta HA thread visualization page shows that my setup is radial (no mesh formed) - since all my thread devices are IKEA battery sleepy endpoints. Fortunately the TBR (Aqara M100) can be placed in a central spot that reaches the basement as well as upstairs devices.
Thanks for that. Thread is still kinda beta for me as a mesh technology, my main goal is establishing an otbr on my green with a zbt2 (done,). It’s definitely on one end of the house for reasons hard to remediate now.
I’ve been moving alpstugas around as endpoints to see if they reach, and they do in three other fast end of the house on the other floor… But not clear on signal strength.
I have one inovelli white fan switch middle-ish to this and will put another on the far end.
Upgrading to beta and seeing that map will be the truth. Great comment, thanks.
Just like with any of the other mesh options like zigbee, zwave etc it’s all about the repeater/routing points between each end point device and the co-ordinator and their placement based on the layout of the location you have to work with.
By looking to add more of the switches that can act as repeaters this will help improve things, and for places where you can’t place them then either install relays behind power sockets or a smart plug that uses the mesh type you need to extend.
Some more observations from my TBR experience so far:
- HVAC metal ducts create significant dead zones.
- The beta HA thread visualization page really helped optimizing TBR placement.
- Agree that a mesh could help (if I had any repeater thread devices).
- However all my powered devices are matter-over-wifi (Wiz lights and Nest thermostat), and all my thread devices are battery sleepy end points.
- Matter-over-wifi vs matter-over-thread is a choice I had not considered prior to introducing a TBR, and I started with matter-over-wifi because it didn’t need a TBR. Something to consider going forward now that I have thread devices…
I’d like to use the visualization to verify that my switch installation built a good mesh. I’ve updated to 2.16.4 a number of days ago and the system has been restarted during that time . I’m not seeing a link in either devices and services or Apps. Do you know how I get myself there?
Credit goes to PrinterElf for describing how to get there "Having found the Thread Mesh map under the Matter server options (enable the beta version under config, then Open Web UI).
I have HA container rather than supervisor so for me the Web UI is on port 5580. Either way the the Thread page should be a navigation button on the top right:
![]()
That got it! I hadn’t drilled down to find enable beta setting. Everything is functioning fine, including my mesh. Initially the red and some of the dashed lines threw me off. Only seeing red and orange threw me off as well, eg no green.
But after looking around at how to read the diagram, it looks like things are pretty healthy and my choice to put to inovelli fan switches at intervals on the second floor built a solid mesh.
Thank you and @PrinterElf !
Good to hear, although for me anything in red used to drop out momentarily every couple of days, so it was worthwhile playing with placement to get everything to green or at least orange.
Another handy-dandy feature I found: You can set custom node labels by clicking on a node detail, then Endpoint 0, then BasicInformation, then enter Node Label:
SMHUB Nano ordered, should be here in a couple of weeks.
Just missed out on getting it on Amazon for pretty much the same price as AliExpress, so going to have to wait for international shipping.
Hub arrived.
-
First hurdle, it can be run from any PoE supply… that isn’t Ubiquiti.
This note was in the packaging,
This Reddit thread suggests the units can run very hot if you do.
Not particularly helpful right now, but we’ll go with USB-C power to start with.
N.B. The USB-C is socket recessed slightly and the space around it is not large, so you’ll need a lead with a small plug on it. -
Boot the unit, let it connect to your router via ethernet and assign it a static IP address.
-
Connect to it via the web UI and start following these instructions:
Using SMHUB as Thread ... | SMLIGHT Manuals
N.B. Pay careful attention to the Firmware & apps (tested on) section at the top of the guide, as quite likely a number of things will need updating before you can follow the steps. -
Head to Settings/Updates and Restore. Update the OTA to the latest and reboot once done.
-
Flash the radio to Thread mode per the guide
-
If when you get to the Apps page, you find that apps are not available to be upgraded to at least the versions mentioned in Firmware & apps (tested on) section at the top of the guide, you will have to go back to Settings/Updates and Restore and change the App Update Channel to “development”.
Back to the Apps page, and refresh the available list. Upgrade the apps from the Firmware & apps (tested on) section at the top of the guide to the latest versions (which should now be new enough to get to installing the openthread app. -
Then follow the rest of the guide to link it into HASS.
Tbh if this behaves itself I’ll seriously consider getting another one to run Z2M.
It uses 802.3AF POE
Pretty much all recent Unifi kit supports 802.3af. I’m not sure why the recommendation is not to use Unifi kit, but I also don’t want a broken device so I’ll work it out later.


