2024.02 Recorder not always logging some entities

[RedNo7]

The problem

Since 2024.02, I have several entities that are either not being recorded at all or some that are only partially recorded.

I have 2 instances (in 2 locations), both running HA Container (docker) on RPi-4s. Both are showing this issue but for different entities.

• instance 1] problem is with all timers.
• Instance 2] problem is with some timers and 1 input_select. For that input_select, is it consistently recording one option, but not the other - super weird.

I'm not sure what yaml will help here as I have not not modified anything since 2023.12.x but happy to share anything that is requested.

I see nothing special in my logs other than what I would consider to be 'the usual' errors.

I have also posted this issue here and added to #110620. I am not sure if this is related to #107241.

Example 1 input_select (instance 2)
If I restart, the input_select shows correctly until the next time it changes from Asleep to Awake when it continues to show Asleep again. Here is a screenshot showing it:

Example 2 timer (instance 1)
All 4 times were running when I took this snapshot:

Example 3 timer (instance 2)

• timer.bath is not running, but history shows it is.
• timer.hallway works fine.
• timer.kitchen is running, but history shows it is not.
  

Things I have tried:

• I have removed the entities, restarted, re-introduced the entities - but nothing has changed.
• I have deleted home-assistant_v2.db, restarted - no change.

What version of Home Assistant Core has the issue?

2024.02

What was the last working version of Home Assistant Core?

2024.01

What type of installation are you running?

Home Assistant Container (on RPi)

Integration causing the issue

Recorder ➜ home-assistant_v2.db

Link to integration documentation on our website

https://www.home-assistant.io/integrations/recorder/

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

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (recorder) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of recorder can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign recorder Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

recorder documentation
recorder source
_{^{(message by IssueLinks)}}

[NzKyle]

I wonder if this is something similar to what I logged in #110495?

[RedNo7]

@NzKyle yes,I think they are the same/similar 👍

[ildar170975]

In my setup none timer entity is shown in History properly:

1. Open History with the timer in one tab.
2. On another tab - open more-info for the timer - and start it.
3. On the History tab I see changes:

4. Refresh the page or reopen the History - it has no changes:

Happens even with default recorder settings (i.e. w/o "recorder.yaml").
2024.2.5

[RedNo7]

@ildar170975 yes, this is the same problem.

[RedNo7]

I've lost all trust in recorder. There is no point recording anything if it is unreliable; Sometimes it works and sometimes it doesn't - it's driving me mad trying to diagnose ghosts.

I am struggling to understand why more people haven't noticed this and why HA don't seem to take this seriously.

[iotmarkh]

I have exactly the same issue with recorder since version 2024.2.1. The timer state changes seems not be recorded at all, and for example input_boolean and schedule states are sometimes recorded and sometimes not. Up to now I have only noticed this in helper entities.

[ildar170975]

Guys, can you check with default recorder settings? I mean - w/o exclude/include.
In my test timer was not saved with default settings.

[RedNo7]

Guys, can you check with default recorder settings?

I not sure this will make any difference. If the problem was with those settings, wouldn't it always not work?
...but will try later anyway 👍

btw, I am not using default settings

[ildar170975]

If the problem was with those settings, wouldn't it always not work?

Some bugs may be erratic.

[RedNo7]

Some bugs may be erratic.

True so, as I wrote, I will try it later but just not sure it will show anything as we both have the same symptoms; you with default and me with configured. ...therefore could you also try it with configured settings? (i.e. we both try the each other's way)?

[ildar170975]

could you also try it with configured settings? (i.e. we both try the each other's way)?

My "normal" settings are based on "exclude-rules". After observing the issue, I retested with default settings.

[RedNo7]

My "normal" settings are based on "exclude-rules". After observing the issue, I retested with default settings.

Got it. Will try later today.

[NzKyle]

Definitely something up with recorder and timers - I've got a few timers and I'm not seeing any recorder entries for any of them.

[RedNo7]

it's not just timer. I have issues with some binary_sensors and input_select.

[NzKyle]

Are those used in automations that trigger timers at all? Because that's the issue I was seeing.

[iotmarkh]

Are those used in automations that trigger timers at all? Because that's the issue I was seeing.

In my case indeed yes, the input_boolean and schedule that have this problem are defined as either action or trigger in the same automation that uses these timers.

[NzKyle]

I just upgraded to 2024.3.0 and I'm seeing the same behaviour.

[ildar170975]

Confirm, timer in 2024.3 is still not recorded.

[RedNo7]

Confirm, timer in 2024.3 is still not recorded.

Same.

[StSaens]

I'm seeing similar. In my case it's 2 motions sensors (beweging zoldertrap, beweging zolderkamer) and a group they're both in (beweging zoldergroep).
See image, where I'd expect beweging zoldergroep to be yellow where either member is.

Group options for beweging zoldergroep are both off (Hide members, All entities).
Automations using the group are working as I'd expect, which suggests it's indeed a logging issue. But not limited to timers.

[RedNo7]

Guys, can you check with default recorder settings? I mean - w/o exclude/include. In my test timer was not saved with default settings.

Hi @ildar170975 - OK, checked and it doesn't work whether I use the default settings or customised ones.

[WarC0zes]

Hi,
I have the same problem. My recorder configuration excludes entities, but I still see the history. Or I have times where there is no history.

  purge_keep_days: 3
  exclude:
    domains:
      - device_tracker

RPI4
HAOS: 12
Core: 2024.3.0
Supervisor: 2024.2.1

[RedNo7]

this appears to be fixed in 2024.3.1

I'll keep an eye on* it and report back.

edit: typo*

[NzKyle]

Can confirm - appears to be working on again for me too on 2024.3.1.

I have a feeling (but I'm not entirely certain) - that the fix comes from the changes made in #112718.

[RedNo7]

Still seems good to me.

[ildar170975]

2024.3.1 - my issue seems to be solved