-
Notifications
You must be signed in to change notification settings - Fork 21
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
sqlalchemy problem: "Requirements for ltss not found" #52
Comments
Hi, The manifest.json for v2.0.1 can be found here: https://github.com/freol35241/ltss/blob/v2.0.1/custom_components/ltss/manifest.json It clearly states Can you please confirm that you have actually upgraded LTSS to v2.0.1 ? |
The best way to check is to look at what is actually inside your custom_components directory. Also, don't forget to restart home assistant after downloading custom components with hacs. |
Hmm, that's weird catch 22 but not much I can do from the ltss side. I think you are better of raising this as an issue in hacs and/or home assistant. I guess a workaround is to simply do a reboot to force a restart of home assistant. |
I have the same issue after the update
I did a rollback to v1.1.0 |
Rollback didn't work... problem persists. |
@verstrepeng
|
Updating to Home Assistrant 2023.3.0 and ltss 2.0.1, I get this when trying to restart:
The system cannot restart because the configuration is not valid: Integration error: ltss - Requirements for ltss not found: ['sqlalchemy>=1.0,<2.0'].
Caused by, presumably,
Setup failed for custom integration ltss: Requirements for ltss not found: ['sqlalchemy>=1.0,<2.0'].
Which in turn comes from
2023-03-02 07:37:10.778 ERROR (SyncWorker_9) [homeassistant.util.package] Unable to install package sqlalchemy>=1.0,<2.0: ERROR: Cannot install sqlalchemy<2.0 and >=1.0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
The text was updated successfully, but these errors were encountered: