-
Notifications
You must be signed in to change notification settings - Fork 4
One Wire Binding
Documentation of the OneWire binding Bundle
The OneWire bus system is a lightweight and cheap bus system mostly used for sensors like, temperature, humidity and presence but there are also switches available. The binding is designed to work as client of the ow-server which implements the owserver-protocol. The OneWire devices could be connected to the machine running ow-server by a USB-Adapter. For detailed information on OneWire please refer to http://en.wikipedia.org/wiki/One_wire or http://owfs.org.
For installation of the binding, please see Wiki page Bindings.
If your 1-Wire Bus System is physically connected to your server and working properely please follow the steps:
- Install and configure the ow-server and ow-shell packages on your 1-wire server
- Copy the binding (e.g. openhab.binding.onewire-1.1.0.jar in the openhab/addons folder
- Edit the relevant section in the openhab configuration file (openhab/configurations/openhab.cfg). If you are running the 1-wire server on the same machine please insert the local ip adress of the server (127.0.0.1) and not localhost in the line onewire:ip. In this case on every onewire update you will have an file system access to the /etc/hosts file.
In order to bind an item to a OneWire 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 for the OneWire binding configuration string is explained here:
onewire="<sensorId>#<unitId>"
Here are some examples of valid binding configuration strings:
onewire="26.AF9C32000000#temperature"
onewire="26.AF9C32000000#humidity"
The sensorId can be either the hex address and an alias if one is configured ( http://owfs.org/index.php?page=aliases )
onewire="bedroom#temperature"
As a result, your lines in the items file might look like the following:
Number Temperature_FF_Office "Temperature [%.1f °C]" <temperature> (FF_Office) { onewire="26.AF9C32000000#temperature" }
The OneWire binding currently accepts only items of type Number which is good enough for temperature and humidity sensors. But for other sensors (e.g. Door contact) it would be good to support Contact items as well. Though you can use Number items with door contacts as well but you have to convert the resulting '0' to CLOSED and the '1' to OPEN with the help of rules.
- make one wire writeable for switch support (e.g. DS2408 1-Wire 8-Channel Addressable Switch)
- non number support
- presence information for iButton support
- 1-wire communication e.g. via GPIO to support devices connected to a Raspberry PI.
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