If the content of “items-to-record.yaml” is included with the !include switch or not (directly integrated in the configuration.yaml) seems not to matter.
I tested if it matters if I have the “domains:” named before the “entities:”. It doesn’t.
At the moment I get this result when clicking on my pm25 sensor:
HASS obviously tells me that I dont have state history. Why this? Can anyone help me?
I had the same issue. I was trying to include light and switch as domains, then also include multiple entitites. The recorder was recording all of the domains, but wasn’t recording any of the entities I had specified.
I removed the domains and instead listed each light and switch entity and it now seems to work fine, recording all of the entities I have specified without missing any.
Looking through the documentation it seems you can exclude both domains and entities, but if you include domains, you can only exclude entities; you can’t include both entities and domains.
I don’t use the includes: part but I use excludes: and it works just fine. Just for giggles, try renaiming your .yaml files you include for history: and recorder: to remove the hyphen. it shouldn’t matter but testing has to start somewhere.
EDIT: I see you said you removed the !include part of your configuration file and it still did not show any history. Did you restart HASS or reload the core config, wait a few minutes, then check again? Does your error log (add logger: to your configuration) show any errors? Does your yaml check as valid?
Thanks for asking! Yes it worked before. I started using hass a year ago and had
history:
recorder:
in my config. Everything (really everything) was recorded. My 16GB SD-Card in my Raspi was filled with a database of a size of 10 GB… I then cleared the database and started to minimze the recorded states with
I have just
history:
recorder:
I see history and logs tabs just fine but when i click on any switch/sensor/device… I get No state history found like in 9 of 10 times
I haven’t changed anything in history, recorder or logbook as far as I can remember but suddenly experience problems. Like @t.srubar wrote, most of the times No state history found. Sometimes the history flashes just before, sometimes it shows up. Seems to be more problems with “binary” stuff, motion and other on/off things and less with lux or temperature.
The 62 update seemingly broke something with the history. I also get: “No state history found” in most cases. It worked perfectly well before the update.
Have to downgrade to 0.61.1 because none of my automations fired today as ubus didn’t detect I wasn’t home (although the BLE Tile portion did) – I sometimes get history per sensor/item (and always shows in history tab) but presence detection doesn’t work reliably (ubus+tile) so I’m going to downgrade for now.