Core
2024.12.5
Supervisor
2024.12.0
Operating System
14.1
Frontend
20241127.8
2024-12-20 19:05:13.532 ERROR (SyncWorker_0) [homeassistant.util.package] Unable to install package xxxxxx==0.x.xx.xxx: error: Failed to fetch: `https://files.pythonhosted.org/packages/6f/cd/117b51f1346b2f073be312b6e6f5fc1bf5e9acaa9fe4fdb7626466aedd96/xxxxx-xx.xx.xx.xx.tar.gz`
Caused by: Could not connect, are you offline?
Caused by: Request failed after 3 retries
Caused by: error sending request for url (https://files.pythonhosted.org/packages/6f/cd/117b51f1346b2f073be312b6e6f5fc1bf5e9acaa9fe4fdb7626466aedd96/petkitaio-xxx.xx.xx.xx.tar.gz)
Caused by: client error (Connect)
Caused by: dns error: failed to lookup address information: Name does not resolve
Caused by: failed to lookup address information: Name does not resolve
on the start, probably all my custom_components failed.
2024-12-20 22:05:28.425 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ecoflow_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-20 22:07:07.623 ERROR (SyncWorker_1) [homeassistant.util.package] Unable to install package reactivex==4.0.4: error: Failed to fetch: `https://files.pythonhosted.org/packages/69/3f/2ed8c1b8fe3fc2ed816ba40554ef703aad8c51700e2606c139fcf9b7f791/reactivex-4.0.4-py3-none-any.whl.metadata`
Caused by: Could not connect, are you offline?
Caused by: Request failed after 3 retries
Caused by: error sending request for url (https://files.pythonhosted.org/packages/69/3f/2ed8c1b8fe3fc2ed816ba40554ef703aad8c51700e2606c139fcf9b7f791/reactivex-4.0.4-py3-none-any.whl.metadata)
Caused by: client error (Connect)
Caused by: dns error: failed to lookup address information: Name does not resolve
Caused by: failed to lookup address information: Name does not resolve
2024-12-20 22:07:11.565 ERROR (SyncWorker_1) [homeassistant.util.package] Unable to install package reactivex==4.0.4: error: Failed to fetch: `https://files.pythonhosted.org/packages/69/3f/2ed8c1b8fe3fc2ed816ba40554ef703aad8c51700e2606c139fcf9b7f791/reactivex-4.0.4-py3-none-any.whl.metadata`
Caused by: Could not connect, are you offline?
Caused by: Request failed after 3 retries
Caused by: error sending request for url (https://files.pythonhosted.org/packages/69/3f/2ed8c1b8fe3fc2ed816ba40554ef703aad8c51700e2606c139fcf9b7f791/reactivex-4.0.4-py3-none-any.whl.metadata)
Caused by: client error (Connect)
Caused by: dns error: failed to lookup address information: Name does not resolve
Caused by: failed to lookup address information: Name does not resolve
2024-12-20 22:07:15.028 ERROR (SyncWorker_1) [homeassistant.util.package] Unable to install package reactivex==4.0.4: error: Failed to fetch: `https://files.pythonhosted.org/packages/69/3f/2ed8c1b8fe3fc2ed816ba40554ef703aad8c51700e2606c139fcf9b7f791/reactivex-4.0.4-py3-none-any.whl.metadata`
Caused by: Could not connect, are you offline?
Caused by: Request failed after 3 retries
Caused by: error sending request for url (https://files.pythonhosted.org/packages/69/3f/2ed8c1b8fe3fc2ed816ba40554ef703aad8c51700e2606c139fcf9b7f791/reactivex-4.0.4-py3-none-any.whl.metadata)
Caused by: client error (Connect)
Caused by: dns error: failed to lookup address information: Name does not resolve
Caused by: failed to lookup address information: Name does not resolve
Same here with some integrations, if I change dns to another one, for example quad9 and then restart ha integrations start properly, then you can roll back to your default dns. In my case, this strange behavior started with 2024.12.4.
I’m having this same issue when trying to integrate Frigate.
I’ve tried the two suggestions in previous messages in this thread. In settings, system, network, disabled IPv6, and changing DNS servers to the Quad9 servers. Restarted Home Assistant and tried to ADD INTEGRATION, Frigate but I’m getting the same errors including:
2025-01-01 11:06:46.822 ERROR (SyncWorker_5) [homeassistant.util.package] Unable to install package hass-web-proxy-lib==0.0.7: error: Failed to fetch: https://files.pythonhosted.org/packages/e0/01/2512288bb73820fa93e119449ee9dfa1a74921db56e238448b7d171cb67b/hass_web_proxy_lib-0.0.7-py3-none-any.whl.metadata
Caused by: Could not connect, are you offline?
Caused by: Request failed after 3 retries
Caused by: error sending request for url
Is there anything else I can try to resolve this issue?
My initial configuration included three DNS servers, one my ISP provided (primary), plus two Google DNS servers 8.8.8.8 (secondary) and 8.8.4.4 (tertiary). I tried removing the DNS server address provided by my ISP and only used the Google servers but with no change in the errors I was receiving. I then tried using only Quad9 IPv4 servers 9.9.9.9 and 149.112.112.112 but still no change. I confirmed from the core command line (via Terminal & SSH Add-On) that I can ping files.pythonhosted.org (domane name resolves to 199.232.36.223). I tried the same ping from the bare metal HAOS command line also getting a good response. I’m assuming I may have a different issue but with similar symptoms to those being discussed in this thread. I’ll try entering this as a new topic with all of my setup and configuration details. Maybe someone will spot an issue with my configuration.
For me what I found was it was not a DNS issue as the system was able to resolve files.pythonhosted.org, but for some reason could not fetch it from the full URL stated in the error message. Doing some more searching I found a related discussion thread here: Dependency not found · Issue #762 · blakeblackshear/frigate-hass-integration · GitHub
As was suggested in that thread I manually installed the web proxy using docker exec and pip install. In my case I installed hass-web-proxy-lib==0.0.7 vs the hass-web-proxy-lib==0.0.6 discussed in the NOV2024 post.
After installing hass-web-proxy-lib==0.0.7 and restarting my system I was able to successfully install the Frigate integration, configure the integration, and it is working now. Obviously, this is probably not the best/final solution for most users, but it did work for me as a quick fix.
