Finally fixed the problem. Was an Amazon eero with latest update that seemed to have been causing all of the carnage.
After doing all of the above and relocating directly to an alternate Internet route - all working and demons purged.!!
Good Luck guys!
Thanks, got it working
Can you provide any additional information here? Been struggling with this for months on one of my two on-site homeassistant instances – both on the same network, both behind an eero system, one works and the other doesn’t…
Same problem here
ERROR (MainThread) [supervisor.store.repository] Can't remove built-in repositories!
So the problem seems to have been caused by one of the eero updates and some caching of bad DNS records.
I fixed the problem by shutting down then relocating ha to connect directly to the Internet (in front of the eero). I then started it up, waited 15mins (for it to refresh everything) then turned it off (as i could not easily access the newly allocated DHCP address from my border router)
After putting it back where it was and powering up again - all sorted.
I also found this which allows for editing HA OS networking config. which was helpful in debugging.
The problem went away for a while then came back.
Lead me to this page:
https://adam.younglogic.com/2019/05/using-nmcli-to-set-nameservers/
The key sections were (where “System eth0” is the network name) :
nmcli conn modify “System eth0” ipv4.ignore-auto-dns yes
nmcli conn modify “System eth0” ipv4.dns “192.168.24.7 8.8.8.8”
systemctl restart NetworkManager
Clearly some behaviour has changed in HA that is in conflict with the way eero is issuing DNS updates
Sadly (after having all of this working) it has now reverted to its previous broken state.
[very frustrated - perhaps one of the devs can offer another suggestion]
Symptoms are still the same - i.e. the HA box cannot resolve GitHub.com
[update] I have just asked the eero folks whether i can downgrade to the previous eero version - this is driving me nuts.
[update] So from the command line I have noticed that the resolution seems to be happening at the docker level. Adding new name servers into /etc/resolv.conf does not appear to help. Does someone know how to update DNS inside docker?
There is a “Local DNS caching” option in the Eero configuration. HAs anyone tried disabling that?
UPDATE: I tried that, and no changes…
I was experiencing this issue on a new install. In the HA command prompt “info” would return an issue with the date/time. It was resolved with the recommendations above. I had to reboot to Raspi OS. There I changed the boot order to wait for network in the GUI. I checked that the time and local were accurate. In the command prompt I activated NPT as described here:
Hope this helps!
UPDATE: I connected my HA server directly on the internet instead of Eero, rebooted, waited 5 minutes, reconnected it behind Eero without rebooting and everything came back magically. This is really strange… But so far so good.
Sadly the problem seems to recur after about 12 hours - perhaps dhcp lease time?
Hi Northwood!
I might be asking a silly question, but i’m just amateur on this 
and i have been struggling with time configuration issue for so long.
If you are using the timedatectl command as all the other commands indicated on the guide you refered to, this means you have installed the Home Assitant container version on a Debian 10 or Raspbian OS, haven’t you? Because is it possible to reconfigure the time through the timedatectl command on the Home Assistant OS install version? i mean were do you type it?
I’m asking this because i have struggled for a long time with this time confguration issue that doesn’t allow the access to the addons repository, for the Home Assistant OS intall version. But the i saw that installing the docker version on Debian 10 for example, will allow me to access to the console command and then disable the NTP time sincronization:
sudo timedatectl set-ntp false
force the change of time:
sudo timedatectl set-time ‘Y:M:D HH:mm:ss’
and then enabling back again the NTP… The problem now is that i have no idea but i have other problems with the docker installation…
So basically i was wondering weather I could go back on installing the Home Assistant OS version, and from there force the time confirguration.
I hope i have been able to make myself understandable 
Thx in advance for your comments.
I am also using docker and have no idea how to change the date and time on it. The times in the log are definitely out for some of the logs - so this is a distinct possibility.
Anyone know how to fix this issue for a docker based install?
I’m running HA on a RPi 4 from SSD. I configured the RPi 4 with RPi OS that had been loaded onto a SD prior to loading HA from the SSD. To fix my issue I had to shutdown HA and unplug my SSD, reload my initial RPi OS image on the SD card to make changes, and then reload my SSD with HA. When I got to prompt and ran “info” I could see that my date/time issue was fixed and once I logged in all the repositories were there.
This is my first install so I’m sorry if I’m not much help. I’ve just gained enough from reading here that I thought I’d chime in.
Issue is slowly back again. Repository by repository, it’s acting up again. Is this an HA issue or a Eero issue? Has anyone contacted and raised an issue with Amazon?
Has anyone reported this issue to Eero? Is any HA dev involved in looking at this?
I contacted Eero and they’re trying to see what’s going on, but I’m afraid their recommended next step will be to completely reset and redo my configuration, which I don’t want to do.
Thanks!
Disabled “Advanced Security” in eero and all repositories came back to life 
Discover → eero Secure → Advanced Security (disabled)
Same here, they are slowly coming back after disabling Advanced Security… Thanks!
I have an open issue with eero and also pointed them to this forum.
Tried all of their suggestions to no avail.
Suggested next steps are to get a packet cap on the HA box of the DHCP negotiation with / without eero involved.
Based on my current analysis i expect that there is an error in the DHCP leasing process that results in the issue. This explains why having the device receive its DHCP info from another source and then putting it back behind the eero works for a short time and is then broken after the lease period expires.
Just attempting another trick to see if we can force DNS correctly.
From the “Supervisor” side menu - select “System” then use the “Host” card to change the IP address.
This will bring up the options for network settings. After first confirming that you have set the DHCP lease to permanent on your router, change this to Static and add the DNS Servers manually - e.g. “8.8.8.8, 1.1.1.1” (without the quotes)
Then save. I will report back how this goes - hopefully it will work and bypass the weirdness being broadcast from the eeros.
[update] - also disabled IPV6 as part of the debugging process.