Could you make it work? Having the same problem here
@aecfxi Thanks for this guide. really clear. got me past the loading screen. I had to do this twice but it was a me (or rather my equipment issue) as as soon as I had resolved the ipv4 dns issue my sd card was having a bad day. I’ve bought a new 32gb sandisk one and redid everything. It has definitely worked. Very happy that i can move on to trying to save some money by storing my solar energy now.
How do I change the screen resolution on Odroid C4?? really, REALLY tiny!! seems like it is on 4K!!
put SD in my windows machine, NO config.txt file is there! any CLI command to get something like
“raspi-config”?
Home Assistant should boot with a configurator on the actual host (Rpi or whatever) before going on… that would help a LOT! like a step by step configurator for network, screen resolution, etc!
Thanks. This solved the problem to me. In my case DNS name to be set had to be the my PIHole DNS address
Adding my two cents. Loading HAOS on an HP t620 with Ubuntu. Had to ignore auto dns. Had to set the dsn twice (used 1.1.1.1), as it seemed not to stick the first time. walked away and did chores for the day. It finally went through and let me register. Thank you!!
Is this same fix applicable to Pi3+?
I’m having the same issue in which “network info” still shows 192.168.1.1. When I do a host restart, I get the same 500 error. Someone else posted you had to do one extra command:
So after the command described in the article:
set ipv4.dns 1.1.1.1
additionally enter:
set ipv4.ignore-auto-dns yes
After doing that I no longer got the 500 errors.
1 Like
This was a live saver. Thanks a lot.
I’ll explain my situation, so that someone might recognize it.
I bought a bigger sdcard. Flashed it with home assistant OS. Powered up the Raspberry Pi 4. Everything went ok. After A few minutes (10), I got to the onboarding screen. There I choose to upload a backup. Fifteen minutes later I could log in with my existing credentials at the_ip_adres:8123 So far so good… I was pleased. Then All my addons where grayed out. But the log stated they actually started. I read somewhere here to restart the host.
I did…
Then the addons weren’t grayed out anymore. I tried to install an new addon but the system said I couldn’t connect. (to the internet) I tried to install addguard and had to put Home Assistant on a fixed IP adres. So I did. Then restarted the host.
Then things went wrong.
The whole system hung at the ‘preparing home installation’ screen. I waited 45 minutes and then I found this post.
I did all steps.
I did a last check of the network info and supervisor log like the text says. Network info didn’t state that the dns, so I feared all steps failed. But the supervisor log showed all green text and no red errors anymore.
On my pc I could navigate to home assistant and this time it proceeded to the install screen. So I reckoned that everything was ok, allthough the network info didn’t state the dns.
I put back the backup. It took 20 minutes. And after that all seems to work flawless.
Thanks for this post. It helped a lot.
1 Like
I had the issue of supervisor not having internet, came across this and didn’t help. Then I realized that my system date was wrong. So I did this:
- typed login to go into different cli
- typed date --set=“2022-12-07 07:00” where the date is your current date
- typed exit
- typed host reboot
and it started to work
1 Like
I followed the Solution provided by the op, however, this did not fully resolve my problem. This was my experience:
After performing the command: set ipv4.dns 1.1.1.1, I was able to verify the new dns setting (1.1.1.1) using “print”. However, after I did a host restart, while there were no boot errors displayed, when the host restarted, the dns setting (1.1.1.1) had been lost. Moreover, there were persistent errors in the supervisor logs, and the stalled/hanged “Preparing Home Installation” screen persisted.
However, if I used the Solution modification provided by meyerdenney (adding: set ipv4.ignore_auto-dns yes), then after the host restart command the HAOS booted successfully (no boot errors and no supervisor log errors) and the HAOS started remotely without stalling at the “Preparing Home Installation” screen (although it took several minutes to finish, as expected).
So for me, the extra command to set ipv4.ignore_auto-dns yes was critical. Thank you all for providing your help. You really saved my bacon.
This was the solution for me. Thanks!
I’m also unable to get the nmcli settings to stick. I update them, print shows that they are present, I enter save and exit and host restart, but when I go back to nmcli the settings have been reset.
How do I get these to stick on a VM?
For users in China: home assistant pulls docker image from ghcr.io, which is blocked in China. A free network is needed.
1 Like
I’ve tried all the suggestions here, many times over, but the settings won’t stick.
I’ve done a couple of previous installs with no issue but on one site decided to separate Frigate and HA to dedicated RPis. I gather the issue may be trigged by attempting a setup with another HA instance already on the network? Can not believe how tedious this is!!!
I’m trying to figure out why the incorrect settings are persisting in a fresh install of the OS…could anything be achieved by setting up the box first with rapsbian? [makes no sense clutching at straws…]
well turned out there was [also] a problem with time not being set preventing the network booting. the steps here yielded success.
Thanks much! I was beating my head against the wall with the DNS change and came across this post. Success! Thank you again for posting.
I had exactly the same situation, but I was restoring HASS yellow - and possibility to access CLI didn’t exist. However, in Asus router, I forced HASS DHCP IP and DHCP DNS server to external (not the router) DNS server. That did the trick and I got rid of “Preparing Home Installation” dialog and forward.
You are a F’in hero! This works…took 2 min after the reboot to get to the final setup. Thank you very much for the great detail!
OMG!!! I might be late to the party, but THANK YOU!!!
I have been trying to get this to work for 2 weeks with no luck. And 10 min after finding your post I got HA up and running.
Thank you for this. It fixed my issue.