Will the GL MT6000 work with a Lennox M30 iComfort Thermostat?

Because it does not seem it will although all my other IoT devices had no problem. I had a TP-Link router before and it seemed to work fine with it. I was looking on the Lennox site regarding the m30 and it did not list a GL.inet as one of the recommended routers for connectivity (but TP-Link wasn’t either).

The thermostat sees my separate 2.4 ghz SSID but can’t connect. I tried everything in the world by finally had some of the system logs analyzed by AI and learned that the problem was NOT due to any of these issues:

WPA/WPA2 issue
Signal strength
DHCP failure
Router blocking ports 80/443

It further said that the thermostat connects successfully, but then fails during its internal setup / cloud communication and drops the connection. Says I am dealing with a network-level restriction or compatibility issue immediately after Wi-Fi connection and it provided several suggestions.

Anybody else know anything about what’s going on here with these two products?

Check if your thermostat can use the channel and bandwidth you selected. Some devices cannot use 40 MHz, for example. And some other devices cannot use channel 13 on 2.4 GHz (I remember that my old Nintendo DS wasn't able to use those "high" channels)

1 Like

Thanks. I’ve literally tried everything but it is currently set to WPA2-PSK on mode 11b/g/c, 20 MHz on channel 6.

Through the logs, I’ve learned that the thermostat connects to Wi-Fi successfully every time…but immediately disconnects before completing network setup.

That almost always means:

“Something on the network (DNS, filtering, or compatibility) is causing it to give up after connecting.”

Hi

Could you try connecting the Lennox M30 to the MT6000 a few times, then export the logs and send them to us via private message so we can review?

How to export logs:

How to send private messages:

Additionally, we suggest trying the OP24 version to see whether the open-source Wi-Fi driver helps.
Download link:

Upgrade guide:

Note that when changing the cipher or encryption you must do the network wizard again on your thermostat, you may want to reset it or forgot the network.

Because some ioT devices just get stuck on a cipher and will not want to acknowledge changes making it disconnect/stuck.

Also another issue can be the mixed variations like wpa2 mixed, or wpa3/wpa2 mixed, they don't always work on some devices, for the most stablest approach I would go with WPA2, and first try with ccmp (yes, you need to reset devices network), if that is not working you can choose a weaker cipher.

(which is not what I recommend but then you need to question if the device is meeting your security standards on your full network), I prob would replace it, because the weaker cipher like tkip are alot more insecure and there are vulnerabilities.

Also in case if you enabled a more advanced option:

802.11W (managed frame protection), will only work on devices which support it, if it doesn't and your wireless does not have it set to optional or disabled, the client will just disconnect, this also happens btw appart from this option if dhcp fails to work.

Sorry, but I had trouble exporting the log and sending it as a private message so I used the process through the admin page accessing customer support. Hope that’s OK.

But date is slightly newer than what a sent a little while ago.

Mon Apr 27 09:48:08 2026 kern.warn kernel: [142279.771212] 7986@C08L2,ap_peer_disassoc_action() 3645: ASSOC - 1 receive DIS-ASSOC request
Mon Apr 27 09:48:08 2026 kern.warn kernel: [142279.779597] 7986@C01L2,wifi_sys_disconn_act() 1002: wdev_idx=0
Mon Apr 27 09:48:08 2026 kern.notice kernel: [142279.785918] 7986@C08L3,hw_ctrl_flow_v2_disconnt_act() 172: wdev_idx=0
Mon Apr 27 09:48:08 2026 kern.warn kernel: [142279.793010] 7986@C13L2,MacTableDeleteEntry() 1938: Del Sta:88:da:1a:34:0c:c0
Mon Apr 27 09:48:09 2026 kern.debug kernel: [142281.201184] entrytb_aid_aquire(): found non-occupied aid:11, allocated from:8
Mon Apr 27 09:48:09 2026 kern.warn kernel: [142281.208422] 7986@C13L2,MacTableInsertEntry() 1577: New Sta:88:da:1a:34:0c:c0
Mon Apr 27 09:48:09 2026 kern.notice kernel: [142281.218828] 7986@C08L3,ap_cmm_peer_assoc_req_action() 1714: Recv Assoc from STA - 88:da:1a:34:0c:c0
Mon Apr 27 09:48:09 2026 kern.notice kernel: [142281.228316] 7986@C08L3,ap_cmm_peer_assoc_req_action() 2241: ASSOC Send ASSOC response (Status=0)...
Mon Apr 27 09:48:09 2026 kern.notice kernel: [142281.237503] 7986@C01L3,wifi_sys_conn_act() 1115: wdev idx = 0
Mon Apr 27 09:48:09 2026 kern.notice kernel: [142281.243641] 7986@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=0
Mon Apr 27 09:48:09 2026 kern.notice kernel: [142281.373966] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Mon Apr 27 09:48:10 2026 kern.notice kernel: [142282.393984] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Mon Apr 27 09:48:10 2026 kern.notice kernel: [142282.400744] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2
Mon Apr 27 09:48:10 2026 kern.notice kernel: [142282.407465] 7986@C15L3,WPABuildPairMsg3() 5595: <=== send Msg3 of 4-way
Mon Apr 27 09:48:10 2026 kern.notice kernel: [142282.414205] 7986@C15L3,PeerPairMsg4Action() 6734: ===>Receive msg 4
Mon Apr 27 09:48:10 2026 kern.warn kernel: [142282.425760] 7986@C15L2,PeerPairMsg4Action() 7098: AP SETKEYS DONE(ra0) - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=4 from 88:da:1a:34:0c:c0
Mon Apr 27 09:48:10 2026 kern.warn kernel: [142282.425760]
Mon Apr 27 09:48:23 2026 kern.warn kernel: [142294.658903] IN=br-lan OUT= MAC=94:83:c4:d1:10:fe:24:4c:e3:c2:d5:ac:08:00 SRC=192.168.8.238 DST=192.168.8.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=10713 DF PROTO=ICMP TYPE=8 CODE=0 ID=56026 SEQ=28087
Mon Apr 27 09:48:27 2026 kern.warn kernel: [142299.245484] IN=br-lan OUT= MAC=94:83:c4:d1:10:fe:18:74:2e:90:e0:ae:08:00 SRC=192.168.8.106 DST=192.168.8.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=40921 DF PROTO=ICMP TYPE=8 CODE=0 ID=56026 SEQ=19447
Mon Apr 27 09:48:28 2026 kern.warn kernel: [142299.945253] IN=br-lan OUT= MAC=94:83:c4:d1:10:fe:38:f7:3d:0e:01:39:08:00 SRC=192.168.8.208 DST=192.168.8.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=50100 DF PROTO=ICMP TYPE=8 CODE=0 ID=56026 SEQ=15389
Mon Apr 27 09:48:32 2026 kern.warn kernel: [142303.557872] IN=br-lan OUT= MAC=94:83:c4:d1:10:fe:88:71:e5:c1:e9:79:08:00 SRC=192.168.8.129 DST=192.168.8.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=14935 DF PROTO=ICMP TYPE=8 CODE=0 ID=56026 SEQ=982
Mon Apr 27 09:48:43 2026 kern.debug kernel: [142315.373804] entrytb_aid_aquire(): found non-occupied aid:26, allocated from:8
Mon Apr 27 09:48:43 2026 kern.warn kernel: [142315.381040] 7986@C13L2,MacTableInsertEntry() 1577: New Sta:c8:fe:0f:25:e3:54
Mon Apr 27 09:48:43 2026 kern.notice kernel: [142315.399746] 7986@C08L3,ap_cmm_peer_assoc_req_action() 1714: Recv Assoc from STA - c8:fe:0f:25:e3:54
Mon Apr 27 09:48:43 2026 kern.notice kernel: [142315.409134] 7986@C08L3,ap_cmm_peer_assoc_req_action() 2241: ASSOC Send ASSOC response (Status=0)...
Mon Apr 27 09:48:43 2026 kern.notice kernel: [142315.418307] 7986@C01L3,wifi_sys_conn_act() 1115: wdev idx = 0
Mon Apr 27 09:48:43 2026 kern.notice kernel: [142315.424464] 7986@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=0
Mon Apr 27 09:48:44 2026 kern.notice kernel: [142315.553692] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Mon Apr 27 09:48:44 2026 kern.notice kernel: [142315.568301] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2
Mon Apr 27 09:48:44 2026 kern.notice kernel: [142315.574983] 7986@C15L3,WPABuildPairMsg3() 5595: <=== send Msg3 of 4-way
Mon Apr 27 09:48:44 2026 kern.notice kernel: [142315.581684] 7986@C15L3,PeerPairMsg4Action() 6734: ===>Receive msg 4
Mon Apr 27 09:48:44 2026 kern.warn kernel: [142315.593287] 7986@C15L2,PeerPairMsg4Action() 7098: AP SETKEYS DONE(ra0) - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=19 from c8:fe:0f:25:e3:54
Mon Apr 27 09:48:44 2026 kern.warn kernel: [142315.593287]
Mon Apr 27 09:48:44 2026 daemon.info dnsmasq-dhcp[22025]: DHCPDISCOVER(br-lan) c8:fe:0f:25:e3:54
Mon Apr 27 09:48:44 2026 daemon.info dnsmasq-dhcp[22025]: DHCPOFFER(br-lan) 192.168.8.131 c8:fe:0f:25:e3:54
Mon Apr 27 09:48:44 2026 daemon.info dnsmasq-dhcp[22025]: DHCPREQUEST(br-lan) 192.168.8.131 c8:fe:0f:25:e3:54
Mon Apr 27 09:48:44 2026 daemon.info dnsmasq-dhcp[22025]: DHCPACK(br-lan) 192.168.8.131 c8:fe:0f:25:e3:54
Mon Apr 27 09:48:56 2026 kern.warn kernel: [142327.896497] 7986@C01L2,wifi_sys_disconn_act() 1002: wdev_idx=0
Mon Apr 27 09:48:56 2026 kern.notice kernel: [142327.902766] 7986@C08L3,hw_ctrl_flow_v2_disconnt_act() 172: wdev_idx=0
Mon Apr 27 09:48:56 2026 kern.warn kernel: [142327.909856] 7986@C13L2,MacTableDeleteEntry() 1938: Del Sta:c8:fe:0f:25:e3:54
Mon Apr 27 09:48:56 2026 kern.notice kernel: [142327.917168] 7986@C08L3,ap_peer_deauth_action() 437: AUTH - receive DE-AUTH(seq-5) from c8:fe:0f:25:e3:54, reason=3

I just sent you the most recent logs after trying to log in a couple of times.

Also, my Fleet 2 came with version 3.8.3, think, and I was contemplating upgrading to 3.8.4 but then decided, what the heck, I went ahead and installed the beta version 4.9.0 a few days ago. You think that was okay? Didn’t seen to affect anything one way another, before or after.

I tired the new separate IoT network earlier but it didn’t work either.

We checked the logs, and it appears that multiple different devices are attempting to connect to the MT6000.
Could you provide the MAC address of the Lennox M30 so we can confirm further?

Additionally, this device seems to have a screen that can display connection-related information.
Could you share any error messages shown after attempting to connect it to Wi-Fi?

Some other users have reported that although the device can connect to the network, it may fail to connect to the server due to time synchronization issues.
It might be worth checking the following:
https://www.reddit.com/r/hvacadvice/comments/q60df1/yet_another_lennox_icomfort_user_who_cannot/