search

custom-components / places

Component to integrate with OpenStreetMap Reverse Geocode (places)
GNU General Public License v3.0
110 stars 22 forks source link

[question] "Places" sensor & Recorder #245

Closed ildar170975 closed 9 months ago

ildar170975 commented 9 months ago

This issue is not a bug report or a FR - it is mainly a question.

A places sensor contains a lot of data in attributes. I believed that all these attributes stored in database - so I excluded all places sensors from Recorder. But may be no all data stored in DB - and hence there is no need to exclude these sensors?

Snuffy2 commented 9 months ago

A places sensor writes to the recorder unless Extended Attributes is enabled. In that case, I exclude it as it is larger than what is accepted by the recorder.

ildar170975 commented 9 months ago

Thank you very much for the answer!

Even w/o "extended attributes" this record seems to be rather huge for me:

изображение

Most of these data are useful & needed, so I think that in a not-powerful PCs (like RPi) users may decide to exclude the places sensors from Recorder. That is why I created a template sensor for storing a state only. The state keeps either a zone's name or a address (if not_home): изображение Hope this is the right settings for me.