-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Update component in HACS: Startup blocking main thread issue. #86
Comments
Hi @mcattle, it sounds like there may be something stuck/broken in your Home Assistant instance interfering with this integration from operating normally. The easiest way prevent this issue would be to restore Home Assistant from backup prior to installing this integration and install the integration cleanly. If that's not possible, please delete the integration from Home Assistant's GUI: Then, manually delete |
Issue found. The version coming up in my HACS is an outdated fork at https://github.com/NemesisRE/sensor.plex_recently_added. Adding your repo to the HACS custom repos allowed me to download the correct version. |
Following the install of the correct repository and version, I'm now only getting this message on startup (which I just set to ignore):
|
Glad you figured it out. I've been waiting nearly a year for the HACS moderators to approve the original UMC and its original integrations back to HACS. It's a bit hard to believe they are nearly 1 year behind! It will be much easier once its all builtin to HACS again. https://github.com/hacs/default/pulls/mkanet Going to close this issue. Stay tuned! |
Describe the Bug
The current version of the component is 0.4.8, but HACS only has 0.3.9. I'm hoping the error I'm getting with 0.3.9 startup has been addressed in 0.4.8.
The Error
Indicate if you followed all steps in the troubleshooting doc
Yes
What data does the sensor display if any?
All data is displayed, the startup error just indicates a blocking call on the main thread, which slows down startup.
Home Assistant Version
2024.12.3
The text was updated successfully, but these errors were encountered: