HAOS 2026.9.2 & several HACS integrations cloud based down

Installation Home Assistant OS
1

After upgrade I had several notifications telling at least 3 of my HACS integrations all with API connections were not loaded.

image
image1666×762 115 KB

For Vigieau :

Cette erreur provient d'une intégration personnalisée.

Logger: custom_components.vigieau
Source: helpers/update_coordinator.py:512
Intégration: Vigieau (Documentation, Problèmes)
Première occurrence: 11:00:11 (1 occurrence)
Dernier enregistrement: 11:00:11

Error fetching vigieau api data: Error communicating with API: Cannot connect to host api.vigieau.beta.gouv.fr:443 ssl:default [DNS server returned answer with no data]```

For met.no

Logger: homeassistant.components.met.coordinator
Source: helpers/update_coordinator.py:512
Intégration: Meteorologisk institutt (Met.no) (Documentation, Problèmes)
Première occurrence: 10:58:53 (1 occurrence)
Dernier enregistrement: 10:58:53

Error fetching met data: Update of data from the web site failed:

Logger: metno
Source: components/met/coordinator.py:78
Première occurrence: 10:58:53 (1 occurrence)
Dernier enregistrement: 10:58:53

Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error ‘ClientConnectorDNSError’


For openmeteo:

Logger: homeassistant.setup
Source: setup.py:276
Première occurrence: 09:59:26 (3 occurrences)
Dernier enregistrement: 10:00:27

Setup failed for custom integration ‘open_meteo_solar_forecast’: Requirements for open_meteo_solar_forecast not found: [‘open_meteo_solar_forecast==0.1.32’].
Setup failed for custom integration ‘solcast_solar’: Requirements for solcast_solar not found: [‘watchfiles>=1.0.0’].


for gtf2 :

Setup failed for custom integration ‘gtfs2’: Requirements for gtfs2 not found: [‘gtfs-realtime-bindings==1.0.0’]. ```

and some related error I think

Logger: homeassistant.util.package
Source: util/package.py:222
Première occurrence: 09:59:10 (9 occurrences)
Dernier enregistrement: 10:00:27

Unable to install package watchfiles>=1.0.0: error: Request failed after 3 retries in 9.7s Caused by: Failed to fetch: `https://files.pythonhosted.org/packages/8f/95/8ef4a95481d3e0cb52d62a06fa6e972e81424be2d9698b91a2fecca9904c/watchfiles-1.2.0-cp314-cp314-musllinux_1_1_aarch64.whl.metadata` Caused by: error sending request for url (https://files.pythonhosted.org/packages/8f/95/8ef4a95481d3e0cb52d62a06fa6e972e81424be2d9698b91a2fecca9904c/watchfiles-1.2.0-cp314-cp314-musllinux_1_1_aarch64.whl.metadata) Caused by: client error (Connect) Caused by: dns error Caused by: failed to lookup address information: Name has no usable address
Unable to install package watchfiles>=1.0.0: error: Request failed after 3 retries in 11.2s Caused by: Failed to fetch: `https://files.pythonhosted.org/packages/8f/95/8ef4a95481d3e0cb52d62a06fa6e972e81424be2d9698b91a2fecca9904c/watchfiles-1.2.0-cp314-cp314-musllinux_1_1_aarch64.whl.metadata` Caused by: error sending request for url (https://files.pythonhosted.org/packages/8f/95/8ef4a95481d3e0cb52d62a06fa6e972e81424be2d9698b91a2fecca9904c/watchfiles-1.2.0-cp314-cp314-musllinux_1_1_aarch64.whl.metadata) Caused by: client error (Connect) Caused by: dns error Caused by: failed to lookup address information: Name has no usable address
Unable to install package gtfs-realtime-bindings==1.0.0: error: Request failed after 3 retries in 5.5s Caused by: Failed to fetch: `https://files.pythonhosted.org/packages/b3/67/1f030547f94716b3259d99ad93467a6608703942bc62f35e43b1bb8bc2e9/gtfs_realtime_bindings-1.0.0-py3-none-any.whl.metadata` Caused by: error sending request for url (https://files.pythonhosted.org/packages/b3/67/1f030547f94716b3259d99ad93467a6608703942bc62f35e43b1bb8bc2e9/gtfs_realtime_bindings-1.0.0-py3-none-any.whl.metadata) Caused by: client error (Connect) Caused by: dns error Caused by: failed to lookup address information: Name has no usable address
Unable to install package gtfs-realtime-bindings==1.0.0: error: Request failed after 3 retries in 11.2s Caused by: Failed to fetch: `https://files.pythonhosted.org/packages/b3/67/1f030547f94716b3259d99ad93467a6608703942bc62f35e43b1bb8bc2e9/gtfs_realtime_bindings-1.0.0-py3-none-any.whl.metadata` Caused by: error sending request for url (https://files.pythonhosted.org/packages/b3/67/1f030547f94716b3259d99ad93467a6608703942bc62f35e43b1bb8bc2e9/gtfs_realtime_bindings-1.0.0-py3-none-any.whl.metadata) Caused by: client error (Connect) Caused by: dns error Caused by: failed to lookup address information: Name has no usable address
Unable to install package gtfs-realtime-bindings==1.0.0: error: Request failed after 3 retries in 5.3s Caused by: Failed to fetch: `https://files.pythonhosted.org/packages/b3/67/1f030547f94716b3259d99ad93467a6608703942bc62f35e43b1bb8bc2e9/gtfs_realtime_bindings-1.0.0-py3-none-any.whl.metadata` Caused by: error sending request for url (https://files.pythonhosted.org/packages/b3/67/1f030547f94716b3259d99ad93467a6608703942bc62f35e43b1bb8bc2e9/gtfs_realtime_bindings-1.0.0-py3-none-any.whl.metadata) Caused by: client error (Connect) Caused by: dns error Caused by: failed to lookup address information: Name has no usable address
2

Who is your internet service provider? Free
Have you tried changing the DNS settings in the network settings? Or even directly on your internet router?

3

Yes Free is my ISP. I tried to add another DNS in HA LAN setting without more success. Was perfectly fine up to 2026.9.1 …

4

Show your network settings please.

5

You need to put the public DNS server first, before your router’s DNS server. And then completely restart the router.

6

No difference as far as I’m concerned. I have the exact same problem with the tapo camera control custom integration.

7

image
image797×620 23.6 KB

Here the new DNS settings… but even after rebooting still not working :frowning:

8

HAOS ? What is your ISP (writting in english to be understood by everyone)

9

Screenshot_20260913-132229
Screenshot_20260913-1322291080×2520 121 KB

IPv6 is set to auto, and the first two nameservers are Quad9’s.

Inside the core, nslookup resolves files.pythonhosted.org only as IPv6, but wget or ping both fail to resolve or connect.

Edit : 2026.9.2, ISP is Free (but my box is set up to use 8.8.8.8 and 8.8.4.4 anyway).

10

Ok … seems related to Free ISP… but why it appears with 2026.9.2 ? that’s the question…

11

So Just to make sure you did a nslookup or eq on the HA console and it resolved the name but only on the ipv6 side?

^^^ This (only resolves as Ipv6) screams DNS issue in the stack on the IPv4 side.

Do those lookups fail from another station on the same subnet? What does the rest of the subnet use for DNS?

12

Works fine from my desktop. It started with 2026.9.2 and doesn’t happen with prior versions.

13

Reboot just HA or the entire machine ?

It’s because of a more modern DNS management system that Free can’t handle.

14

Then that seems to indicate a delta in DNS only in HA. If those other machines hit the same DNS servers.

It also smells of this… 2026.9.2 update breaks zha + zwave_js integrations

Idaho there’s something to the DNS theory but op is using public DNS resolvers.

(op can you try different public DNS like cloudflare or quad9 for a sec and see if it still happens?, I also saw your post on the big thread. Venv? Is this not HAOS?)

15

yes seems very related …

16

Good news… After also install the cloudflare DNS in the list, it’s working again

image
image712×701 23.2 KB

That’s very interesting …

So where is the problem ? from HA side or ISP ? a mismatch between DNS protocols between ?

17

The problem stems from Free’s DNS.

If that weren’t the case, there would be a lot more people affected than this—not just French users. Those using the Free service.

It probably didn’t work with Google’s DNS because, your DNS cache wasn’t completely cleared, but I think Google’s DNS works since some people are using it to discuss this issue.

18

All problems are Name Resolution problems until proven otherwise…

19

Still, something changed between 2026.9.1 and 2026.9.2, since it was fine two days ago before the upgrade, and is fine again if I revert to last week’s backup of the VM.

20

Yes, a change on the HA side that uses a more modern system than Free doesn’t understand, as I mentioned above.