My MT3000 is on firmware 4.1.2 release 4 .
It was working perfect on 4.1.2 release 2 with factory SSID’s.
After upgraded to 4.1.2 release 4 , I have done a reset and changed the SSID’s to match my previous router (AR750S) as all I am not looking forward to reassosciate all my IoT Devices to a new SSID.
Router Temp is hovering at about 68 celsius with no plugins enabled other tham SMB and DLNA.
Uptime : 1d 16h
Problems encountered:
The 2.4GHz SSID name doesn’t come up always when trying to connect to wifi and also if it comes, I can not connect to it always.
The 2.4GHZ SSID seems to kick out some devices and I am not sure why. I have attached here the logs that I can see form Luci ( both System and Kernel logs).
If I manage to connect to the 2.4GHz SSID, the speeds are very slow ( didn’t manage to do a speed test sadly)
Wifi channgel for the 2.4GHz SSID is set to 10 and I have scanned to make sure the spectrum is free in that area. I live in the country side so I don’t have interference.
My AR750S is unplugged so I am very sure there is no problem like having 2 routers with the same SSID connected.
I am happy to perform some diagnosis with guidance as I purely loved thsi router when I was on it’s own. I will factory reset it and use it with the factory programmed SSID now to see how that works though it will not have so many devices on it like has now.
My total IoT devices number is abour 30 devices so it is not a huge clients pool.
IoT devices generally have poor Wi-Fi compatibility, so please check the Wi-Fi Mode to ensure it is the same as the ar750s settings. I suspect that this may have been caused by ax.
Also, please try to test with version 4.2 if it is easier for you. Because issues found will be fixed in the new version and not 4.1.2. Thanks.
I have tried channels 6 and 11 but the result seems to be the same.
I will try the to use a different wi-fi mode without ax now and see if that makes any difference.
My AR750s was having the same settings but indeed without the ax mode.
For security I only use WPA2-PSK as the ar750s was set the same.
I will try without the ax mode. Most of my IoT Devices are based on esp32 and programmed by me so I am in control of the firmware and settings but even if the esp32 is not always a great solution, I am sure there will be customers that face the same issue in the future so if I find a solution, that will be helpful for those customers also :-).
I have matched the settings of my ar750s with the expection of the ax mode but now I have switched the MT3000 to use b/g/n and hopefully this will solve the problem. I will monitor and update the status in 1-2 days.
I have tried both b/g/n/ax and g/n/ax but the result was the same as in the IoT devices were having the same problems.
For me it is the first time using ax so I am learning just now about the compatibility issues .
In 5GHz I only use my phones and a few laptops and I didn’t notice any problem though I am using a/n/ac/ax .
I understand this but most customers will be less technical than us, the ones testing or the team that builds the firmware and the routers so their experience should be as smooth as possible and where issues can occur, it should be labeled for them. In my work life I am a product integrator and I have faced both development teams and customers so there is a balance to be made in the final product
Can you provide the firmware and model number of the IoT device? We would like to install the same firmware into the development board to debug Wi-Fi compatibility.
Sure, I am using M5 atom lite as a platfrom with these sensors and I have programmed them with ESPHome to run on Home Assistant . I am using the latest version of Home Assistant and ESPHome but if needed, I can provide the exact version.
We tested ESPHome firmware with your yaml file and it connects to the MT3000 normally. Can you provide the firmware you compiled and tested? It is better to remove the peripherals and leave only the firmware for wifi configuration.
Hi Kelly, bedroom-factory.bin.zip (617.8 KB)
Please unzip the file ( it was zipped on a Mac so if it makes any issues, try to unzip on a mac) and then use it for the ESP32 device. I will PM you the SSID and password for the Wifi AP .
Thank you for testing the connection with ESP32. My problem comes after a while when the device is connected to the SSID. Let me please try to redescribe the issue :
I can connect the ESP32 to the router after programming while the esp32 is still plugged in my laptop. After this when I disconnect the ESP32 from the laptop and plug it a different power supply to use it, even in the same room, it take a few resets of the esp32 ( using the reset button of the board) to get it to connect to the router ( MT3000) . Once it is connected it will stay mostly connected, but it has random periods of time when the ESP32 disconnects and reconnects or remains disconnected and it exposes it’s fallback AP. In my case this happened over night and I woke up as the heating was off . After I have updated MT3000 to 4.2 beta 2 and set the 2.4GHz network to b/g/n, channel 11, 20MHz it became more stable and I have slowly put more and more sensors and devices on it. Today I am moving the heating on it also to see how it behaves. For now it has part of my esp32 sensors and some 小米 cameras.
We’ve successfully burned your firmware and connected to the MT3000 wifi. We will try to mount it for a few days to see if it becomes unstable. If you have any progress on the test, please also update us.
5G wifi is enabled and the SSID is different
2.4GHz SSID is : GL-AR750S-xx
5GHz SSID is : GL-AR750S-xx-5G
( I have renamed the MT3000 SSID’s to match the ones I had on my old AR750S to make the trasition easy for my IoT devices.)
The reboot logic is part of the ESPHome suite as far as I can tell and there is no obvious way for me to remove it. The entire code/logic the is in the firmware and then compiled by ESPHome in a firmware for the ESP32 is in the yaml file I have posted above . If you think this is issue that I face is worth while your time, you can run HA on almost any SBC like a RaspberryPI, Orange PI or even as a docker container on a machine that runs on the same network with the ESP32. It a quick install in the ESPhome integration is native as they made by the same organisation.
As an update to this thread :
I have been using now for 24h MT3000 with all my devices and all works well with IoT devices and everthing else.
I am now running fw 4.2.0 beta 2 and the 2.4GHz SSID is set to WPA2-PSK , 11b/g/n, 20Mhz, channel 10.
I will mark this post as a solution but I will update in case anything goes wrong.
.
. After I have updated MT3000 to 4.2 beta 2 and set the 2.4GHz network to b/g/n, channel 11, 20MHz it became more stable and I have slowly put more and more sensors and devices on it. Today I am moving the heating on it also to see how it behaves. For now it has part of my esp32 sensors and some 小米 cameras.