Several integrations fail since 2024.7.0

[littletruckman]

The problem

Several integration are failing since the latest update to 2024.7.0.

Returning to 2024.6.4 solve the issues

2024-07-04 15:57:31.544 ERROR (MainThread) [homeassistant.core] Error running job: <Job listen * HassJobType.Callback <function Recorder.async_initialize.._event_listener at 0x7f9bbd24ca40>>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/core.py", line 1559, in async_fire_internal
self._hass.async_run_hass_job(job, event)
File "/usr/src/homeassistant/homeassistant/core.py", line 938, in async_run_hass_job
hassjob.target(*args)
File "/usr/src/homeassistant/homeassistant/components/recorder/core.py", line 330, in _event_listener
if entity_filter(entity_id):
^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/places/recorder_history_prefilter/recorder_prefilter.py", line 123, in entity_filter
return recorder_entity_filter(entity_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not callable

What version of Home Assistant Core has the issue?

2024.7.0

What was the last working version of Home Assistant Core?

2024.6.4

What type of installation are you running?

Home Assistant Container

Integration causing the issue

solaredge, daikin_onecta, places....

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[alrassia]

Could you please attach a full log, the posted part offers only limited information

[joostlek]

This sounds like an issue with theplaces custom_component. You should it open it at their issue tracker

[littletruckman]

Not only if you read description.

Daikin also report same issue in core.
Seems to be related with history values

[littletruckman]

@alrassia : Not sur the full log will help since it contains tons of the same error for several integrations (on top of the fact that it contains personal data) ;-)

@joostlek : Sorry about my previous answer. I was to fast. You are right it seems that this is always the places component that is the root cause of troubles.

Nevertheless, switching back HAcore to 2024.6.4 solve the issue. Maybe there is an issue with recorder component ?
I am not a developer :-) so do you think this is part of HAcore ?

BR

[joostlek]

No, this is something that places does wrong. it might use internal functions that are not meant to be used this way. That's not supported. It might as well just be a regression, but that would require the places maintainer to look into this, since we don't do support for custom integrations

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.