You’re right @Maaniac , the history_stats
component can only track how long a component were in a specific state. It’s not designed to read and save values.
How hard would it be to modify for such a task, assuming time was the only type a numeric state would be valid with?
Is there a way to read the config state as a sensor? To template the output of print_config_parameter?
1 Like
I haven’t tried. print_config_parameter is a service, right? I guess you could read it via the API with a RESTful sensor and parse its output.