-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Failed to setup #180
Comments
Same here. thank you |
Same for me. Stops HA from starting. Going to rollback. Rolled back to 6.0.0 and HA starts as normal now. This release needs pulling. |
My Home assistant instance restarted after the the 6.0.1 update with the almost magical message in the core log: There are no issues. Core 2024.12.2 Nice! |
Can confirm I'm experiencing the same behavior with 6.0.1. Rolling back to 6.0.0 solved the issue. |
Same issue here, reverted to 6.0.0 for now. |
Ditto here, rolled back to 6.0.0 |
Same issue here - 6.0.1 fails to setup. Rolled back to 6.0.0 which is fine. |
As a workaround, you can remove your old yaml config and set it up using the GUI, everything seems to work fine. |
As others, I am getting the same error with 6.0.1. @pinkywafer are you able to have a look? I will roll back today |
It has a GUI? Anyway, same issue here, rolling back to 6.0.0 resolves the issue. |
Removing anniversaries from yaml and setting it up in the UI fixed it for me as well. |
Is UI rather than yaml going to be the way going forward? Not wanting to remove yaml unless its unsupported |
Error setting up Anniversaries:
I'm getting the following error message since this morning when I updated to version 6.0.1:
Error
Log file entry:
Additionally, this Warning shows up even with version 6.0.1:
Detected that custom integration 'anniversaries' sets option flow config_entry explicitly, which is deprecated at custom_components/anniversaries/config_flow.py, line 209: self.config_entry = config_entry. This will stop working in Home Assistant 2025.12, please report it to the author of the 'anniversaries' custom integration
The text was updated successfully, but these errors were encountered: