You were using b/g/n/ax previously ?
To be honest my experience so far, 2.4g ax is much more backwards compatible than 5g ax
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 .
Well there’s also this difference between a750s and mt3000: former is Qualcomm chipset and latter mediatek chipset
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 
1 Like
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.
The Yaml file used to program the M5 Atom is :
esphome:
name: bedroom
esp32:
board: m5stack-atom
framework:
type: arduino
# Enable logging
logger:
# Enable Home Assistant API
api:
encryption:
key: "eXh5TvtGe1ybPAPZThCQUcGWycF4kIzyKp0epWHf4qM="
ota:
password: "fceb4ac977dbfbe73a80eaf8bbd06678"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Bedroom Fallback Hotspot"
password: "aC0PYJyt1wXR"
captive_portal:
i2c:
sda: 26
scl: 32
scan: true
id: bus_a
sensor:
- platform: sht3xd
i2c_id: bus_a
temperature:
name: "Bedroom Temperature"
humidity:
name: "Bedroom Humidity"
address: 0x44
update_interval: 60s
Aside from these, I also use a Shelly Plus 1 Relay with firmware : 20221206-141227/0.12.0-gafc2404
Warm Regards,
Misujr
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.
Here is the esp32 log:
[I][logger:258]: Log initialized
[C][ota:469]: There have been 0 suspected unsuccessful boot attempts.
[D][esp32.preferences:113]: Saving 1 preferences to flash...
[D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[I][app:029]: Running through setup()...
[I][i2c.arduino:175]: Performing I2C bus recovery
[C][wifi:037]: Setting up WiFi...
[C][wifi:038]: Local?MAC: E8:31:CD:08:4B:B8
[D][wifi:386]: Starting scan...
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'GL-MT3000-241' (94:83:C4:28:32:43) �y�{�}��
[D][wifi:446]: Channel: 5
[D][wifi:447]: RSSI: -60 dB
[D][wifi:450]: - 's10-production' (E4:95:6E:47:8C:D4) �y�{�}��
[D][wifi:450]: - 'Hans' (94:83:C4:08:3B:90) �y�{�}��
[D][wifi:450]: - 'GL-AX1800-0a6-Guest' (94:83:C4:12:E0:A9) �y�{�}��
[D][wifi:450]: - 'GL-MT3000-17c' (94:83:C4:22:71:7E) �y�{�}��
[D][wifi:450]: - 'GL-AXT1800-d7e' (94:83:C4:18:7D:80) �y�{�}��
[D][wifi:450]: - '1X329-AXT1800-99c-Guest' (96:83:C4:18:59:9E) �y�{�}��
[D][wifi:450]: - 'KNBA5F00002F' (00:A0:03:97:00:8C) �y�{�}��
[D][wifi:450]: - 'GL-AXT1800-b9c' (94:83:C4:18:1B:9E) �y�{�}��
[D][wifi:450]: - '1X326-AXT1800-99c' (94:83:C4:18:59:9E) �y�{�}��
[D][wifi:450]: - 'GL-AX1800-cbc' (94:83:C4:16:EC:BE) �y�{�}��
[D][wifi:450]: - 'GL-AXT1800-d7a' (94:83:C4:18:7D:7C) �y�{�}��
[D][wifi:450]: - 'GL-B1300-dc6' (94:83:C4:06:DD:C6) �y�{�}��
[D][wifi:450]: - 'GL-A1300-898' (94:83:C4:1D:C8:9A) �y�{�}��
[D][wifi:450]: - 'GL-S1300-cb2' (E4:95:6E:47:8C:B4) �y�{�}��
[D][wifi:450]: - 'GL-AX1800-f42' (00:03:7F:12:66:47) �y�{�}��
[D][wifi:450]: - 'GL-AXT1800-da7-23' (94:83:C4:18:7D:A9) �y�{�}��
[D][wifi:450]: - 'test' (E4:95:6E:40:B6:2D) �y�{�}��
[D][wifi:450]: - 'GL-AXT1800-b73' (94:83:C4:22:2B:75) �y�{�}��
[D][wifi:450]: - 'GL-B1300-9aa' (E4:95:6E:45:19:AA) �y�{�}��
[D][wifi:450]: - 'GL-MT1300-21d' (94:83:C4:20:E2:1F) �y�{�}��
[D][wifi:450]: - 'GL-AXT1800-02f' (94:83:C4:1F:30:31) �y�{�}��
[D][wifi:450]: - '' (7C:A1:77:E6:8B:21) �y�{�}��
[D][wifi:450]: - 'GL-MT3000-1a4' (94:83:C4:22:71:A6) �y�{�}��
[D][wifi:450]: - 'GL-AR750S-fd2' (94:83:C4:0B:EF:D2) �y�{�}��
[D][wifi:450]: - 'GL-AR750-0c2' (94:83:C4:06:00:C2) �y�{�}��
[D][wifi:450]: - 'HUAWEI-2G/5GBand' (7C:A1:77:E6:8B:1C) �y�{�}��
[D][wifi:450]: - 'GL-AR750S-c9c' (94:83:C4:07:0C:9C) �y�{�}��
[D][wifi:450]: - 'GL-AX1800-cdb' (00:03:7F:BA:DB:B0) �y�{�}��
[D][wifi:450]: - 'GL-A1300-5da' (94:83:C4:1C:35:DA) �y�{�}��
[D][wifi:450]: - 'JZT-Work' (80:8F:1D:CF:36:22) �y�{�}��
[D][wifi:450]: - 'GL-AR750S-cf1' (94:83:C4:07:7C:F1) �y�{�}��
[D][wifi:450]: - 'GL-SFT1200-978' (94:83:C4:12:59:7A) �y�{�}��
[D][wifi:450]: - 'GL-A1300-838' (94:83:C4:1D:C8:3A) �y�{�}��
[D][wifi:450]: - '187A1-MT3000-230' (94:83:C4:22:72:32) �y�{�}��
[D][wifi:450]: - 'dddd' (94:83:C4:0D:F1:B4) �y�{�}��
[D][wifi:450]: - 'aaaa2gGUEST' (9A:83:C4:0D:F1:B4) �y�{�}��
[D][wifi:450]: - 'GL-INET-2G' (94:83:C4:04:B4:48) �y�{�}��
[D][wifi:450]: - 'GL-Clam-2.4' (94:83:C4:18:7E:2D) �y�{�}��
[D][wifi:450]: - 'KNBA5F000041' (00:A0:03:97:00:C2) �y�{�}��
[D][wifi:450]: - 'GL-MT3000-254' (94:83:C4:22:72:56) �y�{�}��
[D][wifi:450]: - 'GL-A1300-81c' (94:83:C4:1D:C8:1E) �y�{�}��
[D][wifi:450]: - 'GL-MT300N-test' (94:83:C4:10:93:98) �y�{�}��
[D][wifi:450]: - 'GL-A1300-860' (94:83:C4:1D:C8:62) �y�{�}��
[D][wifi:450]: - 'GL-A1300-860-Guest' (96:83:C4:1D:C8:62) �y�{�}��
[D][wifi:450]: - '802.1r-AR750S' (94:83:C4:15:E7:EA) �y�{�}��
[D][wifi:450]: - 'GL-AX1800-84a' (94:83:C4:14:18:4C) �y�{�}��
[D][wifi:450]: - 'GL-A1300-8cb' (94:83:C4:1D:28:CD) �y�{�}��
[D][wifi:450]: - 'GL-AR750S-7ea-Guest' (96:83:C4:15:E7:EA) �y�{�}��
[D][wifi:450]: - '178AX2-AR150-984' (96:83:C4:04:59:84) �y�{�}��
[D][wifi:450]: - 'GL-AR750S-62e-Guest' (96:83:C4:06:26:2E) �y�{�}��
[D][wifi:450]: - 'GL-X750-8c8-Guest' (96:83:C4:03:18:CA) �y�{�}��
[D][wifi:450]: - 'GL-AXT1800-d8b' (94:83:C4:1F:2D:8D) �y�{�}��
[D][wifi:450]: - 'GL-XE300-6e9' (94:83:C4:06:76:EB) �y�{�}��
[D][wifi:450]: - 'GL-MT3000-58f' (94:83:C4:24:45:91) �y�{�}��
[D][wifi:450]: - 'GL-INET-2G' (34:F7:16:AF:BC:11) �y�{�}��
[D][wifi:450]: - '' (36:F7:16:5F:BC:11) �y�{�}��
[D][wifi:450]: - 'GL-AXT1800-9a0' (94:83:C4:18:59:A2) �y�{�}��
[D][wifi:450]: - 'HKGLinet-2G' (94:83:C4:21:EA:61) �y�{�}��
[D][wifi:450]: - 'GL-SFT1200-c82' (94:83:C4:19:CC:84) �y�{�}��
[D][wifi:450]: - 'GL-MT3000-194' (94:83:C4:22:71:96) �y�{�}��
[D][wifi:450]: - 'GL-AX1800-fa4' (94:83:C4:24:4F:A6) �y�{�}��
[D][wifi:450]: - 'GL-AR750S@EAP-62e' (94:83:C4:06:26:2E) �y�{�}��
[D][wifi:450]: - 'GL-S200-6d3' (94:83:C4:23:86:D3) �y�{�}��
[D][wifi:450]: - 'GL-X750-8c8' (94:83:C4:03:18:CA) �y�{�}��
[D][wifi:450]: - 'GL-A1300-8b3' (94:83:C4:1D:28:B5) �y�{�}��
[D][wifi:450]: - 'RMS-668F' (6C:B1:58:CF:66:8F) �y�{�}��
[D][wifi:450]: - 'GL-A1300-8b3-Guest' (96:83:C4:1D:28:B5) �y�{�}��
[D][wifi:450]: - 'A-SLAM' (A8:5A:E0:A4:0C:F4) �y�{�}��
[D][wifi:450]: - 'GL-MT3000-178' (94:83:C4:22:71:7A) �y�{�}��
[D][wifi:450]: - 'GL-AXT1800-d9f' (94:83:C4:18:7D:A1) �y�{�}��
[D][wifi:450]: - 'Youku-2BAD' (54:36:9B:0F:2B:AE) �y�{�}��
[D][wifi:450]: - '' (9A:97:CC:7B:26:3C) �y�{�}��
[D][wifi:450]: - 'RMS-D85D' (EC:60:73:31:D8:5D) �y�{�}��
[D][wifi:450]: - '' (F6:2A:7D:22:08:81) �y�{�}��
[D][wifi:450]: - 'ChinaNet-E9pM' (A0:4C:0C:23:15:02) �y�{�}��
[D][wifi:450]: - 'ChinaNet-2Xjn' (58:C6:7E:B2:A9:94) �y�{�}��
[I][wifi:257]: WiFi Connecting to 'GL-MT3000-241'...
[I][wifi:518]: WiFi Connected!
[C][wifi:362]: Local MAC: E8:31:CD:08:4B:B8
[C][wifi:363]: SSID: 'GL-MT3000-241'
[C][wifi:364]: IP Address: 192.168.8.227
[C][wifi:366]: BSSID: 94:83:C4:28:32:43
[C][wifi:367]: Hostname: 'bedroom'
[C][wifi:369]: Signal strength: -55 dB �y�{�}��
[C][wifi:373]: Channel: 5
[C][wifi:374]: Subnet: 255.255.255.0
[C][wifi:375]: Gateway: 192.168.8.1
[C][wifi:376]: DNS1: 192.168.8.1
[C][wifi:377]: DNS2: 0.0.0.0
[D][wifi:527]: Disabling AP...
[C][ota:093]: Over-The-Air Updates:
[C][ota:094]: Address: bedroom.local:3232
[C][ota:097]: Using Password.
[C][api:025]: Setting up Home Assistant API server...
[I][app:062]: setup() finished successfully!
[I][app:102]: ESPHome version 2022.11.3 compiled on Jan 4 2023, 11:56:21
[C][wifi:504]: WiFi:
[C][wifi:362]: Local MAC: E8:31:CD:08:4B:B8
[C][wifi:363]: SSID: 'GL-MT3000-241'
[C][wifi:364]: IP Address: 192.168.8.227
[C][wifi:366]: BSSID: 94:83:C4:28:32:43
[C][wifi:367]: Hostname: 'bedroom'
[C][wifi:369]: Signal strength: -56 dB �y�{�}��
[C][wifi:373]: Channel: 5
[C][wifi:374]: Subnet: 255.255.255.0
[C][wifi:375]: Gateway: 192.168.8.1
[C][wifi:376]: DNS1: 192.168.8.1
[C][wifi:377]: DNS2: 0.0.0.0
[C][logger:293]: Logger:
[C][logger:294]: Level: DEBUG
[C][logger:295]: Log Baud Rate: 115200
[C][logger:296]: Hardware UART: UART0
[C][i2c.arduino:052]: I2C Bus:
[C][i2c.arduino:053]: SDA Pin: GPIO26
[C][i2c.arduino:054]: SCL Pin: GPIO32
[C][i2c.arduino:055]: Frequency: 50000 Hz
[C][i2c.arduino:058]: Recovery: bus successfully recovered
[I][i2c.arduino:068]: Results from i2c bus scan:
[I][i2c.arduino:070]: Found no i2c devices!
[C][captive_portal:088]: Captive Portal:
[C][mdns:103]: mDNS:
[C][mdns:104]: Hostname: bedroom
[C][ota:093]: Over-The-Air Updates:
[C][ota:094]: Address: bedroom.local:3232
[C][ota:097]: Using Password.
[C][api:138]: API Server:
[C][api:139]: Address: bedroom.local:6053
[C][api:141]: Using noise encryption: YES
Thanks,
kelly
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.
Warm Regards,
Misujr
Hi Misujr,
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.
Thanks,
kelly
1 Like
5g wifi is always disabled? Or is it same ssid?
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.)
We tested the firmware you supplied, but because there is no upper device (HA) to communicate with esp32, esp32 automatically restarts.
[I][app:102]: ESPHome version 2022.12.3 compiled on Dec 28 2022, 11:27:20
[C][wifi:504]: WiFi:
[C][wifi:362]: Local MAC: E8:31:CD:08:4B:B8
[C][wifi:363]: SSID: 'GL-AR750S-35a'
[C][wifi:364]: IP Address: 192.168.8.227
[C][wifi:366]: BSSID: 94:83:C4:28:32:43
[C][wifi:367]: Hostname: 'bedroom'
[C][wifi:369]: Signal strength: -58 dB ▂▄▆█
[C][wifi:373]: Channel: 9
[C][wifi:374]: Subnet: 255.255.255.0
[C][wifi:375]: Gateway: 192.168.8.1
[C][wifi:376]: DNS1: 192.168.8.1
[C][wifi:377]: DNS2: 0.0.0.0
[C][logger:293]: Logger:
[C][logger:294]: Level: DEBUG
[C][logger:295]: Log Baud Rate: 115200
[C][logger:296]: Hardware UART: UART0
[C][i2c.arduino:052]: I2C Bus:
[C][i2c.arduino:053]: SDA Pin: GPIO26
[C][i2c.arduino:054]: SCL Pin: GPIO32
[C][i2c.arduino:055]: Frequency: 50000 Hz
[C][i2c.arduino:058]: Recovery: bus successfully recovered
[I][i2c.arduino:068]: Results from i2c bus scan:
[I][i2c.arduino:070]: Found no i2c devices!
[C][sht3xd:029]: SHT3xD:
[C][sht3xd:030]: Address: 0x44
[E][sht3xd:032]: Communication with SHT3xD failed!
[C][sht3xd:034]: Update Interval: 60.0s
[C][sht3xd:036]: Temperature 'Bedroom Temperature'
[C][sht3xd:036]: Device Class: 'temperature'
[C][sht3xd:036]: State Class: 'measurement'
[C][sht3xd:036]: Unit of Measurement: '°C'
[C][sht3xd:036]: Accuracy Decimals: 1
[C][sht3xd:037]: Humidity 'Bedroom Humidity'
[C][sht3xd:037]: Device Class: 'humidity'
[C][sht3xd:037]: State Class: 'measurement'
[C][sht3xd:037]: Unit of Measurement: '%'
[C][sht3xd:037]: Accuracy Decimals: 1
[C][captive_portal:088]: Captive Portal:
[C][mdns:103]: mDNS:
[C][mdns:104]: Hostname: bedroom
[C][ota:093]: Over-The-Air Updates:
[C][ota:094]: Address: bedroom.local:3232
[C][ota:097]: Using Password.
[C][api:138]: API Server:
[C][api:139]: Address: bedroom.local:6053
[C][api:141]: Using noise encryption: YES
[I][ota:113]: Boot seems successful, resetting boot loop counter.
[D][esp32.preferences:113]: Saving 1 preferences to flash...
[D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[E][api:127]: No client connected to API. Rebooting...
[I][app:127]: Forcing a reboot...
[W][wifi_esp32:494]: Event: Disconnected ssid='GL-AR750S-35a' bssid=94:83:C4:28:32:43 reason='Association Leave'
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13132
load:0x40080400,len:3036
entry 0x400805e4
[I][logger:258]: Log initialized
Can you remove the reboot logic? Maybe your device going offline also related to this reboot?
Hi Kelly,
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.
BR,
Misujr
Update :
I have experienced the same issues I was claiming before but now I have found the culprit.
In first tests I have stupidly forgot to mention that I also had a USB3.0 Stick connected to the router. A decent USB stick from San Disk 32GB link here .
After I have updated to fw 4.2.0 beta 2 I have not connected the usb stick to the router.
All my tests after the update were without the usb stick and jus tnow I have plugged the USB stick and the entire network became unstable. The 5GHz SSID was appearing and disappearing and the 2.4GHz SSID associated IoT devices started to connect and disconnect. I have removed the USB stick after a few minutes and immediately the router returned to normal. I have attached here the kernel leg between plugging the USB stick and disconnecting the usb stick. It ended up being a 24page long log so whoever will read it will need a beer or a coffee
kernel log usb stick.pdf.zip (90.1 KB)
1 Like
Thanks for your feedback. We will check it.
Also may I ask, are you using the power adapter that came with MT3000?
I am using a different adapter as I need a longer power cable.
I use this power adapter with a 2m cable that is 100W emarked and tested to carry up to 100w. So basically the power shouldn’t be an issue unless the router has difficulty to handle the PD standard but as it powers up when connected to the emarked cable, I assume the implementation of the PD standard is good or it is using 5.1k resistors on the PD line which will give it 5V and 3A .
BR,
Misujr
Software version 4.4.5
a few days ago everything was ok. Today I wanted to scan the list of available wifi networks and it doesn’t find any one. When adding a Wi-Fi network manually, I also cannot connect. I decided to restore the factory settings, after logging in again there was still no wifi available.
I have a Mudi 750 router turned on next to it, so I can see many networks available. On the mt3000, none of them.
What could be the reason?
Not even one?
Is the wifi of MT3000 itself OK?
I checked everything again today.
I have two rutets next to each other
MUDI 750 and the are a lot of available networks - everything is OK.
Below are screenshot from MT3000 (connected via LAN cable) with the current software version is 4.4.5 compile time 2023-08-11
Picture shows list of detected networks → none .On the same screen is a window from computer’s Wi-Fi card, you can see many available networks.
You can also see the available network of the MT3000 itself
also after entering the network manually, i cannot connect.
I can send the logs but I need to know which ones.