-
Notifications
You must be signed in to change notification settings - Fork 23
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 uptime_kuma not found: ['pyuptimekuma==0.0.6']. #37
Comments
I would think that the version of pyuptimekuma should not be coming from github, but rather from pypi which has the 0.0.6 version: |
@meichthys Can you clarify? I have the same issue and don't know what to do to fix it. Maybe this provides a bit more info:
|
@alexruffell and @Egglestron It mayhave something to do with never versions of pip which resolve dependencies differently than in the past. The issue here seems to be that we use pyuptimekuma which relies on a newer version of Since we likely won't get Homeassistant to update their dependency too easily, we may be able to relax our requirement. @jayakornk Do you know if v0.7.1 would work for pyuptimekuma? |
I did not have this issue until updating to 2023.3 public today. I got this same error for other packages as well. I wonder if this broke things. @Egglestron has been, but @alexruffell have you been running beta HA? UPDATE: Links to other integrations I'm having the same issue with: |
@Intecpsp Yes, I was on 2023.3 betas, now stable. |
I can confirm this issue happens wirh 2023.03.0 release, thus breaking the integration. Let me know if you need any more details. |
same problem for me after hassio update 2023.3 Logger: homeassistant.setup Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6']. |
This comment was marked as duplicate.
This comment was marked as duplicate.
Adding yet another instance to the list of affected ones. Integration v2.0.3 via HACS |
Same issue here, after upgrading to 2023.3.0: HAOS 9.5 _Logger: homeassistant.setup Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6']._ |
Same problem here on HA 2023.3.0:
|
Same issue for me since updating to HA 2023.3.0. Had one other integration refuse to load after updating (AsusRouter) but they have put an update out that has fixed it. Any idea on how to fix the uptime kuma integration or do we need to wait until an update is published?
|
Although the release version says 0.0.4 the init.py file says it is 0.0.6. |
This comment was marked as duplicate.
This comment was marked as duplicate.
The version shouldn't be an issue since the correct version is listed in pypi. There is however a package discrepancy with prometheus-client which already exists in homeassistant core (version 0.7.1) while our main dependency pyuptimekuma requires a newer version. Ideally the prometheus integration of homeassistant core would be updated to a newer version but I don't see that happening too soon so I have submitted a proposed fix to our upstream dependency here jayakornk/pyuptimekuma#3 once that is merged, we should be able to push out an update to fix this. In the mean time we may be able to monkey patch our manifest.json to update our requirements but I haven't been able to try it yet. |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
I've found that doing a pip3 install pyuptimekuma==0.0.6 Inside the container fixes it in the interim. |
This comment was marked as duplicate.
This comment was marked as duplicate.
@danielsmith89 could you give some more details around that please, is that in the docker container, what was the command you ran ? as I tried pip3 install pyuptimekuma==0.0.6 thanks |
Yes, go inside the Home Assistant docker container (if that's what you are running HA in) and the issue that comand |
Thank you that worked. |
Any temporary solution available if I run HASS from raspberry OS? |
@danielsmith89 - thanks but no running supported supervisor on Debian. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I don't understand the question |
Workaround fixed it. Integration is working again. If you dont see the container in Portainer check Portainer settings, if there are hidden containers, if so remove them from the list. |
If you check the site you just posted, there are instructions for installation of home assistant core, followed bij home assistant supervised. Check if you followed all steps. You can also check docker containers in the terminal by typing: Docker ps |
And for de HASSIO users, someone a solution? |
See my explaination... |
So I followed the instructions and it was very informative. I performed the pip install --upgrade pip and it seemed to work. However I still get the same error on uptime kuma integration after rebooting the server |
You also need to run the command for upgrading pyuptimekuma. Its further up this thread. And also thanks @Sarnog . I didnt realize the problem was inside home assistant core. Stupid |
Try to remove and re-install the uptime kuma add-on. If that doesn't work, you need to install pyuptimekuma in the terminal as well (where you typed the pip command) |
I have got no clue where to start to attach to docker or get into that part of HAOS on my VMM install. Only place I know is to connect to a terminal directly via VMM where the CMD shows ha > But from there I have no idea what commands to a to work inside the Home assistant container sorta say. |
On your docker host type: |
oke thnx |
Yes, it works. Thanks! |
v 2.1.0 works for me too. |
works perfect, thnx. |
Running 2.1.1 on 23.7.3 (HassOS) and it stopped working after upgrading. Everything else works. Installing works, when adding the integration the following message is thrown: Config flow could not be loaded: {"message":"Invalid handler specified"} DebugLog: 2023-07-24 10:45:43.742 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration uptime_kuma: cannot import name 'UptimeKuma' from 'pyuptimekuma' (/usr/local/lib/python3.11/site-packages/pyuptimekuma/init.py) |
Hi,
Uptime Kuma integration requires dependency pyuptimekuma version 0.0.6, but latest version is 0.0.4 on GitHub.
Please find attached the logs of my Home Assistant instance, version 2023.3.0 b0.
The text was updated successfully, but these errors were encountered: