RFGate binding for openHAB
Go to file
Mike Jagdis 69de5ea151 [rfgate] Remove unused HUM channel type
We're using system.atmospheric-humidity rather than HUM.
(If we did use HUM it should use "%" in the format rather than "%unit%")

Signed-off-by: Mike Jagdis <mjagdis@eris-associates.co.uk>
2023-11-28 09:30:43 +00:00
doc [rfgate] Update TODO 2022-12-09 09:57:16 +00:00
src/main [rfgate] Remove unused HUM channel type 2023-11-28 09:30:43 +00:00
NOTICE [rfgate] Initial version 2022-11-11 12:15:57 +00:00
pom.xml [rfgate] Update to compile against openHAB 3.4 2022-11-29 23:14:52 +00:00
README.md [rfgate] Add "usebridgeids" binding option 2023-11-02 10:20:04 +00:00

RFGate Binding

This binding integrates large number of sensors and actuators from several different manufactures through [RFGate gateways] and RFLink gateways.

RFGate/RFLink gateways may be configured to support RF protocols at 315MHz, 433MHz, 868MHz and 2.4GHz like:

  • HomeEasy
  • Cresta
  • X10
  • La Crosse
  • OWL
  • CoCo (KlikAanKlikUit),
  • PT2262
  • Oregon
  • etc.

See the Supported Devices Lists from [RFGate] and RFLink for the complete list of supported sensors and devices as well as firmware update announcements.

Configuration

usebridgeids

Default: false

OpenHAB really wants devices to be owned by specific bridges and have the bridge ID as part of the device UID however that isn't how 433 MHz RF devices work (at least for RX).

If usebridgeids is false (the default) then discovered devices will not have a bridge ID in their device UID however when you accept a discovered device it will remain in the "ERROR: HANDLER" state until you edit the Thing and set a bridge in its properties. Only once a bridge has been set will the Thing come online and start receiving updates.

If usebridgeids is true discovered devices will have a bridge ID in both their device UID and properties. They will come online immediately after they are accepted however there may be multiple entries in the inbox, one for each bridge that see the signal. The binding knows they are all the same so only one should be accepted and the others removed. If more than one is accepted only Thing will receive updates (probably the last one accepted).

Notes

Need to manually install the serial driver:


openhab> feature:install openhab-transport-serial