Wth we can't configure the recorder via UI

It would be much more helpful to be able to do this via GUI, it would be easier for newcomers, it’s not very hard, but I remember struggling a bit when I first started.

Don’t forget to vote for your own WTH.

1 Like

For integration, device, and entity

1 Like

+1 I’d like to be able to add/remove entities to the recorder in the UI rather than having to use a black/whitelist in the yaml

Currently everything is being tracked which is way too much but I can’t be bothered to add everything manually in the yaml file.

4 Likes

This is my #1 most-wanted feature. As a template, I’ve liked how I can set device/entity rooms that cascade but can be configured separately if necessary.

I would add that a default option should be configurable somewhere in HA. Meaning, default exclude or include on the GUI toggle for each entity when they’re first added to HA.

2 Likes

oh yes! I don’t need to record everything - it would be great to be able to just tick and untick a box (and preferably: unticking a “record this entity” box would also clear it out of the database’s history)

9 Likes

Hi everyone,

Here’s a quick summary of my suggestion:

  • Add the ability to include sensors in the Recorder directly from the UI.
  • Place this option in the detailed sensor view alongside existing options like “Enabled,” “Visible,” and “Area.”
  • Simplify the process without requiring manual YAML configuration.
  • Improve user experience for customizing data logging.

Currently, adding sensors to the Recorder in Home Assistant requires editing YAML files, which can be cumbersome for many users. It would be incredibly helpful to have a user-friendly option in the detailed settings view of each sensor. This view already includes options like “Enabled,” “Visible,” and “Use area of device,” so it seems like a logical place to include a toggle for Recorder integration.

This feature would make it much easier to manage storage space and focus on logging only the most relevant data, all without leaving the UI.

Best regards,
Thomas

There should be a WTH for the forums, named ‘WTH why doesn’t forum posts automatically upvote my own posts?’ :sweat_smile:

3 Likes

I +1 this request and adding a different retention time per sensors.

2 Likes

Could be link with WTH we can not easily control data retention for entities

2 Likes

And to really top it off, while adding an entity actively provide the user with a pop-up stating the preferred/most common settings for the recorder. And when looking up some old value which is currently disabled/ not recorded, give the user a meaningful reply with a direct link to where to enable it.

As I have commented in past years’ WTH months, it would be nice to have a GUI list-with-checkboxes capability for all integrations that use include/exclude lists for entities, as well as enabled/visible/whatever as proposed upthread.

And it would be particularly nice to see it for multiple integrations at a time, so I can scroll down the list/tree of entities and view or change Enabled/Visible/Recorder/Logbook/InfluxDB/Homekit (for example) for each entity all at the same time - so I can avoid making consistency mistakes when setting up new devices. For example, “why is this sensor being sent to Homekit but not recorded in the DB?” That would really be helpful and avoid having to go back and forth between lists.

We could call it something like “Domain and Entity Management.”