Now about 6 days since moving the V2 off the ATT WIFI and it’s still working well. I’m going to call it fixed. Not sure why there would be an issue with the ATT WIFI, but if you have the ATT fiber box for WIFI, try another router.
1 Like
I’m usually just a lurker on these types of forums but glad I was able to help a stranger in a similar predicament.
I am running AT&T fiber it appears the routers that automatically toggle between 2.4 and 5 may be the issue with this doorbell. After fighting for months with the offline issue I ended up installing a netgear nighthawk on the backside of the AT&T router. The netgear has its own radio name for the 2.4 and the 5. I connected all my cameras to the 2.4 wifi only and so far I’ve had four days of uninterrupted service. So the routers that automatically choose connections for 2.4 and 5 may be the issue. I will keep an eye on it further
UPDATE: I purchased an extender for my 2.4Ghz and placed it towards the front of my home and connected both my doorbell v2 and floodlight v2 and they have been good since. I am blaming my att fiber router. Not saying that’s everyone’s issue but it seems like that solved my issue…for now.
1 Like
I did some further testing that adds more evidence to the claim that the ATT BGW320 Wireless Modem/Router is the culprit.
It’s to do with band steering on ATT. Disabled the 2.4GHz radio and things have been very stable. I presume ATT doesn’t handle bandsteering very well, causing the Doorbell to lose connection and not regain it. You do need another Access Point with 2.4GHz to implement this fix, obviously.
Details: Initially I had the 2nd NetGear setup as a duplicate network with same SSID and password. Doorbell was happy to sit on that network. However, any Network person will tell you this creates headaches for devices that look for each other (like airplay, printers). So I fixed it by setting NetGear as AP to have the ATT do the DHCP. Low and behold the issue came back.
I turned off 2.4Ghz on ATT to let all 2.4 traffic connect via NetGear. Everything is stable now.
I did the same thing with my AT&T router. It worked well for 2-3 weeks, but now, after rebooting the doorbell, it goes offline within an hour of being online. I’m not sure if something happened to my doorbell, so I’m waiting for a firmware update.
check the settings on the ATT wifi. Sometimes the settings revert. Make sure 2.4ghz radio is off.
Both of mine are still working great on a different WIFI router.
On the ATT router, I don’t understand how turning off 2.4 could help. I thought this doorbell requires 2.4.
I didn’t disable the 2.4 GHz band; I simply disabled band steering and created separate SSIDs for the 2.4 GHz and 5 GHz bands. It worked well for 2-3 weeks, though I had to reset it every week or so. After each reset, it worked for a minimum of 7-10 days. However, starting last week, the reset is no longer effective. I checked all the settings on my router, and nothing has changed.
in that case, I must adjust my hypothesis to state it’s not band steering that’s the issue, but the 2.4ghz band itself on the ATT router. Getting the device off of ATT is the solution.
1 Like
I think the issue might be related to the AT&T 2.4 GHz band. I’m also an AT&T customer and had a similar problem with my doorbell camera constantly disconnecting. This past weekend, I decided to try a different router — the GL.iNet GL-SFT1200 (Opal) — and it worked like a charm! It’s been 2 days now, and the camera has stayed connected to the 2.4 GHz network on the new router without any issues.
You are correct in that it requires a 2.4ghz. The proposed solution is to get it off the ATT router and onto another router with 2.4ghz.
Been online for a month with my netgear being fed from my AT&T router. No issues since for three properties
That’s good to know. Now I have to look for my old router T_T.
Update!!
I add new router with 2.4 WiFi connect my doorbell. It been 24 hours and my doorbell is still up online.
I had the same WiFi disconnection issue, even thr new door bell didn’t help. I was also connected to AT&T router, separated 5g and 2.4g.
After disabling AT&T 2.4g and connecting to my own netgear router, resolved the issue. It’s up and running since last 2 weeks, without any issue