Weird behavior with BE-86U

[BeachBum77]

So I upgraded from an AC-86U to the BE-86U and ran into something really strange. In setting up the BE I used temporary SSID's and did all my static IP configurations that I needed before I switched over. Then I powered off the old router and renamed the SSID's to match what I had previously. The configuration was a 5Ghz and 2.4Ghz each with unique SSID's as well as a 5Ghz Guest only SSID with it's own unique name. When those all got set everything except a 2.4Ghz Honeywell Thermostat and a 2.4Ghz GE Oven connnected just fine. The other two you could see in the log with the MAC address but it kept repeating wlceventd_proc_event with Assoc, Auth and then Disassoc and Deauth_ind every minute or so. I tried disabling WiFi 7 just to see if that made a difference but nope. Then on a whim I disabled the 5Ghz Guest network and the two devices connected just fine to the 2.4Ghz network! Then I reenabled the guest network but turned on the 2.4Ghz band there as well and did a single SSID for both bands. They both stayed connected for awhile but then the oven eventually started repeating the errors again and disconnected but the thermostat was still rock solid. At this point I disabled the guest network for now and am hoping a future firmware upgrade will resolve this. Just mentioning it all here in case anyone else runs into a similar issue or if anyone has any idea of something else to try. This is all on the most current ASUS firmware I have not installed Merlin on it so far.

 

[CaptainSTX]

So I upgraded from an AC-86U to the BE-86U and ran into something really strange. In setting up the BE I used temporary SSID's and did all my static IP configurations that I needed before I switched over. Then I powered off the old router and renamed the SSID's to match what I had previously. The configuration was a 5Ghz and 2.4Ghz each with unique SSID's as well as a 5Ghz Guest only SSID with it's own unique name. When those all got set everything except a 2.4Ghz Honeywell Thermostat and a 2.4Ghz GE Oven connnected just fine. The other two you could see in the log with the MAC address but it kept repeating wlceventd_proc_event with Assoc, Auth and then Disassoc and Deauth_ind every minute or so. I tried disabling WiFi 7 just to see if that made a difference but nope. Then on a whim I disabled the 5Ghz Guest network and the two devices connected just fine to the 2.4Ghz network! Then I reenabled the guest network but turned on the 2.4Ghz band there as well and did a single SSID for both bands. They both stayed connected for awhile but then the oven eventually started repeating the errors again and disconnected but the thermostat was still rock solid. At this point I disabled the guest network for now and am hoping a future firmware upgrade will resolve this. Just mentioning it all here in case anyone else runs into a similar issue or if anyone has any idea of something else to try. This is all on the most current ASUS firmware I have not installed Merlin on it so far.

My Honeywell thermostat is also problematic for me. I depend on it when traveling to alert me of HVAC issues back at home and on the day of my return to set the AC to a cooler temperature.

I have the thermostat connected to guest network 1. Guest network 1 uses a different subnet than my primary network uses so you can't assign static IPs to devices connecting to this SSIDs at least through the GUI. This guest network 1 has its own SSID and isn't shared with the 5 Ghz radio on guest network 4 To accommodate my IoT devices I had to dumb down my 2.4 Ghz band and use WPA2 on all radios. Lots of discussion on this forum the WiFi setting to tone down or disable to get IoT devices to connect and stay connected to wiFi. My thermostat now connects most of the time though it is usually the last device to come back on line after a router reboot.

I also tried to use SSIDs from prior routers and some IoT devices when trying to connect can't deal with the subtle changes between the old and new router. Bigger issue now with the transition from AC - AX than the change from N to AC. My Alexa devices seem to be very resistant to WiFi radio changes so I finally gave up having them work reliably on a previously used SSID and created a guest network for them to use exclusively.

Good luck with getting your thermostat to connect reliably. It can be done it will just take some trial and error and research on this forum.

In hindsight It probably would have been easier just use an old router double NATed either in front of or behind my AX88 Pro for IoT devices so for WiFi other devices could utilize all the current features and settings.