Safe to disable sensor.givtcp_xxx_invertor_time from recorder? #2958
-
|
I know the sensor sensor.givtcp_xxx_invertor_time is used by the fantastic Predbat but is it safe to disable logging every second into the recorder? I like to stop heavy hitting yet not needed stats from writing to the db with recorder > exclude but don’t want to mess with battys mojo. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Invertor time and invertor last updated time don't update every second, they only update when they change, which depends on your givtcp poll frequency, so typically every 20 or 30 seconds But short answer is yes you can. Predbat has a limited number of entities it needs to look at the history of, for very many of the predbat and givtcp entities it only cares about the current value so you can exclude them from the recorder. See long article I wrote on the givenergy community forum https://community.givenergy.cloud/d/5458-taming-and-reducing-the-home-assistant-database I do plan an update for the predbat documentation to cover the key points of this for predbat |
Beta Was this translation helpful? Give feedback.
-
|
That was really useful. And with the context of Predbat. Time to optimise. |
Beta Was this translation helpful? Give feedback.
Invertor time and invertor last updated time don't update every second, they only update when they change, which depends on your givtcp poll frequency, so typically every 20 or 30 seconds
But short answer is yes you can.
Predbat has a limited number of entities it needs to look at the history of, for very many of the predbat and givtcp entities it only cares about the current value so you can exclude them from the recorder.
I have disabled a number of my givenergy sensors as I never look at them, for some I do exclude them, and for others I keep them and purge them every night. I personally keep the invertor time as its useful check that givtcp is polling, but then I purge every night.
Se…