Show numeric-sensor history in the activity log - #30
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sensor.*with aunit_of_measurement/state_class), so the activity log showed nothing for e.g. a temperature sensor while binary sensors worked fine.client.fetch_state_logsynthesizes logbook-shaped entries from/api/historyfor these entities;HACLI.fetch_log_entriesmerges them into both the fullscreen graph's and main screen's activity log, rendering the entity's unit (21.5 °C).--demomode, plusFakeHAClient/DemoHAClientparity.Fixes #29
Test plan
pytest(full suite, 1210 passed)ruff check .pyrightDemoHAClientsanity check confirming empty logbook + populated state log for a numeric sensor