BE 96U loses IoT SSIDs

[wyliec2]

I’ve had a BE96U installed for 6 months with primary, guest and IoT networks defined. The first 4 months it worked flawlessly but the last few weeks, the guest and IoT 2.4 gHz networks will periodically lose their SSIDs and all the IoT devices become disconnected. Once this occurs, the SSIDs disappear and reappear every 5 minutes or so meaning the IoT devices are largely inoperable. A WiFi scan will show the ‘missing’ 2.4 networks’ MAC address but the SSIDs are blank. A continuous scan will show these SSIDs repeatedly disappear, reappear and disappear.

A router reboot restores the SSIDs - for a while - I’ve always had my router do a scheduled reboot weekly. I changed to twice a week but the problem seems to be occurring more frequently.

This is only happening on the 2.4 guest and IoT networks. The primary 2.4 and all of the 5 gHz and 6 gHz networks are fine.

I have automatic firmware updates disabled so that hasn’t changed.

Has anyone else seen something like this?? After months of reliable operation, this is very frustrating…

 

[degrub]

What has changed in the environment from before this started happening ?

Is the router getting overheated ?

Factory reset and manually configure. Don't restore from a backup config. At least, you will start from a known condition.

 

[wyliec2]

What has changed in the environment from before this started happening ?

Is the router getting overheated ?

Factory reset and manually configure. Don't restore from a backup config. At least, you will start from a known condition.

That’s the thing….i got it configured just how I wanted it and haven’t changed it for months…

No overheating - it’s in a cool basement utility room.

 

[OzarkEdge]

That’s the thing….i got it configured just how I wanted it and haven’t changed it for months…

Me, I would follow the advice in post2... then test run a default/minimal configuration to see if the router (2.4 radio/driver) continues to misbehave.

OE

 

[Vrchesch]

I’ve had a BE96U installed for 6 months with primary, guest and IoT networks defined. The first 4 months it worked flawlessly but the last few weeks, the guest and IoT 2.4 gHz networks will periodically lose their SSIDs and all the IoT devices become disconnected. Once this occurs, the SSIDs disappear and reappear every 5 minutes or so meaning the IoT devices are largely inoperable. A WiFi scan will show the ‘missing’ 2.4 networks’ MAC address but the SSIDs are blank. A continuous scan will show these SSIDs repeatedly disappear, reappear and disappear.

A router reboot restores the SSIDs - for a while - I’ve always had my router do a scheduled reboot weekly. I changed to twice a week but the problem seems to be occurring more frequently.

This is only happening on the 2.4 guest and IoT networks. The primary 2.4 and all of the 5 gHz and 6 gHz networks are fine.

I have automatic firmware updates disabled so that hasn’t changed.

Has anyone else seen something like this?? After months of reliable operation, this is very frustrating…

Hey, I just signed up to let you know I have been having the same exact issue. I bought the be96u over the summer and I think I set up an IoT network 3-4 months ago. I have had issues with the IoT network from the beginning. I set up an iPad just to interact with those devices and pretty much every time I open the ipad up I would struggle to get connected to the network. Then came the issue of my Wyze camera and Amazon devices dropping. Then I too started scheduling early morning reboots and I'm not sure it has really helped that much.

More recently I started noticing the wifi on my iphone was acting really strange. The speed wasn't so bad, but there was always a lag before pages would start loading - almost like using satellite internet or something. Today I finally got fed up with the issues and factory reset the thing. The only configuration I have done was adding both networks back with default settings. The strange wifi issue seems to be fixed. If I notice any changes with the IoT network I will check back in. I don't know if I just tinkered around with the settings too much or starting with a clean slate with some of the newer firmware fixed something. BTW, I'm on the latest Merlin.