Update StateClass of Liters and Seconds sensor #12
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.
While I haven't received mine yet and therefore can't for sure say that this is in fact an issue (hence Draft PR), while researching the topic, I did find this forum post:
https://community.home-assistant.io/t/automation-only-run-if-available-more-than-30-seconds/707187/13
Looking at the protocol documentation here, I can see that the
pulses
are3 bytes
andtime
is2 bytes
.This would mean max values of
~18 hours
and about~6500 liters
, which does sound like it's a lot less than the expected lifetime of a shower head.Therefore, I am relatively confident that the user is right and
TOTAL_INCREASING
is the correct state classConfident enough to open a draft PR at least 🙂
Ref: https://developers.home-assistant.io/docs/core/entity/sensor/#available-state-classes