So I managed to get my GL-S200 Thread border router to run under my HA instance to replace the multipan issues since the skyconnect is now in dedicated zigbee mode.
I can’t for the life of me figure out at this time why HA is not wanting to add it but it has been paired and showing up on the GL-S200, it just keeps failing at Add Matter Device.
I am trying to repair my P2 sensors to start using them again through this setup.
I have restarted the phone, cleared the credentials and resynced them to allow me to get to the point where I am and factory reset the sensors each time just to sanity check them, quite baffled at the moment.
I am using an android phone with the latest companion app build and I have tried both direct via add device through the matter integration and via the popup that comes up when the device is in pairing mode then selecting via another app and selecting HA with scan and manual code input.
Edit: after restarting everything multiple times then doing a cold restart of my HA VM instance I was able to have it be added.
I have my GLS200 setup with the ip of 192.168.1.252 with its pool set to 1.1 - 251 (I can’t go higher than this as it limits the range to what the device itself is set to but my main network gear is 53 and 54 anyways, which is inside the main ip range of my main network).
I have it then just connected via lan port (have the wan setup as lan as well for trying to get it to register internet connection but its not seeing the wan connection coming from my main router).
For the settings on the thread network I have this:
I copied the panid, extended pan etc from the preferred network information when you click the i for more info. Took a bit to work out since I needed to delete the old network after I set the new preferred and to have the name stick etc.
OK thank. So what mode is your GLS200 in? (Admin Panel > THREAD MESH > Advanced > Backbone Router > Backbone Interface).
I’ve tried two methods listed on Work with Home Assistant - GL.iNet IoT Docs
Firstly, my HA was connected directly to my GLS200 via LAN and I selected “br-lan”. I managed to set up the thread and matter on HA. When I added a matter device with the application, the border router thread was detected, the device was added to the thread network, but it was impossible to add the device to matter. And I saw that the GLS200 documentation states: If your Home Assistant Host is on GL-S200’s LAN side(no matter wired or wireless), select “br-lan”, click apply to take effect.
so I decided to connect my HA to WAN
Secondly, I connected my GLS200 in wifi and my HA in cable to a second router. I selected “wlan-sta0” and opened port 8081 TCP/UDP on the GLS200 as indicated in the documentation. I’ve managed to set thread and matter on my HA, but when I want to add a matter device with the application, it can’t find the border router…
br-lan, pretty much all settings are stock other than the changes to copy the thread network details in and the IP changes so that its inside the ip range for the main network.
I also have the REST api opened 8081 and am able to read what is posted via the MQTT messages but still need to work out how to use BT devices through it later when I have more that use it.
Router mode, I mainly just changed the wifi ssid and passpharse from default then shut it off. I am also on FW v4.1.5-0400 which is the latest release as of this reply still.
I tried again but I still have the same problem.
If my HA and GLS200 are connected to my main network, the application on my phone doesn’t see the border router.
Make sure to do a full restart of the HA install once you have the GLS200 connected to it to refresh the connection between them then you can add the devices.
I had to shut off then restart the HA instance I have on my nuc to get it to connect the p2 door and window sensors.
Also don’t forget to update the credentials saved on the companion app.
Make sure as well that IPv6 is enabled in your network and that you are using only the companion app to connect the devices when pairing them once the 200 is added as the main border router.
After trying out Matter over thread for a while with this setup… its not working out especially after restoring a snapshot and it breaking my configuration leading to another session of faffing about with configurations failing to get the sensors paired again as they get stuck in the checking connection to SSID phase.
I am going to remove the thread devices from my setup fully until its more matured and I am able to redo credential syncing without deleting things from google play services since it also wipes my saved cards from my digital wallet.
Matter over Wifi devices paired back up with zero issues to the setup once deleted from the instance and put back into pairing mode and having the code scanned in.
I have re-setup the GL-S200 in my setup and had to use the Uboot flash method to update it to the openwrt-s200-4.7.0-0501-0103-1735869327 firmware currently available on their site as I was getting permission issues via SSH and would not let me update directly in the admin panel.
I was able to connect to it over wifi after updating it then from there I set WAN as LAN so that I could assign it and the other LAN port the same subnet for my setup via the LAN settings then making sure DHCP was disabled (the WAN port once re-enabled gets assigned a static IP from the main router to provide it internet access, the router IP address is assigned to the LAN port and is what is used to access the configuration page).
From there I accessed the Thread Network settings and updated the name to GLS200-HA and let it auto generate the rest.
In home assistant once it found it and I set it as the preferred network for thread and after I exported the Active Dataset TLVs from the devices configuration page and copy and pasted it into the thread configuration page in HA via the add dateset from TLV option I also deleted the pre-generated home-assistant network.
Once done I was able to update the credentials sync in the android companion app without the need to delete any cached data from google play services after making sure that used for android + ios credentials option was clicked and a phone with a key icon was displayed on the border router name.
From this point it was instant setup of one of the Aqara P2 sensors again.
Since I am already using zigbee version of the door sensors for other places I will just leave this one connected for testing restoration down the line when I get a scenario that lets me see if I am able to restore both the HA and GL backups I have now and it not breaking like it did with a snapshot restore previous.
As for the bluetooth function of this model I have installed MQTT explorer for other things and will see how it works when I get around to getting a new battery for the Govee H5179 I still have in my drawer.
I have also added a step in my HA reboot automation to power cycle the TBR 10s after it boots up to help mitigate this since I have it plugged into a zigbee plug anyways.
I will update the thread with any other quirks I find and mitigate, will see if they release more firmware updates as well over the time I have this setup.
