Tried connecting to my Netgear modem (which provides the internet to my house) directly by shutting down HA and VMware (since I run HA in a VM), connecting to the Netgear modem, and then restarting VMware and the home assistant instance. Within a few minutes of starting, everything just magically worked again. I then connected back to the eero but I do not know if it’s going to disappear again.
What’s very interesting is that the repositories in HACS show up just fine, even on the eeros. It can get information from GitHub just fine. When I click on a custom integration to get its info it works perfectly. I did not try installing a custom integration from there but I will try later.
That doesn’t seem to have worked for me. I just made these changes in Eero, reboot the Eero network, then reboot the HA’s exhibiting this issue and no joy.
I’ve also just tried a fresh install of 5.13 on a Pi 4 and that device is having the issue.
So with a fresh install of their respective official images on each:
Pi 3 Home Assistant OS 5.13 - Official add-ons are visible (if I remember correctly I was able to see Community Add-ons below the Official Add-ons when it was first set up and now I cannot)
Pi 4 Home Assistant OS 5.13 - No add-ons visible
NUC Home Assistant OS 5.13 - No add-ons visible
I’m using a net gear modem as well. How did you access HA when connected directly to the modem? I tried this yesterday also but wasn’t able to access HA.
@dwindecker
I had actually had this same issue — had to make sure the network settings were set to Auto/DHCP (while connected to Eero, of course), then shut down home assistant before disconnecting from eero and reconnecting to the Netgear. Afterwards I restarted HA and I was able to access it by connecting my computer to the modem (my Netgear modem is also a router) and going to my ha url. Within minutes the repositories show up.
Just started my HA up again today and the repositories still show up on the eero. They install perfectly fine too even on the eero. I do not know if the repositories install locally or downloads and then installs – but it has worked perfectly and when I started up HA I did not receive the 128 exit code error in the supervisor logs. I didn’t change anything in the eero app but I have noticed I have been getting SERVFAIL DNS errors for tuyaus.com. My tuya devices have been working fine and I can still control them. No github.com SERVFAIL though – at least yet.
UPDATE: Just got the servfail for api.github.com when trying to update an HACS integration but it appears to update just fine. I believe this may be because of the DNS caching from the Netgear? I am not too sure but things seem to be working fine for now. I will keep updating as I get more information about the issue.
I finally learned that I could import a snapshot without having any add-ons at all so I’m back on the NUC but still no access to any add-ons other than what was installed on the snapshot I imported. From HA terminal I am able to ping just about every address on the web except GitHub. GitHub.com returns bad address. Https://GitHub.com returns bad port spec.
I am able to ping from every other device on my network (except the NUC and Pi4 HAs).
I’ve added 8.8.8.8, 8.8.4.4, 9.9.9.9, and 1.1.1.1 to HA dns to no avail.
Anyone have any ideas?
thank you netjedi, i’ve tried some of yours suggestion but the addons are still missing.
if i ping 8.8.8.8 and dnslookup to github.com the results are:
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=114 time=8.814 ms
64 bytes from 8.8.8.8: seq=1 ttl=114 time=8.733 ms
64 bytes from 8.8.8.8: seq=2 ttl=114 time=8.666 ms
64 bytes from 8.8.8.8: seq=3 ttl=114 time=8.630 ms
64 bytes from 8.8.8.8: seq=4 ttl=114 time=8.940 ms
64 bytes from 8.8.8.8: seq=5 ttl=114 time=9.534 ms
64 bytes from 8.8.8.8: seq=6 ttl=114 time=8.811 ms
64 bytes from 8.8.8.8: seq=7 ttl=114 time=8.330 ms
^C
--- 8.8.8.8 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 8.330/8.807/9.534 ms
~ $ nslookup -debug github.com
Server: 127.0.0.11
Address: 127.0.0.11#53
------------
QUESTIONS:
github.com, type = A, class = IN
ANSWERS:
-> github.com
internet address = 140.82.121.4
ttl = 10
AUTHORITY RECORDS:
ADDITIONAL RECORDS:
------------
Non-authoritative answer:
Name: github.com
Address: 140.82.121.4
------------
QUESTIONS:
github.com, type = AAAA, class = IN
ANSWERS:
AUTHORITY RECORDS:
-> github.com
origin = ns-1707.awsdns-21.co.uk
mail addr = awsdns-hostmaster.amazon.com
serial = 1
refresh = 7200
retry = 900
expire = 1209600
minimum = 86400
ttl = 10
ADDITIONAL RECORDS:
------------
I can’t use nmcli because the command is not found. i don’t think its a issue with the virtual environment because for 4-5 days everything was working fine and i’ve done any configuration change! About the network cap…i’m sorry but i’ve no idea what is about.
I’ve also tried ha dns option as you suggested. and in Supervisor → System → Host → IP Address the ip is 192.168.1.128/24 which is the ip of the host.
I can my home assistant core and supervisor without any problem, and also the integration and HACS are working fine.
This is definitely not a DNS, firewall, or 32/64-bit issue as I’ve tried both with fresh installs. Clearly something is broken. I’m hopeful the issue and subsequent fix here (https://github.com/home-assistant/supervisor/pull/2901) resolves the issue.
None of this is working for me either. I’ve even swapped the Eero 6 Pro gateway for an Eero 5 Pro just to make sure I covered everything I could. Toggled every possible setting. Edited Eero’s DNS to add 8.8.8.8. Tried HA Beta installs. Nothing it working.
Hi folks, just a quick update.
I have had an open issue with eero support for a number of months now since the problem arose.
One temporary workaround / kludge is to:
Disconnect your phone from local WiFi (so it is direct to Internet via 4G etc)
Enable WiFi hotspot on your phone
Setup the HA box to connect to WiFi (using the SSID etc of your mobile hotspot)
Shutdown the HA box, disconnect LAN cable
Startup the HA box which should hopefully now connect to WiFi
Leave it up for approx 30mins (allows it to refresh repos)
Connect to the HA box using the HA phone app - confirm status of repos etc
Connect LAN cable back to HA box
Disable phone hotspot
With any luck you will have (at least for a while) - up to date repos and normal connectivity. If not, reboot the HA box again.
Other thoughts
Ideally we need to capture the DHCP negotiation flow when direct to the Internet vs through an eero.
The setup would involve a switch with span / mirror capability and a mac/pc with wireshark.
Hope this helps
Works best if using Nabucasa (as it helps find the device again from the phone)
I’ve turned ON HomeKit security in Eero and set the Home Assistant Bridge item inside HomeKit app > Home > Home Settings > WiFi Network & Routers to “No Restriction”. A reboot of the network followed by a reboot of home assistant and I can now see Official Add-ons and no longer get SERVFAIL when doing an NSLOOKUP of github.com from HA.
eero pro 6’s here and only recently (in the last week) enabled HomeKit security inside the eero app.
Was not aware of the additional step inside the Apple HomeKit app. I expect that this will override any weird default rules that eero had established.
Whilst not ideal, I had been using a multi-homed network setup (with separate access paths - one outside of the eeros) as a workaround (i.e. one for updates from the Internet, the other for the IoT network) - which works but causes other problems.
Eero must choose to place restrictions on some devices regardless of whether HomeKit security is enabled. I had HomeKit enabled at some point last year when my network was all Eero 5 Pros. When I added the 6’s they were not compatible with HomeKit. I had to remove all of the 6’s in order to disable HomeKit and then re-add the 6’s. Good times that was. Seems the only way to change that default restriction is to do it through HomeKit.
Wow, I didn’t even have HomeKit enabled on my HomeAssistant instance (but HomeKit security has been enabled on my eero), and I got bit by this. Just tried adding it as a HomeKit bridge so I’ll now have the ability to set to No Restriction in the Home app. Sheesh, what a mess…
Yet again, I updated HA to the latest release (2021.6), then Re-enabled Advance Security on Eero Pro 6, then rebooted HA. Same issue re-appeared again after 12 hours or so. Disabling Advanced Security and reconfiguring add-ons again…
