Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR]: Allow entity_picture to become optional #230

Open
henriklund opened this issue Feb 4, 2025 · 1 comment
Open

[FR]: Allow entity_picture to become optional #230

henriklund opened this issue Feb 4, 2025 · 1 comment
Labels
feature request New feature or request

Comments

@henriklund
Copy link

Describe the feature you wish to make a request for

Would it be possible to omit entity_picture as an attribute, or have it changed to a reference?

Describe alternatives you've considered

This could either be done through an option in the integration configuration (thus making it optional) or by placing the images in a library on disk (or even both).

Additional context

Reasons are:
a) it does not seem right to include static UI elements as entity attributes
b) removal would eliminate space used in the database(s) storing (what I assume are static) images.

Reg. (b), my observation is that approx. 0,2MB is used per day for storing attributes for the five sensor.affalddk* entities (this is just based on the two days I've had the integration installed). While it does not amount to much, even in one year, and while I could tinker this away by fiddling with the recorder setting in configuration.yaml and do some Influx foo, I still think that maybe it is worth considering if these images belong in their raw form in the attributes in the first place.

Aside from that; nice initiative! Now I can drop my manually updated calendar :)

@henriklund henriklund added the feature request New feature or request label Feb 4, 2025
@briis
Copy link
Owner

briis commented Feb 5, 2025

Yes it would be possible. The thing is, that a lot of people like the pictures, so I would most likely make some happy, and some unhappy.
I need to think about a technical way to make this optional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants