-
Notifications
You must be signed in to change notification settings - Fork 94
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
Integration not getting loaded after upgrading to 2024.10.1 #684
Comments
Try reinstalling, I have been running 2024.10.1 since it has been released with all of my cameras with zero issues. |
I have the same issue. Tried to remove the integration, restart HA, install it again and restart with no success. Error message: Error occurred loading flow for integration tapo_control: cannot import name 'Downloader' from 'pytapo.media_stream.downloader' (/usr/local/lib/python3.12/site-packages/pytapo/media_stream/downloader.py) |
I wonder what is different between our envs, I use RPI 5 HA OS as well. I wonder if it has something to do with https://www.home-assistant.io/blog/2024/10/02/release-202410/#faster-upgrades-when-using-custom-integrations . I double checked developer notes in blog and there is nothing I found that could lead to this issue. |
I use file explorer and I don’t have that folder where the downloader should be located. Maybe there are limitations in the file explorer addon. Anyway, I downgraded to Core 2024.10 from 2024.10.1 and now it seems to be working again. So it should not have anything todo with 2024.10 HA version. |
Closing as this seems to be a weird anomaly with environments, reinstall of intergration/core seems to solve this. |
after the latest 2024.10.x updates the integration no longer works with the following error
|
@Gjonni This works as expected. This is a check for users with nonstandard unrecommended HA setup, where HA is not managing dependencies. You will need to install pytapo 3.3.32 via pip. |
Hi, can you explain better?
the error, therefore, is not the same, would you prefer it to open another issue? |
I have the same issue with the pytapo version not being 3.3.32. I'm simply using the offical HA image with version "2024.10.4". As far as I see there is nothing custom on my setup. I already tried uninstalling and purging everything related to the integration, but after installing the latest version and restarting, I see the same error again.
@Gjonni were you able to solve it by now? |
no he was wrong |
You have invalid pytapo installed. The version is set inside pytapo and integration requires 3.3.32, this is done automatically on normal HA installations methods. If there is wrong version installed, instead of using the (potentionally) incompatible old version resulting in weird issues, there is this check instead. There is absolutely no way how you can have 3.3.32 and this error at the same time. You simply need to ensure that correct pytapo version is installed for HA and this integration default import - in this case 3.3.32 if HA does not install it for you as it usually does. If you are using docker, it needs to be inside docker. |
I understand, but I have never installed anything, it is the official image of HA, stable version. |
You will need to debug it to find out why this happens, kubernetes is an advanced installation method and can result in issues like these if not properly configured. You might want to go into the docker container and install the proper version there manually. |
just for clarity. |
for everyone's benefit, I rolled back the integration to version 5.6.1 and, without doing anything else, it was working properly again. At the moment I will stay on version 5.6.1 to be able to use the device, hoping that the BUG will be resolved as soon as possible. Thank you |
As described previously, this is not a bug and there is nothing to resolve here. The environment where you are running it needs to be fixed. 5.6.1 you rolled back to uses pytapo 3.3.30 which your environment currently has installed where as the newest uses 3.3.32. I recommend either learning a bit about kubernetes/docker and how to install packages via pip there, or migrating to something simpler like HA OS that manages depedencies for you automatically - https://www.home-assistant.io/installation/. |
:-) I don't agree with you. |
That's great. I am sure someone with your skills will have no issues figuring this out and fixing their environment on their own.
If a package was updated correctly, it would not show the old version and this error would not happen. The version is coming from the package itself.
There is no need, HA integration dependencies have absolutely nothing to do with dockerfile, but I am sure you know that.
User @Gjonni has been blocked. For anyone else experiencing this issue, message me at [email protected] and we can have a quick look and I can help you fix the environment on a call. In case this is a HA (not integration) bug we can open a bug report as well - I doubt that though because of number of users of the integration and lack of any bug reports so far. |
@JurajNyiri as said before, I'm facing the same problem as @Gjonni and I'm not sure what you mean by "installing it ourself", I never installed any python dependency myself into the image/container. So it either comes with the image or it is installed at runtime by the integration. That's what confuses me about this issue. Thank you for your offer, that is really appreciated! I'll write you a mail as soon as I find time to schedule a call. For now I just stick with the version that runs on 3.3.30, I'm fine with that. |
Integration defines requirements in manifest file - https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/blob/main/custom_components/tapo_control/manifest.json#L11 . This is correctly set in both versions. HA is responsible for installing this dependency, before starting the integration. If that does not happen it is either a HA bug or an environment issue (resulting in HA not being able to install dependencies for some reason). That's what we will need to figure out. |
I also run home assistant in a kubernetes cluster and had this issue now. This time it worked by removing the old pytapo and pytapo-3.3.30.dist-info directories in deps/lib/python3.12/site-packages. |
Possibly related to home-assistant/core#127966 ? |
I ran into the Turned out that in my case the issue was a I resolved the issue by removing the following two directories before triggering the upgrade from 3.6.1 to 3.8.1:
Hope this helps. |
Thanks for your update @martinohmann, I played around with it as well and installed the new version manually with and without having the old one, also installing it in the local python paths and the homeassistant config/deps path.
Edit: It worked now! It was the second folder,
that made it work! I checked the system lib/python3.12 all the time... Thank you again! |
Description
After upgrading to 2024.10.1, the integration is not getting loaded.
Reproduction Steps
Just added the integration through config flow.
Expected behavior
The integration to be loaded
If applicable, add error logs.
Device Firmware
1.3.11 Build 231115 Rel.85532n(4555)
Integration Version
5.6.1
Using stream component
Yes
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
Yes
HASS Environment
HA OS on RPi4
Search for similar issues
Yes
Additional information
No response
The text was updated successfully, but these errors were encountered: