@bdraco is there a good way to programmatically exclude an entire entity from the recorder similar to how you can do it in configuration.yml? That is what @gcobb321 and I were doing with recorder_history_prefilter in icloud3, places, and hass-variables and what is causing the error above posted in multiple other issues since 2024.7 was released.
I guess we could alternatively just exclude all of the attributes of an entity using MATCH_ALL but it notes that this needs to be a class attribute. As a class attribute can I still make it an option per instance to enable this in the recorder or not?
I love HA however the removal of the switch functionality from the Logitech Harmony integration is such a backwards step in useability. Now instead of doing easy setup and changes through the UI, I have to resort to YAML in scripts and automations just to make the activities work the way I want. Select doesnāt work for everyone one, especially if your hub controls devices & activities that arenāt used together, like a tv and fireplace fan. Such an easy thing has now been made so much more difficult, especially when itās not like Logitech is changing their API, it seems kinda pointless to remove now, it just makes things so much harder for folks to setup how they actually want and had working already. If it aināt broke, donāt āfixā itā¦
Anyway said my bit, Iāll go back to writing YAML for the next few hours for the many multuple activities that were already working fine beforeā¦
I do have to agree here, i always thought that HA ethos was if it works today it should work forever unless the vendor changes something or there is a technical reason why it needs to change to prevent issue elsewhere or further down the line.
However in the case of harmony the only reasoning given for the removal of the oh so simple switches was that we donāt need multiple ways to switch activities - why not?
Seems you know where you are talking about, so I dare to ask thes question here: What is the meaning with all the cards and the tile-card?
Is the tile card going to be the new Swiss army knife of all cards, and is it thinkable that the rest of the cards will be deprecated/absolete in the future?
Will the tile-card be āthe oneā?
If the other cards are going to be redesigned, will the be soms sort of consistency between the cards? Right now, styles/form and presentation is quite a messā¦
Looking forward to help out, if consistency in presentation/styling will be on the roadmapā¦ Margins/paddings/cards/fonts/pages/everything seems to be inconsistent when you look at the styling and presentation of the UI.
Iām not a user of the Harmony integration but as far as I understand, the change was to remove individual activity switches in favour of a single select entity. How would that force you to use YAML?
Can you give an example of how you use the switches now?
I gave the new core a go and had a few oddities - my qbittorrent integration suddenly didnāt expose qbittorrent_all_torrents for example. Iāve reverted will try the next release.
this Historical Data āissueā is mentioned a few times in this release thread but no one will give more info than āitās not workingāā¦history is working for many (me included) so those with issues should probably start giving some more info around install type, database used, logs, etc, etc and/or open a GitHub issue or this is just going to drag on without a fixā¦and I can only imagine the frustration itās causingā¦
I can give info about my installation. Energy dashboard is not working anymore since I installed the update. Also long term statistics view using developer tools is completely empty. If I try to go to my energy dashboard configuration, I only see āUnknown Errorā and a back button. The most obvious error I see that is related to this is this one:
Logger: homeassistant.core
Bron: core.py:1559
Eerst voorgekomen: 4 juli 2024 om 09:41:45 (1322450 gebeurtenissen)
Laatst gelogd: 14:47:00
Error running job: <Job listen * HassJobType.Callback <function Recorder.async_initialize.<locals>._event_listener at 0x7f1f0e05b100>>
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/icloud3/support/recorder_prefilter.py", line 123, in entity_filter
return recorder_entity_filter(entity_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not callable
Setup details:
Core 2024.7.0
Supervisor 2024.06.2
Operating System12.4
Frontend 20240703.0
Using MariaDB as add-on as my database version 2.7.1
Hope this helps? Happy to provide additional info if neededā¦
Since updated to 2024.7, I observed issue where all the sensors are no more recording data to database (I use default HA config). Also CPU is increasing at that moment till I reboot. Itās second time occurring.
When restarting , seems the DB was locked as I see : The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
There is no logs for any particular issue related to recording. Sensors still updated and I can see live data but not stored anymore. From my point of view, itās something introduced with 2024.7ā¦
Iām the only one with this ?
How can I troubleshoot ?
The first problem appear at 4am when there is db cleanup core routine (my 2 cents). Restarting result that DB is storing again and energy dashboard was again running but at 2pm, itās stopped again, resulting in this kind of data missing dashboard;
