Your comments
How does this prevent using it? 2 degrees is 0.02 kW. Shouldn't that be more than high enough resolution? If I have a lower reset threshold I'll end up jamming people with emails. A lot of the sensors are fluctuating +/- 1 degree and it would cause the alarms to set, reset, set, reset a whole lot.
11 years ago
This is all from: http://foogadgets.tictail.com/product/wireless-ene...
The primary sensor and the secondary sensor both consists of a temp/humidity pair.
The temperature is the number of blinks the last minute (/10). The humidity is a reading counter (0-99).
The secondary sensor is showing the primary sensors previous value. So using the humidity counter one can detect that a package has gone missing and then use the secondary sensors value instead.
Tellstick is not a reliable system and packages go missing all the time. That is why FooGadget has built in the secondary sensors as a backup. The primary and secondary values should follow each other. If not, there is something very wrong. Perhaps you need to update the firmware of the energy meter.
Tellmon does not support the secondary sensor yet since it's monitoring about 2100 sensors and 4900 devices the database is about 5 GB pr. month since I store all values. I'm working on resampling the data into hourly averages for data more than one month old. I'm also looking into ways to support the secondary sensor, but it needs to be in a way that is not CPU intensive because of the large volume of data coming in.
The primary sensor and the secondary sensor both consists of a temp/humidity pair.
The temperature is the number of blinks the last minute (/10). The humidity is a reading counter (0-99).
The secondary sensor is showing the primary sensors previous value. So using the humidity counter one can detect that a package has gone missing and then use the secondary sensors value instead.
Tellstick is not a reliable system and packages go missing all the time. That is why FooGadget has built in the secondary sensors as a backup. The primary and secondary values should follow each other. If not, there is something very wrong. Perhaps you need to update the firmware of the energy meter.
Tellmon does not support the secondary sensor yet since it's monitoring about 2100 sensors and 4900 devices the database is about 5 GB pr. month since I store all values. I'm working on resampling the data into hourly averages for data more than one month old. I'm also looking into ways to support the secondary sensor, but it needs to be in a way that is not CPU intensive because of the large volume of data coming in.
I think you need to recalculate that. 0.5 * 10 * 1 / 1000 is actually 0.005.
But I agree that there is something wrong somewhere :)
But I agree that there is something wrong somewhere :)
The graph values are rounded to two decimals. 0.004 rounded is 0.00 so the label is fine.
The formula used to convert the "temp" reading to kW is:
kW = temp * 10 * WhPrBlink / 1000
Your sensor is reporting a temp value of 0.5. And you have entered that your power meter blinks once pr. Wh.
0.5 * 10 * 1 / 1000 = 0,005 kW which corresponds to what your graph is showing. Either your value for Watt-hours pr. blink is wrong (see https://tellmon.userecho.com/topic/412401-how-to-s... or your reader is not aligned properly to catch all the "blinks".
Either way, please contact FooGadgets where you purchased your power reader as I don't have anything to do with them.
kW = temp * 10 * WhPrBlink / 1000
Your sensor is reporting a temp value of 0.5. And you have entered that your power meter blinks once pr. Wh.
0.5 * 10 * 1 / 1000 = 0,005 kW which corresponds to what your graph is showing. Either your value for Watt-hours pr. blink is wrong (see https://tellmon.userecho.com/topic/412401-how-to-s... or your reader is not aligned properly to catch all the "blinks".
Either way, please contact FooGadgets where you purchased your power reader as I don't have anything to do with them.
Should be fixed now
I did some bug fixing. Can you please have another try now?
I updated tellmon about 1.5 hours ago. I must have introduced a bug then. Will look into it. I dont have an energy meter myself, so it's a bit tricky to test for it.
Support for multiple sensors on same graph has been added.
It will come. In some form or another.
Customer support service by UserEcho