Video Doorbell can't connect to internet

[isiddiqi]

Hi,

I am using firmware version 3.0.0.6.102_3_0 on my GT-BE98 Pro and having problem with my Eufy E340 doorbell with Mini Chime Homebase connecting via 2.4GHz using WPA2 recently.

Before yesterday, everything was working perfectly, but since yesterday noticed that the Chime was not connected to internet. Tried multiple times to reconnect, but no go, the Chime would say it connected to Wifi but could not connect to internet.

Then I created an IoT network and tried to connect to it, but still understandably see the same issue.

For the heck of it, I tried to connect it to Guest network, and suddenly everything worked fine. Just to verify I retried connecting to main network again, but same issue, no internet. So right now it is working with Guest network without issue.

Both Main and Guest network are using WPA2, ofcourse the IPs are different, I use 10.0.x.x for main and 192.168.x.x for Guest.

I do use Diversion and Skynet, and intend to disable both to see if that makes a difference by chance.

I am hoping someone could give me pointers on what to look for possible differences considering all other devices, including cameras and other IoT work fine on both networks besides this one device that stopped working on main and now only works on Guest network

 

[Tech9]

give me pointers on what to look for

This?

 

[bbunge]

Hi,

I am using firmware version 3.0.0.6.102_3_0 on my GT-BE98 Pro and having problem with my Eufy E340 doorbell with Mini Chime Homebase connecting via 2.4GHz using WPA2 recently.

Before yesterday, everything was working perfectly, but since yesterday noticed that the Chime was not connected to internet. Tried multiple times to reconnect, but no go, the Chime would say it connected to Wifi but could not connect to internet.

Then I created an IoT network and tried to connect to it, but still understandably see the same issue.

For the heck of it, I tried to connect it to Guest network, and sudfenly everything worked fine. Just to verify I retried connecting to main network again, but same issue, no internet. So right now it is working with Guest network without issue.

Both Main and Guest network are using WPA2, ofcourse the IPs are different, I use 10.0.x.x for main and 192.168.x.x for Guest.

I do use Diversion and Skynet, and intent to disable both to see if that makes a different by chance.

I am hoping someone could give me pointers on what to look for possible differences considering all other devices, including cameras and other IoT work fine on both networks besides this one device that stopped working on main and now only works on Guest network

Go back to the default LAN subnet of 192.168.50.0/24

 

[isiddiqi]

But everything had been working fine for over a year, and this happened all of a sudden yesterday...

 

[bbunge]

Bet the doorbell got a firmware upgrade...

 

[aex.perez]

The E340 didn't (mine didn't) but I think the Homebase did...

 

[Poul Bak]

May be the doorbll doesn't use DHCP and have a static ip address on the other subnet.

 

[aex.perez]

The Eufy 340 does use DHCP, got 0 issues in my environment. Connected right up when installed and stays connected and connects over the dedicated 2.4ghz SSID or the or the Smart Connect SSID on my AX88u and it’s nodes. Even though it doesn’t support 5Ghz. Running on battery (replaceable, learned my lesson with my previous Nest Hello) and wired.

The HomeBase (3?) or Mini chime, I can’t speak to those as I don’t have either, but are you getting the videos from the camera on it? Or just that Mini chime isn’t working. Assuming all three show up in the app? And you see all three on the router?

I have it integrated with Alexa, my Echo devices are the chime and on the Samsung TV’s (Alexa Show Doorbell) to see it’s live feed. Didn’t bother with the Homebase for just the doorbell, but when the flood lights get installed, then.

There are a couple of Eufy groups on Reddit, you might have better luck resolving your issue there…

 

[isiddiqi]

Thanks for your reply @aex.perez, appreciate very much.

I am using 2.4GHz and the connection is E340-->Mini Chime-->Router

The E340 connects and send videos to the Chime that has an SD card. The Chime that acts like a Homebase connects to internet. Only Chime would show up on router. And both Doorbell and Chime show up on app with wifi logo that it is connected.

Exact same setup was working fine for over a year with absolutely no issues until one day it just stopped working.

Now, when I connect the Chime to my Guest network on 2.4GHz it works and whenever I try to connect it to main network, it says connected to Wifi but failed to connect to Internet, so I had to assume there was something in router that was blocking the Chime to communicate to internet on main network.

Coming here I was hoping that I would not have to reset the router to factory, but sounds like that is the option I should opt for, just that it is more work to bring everything back to where it is.

I don't think it's a Eufy problem though, sinve it can connect to Guest neywork with zero issues, that is why I decided to come here and not to Reddit.

 

[bennor]

@isiddiqi, are you sure you have fully disabled Diversion and Skynet? If they are disabled what DNS servers are being used by the main LAN WiFi clients? The fact you say it works on Guest Network but not main LAN WiFi would seem to point to an issue with main LAN configuration. Double check you haven't inadvertently enabled the option to block the Internet for the MAC/IP of the Mini Chime under Parental Controls.

What else do you have enabled? Is AiProtection enabled? What other scripts are you running besides Diversion and Skynet? Have you configured a manual IP address for the Mini Chime? Are you blocking any of the DNS addresses used by the Mini Chime? Have you enabled DNS Director? What about VPN, any VPN configured or enabled for main LAN clients or guest wifi clients?

 

[dosborne]

I do use Diversion and Skynet, and intent to disable both to see if that makes a different by chance.

Sounds like the next step before wasting time on anything else.

 

[aex.perez]

@isiddiqi, are you sure you have fully disabled Diversion and Skynet? If they are disabled what DNS servers are being used by the main LAN WiFi clients? The fact you say it works on Guest Network but not main LAN WiFi would seem to point to an issue with main LAN configuration. Double check you haven't inadvertently enabled the option to block the Internet for the MAC/IP of the Mini Chime under Parental Controls.

What else do you have enabled? Is AiProtection enabled? What other scripts are you running besides Diversion and Skynet? Have you configured a manual IP address for the Mini Chime? Are you blocking any of the DNS addresses used by the Mini Chime? Have you enabled DNS Director? What about VPN, any VPN configured or enabled for main LAN clients or guest wifi clients?

While your at it double check that you haven't set any options in the eufy App to disable the ring from the doorbell (E340 settings) and that you have Indoor Chime configured correctly (for the right chime your using). And all the Eufy devices you reference communicate to each other over WiFi, got to add them all in the App to set them up. So what you show from a connectivy perspective is mostly correct, but both acctually connect to the Internet, the E340 sends a Doorbell pess to the chime over WiFi/LAN. Then depending on the chime, USB dongle from the Homebase (2 or 3) to the chime if using those.

Screen shots of the the Eufy App, E340 settings, indoor chime and detail on tso oh the options, for Alexa integration you'll need the Eufy skill.

Hopefully this helps clarify a bit...

 

[isiddiqi]

While your at it double check that you haven't set any options in the eufy App to disable the ring from the doorbell (E340 settings) and that you have Indoor Chime configured correctly (for the right chime your using). And all the Eufy devices you reference communicate to each other over WiFi, got to add them all in the App to set them up. So what you show from a connectivy perspective is mostly correct, but both acctually connect to the Internet, the E340 sends a Doorbell pess to the chime over WiFi/LAN. Then depending on the chime, USB dongle from the Homebase (2 or 3) to the chime if using those.

Screen shots of the the Eufy App, E340 settings, indoor chime and detail on tso oh the options, for Alexa integration you'll need the Eufy skill.

View attachment 63817View attachment 63818View attachment 63819

Hopefully this helps clarify a bit...

Thanks for your reply. I had confirmed this is ok. The Doorbell-Chime-Router combo works on Guest account is, imho, a proof of that too.

Also, when connected to main network, each doorbell press still rings the Chime, it's just that the Chime cannot access internet.

On the weekend I am opting for a router factory reset, let's see how that goes.

 

[isiddiqi]

@isiddiqi, are you sure you have fully disabled Diversion and Skynet? If they are disabled what DNS servers are being used by the main LAN WiFi clients? The fact you say it works on Guest Network but not main LAN WiFi would seem to point to an issue with main LAN configuration. Double check you haven't inadvertently enabled the option to block the Internet for the MAC/IP of the Mini Chime under Parental Controls.

What else do you have enabled? Is AiProtection enabled? What other scripts are you running besides Diversion and Skynet? Have you configured a manual IP address for the Mini Chime? Are you blocking any of the DNS addresses used by the Mini Chime? Have you enabled DNS Director? What about VPN, any VPN configured or enabled for main LAN clients or guest wifi clients?

So, I ensure to fully disable Diversion and Skynet, and also removed the USB and rebooted the router to no avail.

Then as an addon, I also disabled AIProtection, to no avail.

Next I changed my DNS from Cloudflaire to ISP, and even Google, to no avail.

Then I also went in and disabled DNS Director to no avail.

All other devices work perfect with the exception of Eufy that used to work and now only works on Guest network.

I think a router factory reset is probably in order. Will do this weekend. It has to be something in router setting that is causing this, but ironically I had not touched the router for so many weeks.

 

[isiddiqi]

Bet the doorbell got a firmware upgrade...

I checked last FW update was in Dec'2024