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

Warning in systemlog about deprecated functions (2024.9) #161

Open
fribse opened this issue Apr 6, 2024 · 5 comments
Open

Warning in systemlog about deprecated functions (2024.9) #161

fribse opened this issue Apr 6, 2024 · 5 comments

Comments

@fribse
Copy link

fribse commented Apr 6, 2024

Anniversaries is at 5.2.0

Saw two warnings about deprecated functions.

First one is the closest version, second is some time away...

Detected that custom integration 'anniversaries' sets "options" directly to update a config entry. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to use async_update_entry instead at custom_components/anniversaries/__init__.py, line 62: config_entry.options = config_entry.data, please report it to the author of the 'anniversaries' custom integration
And
Detected that custom integration 'anniversaries' calls async_add_job, which is deprecated and will be removed in Home Assistant 2025.4; Please review https://developers.home-assistant.io/blog/2024/03/13/deprecate_add_run_job for replacement options at custom_components/anniversaries/__init__.py, line 65: hass.async_add_job(, please report it to the author of the 'anniversaries' custom integration

Just a heads up :-)

@SupremeSports
Copy link

Also got this one:

Detected code that calls async_forward_entry_setup for integration, anniversaries with title: [redacted]'s Birthday and entry_id: 908e1d3405eda80e034fe6c2f7a052d3, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead. Please report this issue.

@loryanstrant
Copy link

Seeing the same one as @SupremeSports in mine too.
Even deleted all existing entries, restarted HA, added one back in and instantly got that message.

@BebeMischa
Copy link

Seeing the same one as @SupremeSports in mine too. Even deleted all existing entries, restarted HA, added one back in and instantly got that message.

Which version of Anniversaries are you running?

@fribse
Copy link
Author

fribse commented Oct 19, 2024

I removed all the anniversaries defined in the GUI, and added them back in yaml, and it works here.
This is anniversaries 6.0.0

@BebeMischa
Copy link

That's strange. I have no more issues with UI generated on 6.0.0 version...

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

4 participants