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
It would be really great if you could store the date / time when an Energy Management device was last reset. See the attached screen shot:
Normally, when a user resets the kWh meter, they want to record how much energy has been used for a period x in time. A simple display of hours / mins since last reset, would help enormously to work out how much energy has been used over time. Without a time reference, it is hard to accurately project past / future usage. Especially if the device is being moved around between appliances.
I realise kWh is in of itself an average measurement but kWh / h is not. Compare it to speed versus acceleration. M/s v's M/s2.
You have a fantastic product. I realize this is icing on the cake.
Describe alternatives you've considered
None.
Is your feature request related to a problem?
No
Additional information
No response
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
It would be really great if you could store the date / time when an Energy Management device was last reset. See the attached screen shot:
Normally, when a user resets the kWh meter, they want to record how much energy has been used for a period x in time. A simple display of hours / mins since last reset, would help enormously to work out how much energy has been used over time. Without a time reference, it is hard to accurately project past / future usage. Especially if the device is being moved around between appliances.
I realise kWh is in of itself an average measurement but kWh / h is not. Compare it to speed versus acceleration. M/s v's M/s2.
You have a fantastic product. I realize this is icing on the cake.
Describe alternatives you've considered
None.
Is your feature request related to a problem?
No
Additional information
No response
The text was updated successfully, but these errors were encountered: