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
In my heatpump are counter for the on-time of heating, cooling, warmwater, overall running time.
But units are not kWh or liters but ... MINUTES.
The direction is not strictliy in the categoriy "consumed" or "delivered", but "delivered" is ok, running is a kind of delivering work :-) Or think about a "costs/earnings" type of "runtime" ....
Please think about time units, like minutes or hours. Days, years ..... as unit seem odd to me.
IMHO months (and quarters) is a bit off, but something like "2 years, 230 days, 8 hours, 34 minutes" looks more common to me. If original unit is minutes, always show minutes. Alternativly it is also sufficient to keep it minutes (or the selected value, could be also in hours) and dont calculate with 60 mins, 24h, 365 days, just to keep it simple.
Also there is a simple UP-counter (of starts of the heatpump, cooling starts ...) since start of the heatpump. So there is a unit of "counter", with no direction (cost/earnings = consumed/delivered) but simply counts, no monthly "costs" here to calculate.
Might be interesting to put this counter also in rotation timeslots as the original task of sourceanalytics.
Thank You!
cu
Harvey
PS: please also look into the problem #905 with the not running midnight scheduler - thank you
PPS: bye the way "heatpomp" in the admin page/costs is a typo :-)
The text was updated successfully, but these errors were encountered:
HI,
In my heatpump are counter for the on-time of heating, cooling, warmwater, overall running time.
But units are not kWh or liters but ... MINUTES.
The direction is not strictliy in the categoriy "consumed" or "delivered", but "delivered" is ok, running is a kind of delivering work :-) Or think about a "costs/earnings" type of "runtime" ....
Please think about time units, like minutes or hours. Days, years ..... as unit seem odd to me.
IMHO months (and quarters) is a bit off, but something like "2 years, 230 days, 8 hours, 34 minutes" looks more common to me. If original unit is minutes, always show minutes. Alternativly it is also sufficient to keep it minutes (or the selected value, could be also in hours) and dont calculate with 60 mins, 24h, 365 days, just to keep it simple.
Also there is a simple UP-counter (of starts of the heatpump, cooling starts ...) since start of the heatpump. So there is a unit of "counter", with no direction (cost/earnings = consumed/delivered) but simply counts, no monthly "costs" here to calculate.
Might be interesting to put this counter also in rotation timeslots as the original task of sourceanalytics.
Thank You!
cu
Harvey
PS: please also look into the problem #905 with the not running midnight scheduler - thank you
PPS: bye the way "heatpomp" in the admin page/costs is a typo :-)
The text was updated successfully, but these errors were encountered: