New owner of a Home Assitant Green box.
I didn’t believe the warning on the wall that factory resetting would could cause more problem that it would solve.
Anyway, the deed is done and I’ve factory resetted without taking any backup.
I’m currently unable to access anyway through the network. I can ping the box, but there is nothing responding on 8123
I plugged a display and a keyboard on the box to investigate, and I’m on the emergency console.
Investigating the boot sequence, I can see that it "Failed to start Wait until-wait-sync.service and points me toward the systemd-time-wait-sync.service.
Afterwards, it tries to start HassOS AppArmor, then the emergency cli shows up. I’ve also waited a few hours.
In the cli, I am unable to ping my router/gateway (192.168.2.1), but, as stated previously, other machine can ping the Home Assistant Box.
In the nmcli, I confirm that the inet4 address is the static IP i’ve setup in my router for the box. The network mask is allow 192.169.2.0\24 as expected.
I also can see in the log that the machine time is way off. The date command gives me “2024-10-08 […]”.
Before I go out to buy a SDCard and an SDCard Reader to flash this thing, I would like to know if any of you have experienced something like this, since I’ve not found a working solution previously.
My first theory would be to try to understand why the box can’t ping the router, when the router can ping the box.
The journalctl -e is ending with a lot of “homeassistant systemd-resolve[416]: :5:185mmUsing degraded feature set [UDP|TCP] instead of of [TCP|UDP] for DNS server [ip1 | ip2]”
Did you install the optional CR2032 button cell to keep the time?
Strange fix? There have been reports of the update process stopping due to incorrect time [epoch time 1/1/1970] making some critical security certificates invalid. Once the time is correct (or close), the NTP sync later in the update process will take over, and all should be well until next time you power off.
A gotcha that could have been completely avoided by just adding the battery in the box to start with.
When I made the first post, I tried setting the time with the command date '2026-01-07 12:13:14, when the time was UTC.
It didn’t seems to make pinging the internet work.
Today, I did three things at the same time, so I can’t be sure about what fixed what.
Firstly I inserted a CR2032 battery in the slot.
Secondly, I moved my Home Assistant Green Box next to my PC, and I tethered its wifi through the ethernet port. I was sick of debugging in the living room.
(https://superuser.com/a/1295683)
Thirdly, I changed the clock time again with date '2026-01-10 00:01:02 using the current UTC time (It was set at a 2025 date when I plugged the box), but I also changed the hardware clock using the command hwclock --systohc
(https://unix.stackexchange.com/questions/151547/linux-set-date-through-command-line) I was previously set at an 1991-xx-xx date.
Following this command, I was now able to ping 8.8.8.8.
I will now wait an hour to see if the install goes through, and will report back.
Currently, I can now see with docker ps -a that a "/init" command is running for the hassio_supervisor
Edit:
I have rebooted the devices, and the installation went through as desired.
I can now login through the web interface.