Thermostat network problem, RT-AX88U Pro on 3006.102.4

[JGrana]

With 3006.102.4, no. It wouldn't connect. Didn't matter what combination of settings I tried.

Once I reverted to 3004.388.8_4, with the network settings at the defaults, it connected immediately.

This is a wipe before update, update, wipe, configure from scratch on 3006.102.4, and same procedure downgrading to 3004.388.8_4.

My ecobees connect fine with both 3004.XXX and 3006.XXX.
Just saying ;-)

 

[ApexRon]

I have an older Honeywell thermostat that looks like this:

Initially I had WiFi connection issues though the AC86U was in line of site, 10 ft away. I determined that there were many other WiFi nearby using the same channel. I moved the 2.4 GHz channel to another lesser used one and no longer had any issues until my WiFi router started having radio issues. The thermostat WiFi connection has been a rock since I replaced router with an AX86U-Pro.

 

[bluzfanmr1]

My ecobees connect fine with both 3004.XXX and 3006.XXX.
Just saying ;-)

I bought my first wifi thermostat, an ecobee, a few months ago and love it and haven't had any connection issues. They have had a few hiccups lately with the app though, and eco+ has stopped pre-cooling the house, but I believe it's my power company and not ecobee.

 

[Clark Griswald]

I also have an older Honeywell thermostat (same as ApexRon), and I have not had any issues since updating to RMerlin's latest. I placed the thermostat on the GNP IoT (isolated).

 

[The_Bishop]

The Honeywell thermostat I had was the older design without the digital interface display, and I'm banking that it just had an antique wifi chip that wasn't going to work.

The new Sensi Touch-2 has been working flawlessly, and everything on the network has been rock-stable once I re-installed 3004.388.8_4 and configured from scratch. For some reason or another I wasn't able to just re-load the saved config file I had made prior to the upgrade, gave the router strange issues, like missing pages in the config screens.

 

[CaptainSTX]

The Honeywell thermostat I had was the older design without the digital interface display, and I'm banking that it just had an antique wifi chip that wasn't going to work.

The new Sensi Touch-2 has been working flawlessly, and everything on the network has been rock-stable once I re-installed 3004.388.8_4 and configured from scratch. For some reason or another I wasn't able to just re-load the saved config file I had made prior to the upgrade, gave the router strange issues, like missing pages in the config screens.

102.5 beta1 adds back support for AES/TKIP which in my setup seems to be required/useful in getting my Honeywell to connect and staying connected. Once 102.5 is final release I plan to see if I can connect the thermostat to my AX88 Pro and eliminate the travel router that I use as an AP now.

 

[The_Bishop]

Since I have everything stable now, I'll wait for the 102.5 to hit release status. Don't know why I couldn't just re-load my old configuration file once I down-graded, but it is what it is.

 

[chateau]

I recently upgraded to an Asus RT-AC86U Pro running Merlin 3006.102.4 and created a new IOT WiFi network to put all my IOT devices in.

The new IOT network has a couple of special characters along with numbers and characters in the WiFi password. Every IOT device, including Wyze cameras, Smart Plugs, etc. connected without issue except a Honeywell WiFi thermostat that has been around for probably ten years or more and has always worked flawlessly in the past on my old WiFi guest network.

After searching around on the Internet for answers, I found a post somewhere on a Honeywell site or whatever advising to not use special characters in the WiFi password since older Honeywell thermostats would not work with them.

As a test I created a second IOT network without special characters in the WiFi password just for the Honeywell thermostat and it connected without issue and has been working reliably ever since. This thermostat is the only device in that IOT network.

For reference, both the IOT network with special characters in WiFi password and the other one without special characters in WiFi password are both set to WPA2-Personal and 2.4 Ghz only.

Correction: My thermostat is a Honeywell RTH6850WF1001 per label on back of thermostat.

 

[CaptainSTX]

I recently upgraded to an Asus RT-AC86U Pro running Merlin 3006.102.4 and created a new IOT WiFi network to put all my IOT devices in.

The new IOT network has a couple of special characters along with numbers and characters in the WiFi password. Every IOT device, including Wyze cameras, Smart Plugs, etc. connected without issue except a Honeywell WiFi thermostat that has been around for probably ten years or more and has always worked flawlessly in the past on my old WiFi guest network.

After searching around on the Internet for answers, I found a post somewhere on a Honeywell site or whatever advising to not use special characters in the WiFi password since older Honeywell thermostats would not work with them.

As a test I created a second IOT network without special characters in the WiFi password just for the Honeywell thermostat and it connected without issue and has been working reliably ever since. This thermostat is the only device in that IOT network.

For reference, both the IOT network with special characters in WiFi password and the other one without special characters in WiFi password are both set to WPA2-Personal and 2.4 Ghz only.

My thermostat is a Honeywell RTH6500

View attachment 66741

I have the same model thermostat, and I have had problems getting it to connect to my primary router using firmware prior 102.5 beta1 so I installed an old travel router as an AP for use only by the thermostat and no issues even though the SSID has two special characters so I'm not sure your solution will work for everyone. I also had no issues with the thermostat connecting to a Netgear R7000 running Tomato and again the SSID had special characters.

 

[chateau]

I have the same model thermostat, and I have had problems getting it to connect to my primary router using firmware prior 102.5 beta1 so I installed an old travel router as an AP for use only by the thermostat and no issues even though the SSID has two special characters so I'm not sure your solution will work for everyone. I also had no issues with the thermostat connecting to a Netgear R7000 running Tomato and again the SSID had special characters.

Strange as mine would not connect at all with special characters in password. Correction on my model number, mine is a Model RTH6850WF1001 per label on back of thermostat.