Great idea, these options could also appear on the entities pop-up like the Area does now.
1 Like
I think there should be a migration. After the migration process, yaml config will be disabled
1 Like
dev team please make it happen…
How would you handle domains, globs and excludes?
Sacrificing functionality for convenience is not the ways to go.
1 Like
Thanks for bumping this thread, I apparently missed it first time around. It’s got my vote!
I have a related (and possibly conflicting) FR to allow individual keep_days for each entity. I’ve also seen comments about the horrible database design HA uses, which as a former DBA I can confirm.
Maybe we need a “month of database” where fixes, updates and improvements for the database are discussed and a direction agreed upon. It seems this area gets very little development attention.
1 Like
domains could be exposed in the UI, excludes don’t need anything because entities would be unchecked by default.
I don’t know how it could be considered sacrificing functionality, it’s the same, just more convenient.
2 Likes
Yes, if the default is to have entities unchecked, that would solve a lot of problems.
There could be a prompt or option when the entity is created, just as today we’re prompted to add entities to areas.
I had another thought, sort of a combination of this FR and the one I submitted (see above.) What if, instead of check boxes, the display in the OP allowed entry of keep_days for each entity?
Not everything needs to be retained for the same length of time. I may not care how often my living room light was turned on last week, but I do want to keep my heating system run time statistics for months.
I think allowing for a retention setting is a great idea as well.
Would love this as well to better track unwanted database usage. I had an uptime counter being recorded each second up to the millions. No real use case there. Was looking for a quick way to set this for all entities, but requires a lot of exclude/include work.
Still I think it would be possible to set it up in a similar way then e.g. Apple Homekit. If I recall correctly you can set first include/exclude based on categories (or domains), and in the next step click to exclude/include resp. Would be a nice interface to do it.
That could be handled quite nicely, if it’s declared or covered by a glob in yaml then just disable the toggle in the entity settings
I like to have this option as well.
I noticed i had many “unwanted” logging ( few examples below ).
- sensor.processor_use
- sensor.date
- sensor.date_time
- sensor.time
- sensor.time_date
I run home assistant on a RPI 3 connected to a database on my NAS. My nas had a lot of database activities all the time because of the above default enabled loggings. Excluding these entities using yaml is not a big issue and the DB activity dropped a lot but it would be really nice if i can just toggle it from the gui for each entity.
1 Like
Bumping for attention - this would be a really useful feature please!
Agreed, would use this for sure!
You wouldn’t remove existing functionality, you would add an additional filter after the existing filter in the pipeline that could override the global behavior
Regular filter still work
exclude:
entities_glob: sensors.*
on the entity provide a setting that can add it back into the list if its filtered out, or ignore it
some entity:
Logbook Override: dropdown-> Default, Always, Never
or, for the power user, allow setting when the filter is applied, before or after global filter (the before would be applied in code as if they were put in the existing “include → entities” list or “exclude → entities” list from yaml.
some entity:
Logbook: dropdown-> Default, Always, Never , include, exclude
No reason to break anything. There would possibly be the issue that you double listed an entity (one in include and one in exclude for example) but that issue is possible and exists today so its not a new problem. It can be handled the same way or improved upon.
1 Like
Bumping an old thread but very curious if this is on the roadmap… would absolutely use it
bumping up a really useful feature.
Bumping!! Could ABSOLUTELY use this feature!
1 Like
Another bump, I don’t want to log history or anything for bulbs and even some appliance status, I don’t need to know that my washing machine was 70% compete at midday 3 weeks ago 
1 Like
I just thought of another great use for this feature. Sometimes I’d like to keep an eye on a particular entity for a day or a few days. Maybe I’m changing something, maybe I want to verify that an automation has been running correctly, flipping switches or whatever which I typically don’t care about monitoring.
Wouldn’t it be great if we could go into the UI, check a box and start recording all that data which is typically useless? Then when I’m finished debugging, un-check it just as easily.
As far as I know, right now the only way to do this is to modify the YAML and restart HA.