Hi,
I've noticed a strange issue with my GL-S200.
I commissioned two devices that work properly at first, they respond to my requests and return values correctly.
However, after about a day, they stop responding, and the websocket reply shows:
...node not available yet.
If I reboot the GL-S200, the devices start working properly again.
How can I debug the GL-S200 to check if there's a problem with the Thread network?
Thank you
Hi,
Please let me know the S200 firmware, and share the issue syslog.
Hi,
I just noticed the final version v4.7.0-0500, I was stuck on the previous beta, so I went ahead and updated.
I also disabled the Backbone Router on the LAN, since my GL-S200 is configured as an Access Point using the WAN port.
After these adjustments, the issue disappeared.
Also, is it correct to disable the Backbone Router on the LAN when the GL-S200 is set up as an Access Point via WAN?
Thank you
Hi,
I think it based on your topology, to determine if requires configuring Backbone interface
The problem just happen again.
This is the GL-S200 log, please could you check it?
There are many messages like:
ChannelAccessFailure
radio tx timeout
RCP failure detected followed by Reset info: 0x3 (EXT) / Extended Reset info: 0x301 (PIN)
meshdiag routerneighbortable 0x6c00 failed
Thank you
logread.tar (189 KB)
I found an answer to my problem.
Basically one of the Thread devices, decided to become a Leader and this interrupt the Thread communication.
I pushed the Try to become a Leader button on the GL-S200 and the devices reprise to communicate without problems.
There is a solution to this problem?
R&D checked the log, found that the 2.4GHz wireless environment which the device is located is very poor, the 2.4GHz channel interference is relatively large.
It is recommended to set up high-performance devices as leaders to manage the network.
Hi, thank you for your answer. The GL-iNet is located about 50 cm from the devices I use for testing. I tried moving the GL-S200 to another location within the same room, but the problem persists. I also tried another border router (Tado Bridge), which works without interruptions.
Could you help me understand what I should do to solve this problem?
Thank you
BTW, the GL-iNet is connected via LAN cable. I can disable its Wi-Fi if necessary. I only need the Thread network and the LAN to interact with it.
Thank you.
Hello,
Please share this issue log to us.
You can find the log on my first post at the beginning of this thread.
https://forum.gl-inet.com/uploads/short-url/hw1YgUWgRWTXv311po1mCf64eCA.tar
Thank you
Is the log of this problem the same as the log of the last one?
Hi, I apologize for the late reply.
Yes, the issue is related to the first post and the log I had sent you.
Specifically, I need to understand whether this problem, which occurs only with the GL-S200, is something you will be able to fix with upcoming firmware updates, or if it is a hardware limitation.
We are planning to use your Thread border routers for our installations, but we need a stable product that does not require reboots as I currently have to do, or a forced re-election as leader every few days.
The issue only occurs with your border router; other border routers such as the Tado bridge X or other products work normally in the same environment and therefore under the same interference conditions.
Hi,
You mentioned that there are 2 units of S200 you have (if I did not misunderstand), are there any problems with these 2 units?
If you can replace another S200, please check if there is same issue.
If no luck, please contact CS by email [email protected] to provide order number, cc this thread, and ask to return your S200 to Headquarter Shenzhen.
May I know what thread equipment is there in your thread topology? Whether the topology can be provided, R&D may need to check the issue locally.
Hi,
no, I only have a GL-S200, and I would like to understand with you why it freezes so easily on a congested network (as you explained to me).
In the past few days, I ran a series of tests by changing the Thread network channel from 26 to 16. Now the situation has improved, and the Thread network has not frozen anymore.
However, I wonder if you could enable a firmware feature that automatically searches for the channel with the least traffic and configures the device on that channel.
This feature is very common in Wi-Fi devices, could you enable the same automation for the Thread network channel as well?
As requested, my Thread topology includes only two Matter Thread devices connected to the GL-S200 Thread Network.
Thanks
Yes, great idea, I will submit it to PM team for evaluation.
Good to hear this news. It's possible that there's a lot of interference at 2.4GHz around, including Bluetooth/WiFi/Zigbee (like wireless control toys and game controllers, wireless mice keyboards, wireless mic, IoT devices, etc.).
Are these two Thread devices far from the S200?
Hi, both devices are about 70 cm away from the S200.
Thank you
Hello,
The Thread provided a channel monitor function, please refer to the following link, which can view the busyness of the current channel.
Hi, thank you for your response and sorry for the late reply.
Unfortunately, this is not a channel interference issue. The GL-S200 randomly loses Thread communication with the devices. This happens every few days or even multiple times a day — it is completely random.
If I reboot the GL-S200, all devices start working again.
The channel 11 used by the GL-S200 is clean:
root@GL-S200:~# ot-ctl channel monitor
enabled: 1
interval: 41000
threshold: -75
window: 960
count: 4
occupancies:
ch 11 (0x0000) 0.00% busy
ch 12 (0x0000) 0.00% busy
ch 13 (0x0000) 0.00% busy
ch 14 (0x0000) 0.00% busy
ch 15 (0x0000) 0.00% busy
ch 16 (0x6665) 39.99% busy
ch 17 (0x0000) 0.00% busy
ch 18 (0x3fff) 24.99% busy
ch 19 (0x0000) 0.00% busy
ch 20 (0x0000) 0.00% busy
ch 21 (0x0000) 0.00% busy
ch 22 (0x0000) 0.00% busy
ch 23 (0x0000) 0.00% busy
ch 24 (0x0000) 0.00% busy
ch 25 (0x0000) 0.00% busy
ch 26 (0x0000) 0.00% busy
Done
Moreover, the GL-S200 is connected to a UPS.
Is the GL-S200 defective, or is it simply not as robust as other Thread devices that do not stop working?
Thank you
Is only thread communication lost? Is WiFi or wired communication normal?
When the thread is disconnected, export the log and write down the approximate time. I will check in the log to find what happened during this time.
Is the power supply of the UPS a 110-220V output socket (and through the power adapter AC > DC to S200), or is it a direct DC 12V output to the S200?