-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency not found #762
Comments
for me, updating HA to 2024.11.0 resolves the issue |
I'm on 2024.11.0 docker image, Similar issue with 5.4.1 upgrade, in my case 'hass_web_proxy_lib' is not found at all
|
@lezruk I would expect that to be installed automatically. Have you tried downing / upping your HA instance? |
5.4.1 integration I updated once it popped up in HACS, HASS updated automatically, just today updated HASS to 2024.11.1 - same behaviour - 'hass_web_proxy_lib' load issue. Downgrading to 5.4.0 works fine though |
FYI: I just tested this by updating the Frigate integration via HACS to |
v5.4.1
[preview release]: dependency not found
HA was 2024.10.x |
@rsteckler Are you using HA in a docker container, or HAOS? Is there anything in your HA log, shortly after startup, about trying to install the dependency (search for |
I'm running in a kubernetes environment, but it's essentially docker. |
Would you mind searching for |
Upgraded back to 5.4.1 and restarted. Here are the logs, including some other content that might be related. Log
|
Thanks @rsteckler . Not really conclusive, still can't figure out why the package is not being installed for you. If you are comfortable doing so, would you mind logging in to your HA instance via ssh / docker exec and running:
This is what Home Assistant should be running to install the dependency, I'm trying to figure out if there's some subset of users / scenarios in which that doesn't work ... or whether HA is just not trying to install it. (Doesn't matter whether you're running |
Sure - happy to help. Upgraded again to 5.4.1. Verified the error exists in the logs still. Logged into the pod and here's the output: Details
At that point the frigate integration was not loaded and didn't have a "reload" option in HA. I restarted HA and this time there's no error in the logs and the Frigate installation loaded successfully. If you're unable to repro on your side and have any hypotheses on why it might be failing on some machines, I'm happy to remove the hass-web-proxy-lib package and tail some logs or something while HA is starting up. One would assume it's logging something, somewhere when it should attempt to run the pip install. For now, appreciate having it upgraded. Thanks for the workaround! |
Thanks @rsteckler , that's really helpful. I have (currently) no idea why HA would not install the requirements. You have proven they work, but HA isn't trying to install them ... |
According to the faq HA installs dependencies in /config/deps (this is persistent volume for containerized setup) , and I can see it there, even if manually deleted it pulls it back upon container restart. By saying that, it looks like integration doesn't find/search module in /config/deps but instead in pip default location - /usr/local/lib/python3.12/site-packages. That explains why manual install with pip works. Unfortunately /usr/local/ won;t survive container restart and module needs to be located in /config/deps instead
|
Yeah something is/was up with |
I'm hitting the same high level error, but with possibly different logs relating to Logs
As with the previous comments, pip install logs
|
The integration does not control (nor should set) the module search path, Home Assistant does and this is supposed to "just work" (and does for me, both in a test install and in the devcontainer). A few ideas:
I strongly suspect this depends on the install type. Using the official Home Assistant docker image, |
I'm not a python dev and don't know the HA system well, so this might not be well-informed, but.... Responding to your hypothesis on python version:
Also,
and...
Also:
I know none of these really helps towards a solution, but lmk if you need anything from a broken system. |
One more interesting thing (at least to me, who has no idea what I'm doing) It looks like HA is trying to install the package, specifically into /config/deps
When I run the command it runs, it audits 91 packages, seeing that hass-web-proxy-url is correctly installed in the /config/deps directory. But it's not shown as 'installed' by pip:
Here it is in the /config/deps directory:
In this scenario, HA fails to load the frigate integration but happily checks hass-web-proxy-lib is installed exactly where it wants it to be. Running My guess, again knowing nothing about python, is that the frigate integration is trying to import the proxy library from the pip system path, rather than from /config/deps. I'm also guessing it's working on your machine because you have it installed there, or your version of HA is using the system pip path instead of /config/deps. Hope something in there helps. |
The Frigate integration does not control the search path for modules. It simply tells HA "Please install dependency X" and then tries to import it from the module path (that is also controlled by HA and/or the system configuration). I suspect this is actually a Home Assistant issue, perhaps this one: home-assistant/core#127966 . There's also a workaround linked you could try. |
Good find. I agree that's exactly the problem and, as mentioned in the other thread, I'm running in a kunernetes environment. |
Just confirming that the kubernetes solution in the other thread solves this. I would close this as an upstream issue and point people there. |
Unable to install package hass-web-proxy-lib==0.0.6: × No solution found when resolving dependencies: ╰─▶ Because homeassistant>=2024.10.3,<=2024.10.4 depends on yarl==1.13.1 and yarl==1.17.2, we can conclude that homeassistant>=2024.10.3,<=2024.10.4 cannot be used. And because only the following versions of homeassistant are available: homeassistant<=2024.10.4 homeassistant>=2024.11.0 we can conclude that homeassistant>=2024.10.3,<2024.11.0 cannot be used. (1) Because homeassistant>=2024.11.0 depends on webrtc-models==0.2.0 and webrtc-models==0.3.0, we can conclude that homeassistant>=2024.11.0 cannot be used. And because we know from (1) that homeassistant>=2024.10.3,<2024.11.0 cannot be used, we can conclude that homeassistant>=2024.10.3 cannot be used. And because hass-web-proxy-lib==0.0.6 depends on homeassistant>=2024.10.3 and you require hass-web-proxy-lib==0.0.6, we can conclude that your requirements are unsatisfiable. hint: Pre-releases are available for homeassistant in the requested range (e.g., 2024.11.0b9), but pre-releases weren't enabled (try: This is the error i get when looking through logs. |
@awptechnologies Not sure, but guessing that because you're using an unreleased HomeAssistant version, there's not yet a HA library that's been released that matches the required dependencies. If this is right, you can just wait for the HA team to do a library release, or change to an official HA version (and not |
@awptechnologies Rethinking this -- I think this library that |
@awptechnologies Can you try to latest v5.5.0 pre-release. I hope it will help your specific problem. (Won't change anything for anyone else who is impacted with the HA-wide import issue as discussed earlier in this thread) |
5.5.0 works great thanks. |
I am closing this issue as I don't think there is anything to be done on the Frigate side: |
It might be worth noting that the |
v5.4.1
[preview release]: dependency not found
Version of the custom_component
5.4.1
Configuration
Add your logs here.
Describe the bug
A clear and concise description of what the bug is.
Debug log
The text was updated successfully, but these errors were encountered: