I'm using the GL-S20 IoT gateway as a Border Router in my Thread network.
I have several Full Thread Devices connected, but they remain in the child state and almost never get promoted to router.
Interestingly, when I connect the same devices to a GL-S200, they do become routers as expected.
Is there a specific setting that needs to be enabled on the GL-S20, or are there conditions that would prevent it from promoting devices to router?
Also, I noticed that if the GL-S20 is not the Leader of the Thread network, it doesn't obtain an OMR Address and doesn't act as a gateway between the Thread network and my LAN.
Is this expected behavior?
I'm a product architect, and I'm building Thread devices for a professional application. The GL-S20 is only used as a border router witouth customisation in the firmware.
Devices are only Thread, more specific CoAP. I'm not able to support Matter.
Hi Lancer,
sorry for the late reply, I was working with my team on the first bug we had, and I believed that we solved it !
firstly to answer your question, I haven't save the log, but if I 'm remember well, the code was crashing at the starting on a pointer error. I will try again this week to update the S20 with the latest release of Espressif, I will let you know if a succeed or not.
For the initial issue, I believe we've finally identified what was missing in our Thread setup.
We had overlooked the IPv6 prefix in the dataset. In fact, we configured the Network Name, Network Key, PAN ID, Extended PAN ID, and Channel. That was enough to create a Thread network, but not sufficient to route data over the internet.
When the network was started with the Border Router (BR) first (we always generate a full setup and copy/paste the Network Name, Network Key, PAN ID, Extended PAN ID, and Channel to our devices), everything worked fine because the BR was sending the IPv6 prefix to our devices.
However, when our devices started before the BR, one of them became the leader and never sent the IPv6 prefix to the BR.
That’s why we initially thought the BR needed to be the leader in order to route data over the internet.
At the end, I can say a big thank you to everyone helped us !
Hi Lancer,
I'm familiar with this thread , it was originally opened by my colleague regarding the same issue.
It's great news that a firmware update is planned. Do you have an estimated release date?
On my side, I’ll try this week using the GitHub repository you shared.
I’ll go ahead and close this thread, and if I encounter any issues while building the open-source firmware, I’ll open a new one.
, it was originally opened by my colleague regarding the same issue.