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

lennoxuser · April 26, 2026, 7:30pm

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?

admon · April 26, 2026, 7:31pm

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)

lennoxuser · April 27, 2026, 1:13am

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.”

will.qiu · April 27, 2026, 9:27am

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:

xize11 · April 27, 2026, 10:46am

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.

lennoxuser · April 27, 2026, 2:44pm

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:xx:xx:xx
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:xx:xx:xx
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:xx:xx:xx
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:xx:xx:xx
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:xx:xx:xx:24:4c:e3:xx:xx:xx: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:xx:xx:xx:18:74:2e:xx:xx:xx: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:xx:xx:xx:38:f7:3d:xx:xx:xx: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:xx:xx:xx:88:71:e5:xx:xx:xx: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:xx:xx:xx
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:xx:xx:xx
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:xx:xx:xx
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:xx:xx:xx
Mon Apr 27 09:48:44 2026 daemon.info dnsmasq-dhcp[22025]: DHCPOFFER(br-lan) 192.168.8.131 c8:fe:0f:xx:xx:xx
Mon Apr 27 09:48:44 2026 daemon.info dnsmasq-dhcp[22025]: DHCPREQUEST(br-lan) 192.168.8.131 c8:fe:0f:xx:xx:xx
Mon Apr 27 09:48:44 2026 daemon.info dnsmasq-dhcp[22025]: DHCPACK(br-lan) 192.168.8.131 c8:fe:0f:xx:xx:xx
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:xx:xx:xx
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:xx:xx:xx, reason=3

lennoxuser · April 27, 2026, 2:44pm

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.

will.qiu · April 28, 2026, 3:02am

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/

lennoxuser · April 28, 2026, 8:10pm

Thank-you. I believe the MAC address for the thermostat is 88:da:1a:xx:xx:xx

But it may change to this after it fails to connect c8:fe:0f:xx:xx:xx (or to something else).

Maybe the Lennox iComfort M30 is using randomized MAC addresses?

And the thermostat screen doesn’t provide much information but I’ve provided some photos of what it does share:

I’m not using a TP-Link router, I just kept the SSID name the same from when I did.

will.qiu · April 29, 2026, 9:45am

These two MAC addresses are not randomized MACs and belong to different manufacturers, so they are unlikely all to be from the Lennox M30 iComfort.

From the logs, we can see:

88:da:1a:xx:xx:xx can connect to Wi-Fi normally, but does not send DHCP requests, and then disconnects and reconnects after about 8–9 minutes.
c8:fe:0f:xx:xx:xx can connect to Wi-Fi and obtain an IP address normally, but disconnects and reconnects after about 1 minute.

Could you please double-check which MAC address belongs to the Lennox M30 iComfort, and which behavior better matches what you observe (e.g., whether it obtains an IP address)?

Additionally, could you further test the following:

If you configure the 2.4GHz network as Open (no encryption, no password), can the Lennox M30 iComfort connect and access the network normally?
As mentioned earlier, if you install the v4.8.3-op24 version (which uses the open-source Wi-Fi driver), does it help?

lennoxuser · April 30, 2026, 3:53am

I can’t find the thermostat MAC address anywhere but it must be the one that starts with “88” because when I attempt to connect, and as soon as it fails, I rush to look at the system log and that is the only MAC address I’m seeing.

But I also tried connecting with the 2.4 GHz network completely open but it didn’t work and I went back to ver. 4.8.3, but no luck.

I don’t suppose the fact that the Fleet 2 is Ipv.6 (even though it is disabled) has any bearing on this connection issue?

The thermostat apparently connects without a problem but just won’t stay connected. Maybe it can’t reach the Lennox server to verify so something.

I wish I knew if someone else in the world had this exact same thermostat along with the same router, but connected it successfully. But the thermostat works fine, otherwise, I just can’t connect to Wi-Fi or use “Alexa” like I did with the TP-Link Archer AX 55 router.

I might have to breakdown and call Lennox and see if they can offer any insight but I’m doubtful.

will.qiu · April 30, 2026, 8:43am

Thank you for the clarification.

We’ll have our R&D team review the logs and investigate further.

However, our office will be closed soon due to a national holiday, so we may need to continue the review and provide an update after we return on May 6.

lennoxuser · April 30, 2026, 11:13pm

Thanks for trying to help. Real quick, I just wanted to add that a week or two ago I connected my older TP-Link router (that worked with the thermostat) to my Fleet 2 as an access point, but still couldn’t connect to the Internet even after seeing the SSID as usual. Maybe the settings in the MT6000 carried over into the AP. I guess that’s how it works.

lennoxuser · May 1, 2026, 9:33pm

Update: I was finally able to TRY and connect the thermostat to this router with a hotspot from a laptop -– but no luck, so I guess the problem must be with the thermostat although the problem started when I changed routers.

lennoxuser · May 6, 2026, 1:11am

I finally called the local HVAC/R company that installed the unit a few years ago. They said they only installed Lennox systems for one year. Oh well.

Anyway, they couldn’t figures it out, so naturally, they suggested I get a new thermostat and they suggested a Honeywell T6 Pro Smart, which I went for. Actually, it’s a simpler thermostat than the Lennox, but it connected right up to the Wi-Fi and Internet using the MT6000 easily without a hitch.

But thanks for your help.

will.qiu · May 6, 2026, 4:02am

Thank you for the update.

Yes, if the Lennox M30 iComfort is also unable to connect to the original TP-Link or other hotspots, then the issue is likely with the Lennox M30 iComfort device itself.

The timing may just be a coincidence, or the device may have been stuck on the previous AP for some reason and refused to connect to a new one.
In any case, we’re glad to hear that everything is working properly after replacing the device.