After 2022.11 filters broken

I’ve updated to 2022.11 and I notice now it takes a REALLY long time for HA to start up and I don’t understand why or where to look.

I do see this in the log, but it doesn’t explain what/why it takes many minutes to start when it was nearly instant before?

Starting sensor.filter, not everything will be available until it is finished.

Go here Open your Home Assistant instance and show your repairs. then from the overflow menu choose Integration Startup Time. Perhaps an integration is in need of an update.

Unsure if it’s related, but I also apparently can’t downgrade to my backup of 2022.10.5 (it tries but stays at 2022.11).

Very frustrating :frowning:

Run

ha core update --version 2022.10.5

Your filter integration is probably at fault. It is taking an order of magnitude longer to setup than anything else.

1 Like

Yes, as I said in the start of the thread it’s giving a warning that the filter is starting up for a really long time.

I don’t see anything in breaking changes or release notes about why it would go from like ~1 minute to ~10 minutes with the change of versions?

That downgrade command did work, and now once again it starts up super fast. I think there’s something wrong in 2022.11 version.

All I did was downgrade the core with your command and this is the startup times, practically instant again:

Yes but now we have quantified it! Can you please bump up logging on filter and post an issue on github. It is the only way these things get fixed. There are none at present, so it may be something in your setup. Issues · home-assistant/core · GitHub

Happy to create an issue for it (this isn’t my first I’ve found) - suggestion on what to set for logging so I can attach the most appropriate thing? I’ve not had to increase logging previously and didn’t see anything in the regular log output.

1 Like

Thanks, I got the logfile (truncated ~2 minutes after it started up because it’s HUGE) and posted to my issue ticket.

Still seems to be an issue in 2022.12 now as well.

Also looks like the issue causes filters to not update (flat-line) if you wait for it to eventually load.

Example - going from 2022.10.5 → 2022.12.1 for a few hours → rollback 2022.10.5