A sensor value is returned as a datetime object for when a battery was last fully charged.
Updates are every 10 seconds and this value may stay the same for a day, or longer when overcast, until the battery is next fully charged.
Another sensor that returns a string value, correctly updates only when that value changes:
Many posts describe blocking datetime values from being recorded, which I do block a number of them, not this one.
This particular value is interesting to know when the battery was last fully charged, but logbook does not work properly for this type of value.
Has anyone had success with a datetime logbook value? Any clues as to what can be done?
I’m thinking next clue will be to look at code to see how a change is determined for logging.
Related to this, some other posts also discuss when a new logbook is created it does not show the initial value when the logbook was created. The initial value should be the next update when the sensor value changes from ‘undefined’ to ‘defined’, with that defined value being the first value logged.
Current behaviour results in the sensor value when the logbook is created is never logged.
There is a battery sensor that may not change for weeks or months, meaning the predominant value for a long period is never logged. /
This leaves a blank logbook that looks like it’s not working properly by not showing the current long-lived value of the sensor.