i found the solution.
i configure the pulse meter data with original data and created a virtual sensor (which must have come with one of the latest software updates) with the necessary granularity.
thank you for bringing me on the right track
The Meteohub stores the data Wh (i.e. each LED puklse adds 1 to the count stoerd in Meteohub). If I want kWh all I need to do is divide by 1000 where I want to show the vale as kWh.
e.g. The sensors page currently shows a value of 419963.00 for my import meter, so that is 419963 Wh, or 419.963 ...
Why don't you go with storing Watts instead of kW? Then precision should be fine.
This would not change anything with the granularity. Meters with S0 output only support sending pulses (i.e. to pulsemeter of RFXmeter and their pulse module). With the current implementation Meteohub only considers ...
The sensor (I have one too) is only reporting integer values (watts), so neither of the existing decimal places are used. I'm puzzled why would you want a third unused decimal?
The sensor is sending the impulses to Rfxmeter, 1000 for 1 kwh. With the current ...
gdfde: How are the 2 meters arranged? Is it possible that there is something between them that is consuming 12.5 watts (12.5 wats x 24h => 0.3 kWh). Presumably the meter must use at least some power itself, though 12.5 watts would seem unlikley (you could run a couple of ALIX-1D's on that!).
The RFXReceiver will pass data to Meteohub each time data is received from the RFXMeter.
The RFXMeter can be set to send data at various intervals. I think the default is 30 seconds? If you are not sure how yours is set then taking a look in Meteohub => Inspect Data is probably the simplest ...
thank you for this excellent hint. In my case i just need to find out the frequency of sending data from the RFXReceiver (on which the RFXmeter for the power consumption is connected) to Meteohub :-)
There is only one very small disadvantage...in case, when there are some data ...
I still didn´t get it.
In the calibration section i can configure an offset, which is a fix value, and a factor (i.e. 0.001 for 1000 impuls for 1 kwh).
My problem is, that my power meter counts 0.3 kwh per day too less.
the calibration will not work.
There it´s only possible to configure a fix offset, which is only considered once.
In my case, the offset of 0.3 kwh should be considered on a daily base.
i installed a separate power meter with S0 output, because the powermeter from the energy company does not support S0. This additional power meter is connected with RFXmeter to Meteohub.
Now i have the problem, that the difference between the 1st powermeter, which is relevant for my energy ...
It's definitely not related to RF interference; When I kept the Sheeva powered on in the close vicinity of the NSLU2 (USB still connected to the NSLU2), I was not able to detected any issues. The moment the USB was connected to the Sheeva I experienced more sensitivity issues. Tried a longer USB ...
I don't have a Sheeva myself, and some of these things have already been mentioned or hinted at by earlier posters, but maybe there might be something here that helps?
as I suspect the interfence is coming down the USB line from the base station. If that is the ...