-
Notifications
You must be signed in to change notification settings - Fork 0
RTSI Binding
The Somfy URTSI II binding bundle is available as a separate (optional) download. If you want to communicate with a Somfy URTSI II device, please place this bundle in the folder ${openhab_home}/addons and add binding information to your configuration. See the following sections on how to do this.
First of all you need to introduce your Somfy URTSI II devices in the openhab.cfg file (in the folder '${openhab_home}/configurations').
######################## Somfy URTSI II Binding ############################################
# Host and port of the first device to control
# urtsi:<deviceId1>.port=
# Host and port of the second device to control
# urtsi:<deviceId2>.port=
The urtsi:<deviceId>.port
value is the identification of the serial port on the host system, e.g. "COM1" on Windows, "/dev/ttyS0" on Linux or "/dev/tty.PL2303-0000103D" on Mac.
In order to bind an item to an URTSI II 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 format of the binding configuration is simple and looks like this: urtsi="<deviceId>:<channelId>"
The deviceId corresponds device which is introduced in openhab.cfg.
The channelId is the configured RTS channel you want the item to bind to. Each URTSI device supports up to 16 channels (1 - 16).
Only rollershutter items are allowed to use this binding. The binding is able to handle UP, DOWN and MOVE commands.
As a result, your lines in the items file might look like the following: Rollershutter RollershutterKitchen "Kitchen" { urtsi="device1:1" }
Rollershutter RollershutterLivingRoom "Living room" { urtsi="device1:2" }
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