-
Notifications
You must be signed in to change notification settings - Fork 4
Open Energy Monitor Binding
Documentation of the Open Energy Monitor binding Bundle
Open Energy Monitor binding is used to get live data from open energy monitor devices.
rfm12pigw is application read telegram from RFM12Pi module and relay untouched telegrams to openhab via UDP packet. Open Energy Monitor binding listening UDP port and parse data from UDP telegrams.
C code is available on here
build command:
gcc -std=gnu99 -o rfm12pigw rfm12pigw.c
execution:
rfm12pigw -v -d /dev/ttyUSB0 -a 192.168.1.10
Swegongw help is avail be by command execution:
rfm12pigw -h
For installation of the binding, please see Wiki page Bindings.
openhab.cfg file (in the folder '${openhab_home}/configurations').
########################### Open Energy Monitor Binding ###############################
#
# UDP port of the Open Energy Monitor devices (optional, defaults to 9997)
#openenergymonitor:udpPort=9997
#
#openenergymonitor:<parser rule name>=<node address>:<data type(byte indexes)>
#openenergymonitor:<parser rule name>=<node address>:<data type(byte indexes)>
The openenergymonitor:udpPort
value specify UDP port which binding will listening. Configuration is optional, by default binding listening UDP port 9997.
In order to bind an item to the device, you need to provide 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:
openenergymonitor =""
Where
…
openenergymonitor:phase1RealPower=10:U16(2|1)
openenergymonitor:phase1ApparentPower=10:U16(4|3)
openenergymonitor:phase1Current=10:U16(6|5)
openenergymonitor:phase1PowerFactor=10:U16(8|7)
openenergymonitor:phase2RealPower=10:U16(10|9)
openenergymonitor:phase2ApparentPower=10:U16(12|11)
openenergymonitor:phase2Current=10:U16(14|13)
openenergymonitor:phase2PowerFactor=10:U16(16|15)
openenergymonitor:phase3RealPower=10:U16(18|17)
openenergymonitor:phase3ApparentPower=10:U16(20|19)
openenergymonitor:phase3Current=10:U16(22|21)
openenergymonitor:phase3PowerFactor=10:U16(24|23)
openenergymonitor:realPower=10:U16(26|25)
openenergymonitor:apparentPower=10:U16(28|27)
openenergymonitor:voltage=10:U16(30|29)
openenergymonitor:pulseCount=10:U32(34|33|32|31)
openenergymonitor:pulsePower=10:U16(36|35)
Number RealPower { openenergymonitor="realPower" }
Number ApparentPower { openenergymonitor="apparentPower" }
Number Voltage { openenergymonitor="voltage" }
Number Phase1RealPower { openenergymonitor="phase1RealPower" }
Number Phase1ApparentPower { openenergymonitor="phase1ApparentPower" }
Number Phase1Current { openenergymonitor="phase1Current:JS(divideby100.js)" }
Number Phase1PowerFactor { openenergymonitor="phase1PowerFactor" }
Number Phase2RealPower { openenergymonitor="phase2RealPower" }
Number Phase2ApparentPower { openenergymonitor="phase2ApparentPower" }
Number Phase2Current { openenergymonitor="phase2Current:JS(divideby100.js)" }
Number Phase2PowerFactor { openenergymonitor="phase2PowerFactor" }
Number Phase3RealPower { openenergymonitor="phase3RealPower" }
Number Phase3ApparentPower { openenergymonitor="phase3ApparentPower" }
Number Phase3Current { openenergymonitor="phase3Current / 100" }
Number Phase3PowerFactor { openenergymonitor="phase3PowerFactor" }
Number PulseEnergy { openenergymonitor="cumulative(pulseCount):JS(divideby5000.js)" }
Number PulsePower { openenergymonitor="pulsePower" }
Number Phase123RealPower { openenergymonitor="phase1RealPower+phase2RealPower+phase3RealPower" }
Number Phase123Current { openenergymonitor="phase1Current+phase2Current+phase3Current:JS(divideby100.js)" }
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