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
Is your feature request related to a problem? Please describe.
Different parts of predbat require input at different scales (pv_power is in watts, for example)
Describe the solution you'd like
Where possible, I'd like predbat to use the unit of the sensor to determine how to scale the output.
As a sidle effect of this, predbat could also issue warnings when the input isn't an expected unit.
Describe alternatives you've considered
At the moment, I'm using a template sensor to convert the value before input to predbat, but this requires extra storage in the db history.
Additional context
As a new user, understanding this all has been the major hurdle to getting something setup. At some point, it would be great if there was a UI for all of this that only allowed likely inputs, like the HA Energy Dashboard does.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Different parts of predbat require input at different scales (pv_power is in watts, for example)
Describe the solution you'd like
Where possible, I'd like predbat to use the unit of the sensor to determine how to scale the output.
As a sidle effect of this, predbat could also issue warnings when the input isn't an expected unit.
Describe alternatives you've considered
At the moment, I'm using a template sensor to convert the value before input to predbat, but this requires extra storage in the db history.
Additional context
As a new user, understanding this all has been the major hurdle to getting something setup. At some point, it would be great if there was a UI for all of this that only allowed likely inputs, like the HA Energy Dashboard does.
The text was updated successfully, but these errors were encountered: