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

sensor.hc_mode_date_time_daikin is flooding my logbook with every second update #104

Open
nash1975 opened this issue Jun 4, 2024 · 5 comments

Comments

@nash1975
Copy link

nash1975 commented Jun 4, 2024

This sensor is reflecting the date and time of the heatpump.
It is changing every second and by this flooding the history

@Arnold-n
Copy link
Owner

Arnold-n commented Jun 4, 2024

There are so many history changes, so I wonder which ones we should limit, and which not? I like to have the correct time visible on a dashboard and do not use history. For the longer term I'd like to make everything configurable using config-files on the ESP, for now I wonder if this justifies a lower update frequency, or alternatively making an option to have the entity disappear?

@nash1975
Copy link
Author

nash1975 commented Jun 5, 2024

For me ignoring the seconds of the date time and updating on minute change would be the sweet spot.
For my setup I deactivated the entity completely as I have no real need of it.

@Arnold-n
Copy link
Owner

Arnold-n commented Jun 5, 2024

In v0.9.53 a parameter 48 is added to remove reporting of seconds in the time format. Commands required to use this are P48 1 followed by D5.

@WTH70
Copy link

WTH70 commented Oct 3, 2024

You could add this to your configuration.yaml file:

logbook:
exclude:
entities:
- sensor.hc_mode_date_time_daikin

@nash1975
Copy link
Author

nash1975 commented Oct 5, 2024

Thanks, I will try.
I was not aware of this exclude option for the logbook.
I can use also for another entity.

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

No branches or pull requests

3 participants