You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Charge Added is a cumulative value of charge diverted (and boosted?) in to an EV, which can span multiple days (charging sessions) until the plug is disconnected. The zappi and myenergi app behaves the same so I'm presuming it's a myenergi API value.
What entity could I use to track 'charge diverted today' and 'charge added today'?
I don't really care about cumulative charge since the plug was connected. Happy for a daily value to potentially include multiple charging sessions.
If there isn't a practical way to do this with the properties currently exposed by ha-myenergi, would I be correct in thinking the feature request I should raise would be to ask for h1d and h1b to be included? Perhaps as h1d_kWh (calculated from h1d / 3600000)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Charge Added is a cumulative value of charge diverted (and boosted?) in to an EV, which can span multiple days (charging sessions) until the plug is disconnected. The zappi and myenergi app behaves the same so I'm presuming it's a myenergi API value.
What entity could I use to track 'charge diverted today' and 'charge added today'?
I don't really care about cumulative charge since the plug was connected. Happy for a daily value to potentially include multiple charging sessions.
If there isn't a practical way to do this with the properties currently exposed by ha-myenergi, would I be correct in thinking the feature request I should raise would be to ask for h1d and h1b to be included? Perhaps as h1d_kWh (calculated from h1d / 3600000)?
Beta Was this translation helpful? Give feedback.
All reactions