-
Notifications
You must be signed in to change notification settings - Fork 0
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
2024.10 beta Requirements for entity_tz not found: ['timezonefinder==5.2.0']. #16
Comments
I got the same result when I tried running 2024.10.0b0. But when I went back to 2024.9.3, it worked just fine. Also, I created a separate Python 3.12 venv and installed timezonefinder, and that worked ok, too. So, it seems they broke something in 2024.10.0b0. Not sure there is anything I can do about it. |
yes it's what Joost said, they changed internals. I can ask him whether he can assist in fixing this? |
As far as I can tell, the problem is either 1) the authors of timezonefinder did not properly distribute on pypi.org, or 2) the authors of HomeAssistant are being too restrictive. I don't claim to know which it is. Like I said, I can install it just fine using pip, so I'm not sure why HA's equivalent can't. But, again, not sure there's anything I can do about it. Maybe you could post an issue on the timezonefinder project. |
Not sure it's 100% related, but found this: jannikmi/timezonefinder#243 |
as far as I understood the devs , they have the 1 perspective. I certainly want to issue in the timezonefinder project, though I fear as a mere user of your integration, my description wouldn't be as succinct as required. But, let me try.. I really use your integration and want it back;-) update |
You might also try newer versions of timezonefinder by modifying manifest.json. As far as I can tell, the API that my integration uses hasn't changed. |
where can I find those versions? |
https://pypi.org/project/timezonefinder/#history https://github.com/jannikmi/timezonefinder/releases Looks like 5.2.0 was the last 5.x release. |
o dear, and we're using 5.2.0, thats a long time ago in their history.. update
will keep an eye on the processor, but this is good news. |
I think I was using 5.2.0 because that's what I had been using with the composite integration, and I didn't want to deal with a major version change. I would think latest & greatest is probably best. I have no idea if there's any difference in CPU usage, good or bad. I'll give 6.5.3 a try, too. If it works for both of us, I'll go ahead and release a new version of the integration with that manifest.json update. |
Released 1.2.2 w/ updated timezonefinder version. |
Hi. `Registrador: aiohttp.server Error handling request And installing custom component (ignoring the warning that the integration is still installed): `Logger: homeassistant.loader Error parsing manifest.json file at /config/custom_components/google_geocode/manifest.json: unexpected character: line 8 column 3 (char 201)` `Registrador: homeassistant.util.package Unable to install package timezonefinder==6.5.3: error: Failed to prepare distributions Caused by: Failed to fetch wheel: h3==3.7.7 Caused by: Build backend failed to build wheel through Registrador: homeassistant.setup Setup failed for custom integration 'entity_tz': Requirements for entity_tz not found: ['timezonefinder==6.5.3'].` |
@edu24x how are you trying to install and uninstall the entity_tz custom integration? |
Removing the services, but the integration persists. 08-10-2024_00-53-55.mp4 |
You're showing how you're attempting to remove the configuration entries for the integration, not how you installed or attempted to uninstall it. So, how did you install it? HACS? What version of HA are you using? The bottom line is, the error says timezonefinder 6.5.3 can't be found, but it is definitely on pypi.org (i.e., https://pypi.org/project/timezonefinder/). So, I have no idea what HA's problem is. FWIW, I'm using entity_tz 1.2.2 just fine on HA 2024.10.1. |
I followed the instructions. In HACS I downloaded the custom repository and installed it. Then I searched for the integration and installed it. The problem is that now I can't update the repository because it tells me that to do so I have to uninstall the integration first and if I ignore that warning it installs 1.2.2 but not the timezonefinder==6.5.3 module. So if I can't uninstall the integration first, it can't be updated correctly. How do I uninstall the integration, I don't see that option? 09-10-2024_00-57-49.mp4 |
When HACS installs the custom integration, as far as I know, it is NOT responsible for installing the integration's requirements (in this case, timezonefinder.) It is HA's responsibility to make sure the integration's requirements are installed when it starts the integration. This would normally only happen the first time the integration is started after it is installed. HA is having trouble doing that for some reason on your system (but does not have a problem doing so on my system.) So, you should not need to uninstall or reinstall the custom integration. But, if you want to uninstall it, you would do that via HACS, not HA's integration page. HA's integration page is only for removing configuration entries. (And you should not need to remove the configuration entry or entries before removing the custom integration.) |
That's what I do. I try to remove the custom integration from HACS, but it warns me that in order to remove it I must first remove the integration. The warning gives me two options: navigate to the HA integrations page (there is no option to uninstall) or ignore the warning (it lets me remove the custom integration). But if I reinstall the custom integration from HACS I get the errors in the log mentioned above and the integration does not work. Regards |
Could you try adding the following to your configuration.yaml file?
Restart HA (with entity_tz installed), and look for any messages in the log that contain any of the following strings:
FWIW, this is what I see:
|
|
What hardware are you running on? |
Raspberry Pi 4 4GB with an SSD. |
@edu24x, that probably explains why it works for me but not for you. I'm running HA on an Intel based system, and you're running on an ARM based system. It's also possible your system is not configured correctly given the original errors you shared which showed it couldn't build wheels due to lack of gcc. What kind of HA install are you using? BTW, I did not see any DEBUG messages from you above. Are you sure you enabled the ones I asked for and then restarted HA? I'd really like to see the one from your system that is equivalent to this one from my system:
|
Yes, here it is. I had changed some parameters in the logger configuration:
I have HAOS 2024.10.1, the integration has been working fine for months, I don't know exactly in which update it stopped working, with the "not loaded" warning. Definitely, Is there any way to delete the entity_tz integration from the integrations page or from some configuration file to retry the installation from the beginning? |
Ok, that "uv pip install" command is the same, as expected. No surprises there. I'm pretty sure the problem started with 2024.10, with this change: This changes how HA installs pypi.org packages that integrations use. In this case, it appears h3 (which is used indirectly by timezonefinder) installs ok on x86, but not on ARM. I doubt that any reinstalling of entity_tz will make any difference. The problem is not the installation of the entity_tz integration, but the installation of the pypi.org packages it uses (indirectly.) I honestly have no idea what the ultimate fix could/would be. I suspect it is either the h3 package itself, or the "wheel" infrastructure in HAOS. @Mariusthvdb, any ideas? Do you run on ARM hardware, or x86? |
running x86 here, and never looked back after the change in HA beta and using "timezonefinder==6.5.3" |
Closing since there's really nothing I can do in this integration to fix the problem on ARM-based systems (short of not using timezonefinder anymore.) |
Entity TZ integration error thrown during beta 2024.10
Entity_tz version 1.2.1
and
According to Frenck:
And Joost:
The text was updated successfully, but these errors were encountered: