What can meterN do for you ?
meterN aim is to monitor meters like electrical energy ones. It simply needs to retrieve the total quantity counter value, this reading is done on a 5 min basis.
Some first configuration thoughts
You can set up either : meter and sensor logger and also indicator. The 'Meter' type is used for.. meters ;), 'Sensor' is to monitor any values such as a temperature or an humidity. 'Indicator' is simply for showing a live value that don't need to be recorded, like voltage or frequency
Configuring meters and sensors
When you'll be configuring a meter, you are required to set a main 'Command' that will return the total quantity (eg: Total Liter, Total Watt per hour, Total m³, ..). For a sensor, that could be any value (eg: Temperature, Voltage, ..).
Then you can also set a 'Live command', a non-mandatory value to be shown on the dashbord. meterN will retrieve this one continously, the refreshing time will depend mostly on your communication application.
There is two different live modes: Value or State.
- The value mode is when the com. app. return an instantaneous value (eg: Liter per minute, Watt, ..) But, it could also show a text, like a device status (eg: hot/cold, charging/discharging, ..)
- The state mode, if the com. app. return a '1' for 'On' or a '0' for 'Off' information (eg. the tap is open/close, the boiler is running,..)
For an electrical meter this could be like this : The main command return Watt per hour, the live command return Watt (value mode) or on/off (state mode) or even charging/discharging (value mode).
But wait, we need to speak a common language first !
The output format of the communication(s) application(s) must respect the IEC 62056 data set structure, that look scary but it is quite simple :
It is the same format used in, the better know, "P1 interface" a communication interface available in some smart meters for local communication utility use.
Some valid outputs :
Important notes :
- meterN need to get the values without any unit prefix. eg: elect(39464*Wh) is valid. elect(39.464*kWh) is not.
- For decimal values, only points (not commas) shall be used
- Front "(" and rear ")" boundary characters are needed
- The separator character "*" between value and unit is needed
- The meter counter can't reset to 0 (eg. after a surge), it should always increase until it pass-over.
Now than you've understand how meterN discuss with a communication application, you are ready to set-up !
When you'll start the admin. interface (see the tour), you had to set :
- A meterID corresponding to your meter dataset ID
- A 'Main pooling' command for the communication application that return a quantity value. eg: elect(10923*Wh)
- A pass-over value. It's simply the value up to where the counter can count until it return to zero. It can be disabled by putting it to zero.
- A precision value. It's the meter's resolution, the numbers behind the unity. eg: 3 for a 0.001m³ accuracy
The dashboard pooling section, it's where the (non mandatory) live values will be shown :
Choose one of the two differents modes: Value or State.
- The value mode is when the com. app. return an instantaneous value. eg: elect(256*W)
- The state mode, if the com. app. return a '1' for 'On' or a '0' for 'Off' information. eg: 1(0*W)
House's electrical consumption and production
If you own a electrical production and/or production unit, you can setup a such meters. It will allow to visualize the electical energy flow with the main gauge and in the dashboard .