-
Notifications
You must be signed in to change notification settings - Fork 0
MQTT Persistence
This service allows you to feed item states to an MQTT broker using the openHAB persistence strategies. The destination broker, topic and messages are configurable.
Note: The service only supports sending information, not retrieving information.
For installation of this persistence package please follow the same steps as you would Bindings.
Additionally, create a persistence file 'mqtt.persist
' in the ${openhab.home}/configuration/persistence
folder.
The file should follow the regular openHAB persistence format.
This persistence service can be configured in the "MQTT Persistence Service" section in openhab.cfg
.
The MQTT persistence can be configured with the following properties:
**Property** | **Description** |
mqtt-persistence:broker | The name of the broker as defined in the mqtt:``.url. See the [MQTTBinding] for more information on how to configure MQTT broker connections. |
mqtt-persistence:topic | The MQTT topic to which the persistence messages should be sent. This string may include parameters, see table below. |
mqtt-persistence:message | A string representing the persistence message content. This string may include parameters, see table below. |
Both the topic and message values are reformatted using String.format at the time of publishing. During this reformat, the following parameters are provided to the format function:
**Parameter** | **Description** |
1$ | Item name. |
2$ | Item alias as defined in the `mqtt.persist` file. |
3$ | Item state. A string representation of the item state. ON/OFF, OPEN/CLOSED and UP/DOWN states are transformed to 1/0 values respectively. |
4$ | Current DateTime in long format. |
All item and timing related configuration is done in the mqtt.persist file using the standard Persistence.
The following is an example configuration that can be used to persist item states with Xively using the csv format. The messages sent to Xively will have the format <openhab_item>, For example: light_office, 1
First, we need to define the MQTT broker connection in the openhab.cfg
file:
mqtt:xively.url=tcp://api.xively.com:1883
mqtt:xively.user=
As , use the device/API key you get from Xively.
Next, we need to configure the MQTT persistence service. To do this add the following entries to openhab.cfg
:
mqtt-persistence:broker=xively
mqtt-persistence:topic=/v2/feeds/<feed id>.csv
mqtt-persistence:message=%1$s, %3$s
where is your Xively feed id.
And finally, add a persistence strategy in the mqtt.persist
file:
Strategies {
everyHour : "0 0 * * * ?"
default = everyChange
}
Items {
// persist all items every hour and on every change
* : strategy = everyChange, everyHour
}
With this configuration, all items will persisted whenever their state changes and once per hour.
Installation
Community
- Support
- News Archive
- Presentations
- How to Contribute
- IDE Setup
- How to Implement a Binding
- How to Implement an Actions
- User Interfaces
- Classic UI
- iOS Client
- Android Client
- GreenT UI
- CometVisu
- Bindings
- Asterisk Binding
- Bluetooth Binding
- Comfo Air Binding
- CUPS Binding
- digitalSTROM Binding
- DMX512 Binding
- EnOcean Binding
- Epson Projector Binding
- Exec Binding
- Fritz!Box Binding
- Fritz AHA Binding
- Heatmiser Binding
- Homematic Binding
- HTTP Binding
- IHC / ELKO Binding
- Insteon Hub Binding
- KNX Binding
- Koubachi Binding
- MAX!Cube-Binding
- MiLight Binding
- Modbus TCP Binding
- MPD Binding
- MQTT Binding
- Network Health Binding
- Nibe Heatpump Binding
- Nikobus Binding
- Novelan/Luxtronic Heatpump Binding
- NTP Binding
- One-Wire Binding
- Onkyo AV Receiver 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
- TCP/UDP Binding
- TinkerForge Binding
- VDR Binding
- Wake-on-LAN Binding
- Z-Wave Binding
- Persistence
- db4o Persistence
- rrd4j Persistence
- Sql Persistence
- Sen.Se Persistence
- Cosm Persistence
- Logging Persistence
- Exec 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
Release Notes