-
Notifications
You must be signed in to change notification settings - Fork 0
my.openHAB Persistence
my.openHAB Persistence
- What is my.openHAB?
- Installation and registration
- Selective persistence
- Selectively adding specific items to my.openHAB
- IFTTT and other cloud based services
- REST through my.openHAB
my.openHAB.org is a cloud service provided to you by openHAB and is well worth having a look at. After installing and registering, you can send Items and Events to the cloud where you can view them on the site. Whilst that is not the most exciting thing in the world, it does then allow you to have access to your openHAB installation outside of your network via the iOS and Android apps without having to open up your home network.
It also allows you to connect to IFTTT and all the hundreds of channels they offer. Including IFTTT's own very handy Maker Channel. Which essentially gives you a REST API through IFTTT into OpenHAB. Again without having to set up the network and port forwarding yourself.
First signup at my.openhab.org and follow the docs to install the binding, register and configure your setup.
Create a file called myopenhab.persist
in your persistence folder, and define the policy to store your data.
The policy on the my.openHAB site
The example on the my.openHAB site (for all items):
Strategies {
default = everyChange
}
Items {
* : strategy = everyChange
}
Be aware that above example will persist ALL your items, and every change to my.openHAB cloud.
Currently (21 Sept 2015) there is no method to remove data or items from the my.openHAB cloud.
Though there are plans to add the option https://community.openhab.org/t/cleaning-up-demo-items-from-myopenhab/1689
This means if you change the name of an item, the old "item" will still appear on my.openHAB cloud and also appear in your IFTTT dropdown. Also, if you set up my.openHAB with the demo configuration still setup, all of those items will also appear.
Any items such as a PIR or any type of sensor that sends constant updates to OpenHAB and will quickly clutter it up. So you probably don't need or want, the thousands of updates that will be logged to my.openHAB if you catchall.
People starting out should be aware of this due to the immense experimenting and testing that comes with learning OpenHAB. You will quickly find that the item list will contain a whole load of items that you no longer need.
Create a group to identify your items
Group gMyOpenHAB
Then add items you know you need to log to that group. This will greatly help keep things under control.
e.g. Here only the on/off state of the switch is logged. There was no need to log every brightness state
Switch Light_GF_Lounge_All "Lounge All" (GF_Lounge, gMyOpenHAB) {milight="bridge01;6"}
Dimmer Light_GF_Lounge_All_B "Lounge All Brightness" (GF_Lounge) {milight="bridge01;6;brightness;27"}
Finally, configure your my.openHAB persistence file myopenhab.persist
to only persist items in the group
Strategies {
default = everyChange
}
Items {
gMyOpenHAB* : strategy = everyChange
}
Be aware that Sending persistence data to my.openHAB is required if you use any data-driven cloud functions, IFTTT integration for example.
Meaning, if you want to control the brightness (or any item) using the OpenHAB IFTTT Channel, be sure that the item is in the gMyOpenHAB group, or it won't appear in the dropdown on IFTTT.
It is also required by the apps when used outside your local network.
You can also use REST through my.openHAB.org.
e.g.
To get the state of all items (remember my.openHAB will only display items that you have persisted to it)
https://my.openhab.org/rest/items
You can specify:
https://my.openhab.org/rest/items/Light_FF_Office_Desk
You can also send commands:
https://my.openhab.org/CMD?Light_FF_Office_Desk=TOGGLE
https://my.openhab.org/CMD?Light_FF_Office_Ceiling=ON
###Linux / OS X
###Windows
- Cosm Persistence
- db4o Persistence
- Exec Persistence
- InfluxDB Persistence
- JDBC Persistence
- JPA Persistence
- Logging Persistence
- mapdb Persistence
- MongoDB Persistence
- MQTT Persistence
- my.openHAB Persistence
- MySQL Persistence
- rrd4j Persistence
- Sen.Se Persistence
- SiteWhere Persistence
- AlarmDecoder Binding
- Anel Binding
- Arduino SmartHome Souliss Binding
- Asterisk Binding
- Astro Binding
- Autelis Pool Control Binding
- BenQ Projector Binding
- Bluetooth Binding
- Bticino Binding
- CalDAV Binding
- Comfo Air Binding
- Config Admin Binding
- CUL Binding
- CUL Intertechno Binding
- CUPS Binding
- DAIKIN Binding
- Davis Binding
- Denon Binding
- digitalSTROM Binding
- DMX512 Binding
- DSC Alarm Binding
- DSMR Binding
- eBUS Binding
- Ecobee Binding
- EDS OWSever Binding
- eKey Binding
- Energenie Binding
- EnOcean Binding
- Enphase Energy Binding
- Epson Projector Binding
- Exec Binding
- Freebox Binding
- Freeswitch Binding
- Frontier Silicon Radio Binding
- Fritz AHA Binding
- Fritz!Box Binding
- FS20 Binding
- Global Cache IR Binding
- GPIO Binding
- HAI/Leviton OmniLink Binding
- HDAnywhere Binding
- Heatmiser Binding
- Homematic / Homegear Binding
- HTTP Binding
- IEC 62056-21 Binding
- IHC / ELKO Binding
- ImperiHome Binding
- Insteon Hub Binding
- Insteon PLM Binding
- IPX800 Binding
- IRtrans Binding
- jointSPACE-Binding
- KNX Binding
- Koubachi Binding
- LCN Binding
- LightwaveRF Binding
- Leviton/HAI Omnilink Binding
- Lg TV Binding
- Logitech Harmony Hub
- MailControl Binding
- MAX!Cube-Binding
- MAX! CUL Binding
- MiLight Binding
- MiOS Binding
- Modbus TCP Binding
- MPD Binding
- MQTT Binding
- MQTTitude binding
- Neohub Binding
- Nest Binding
- Netatmo Binding
- Network Health Binding
- Network UPS Tools 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
- Panasonic TV Bindung
- panStamp Binding
- Philips Hue Binding
- Piface Binding
- pilight Binding
- Pioneer-AVR-Binding
- Plex Binding
- Plugwise Binding
- PLCBus Binding
- Primare Binding
- Pulseaudio Binding
- RFXCOM Binding
- RWE Smarthome Binding
- Sager WeatherCaster Binding
- Samsung AC Binding
- Samsung TV Binding
- Serial Binding
- Sallegra Binding
- Satel Alarm Binding
- Sinthesi Sapp Binding
- Snmp Binding
- Somfy URTSI II Binding
- Sonos Binding
- Squeezebox Binding
- Swegon ventilation Binding
- System Info Binding
- TA CMI Binding
- TCP/UDP Binding
- Tellstick Binding
- TinkerForge Binding
- Tivo Binding
- VDR Binding
- Velleman-K8055-Binding
- Wago Binding
- Wake-on-LAN Binding
- Waterkotte EcoTouch Heatpump Binding
- Weather Binding
- Wemo Binding
- Withings Binding
- XBMC Binding
- xPL Binding
- Yamahareceiver Binding
- Zibase Binding
- Z-Wave Binding
- Asterisk
- Google Calendar
- Linux Media Players
- ROS Robot Operating System
- Telldus Tellstick
- Zoneminder
- Wink Hub (rooted)
- Wink Monitoring
- Transformations
- XSLT
- JSON
- REST-API
- Security
- Service Discovery
- Voice Control
- BritishGasHive-Using-Ruby
- Dropbox Bundle
A good source of inspiration and tips from users gathered over the years. Be aware that things may have changed since they were written and some examples might not work correctly.
Please update the wiki if you do come across any out of date information.
- Comfo Air Binding
- Ecobee Examples
- Nest Examples
- Rollershutter Bindings
- Squeezebox
- WAC Binding
- WebSolarLog
- Alarm Clock
- Convert Farenheit to Celcius
- The mother of all lighting rules
- Reusable Rules via Functions
- Combining different Items
- Items, Rules and more Examples of a SmartHome
- Google Map
- Controlling openHAB with Android
- Usecase examples
- B-Control Manager
- Spell checking for foreign languages
- Flic via Tasker
- Chromecast via castnow