1.0.1 • Published 4 years ago

homebridge-garagedoor-iologik v1.0.1

Weekly downloads
4
License
ISC
Repository
github
Last release
4 years ago

homebridge-garagedoor-iologik

npm npm npm

Hörmann Supramatic garage door opener plugin for Homebridge.

Hörmann and Supramatic are trademarks owned by Hörmann KG Verkaufsgesellschaft.

Moxa and ioLogik are trademarks owned by Moxa Inc.

This plugin was developed for a Hörmann Supramatic garage door opener connected via a UAP1 (Universal Adapter Print) and a Moxa ioLogik E1214 remote Ethernet I/O server.

Installation

  1. Connect and configure the UAP1 and ioLogik E1214 (see wiring and configuration guide below).
  2. Install this plugin using: npm install -g homebridge-garagedoor-iologik
  3. Edit config.json and add a Garagedoor-ioLogik accessory for each garage door to be controlled (see example below).
  4. Run Homebridge.

Wiring

The Supramatic provides 24V DC power to the ioLogik E1214 via the UAP1. The power terminal block on the top panel of the ioLogik E1214 should be connected to the main terminal block in the UAP1 as follows:

ioLogik E1214UAP1Description
V+5 (24V)Power supply for ioLogik E1214
V-20 (0V)Power supply for ioLogik E1214
GNDGround not connected to UAP1

The ioLogik E1214 main I/O channels terminal block is wired to the UAP1 as follows:

ioLogik E1214UAP1Description
COM5 (24V)Common for DI channels
DI0K01.8DI-00 input: Door open
DI1K02.8DI-01 input: Door closed
DI2-(not connected)
DI3-(not connected)
DI4-(not connected)
DI5-(not connected)
GND20 (0V)Ground for DI channels
R0_NO-(not connected)
R0_C-(not connected)
R1_NO-(not connected)
R1_C-(not connected)
R2_NO15 (S2)DO-02 relay output: Go open
R2_C20 (0V)DO-02 relay common: Go open
R3_NO23 (S3)DO-02 relay output: Go partial open
R3_C20 (0V)DO-02 relay common: Go partial open
R4_NO17 (S4)DO-02 relay output: Go close
R4_C20 (0V)DO-02 relay common: Go close
R5_NO10 (S5)DO-02 relay output: Toggle light
R5_C20 (0V)DO-02 relay common: Toggle light

The DI channels are connected to the UAP1 relays as dry contacts. The DO channels connect the UAP1 inputs to 0V when the relays are activated.

ioLogik Configuration

The ioLogik E1214 must be running firmware version 2.5 or later to support RESTful API. Ensure that the Enable Resful API option is enabled.

The DI channels should be configured as follows:

DI ChannelModeFilterAlias of ChannelAlias of OFF StatusAlias of ON Status
DI-00DI100msDoor is openNot openOpen
DI-01DI100msDoor is closedNot closedClosed
DI-02DI100msDIOFFON
DI-03DI100msDIOFFON
DI-04DI100msDIOFFON
DI-05DI100msDIOFFON

The DO channels should be configured as follows:

DO ChannelModeOFF WidthON WidthPulse CountAlias of ChannelAlias of OFF StatusAlias of ON Status
DO-00DODOOFFON
DO-01DODOOFFON
DO-02Pulse Output1 (1.5s)1 (1.5s)1OpenIdleGo open
DO-03Pulse Output1 (1.5s)1 (1.5s)1Partial openIdleGo partial open
DO-04Pulse Output1 (1.5s)1 (1.5s)1CloseIdleGo close
DO-05Pulse Output1 (1.5s)1 (1.5s)1LightIdleToggle light

Example config.json

{
    "accessories":
    [{
        "accessory":    "Garagedoor-ioLogik",
        "name":         "Bunker Door",
        "host":         "iologik-e1214"
    }]
}

Multiple accessories can be added to control different garage doors. They must be each given a unique name.

The host specifies how to reach the ioLogik E1214.

Notes

The following (non-default) timings are hardcoded in the plugin:

MENU 2Switch-off delayDescription
55 minutesIllumination during and after door movement
915 minutesSwitched via radio/external button

License

ISC License (ISC)Copyright © 2019 Alexander Thoukydides

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.