RFXCOM2MQTT

RFXCOM to MQTT bridge for RFXtrx433 devices

All received RFXCOM events are published to the MQTT rfxcom2mqtt/devices/\<id> topic. It is up to the MQTT receiver to filter these messages or to have a register/learning/pairing mechanism.

Usage

Configuration

See example config.yml

List of available commands: DeviceCommands

Subscribe to topic rfxcom2mqtt/devices to receive incoming messages.

Example JSON message on topic "rfxcom2mqtt/devices/0x5C02":

{
  "title": "Bathroom Temp & Hum",
  "type":"temperaturehumidity1",
  "subtype": 13,
  "id": "0x5C03",
  "seqnbr": 12,
  "temperature": 18,
  "humidity": 74,
  "humidityStatus": 3,
  "batteryLevel": 9,
  "rssi": 6
}

Publish command examples (topic/payload)

rfxcom2mqtt/commmand/CucuDimmer
on

rfxcom2mqtt/commmand/CucuDimmer
off

rfxcom2mqtt/commmand/CucuDimmer
level 15

rfxcom2mqtt/commmand/Switch1 (lighting4, payload identifies device)
on

rfxcom2mqtt/commmand/Switch1
off

rfxcom2mqtt/commmand/Lights/Light1  (lighting2, unitName identifies device)
on

rfxcom2mqtt/commmand/Lights/Light1
off

Healthcheck

If healthcheck is enabled in the config, the rfxcom status will checked every minute. In case of an error the node process will exit. If installed in docker the container will try to restart try to reconnect to the RFXCOM device.

Dependencies:

The RFXCOM Node library for the communication with the RFXCOM RFXtrx433 433.92MHz Transceiver.

The MQTT.js library for sending and receiving MQTT messages.