-
Notifications
You must be signed in to change notification settings - Fork 4
IEC 62056 21 Meter Binding
Documentation of the IEC 62056-21 meter binding bundle
This binding is used to communicate to metering devices supporting serial communication according IEC 62056-21 mode C master. It can be used to read metering data from slaves such as gas, water, heat, or electricity meters. For further information read Wiki page of IEC_62056-21.
Information receive from the meter device are structured according IEC 62056-6-1:2013, Object identification system (OBIS). For further information read Wiki page of OBIS ("Object Identification System").
For installation of the binding, please see Wiki page Bindings.
The openhab.cfg file (in the folder '${openhab_home}/configurations') contain following config parameters to configure the binding. The configuration allows the definition of multiple meter devices.
######################### IEC 620562-21 Meter Binding ####################
# the serial port to use for connecting to the metering device e.g. COM1 for Windows and /dev/ttyS0 or
# /dev/ttyUSB0 for Linux
iec6205621meter:<meter-id1>.serialPort=/dev/ttyS0
# Delay of baud rate change in ms. Default is 0. USB to serial converters often require a delay of up to 250ms
# default is 0ms
iec6205621meter:<meter-id1>.baudRateChangeDelay=0
# Enable handling of echos caused by some optical tranceivers
# default is true
iec6205621meter:<meter-id1>.echoHandling=true
# Perform a module status query every x seconds (optional, defaults to 600 (10 minutes)).
iec6205621meter:refresh=60
NOTE: the <meter-id1>
will be used in both the binding item configs and the action calls to defined which of your meter devices is connected to the item.
In order to bind an item to the data received from the meter device , you need to provide item configuration settings. The easiest way to do so is to add some binding information in your item file (in the folder configurations/items`). The syntax of the binding configuration strings accepted is the following: The syntax of an item configuration is shown in the following line in general:
iec6205621meter="<meter-id>:<OBIS>"
Where meter-id matches one of the ids defined in your openhab.cfg file.
If you do not know the available OBIS on your meter device you propably find them on the local HMI of you meter device. Please review you manual of the meter device or read the instruction of your utility. You can also start openhab in debug mode, the binding will then dump all available OBIS it receives from the meter device in the osgi console.
Below is an example of represent the current energy counter tarif values as numeric items.
/* IEC 62056-21 Meter data */
Number Tarif_Period "Chart Period"
Number Tarif1 "High price tarif [%d kwh]" (gEnergy) { iec6205621meter="meter1:1.8.1" }
Number Tarif2 "Low price tarif [%d kwh]" (gEnergy) { iec6205621meter="meter1:1.8.2" }
In order to calculate the daily accumulated energy consumption below item and script will allow you to present a chart in your sitemap. First create the necessary items:
Number Tarif1Today "Daily Consumption High Price" (gEnergieConsumption)
Number Tarif2Today "Daily Consumption Low Price" (gEnergieConsumption)
Second add below script to your rules:
rule "Energy chart"
when
Item Tarif1 changed or
Item Tarif2 changed
then
var Number tmp
var Number stopTarif1
var Number stopTarif2
var Number startTarif1
var Number startTarif2
if (Tarif1.state instanceof DecimalType && Tarif2.state instanceof DecimalType) {
stopTarif1 = Tarif1.maximumSince(now.toDateMidnight).state as DecimalType
stopTarif2 = Tarif2.maximumSince(now.toDateMidnight).state as DecimalType
//Today
startTarif1 = Tarif1.minimumSince(now.toDateMidnight).state as DecimalType
startTarif2 = Tarif2.minimumSince(now.toDateMidnight).state as DecimalType
tmp = stopTarif1 - startTarif1
postUpdate(Tarif1Today, tmp)
tmp = stopTarif2 - startTarif2
postUpdate(Tarif2Today, tmp)
}
end
Third add below Frame to your sitemap:
Frame label="Energie" {
Text item=Tarif1 {
Frame {
Text item=Tarif1
Text item=Tarif2
Chart item=gEnergieVerbrauch period=D refresh=600
Chart item=gEnergieVerbrauch period=W refresh=3600
}
}
}
The binding has been successfully tested with below hardware configuration:
- Landis & Gyr meter ZMD120AR connected via IR-Reader from open hardware project in volkszaehler
Installation
Community
- Support
- News Archive
- Presentations
- How to Contribute
- IDE Setup
- How to Implement a Binding
- How to Implement an Action
- Projects using openHAB
- User Interfaces
- Classic UI
- iOS Client
- Android Client
- GreenT UI
- CometVisu
- Bindings
- Asterisk Binding
- Astro Binding
- Bluetooth Binding
- Comfo Air Binding
- CUL Binding
- CUPS Binding
- digitalSTROM Binding
- DMX512 Binding
- EnOcean Binding
- Epson Projector Binding
- Exec Binding
- Fritz!Box Binding
- Fritz AHA Binding
- GPIO Binding
- HDAnywhere binding
- Heatmiser Binding
- Homematic Binding
- HTTP Binding
- IHC / ELKO Binding
- Insteon Hub Binding
- Insteon PLM Binding
- Ir-Trans Binding
- KNX Binding
- Koubachi Binding
- MAX!Cube-Binding
- MiLight Binding
- Modbus TCP Binding
- MPD Binding
- MQTT Binding
- MQTTitude binding
- Neohub Binding (Preview)
- Netatmo Binding
- Network Health Binding
- Nibe Heatpump Binding
- Nikobus Binding
- Novelan/Luxtronic Heatpump Binding
- NTP Binding
- One-Wire Binding
- Onkyo AV Receiver Binding
- Open Energy Monitor Binding
- OpenPaths presence detection binding
- OpenSprinkler Binding
- OSGi Configuration Admin Binding
- Philips Hue Binding
- Piface Binding
- Pioneer-AVR-Binding
- Plugwise Binding
- PLCBus Binding
- Pulseaudio Binding
- RFXCOM Binding
- Samsung TV Binding
- Serial Binding
- Snmp Binding
- Squeezebox Binding
- System Info Binding
- Somfy URTSI II Binding
- Sonos Binding
- Swegon ventilation Binding
- TCP/UDP Binding
- Tellstick Binding
- TinkerForge Binding
- VDR Binding
- Velleman-K8055-Binding
- Wake-on-LAN Binding
- Withings Binding
- XBMC Binding
- xPL Binding
- Z-Wave Binding
- Persistence
- db4o Persistence
- rrd4j Persistence
- MySQL Persistence
- MongoDB Persistence
- Sen.Se Persistence
- Cosm Persistence
- Logging Persistence
- Exec Persistence
- MQTT Persistence
- Automation
- Scripts
- Rules
- Actions
- Misc
- REST-API
- Security
- Google Calendar Support
- Twitter Action
- Service Discovery
- Dropbox Bundle
Samples
- Item definitions
- Sitemap definitions
- Binding configurations
- Rules
- REST Examples
- Tips & Tricks
- FAQ
- XSLT Transforms
- Scripts
- Integration with other applications
- Syntax highlighting for external editors
- Update-Scripts
- Samples-Comfo-Air-Binding
- Samples WAC Binding
Release Notes