#To install Home Assistant on my Raspberry Pi 5, I had to use my phone's data connection by tethering

1 messages · Page 1 of 1 (latest)

reef dragon
#

When the Raspberry Pi was connected to my home Wi-Fi, it kept giving me an error that the supervisor couldn't connect to the internet. I also noticed the time was completely wrong. I tried pinging Google's DNS servers from the shell, and that worked, which proved the Raspberry Pi had internet access but couldn't get the correct date and time or connect to proceed with the installation. So, I switched to using my phone's hotspot by connecting an ethernet cable from my phone's USB-C port to the Raspberry Pi, and this allowed the installation to complete.

My provider is Eolo, and I can't open ports because I don't have a static IP address. I also don't even have a router page to access and configure things (I know it's strange, but if I literally try to connect to the gateway's IP address, nothing exists).

This issue where the supervisor couldn't connect initially—could it be a problem in the future? Right now, Home Assistant works even on my home network, and with Dataplicity, I can connect to it remotely and it communicates fine with external services like Google, but I'm sure the supervisor problems will reappear.

Do you have any advice or information?

glacial goblet
#

Where did you plug the pi into before?

reef dragon
glacial goblet
#

Can you connect it again and share ha network info?

reef dragon
reef dragon
glacial goblet
#

That looks okay. Maybe NTP is blocked on your main network?

reef dragon
#

how can i check that?

#

maybe with a ping from the console?

reef dragon
glacial goblet
#

I think it uses time.cloudflare.com but pinging it is very different than using NTP.

reef dragon
#

if make sense testing

glacial goblet
#

You need a NTP client but HAOS makes that a pain.

reef dragon
glacial goblet
#

Not sure. Guess we'll see.