-
Notifications
You must be signed in to change notification settings - Fork 2
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
Requirements for worldtidesinfocustom not found: ['matplotlib>=3.4.2'] #24
Comments
Hello, Your error message seems to tell that matplotlib cannot be successfully installed via pip. Thank you in advance for your feed back . |
I was just commenting that I'd skipped 2023.7 so was unsure if the issue may have been evident in that build. As I use docker that packages are pre-packed. Is the matplotlib issue related to a version packed with the official docker image or is it just missing? |
I installed matplotlib via the terminal window and restarted HA. The custom component now works as expected. Then I ran the pipdeptree command to see what the dependancies were. Result:
Running pipdeptree on gps3 doesn't yield any result. I'm struggling to determine if worldtideinfocustom is requiring gps3 which triggers the matploblib warning? I note in April the code was updated with a few matplot additions? |
Same issue. This is such an important integration for those dependent on tides. Hope it can be fixed as there must be many like myself who can no longer update HA core. |
Hello But when I fix it : I fall on a pip error installation. I look for a solution... |
Thanks very much for you effort on this. Very grateful. |
seems same as issue #26 |
Setup failed for custom integration worldtidesinfocustom: Requirements for worldtidesinfocustom not found: ['matplotlib>=3.4.2'].
Upgraded HA from 2023.06.02 to 2023.08.02 and this issue appeared. HA runs in Synology Container [docker]. The above log is flagged against worldtidesinfocustom
Upon startup the homassistant.util.package log records
Is it relying on an old package for the integration? I'm unsure if 2023.07.xx would have displayed the same issue.
The text was updated successfully, but these errors were encountered: