after rebooting my raspy with HA running HAOS I only get to the HA CLI. There, the v4 IP address is empty, which explains why I am not able to reach the guy via browser.
During the startup of the system, the following lines/failures appear:
OK - Started network Manager script Dispatcher Service.
XX - (1 of 2) A start job is running for Wait until Kernel Time Synchronised
FAILED to start Network Manager Wait Online
see systemctl status NetworkManager-wait-online.service for details
OK - Reached target Network is online.
A start job is running for Wait Until Kernel Time is synchronized…
OS Version: Home Assistant OS 7.2
HA Core 2021.12.12
I do not know how to reset the network config, a reboot of the system does not help. I changed nothing in my network and only docker has a internal IP of 172.30.X.X - which is strange as I do not use this range in my LAN… so I guess it is Docker-internal.
Any help would be appreciated!
P.S: How do I enter the CLI from the linux OS instead of HA CLI?
in the logs I can find that the internet connection does not work properly, but I do not notice any problems at all with my internet connection… I have access to the Raspi in the HA console, just tried “core restart” -
What else can I do there to solve my prob? Ic can not find any logs
Which means, the GUI at Homeassistent.local is not available or cannot be reached, but the console and PI are still running. When I pull the power plug it reboots and is back, but seems to happen on a daily base…
No, nothing… only one person who said I should I need to check my network, but to be honest I think this is not really the point. It was working within theist days, then started to crash day by day. Now I can see the same errors you posted in your screens.
My problem is, I would love to check any logs, what exactly is happening, but I can not because obviously there is no one who can tell me or there are not further logs. And I can not find any further commands to restart the network manager in the ha console…
My networking manager does not want to start, that’s why I do not get any IP from my DHCP server.
mmh, maybe this might be the problem. If I use the sd card in my normal Mac or win pc, on WIN the boot partition is visible, but nothing more. in Mac OS I can see nothing - is this normal?
only the partition with Hass OS is usable, the other one is not readable. Maybe the sd card is crashed?
Now I rebooted, after trying to access the SSD on my PC, and it works again… got an IP and is working properly. Just needed to install OS 7.3, reboot is done and HA OS still working…
Hmm, I do not know if this solves it… all other devices are running without any problem, I have a 5 Port switch between the PI and the router, but I can not identify any problems within my network…
I had the same issue. It would also cause my pi-hole to not work. When i manually set an IP via DHCP reservation i could get it to take an IP but it would have no internet access.
Cleared all network table data in my pihole and router but still no fix…
The fix for me (for now will see if it happens again) was to switch what port it connected to on my router… I do ISP tech support for a living and this makes no sense why that would fix it but for now it seems to have.
EDIT: My home assistant and pihole each run on a separate raspberry pi4 4GB.
I had the same errors and it turns out that the 10Gbit NIC in my Proxmox server was not connecting (no idea why) while the 1Gbit NIC in the same server was. The Proxmox UI and a VM on the 1Gbit port were connected and working, while HA and OpenSpeedTest VM that both use the 10Gbit port were not accessible. When I took a peek at the console I saw the errors reported above (I had just rebooted the system). Once HA fully booted, I used ha network info to see if it was connected and sure enough it was not connected… a reboot of the server restored the problem but now I have to figure out what the card sometimes does not come up.
