Skip to content
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

Open
bt-beardedtechie opened this issue Dec 11, 2024 · 12 comments
Open

Failed to setup #180

bt-beardedtechie opened this issue Dec 11, 2024 · 12 comments

Comments

@bt-beardedtechie
Copy link

bt-beardedtechie commented Dec 11, 2024

Error setting up Anniversaries:

I'm getting the following error message since this morning when I updated to version 6.0.1:

Error

Config flow could not be loaded: {"message":"Handler OptionsFlowManager doesn't support step init"}

Log file entry:

Logger: homeassistant.config_entries
Source: config_entries.py:640
First occurred: 11:53:11 AM (3 occurrences)
Last logged: 12:46:19 PM

Error setting up entry configuration.yaml for anniversaries
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 640, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/anniversaries/__init__.py", line 56, in async_setup_entry
    await hass.config_entries.async_remove(config_entry.entry_id)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1921, in async_remove
    unload_success, entry = await self._async_remove(entry_id)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1937, in _async_remove
    async with entry.setup_lock:
               ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/locks.py", line 14, in __aenter__
    await self.acquire()
  File "/usr/local/lib/python3.13/asyncio/locks.py", line 110, in acquire
    await fut
asyncio.exceptions.CancelledError: Global task timeout

Additionally, this Warning shows up even with version 6.0.1:

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:324
First occurred: 12:35:19 PM (1 occurrences)
Last logged: 12:35:19 PM

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

@fft1010
Copy link

fft1010 commented Dec 11, 2024

Same here.
Symptom… HA takes ages to start, and it complains somehow about anniversaries stopping it from working. I needed to make a full new install of HA, and than installed with the last backup. 6.0.0 worked just fine.

thank you
Juergen

@BertrumUK
Copy link

BertrumUK commented Dec 11, 2024

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.

@BebeMischa
Copy link

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
Supervisor 2024.11.4
Operating System 14.0
Frontend 20241127.7

Nice!

@j-inc
Copy link

j-inc commented Dec 11, 2024

Can confirm I'm experiencing the same behavior with 6.0.1. Rolling back to 6.0.0 solved the issue.

@I-G-1-1
Copy link

I-G-1-1 commented Dec 12, 2024

Same issue here, reverted to 6.0.0 for now.

@leonwebcreators
Copy link

Ditto here, rolled back to 6.0.0

@RedNo7
Copy link

RedNo7 commented Dec 13, 2024

Same issue here - 6.0.1 fails to setup. Rolled back to 6.0.0 which is fine.

@cweakland
Copy link

As a workaround, you can remove your old yaml config and set it up using the GUI, everything seems to work fine.

@DrSpaldo
Copy link

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

@SavageAUS
Copy link

As a workaround, you can remove your old yaml config and set it up using the GUI, everything seems to work fine.

It has a GUI?

Anyway, same issue here, rolling back to 6.0.0 resolves the issue.

@mpepping
Copy link

As a workaround, you can remove your old yaml config and set it up using the GUI, everything seems to work fine.

Removing anniversaries from yaml and setting it up in the UI fixed it for me as well.

@Shaun-Harrison
Copy link

Is UI rather than yaml going to be the way going forward? Not wanting to remove yaml unless its unsupported

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests