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.
1 Like
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)
1 Like
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.
1 Like
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.
I did so, but i have the same problem 
I updated HA to the latest release (yesterday), then Re-enabled Advance Security on Eero , then rebooted HA. All seems fine, it’s been over 12 hours. Maybe something within HA got updated that fixed this?
UPDATE: After another 24 hours, they slowly start disappearing again… I will disable Advance Security again.
Followed the advice in the last entry for this issue and it seems to have helped.
Other options are:
- Periodically shutting down and connecting the device directly to an internet connected modem/router - so it can get updates etc
- multi-homing the device (not advisable or a good security option) into a network that is not behind an eero
i’m using win10 as a host and ha os as guest with vmware workstation. I don’t have any amazon eero. how can i try to fix the time issue?
Hi @davrte , although I am not on win10 or vmware, the issue seems to most often relate to DNS resolution. I would start by debugging what networking works from the command line in ha.
- Can you ping 8.8.8.8?
- does an nslookup of github.com work?
- does using the nmcli commands below change the outcome of this:
nmcli conn modify “System eth0” ipv4.ignore-auto-dns yes
nmcli conn modify “System eth0” ipv4.dns “1.1.1.1 8.8.8.8”
systemctl restart NetworkManager
- Other things to check on a virtual environment:
- routing
- local network filtering or firewalls (especially when dealing with VMware virtual interfaces etc)
- As you can control both devices, I would also suggest looking at a basic network packet cap for all DNS related traffic to see if you can see where things are breaking
- What does the Supervisor → System → Host → IP Address content say? Is the DNS set to the local host and blocking queries. Also worth checking the VMWare networking mode to confirm this is as expected.
As it is some time since I played with vmware, I’m afraid thats as much as I can think of off the top of my head.
Also worth trying this:
ha dns options --servers dns://1.1.1.1
ha dns restart
After which I would re-try the above networking tests
I have this same problem (also on Eeros), but none of the above suggestions have provided a fix…
Eero has a new update version 6.3.1 which I’m waiting to show up on my end. Let us hope this fixes the issue for us here.
I have this same problem on the Eeros. On my old Cox Panoramic WiFi Gateway it worked but ever since we got rid of that ISP modem router and upgraded to the eeros and using our own modem we have been having issues… I changed the WiFi card settings in Windows to have DNS server 1.1.1.1
I am also running VMware on windows and have done the suggestions listed above.
Here are my logs:
21-05-13 14:05:58 INFO (MainThread) [supervisor.store.git] Cloning add-on https://github.com/home-assistant/addons repository
21-05-13 14:06:03 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/home-assistant/addons repository: Cmd('git') failed due to: exit code(128)
cmdline: git clone -v --recursive --depth=1 --shallow-submodules --progress https://github.com/home-assistant/addons /data/addons/core.
21-05-13 14:06:03 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.FATAL_ERROR - ContextType.STORE / core
21-05-13 14:06:03 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.EXECUTE_REMOVE - ContextType.STORE / core
21-05-13 14:06:03 ERROR (MainThread) [supervisor.store] Can't load data from repository core
21-05-13 14:06:03 INFO (MainThread) [supervisor.store] Loading add-ons from store: 0 all - 0 new - 0 remove
21-05-13 14:06:03 INFO (MainThread) [supervisor.addons] Found 4 installed add-ons
I just saw the new release as of today. I will try it out…
UPDATE: It took a long time for the update to show up. It finally did, I applied the latest firmware release and it did NOT correct the issues.