#Howdy All,

1 messages · Page 1 of 1 (latest)

native needle
#

New to HA, Installing on a Raspberry Pi 5 8gb.
Used the Raspberry pi Imager 1.9.6 to install HA OS 16.1 (RPI5) Released 2025-08-13
Booted up, was able to open URL in a browser and get errors main two being:
can't find hassio_observer: 404 Client Error
Fatal error happening on load Task <coroutine object Core._adjust_system_datetime at 0x7f91c4c9a0>: Automatic time synchronization is enabled

Assuming I need to set the time / date manually, just don't know how to do it.
That I am hoping will also resolve the additional errors:

WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec

https://paste.debian.net/1391657

Edit. Looks like timezone set itself correctly. Not sure re date and time. Attached few screenshots of info hoping someone can help.

Thank you

IMG_3317.png IMG_3316.png IMG_3315.png IMG_3314.png
lean marlin
#

Are you blocking NTP in some way?

#

What does ha network info say?

#

Also check timedatectl status. You might have to enter login first.

native needle
#

Thank you.

No NTP blocking on my end. Is there a way I can test if my isp blocks it using my pc?

Couldn't figure out how to exit the HA terminal to enter the timedatectl status command. Is there another way?

Network showing IP address and looks ok.

lean marlin
#

You might have to enter login first.

native needle
#

I decided to create a new image using a different micro SD card but sadly I get the same errors 😢

how does one login?

lean marlin
#

enter login

native needle
#

Sorry. Still not following. Enter 'login' at the HA prompt? What's the default user / password?

lean marlin
#

Just root.

native needle
#

sorry, I'm super new to this. Not sure what you mean

lean marlin
#

The username is root. No password.

native needle
#

ah ty

#

Yup. Date is set to 2024.

IMG_3322.jpg
lean marlin
#

You can manually set the time with that tool.

native needle
#

Dang. Tried and got error.

IMG_3323.jpg
lean marlin
#

Hmm. Hold on.

native needle
#

All g. No rush. Appreciate the help.

lean marlin
#

Maybe your router forces a specific invalid NTP server or something?

#

What does journalctl -ru systemd-timesyncd say?

native needle
lean marlin
#

Hmm.

native needle
#

I'm guessing ntp block / date time not set right being the issue, but I'm blocked in changing the time

lean marlin
#

Not quite sure how best to fix this. Does normal networking such as ping 1.1.1.1 work?

native needle
#

yep, pinged 1.1.1.1, 192.168.1.1 and google.com all said alive!

lean marlin
#

Seems like 123.200.159.123 is provides by your ISP. Iseek?

native needle
#

im through Aussie bradband, which use optus

#

testing on home pc, times out to that ip address too

#

just tried pinging from mobile on a different network and got 100% packet loss too 🙁

lean marlin
#

Not all servers respond to pings or are accessible via HTTP. Doesn't have to mean anything.

# 
# nc -w3 -vzu 123.200.159.123 123
(UNKNOWN) [123.200.159.123] 123 (ntp) open
#

So basically it seems like your router provides this as NTP server but the server does not respond to you. I have no clue why.

native needle
#

no worries, I'll hit up my ISP and get them to check

#

Thank you so much for the help

lean marlin
#

I might have one idea we can try. Run this

echo "NTP=time.cloudflare.com" >> /etc/systemd/timesyncd.conf
systemctl restart systemd-timesyncd.service

Then check

timedatectl status
timedatectl show-timesync
journalctl -ru systemd-timesyncd
native needle
#

Did I make any typos?

IMG_3328.jpg
#

Ah 2.coms

lean marlin
#

Gotta get a handle on the typos.

native needle
#

gotta love the keyboard on ground plugged into 80" tv

lean marlin
#

Having the NTP key twice might cause issues. You need to get familiar with vi to fix that file.

native needle
#

Sorry if orders out. The journal command returned. No data.

lean marlin
#

The time looks okay now though, right?

#

reboot and see if the problems go away.

native needle
#

yup, that's fixed it

#

I don't know what we did, but you are a champ !

#

Thank you

lean marlin
#

The DHCP provided NTP server has priority in HAOS. The one your router provides just doesn't work and we made the system prefer time.cloudflare.com. You will have that problem again in the future unless you fix the bogus NTP server your router gives out.

native needle
#

ah so my router is the issue in terms of underlying cause

#

and it's the last lot of commands that fixed it switching to cloudflare

lean marlin
#

Basically just the first one here: #1405714791166640179 message
The one below it is to restart the service so it reads the config again. The other commands are just to verify.

native needle
#

rebooting would restart the service too?

lean marlin
#

Yep, of course.

native needle
#

I'll document the fix on my reddit post too, saw plenty of people with the same error, never found solutions though

lean marlin
#

Just be aware that many similar sounding problems can have wildly different root caused and fixes.

#

I think this is the first time I've seen a bogus NTP server here.

native needle
#

no worries, I'll document it from the perspective of my hardware

lean marlin
#

Do you mind linking the post?

native needle
lean marlin
#

Do you know your router model? Maybe I can figure somethng out.

native needle
#

Deco X10

lean marlin
native needle
lean marlin
#

Hmm. Seems like this is just a modem without real router or extra functionality so if that's all you have you might be out of luck here.
How is the pi itself connected to the network?

native needle
#

NBN box (ie the Cm8200B -> Deco - <cable from the Deco to Pi

lean marlin
#

Then unfortunately I don't think you can do anything here. Not a fan of the deco. It doesn't even have a web interface it seems.

native needle
#

and a very minimal app to control it too

#

Sincerely, thank you. I would have had no idea