-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Utility Meter should allow setting a yearly offset on a specific day #20918
Comments
Hi @RezzZ |
Currently you use 15 |
Thanks @dgomes ! And one more question. |
The utility_meter source MUST be an energy value (therefore expressed in kWh) I would use "Energy Total" |
Sorry for all the question!
or
It is not very clear into the description |
currently:
If my PR gets merged (fixing this issue):
|
Take my word, use Energy Total. If you setup a daily utility_meter the values in "Energy Today" and "Energy Yesterday" will hopefully be the same, proving that the utility_meter is working correctly. Even if the energy total resets, you will lose a very small amount of energy account . |
Ok thanks for that info! |
And last ... promise! |
no, that's the all point of utility_meter, it resets for you |
Awesome! |
Home Assistant release with the issue:
0.87.0
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
RPi3b+, raspbian stretch (up to date), docker
Component/platform:
utility_meter
Description of problem:
I just enabled the new utility_meter:
https://www.home-assistant.io/components/utility_meter/
and want to set the offset for the yearly sensors to May 11th.
According to @dgomes (who was kind enough to reply awesomely quick here (#19718 (comment)) the offset for yearly sensors is the nr of months.
Unfortunately in the Netherlands cycles never start on the 1st of a month (unless you actually buy a house on the 1st of a month and start your energy contract at that date). Did I misunderstand of can we actually set a specific day of a year for the offset cycle? like daynr?
The text was updated successfully, but these errors were encountered: