You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :)
The text was updated successfully, but these errors were encountered:
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.
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 :)
The text was updated successfully, but these errors were encountered: