-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
0.111.0: Upgrade from 0.110.7 fails #36654
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
Comments
Hi there @bacco007! Thanks for opening up an issue. This is usually caused by integration not handling its options correctly when using split configuration / packages. Unfortunately, we can't figure it out by error message. The only wait to attach this currently is by trying to disable/enable each integration you have defined in a package one by one, until you find the culprit. If you've found it, could you share the name of the integration, so we can take a look? Thanks! 👍 |
Turns out its the OpenUV integration - removing it from my config appears to have resolved the problem. I get that it's now a deprecated way of configuring the integration, but is it supposed to fail like this or more gracefully? |
@bacco007 Its a bug, has nothing to do with the deprecation itself. Thanks for pointing out the integration! 👍 |
openuv documentation |
< 8000 details-menu class="dropdown-menu dropdown-menu-sw show-more-popover color-fg-default" style="width:185px" src="" preload >
Hi ! Same issue for me but I don't have any openuv integration. I can't find why this upgrade is rolling back :( and now my google cast integration doesn't work. |
@frenck What’s suggestion here? Have an empty schema (with a deprecation notice, perhaps)? |
Sorry, I planned to look at it, but life got me drifting off my target. https://github.com/home-assistant/core/blob/dev/tests/test_config.py#L1034 |
The fix is tagged for 0.111.1, which is on route now. Thanks for reporting @bacco007 |
The problem
Attempted to upgrade from Supervisor panel, update downloads and reboots - but does not complete update, rolling back to 0.110.7
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: