This object is in archive!
Consumption graphs aren't scaled
Under Consideration
it's impossible to monitor a device using less than 50-100 watt (unit in kWh).
Can you auto-scale the graph (normalize it's amplitude) ?
I like this idea 
No connection
Real-time notifications may not work
You mean on "Energy" or "Current value" widget?
Because "Energy" widget graph is auto scaled and "Current value" widget minimum scale is 100 but we can lower that.
You mean on "Energy" or "Current value" widget?
Because "Energy" widget graph is auto scaled and "Current value" widget minimum scale is 100 but we can lower that.
You'll find attached a screenshot. I've a dimmer with a powermeter integrated. The light use something like 50-60W at full power. kWh aren't a good unit for a 60W light on a dimmer :)
You'll find attached a screenshot. I've a dimmer with a powermeter integrated. The light use something like 50-60W at full power. kWh aren't a good unit for a 60W light on a dimmer :)
Ok, the thing is that on "Energy" graph you can see only cumulative consumption (kWh) of the device.
Current consumption is measured in W witch is not shown on graph but we have a plan to add that.
Ok, the thing is that on "Energy" graph you can see only cumulative consumption (kWh) of the device.
Current consumption is measured in W witch is not shown on graph but we have a plan to add that.
Ok, then perhaps there is a bug : in my opinion it is the instantaneous value which is displayed here.
I used my light this morning, and the attribute CURRENT_CONSUMPTION was set to 33,7W during something like 30min. The attribute CUMULATIVE_CONSUMPTION is much higher than that (curently 1.46kWh).
Clearly, we can observe a little pick. Without a reset, a cumulative consumption need to be a strictly growing curves, in my opinion.
Moreover, i suspect that the probleme can come from the configuration for my Aeon Labs Smart Illuminator.
I request the CURRENT_CONSUMPTION in one group and the CUMULATIVE_CONSUMPTION in another group. I'm not sure (test in progress), but i seems that the opposite occurs and the two groups are interchanged ( i've differents intervals).
However, values in the events widget are consistents with the label.
Ok, then perhaps there is a bug : in my opinion it is the instantaneous value which is displayed here.
I used my light this morning, and the attribute CURRENT_CONSUMPTION was set to 33,7W during something like 30min. The attribute CUMULATIVE_CONSUMPTION is much higher than that (curently 1.46kWh).
Clearly, we can observe a little pick. Without a reset, a cumulative consumption need to be a strictly growing curves, in my opinion.
Moreover, i suspect that the probleme can come from the configuration for my Aeon Labs Smart Illuminator.
I request the CURRENT_CONSUMPTION in one group and the CUMULATIVE_CONSUMPTION in another group. I'm not sure (test in progress), but i seems that the opposite occurs and the two groups are interchanged ( i've differents intervals).
However, values in the events widget are consistents with the label.
You are right CUMULATIVE_CONSUMPTION is value that grows over time. But on energy graph we are doing calculation that is showing total consumption over some time period (hour, day, week...). You cold better see that if you switch chart type to Column.
You are right CUMULATIVE_CONSUMPTION is value that grows over time. But on energy graph we are doing calculation that is showing total consumption over some time period (hour, day, week...). You cold better see that if you switch chart type to Column.
Ok. However I'm a little disappointed with your choice of calculating a value who already exist in the sensor. And cumulative consumption or not, I really think that kWh aren't the good unit to measure the (cumulative) consumption of a dimmer, who can consume 500-600W max. And with led lights it will just be impossible to monitor.
The only graphical view where I can check past values isn't usable for me .......
(But don't worry, I like my zipabox ! Just add some graphs to check past values for meters... It's a must)
Ok. However I'm a little disappointed with your choice of calculating a value who already exist in the sensor. And cumulative consumption or not, I really think that kWh aren't the good unit to measure the (cumulative) consumption of a dimmer, who can consume 500-600W max. And with led lights it will just be impossible to monitor.
The only graphical view where I can check past values isn't usable for me .......
(But don't worry, I like my zipabox ! Just add some graphs to check past values for meters... It's a must)
CUMULATIVE_CONSUMPTION witch is measured in kWh that only grows over time is not usable if we show it on graph as it is. So we decided to make calculation that uses cumulative consumption values reported by device and represent it as total consumption in some time period.
Lets say you want to know how much energy (kWh) you spent last month.
If we show you cumulative consumption values reported by your meter you would need to find first and last value that was reported last month and subtract them. It's a very inconvenient so we are doing that calculation for you. You can also choose different time periods to display (hour, day, week, month, year).
And we will certainly add graphs for past meter values, don't worry :)
CUMULATIVE_CONSUMPTION witch is measured in kWh that only grows over time is not usable if we show it on graph as it is. So we decided to make calculation that uses cumulative consumption values reported by device and represent it as total consumption in some time period.
Lets say you want to know how much energy (kWh) you spent last month.
If we show you cumulative consumption values reported by your meter you would need to find first and last value that was reported last month and subtract them. It's a very inconvenient so we are doing that calculation for you. You can also choose different time periods to display (hour, day, week, month, year).
And we will certainly add graphs for past meter values, don't worry :)
Ok, i understand. But it's curious to add an advanced functionnality like that without graphing raw data before !
I'll count days until the past-values graph ! :)
Ok, i understand. But it's curious to add an advanced functionnality like that without graphing raw data before !
I'll count days until the past-values graph ! :)
Replies have been locked on this page!