Your comments

That's too bad. If I were you, I would make a mobile app for ios & android just for energy display (if not for all tellmon functionality. I would purchase such an app.
What is even more interesting is that I CAN ACCESS IT from Tor Browser, on the same computer where no other browser works.

http://crashtest.ninja and http://paks.no are also NOT accessible from Chrome, but accessible from Tor...
it happens to me as well for some time. however, it works from my ios phone, from within the same network. I have the feeling it has something to do with cookies, because it didn't work on ios either, until I cleared the cache & history in safari & chrome mobile. then it started to work, loading the cookie message at first access, and checking the checkmark there. I would suggest to suspend the cookie action temporarely from your website, to see if that solves the problem of accessing your website. a ping or tracert to tellmon.net gets through, though!
it's the old type of sensor, probably Type 1, at least this is how is set for now. 1 Watt hour per blink (1000 pulses means 1 KW on my meter).
Here is for instance how the newly introduced Energy Monitor from Coco Technologgy displays this in their mobile app http://www.klikaanklikuit.nl/shop/nl/producten-1/...



Here you can see the units used to display the numbers. I do not have that actual monitor.

All the monitors on the market display in these unit of measure. So it is just about that, display instant consumption in kWh. You display in kWmin.

And I really can't understand how adjusting the formula to take into account time interval would complicate things in hosting. The result of the formula would be just another number to store. and the calculus I doubt it would be so processor intensive, but yes, I do not know that for a fact, you may know better.
Both your statements are true. It is my "mistake" to refer to "power" I should have said consumption. Anyway, it is nothing incorrect here, except is unusual to display consumption in watts per minute, every minute, and also not make corrections based on timeNow - timePrevious. The graph is a coarse guess and it will never display the real instant consumption numbers. just an aproximation and a trend variation.


Maybe it should take into consideration the way other energy monitors on the market display their numbers for instant consumption.


I guess I have a lower footprint than most of the users. 2 points threshold for me is way too much. I deal with 0.1 - 0.8 graph movements so far, occasionally (rarely)  I reach 2.0. Please bear in mind that these numbers are PER MINUTE values, since you decided to display consumption in kW/minute, which is unusual.
The real problem with the measurement without implementing a formula involving TimeNow - TimePrevious is that each 0.1 given by the sensor as temperature translates into 60Wh. Nothing in betwin, if measurement is done every 60 seconds but on server side the logging time is not taken into account.
I have counted the number of blinks myself and noticed that if there are 4 blinks over one minute for 240W indicated by my digital meters, the sensor also sends 0.4 value. That means the power consumed in this minute (for 1000 blinks/kW) it is given by formula:

4 blinks per passed time between 2 records / 1000 blinks per kW = 0.004 kW in the passing time

If I had a 324 blinks within one minute, the sensor would have sent 32.4 at one recorded time. and the consumption in that minute would be:

4 blinks per passed time between 2 records / 1000 blinks per kW = 0.324 kW in the passing time

All goods, but the power is displayed in kWh not kW. So the last number should be transformed to kWh. Say the interval for the above example is exactly 60 seconds; that means the numbers in kWh would be 0.24kWh and 19.44kWh, which is the nominal power.

In fact the precise formula is given by FooGadgets:

Pmom = temp*10/1000*60* 60/(Time_now - Time_previous)

That means that the way is displayed now, it is correct, but with confusion, because the power is usually expressed in kWhour not kW. That's all. I dare to suggest to implement this exact formula, to avoid missunderstandings. It is much more intuitively to read an energy meter that shows an instant consumption of say 0.240kWh instead of 0.004kW since the last reading. Otherwise, eeach user would have to figure out by multiplying 0.004 with 60 minutes.



I understand. 

What I don't understand is why my plug meters show something so different than Energy Meter. I mean, is desirable to consume 200W and my counter have on record 5W, but I don't think this is the actual fact. I have rechecked the alignment of the sensor, and is ok.