Using RFXCOM-Command with multiple values, but binding expects switch

  • Platform information:
    • Hardware: i3-4010U/8GB Ram/500GB SSD
    • OS: Ubuntu Ubuntu 18.04.2 LTS
    • Java Runtime Environment: Java™ SE Runtime Environment (build 1.8.0_201-b09)
    • openHAB version: 2.4.1
  • Issue of the topic: The RFXCOM-Binding is used to control my fire place. The binding offers an Switch-Item which works (turn on/off), but does not recognize other commands (up/down, second flame).

I am using a RFXCOM to control my Somfy-blinds and working on integrating my fire place. Connection between the transceiver and the fire place works. I can turn it on and off using a switch item like described in the manual [1].

Thing-file:

Bridge rfxcom:bridge:usb [ serialPort="/dev/rfxcom", transmitPower="0", transceiverType="433.92MHz", enableMertik=true ] {
    Thing thermostat3 kamin [ deviceId="xxxxxx", subType="MERTIK__G6R_H4TB__G6R_H4T__G6R_H4T21_Z22" ]
}

Items-file:

Switch  Kamin   "Steuerung Kamin"   {channel="rfxcom:thermostat3:usb:kamin"}

Nevertheless, the binding seems to offer more control-options like the number of flames (SECOND_ON/SECOND_OFF) and the flame-height (UP/DOWN). I copied part of the source below.

binding-source on github [1, line 59ff.]:

    public enum Commands implements ByteEnumWrapper {
        OFF(0),
        ON(1),
        UP(2),
        DOWN(3),
        RUN_UP(4, MERTIK__G6R_H4T1),
        SECOND_OFF(4, MERTIK__G6R_H4TB__G6R_H4T__G6R_H4T21_Z22),
        RUN_DOWN(5, MERTIK__G6R_H4T1),
        SECOND_ON(5, MERTIK__G6R_H4TB__G6R_H4T__G6R_H4T21_Z22),
        STOP(6, MERTIK__G6R_H4T1);

I’m stuck now als switch-items only support ON/OFF. Using a string-item does not solve the problem either.
Any hints?

Kind regards!

[1] https://www.openhab.org/addons/bindings/rfxcom/#thermostat3---rfxcom-thermostat3-sensor
[2] https://github.com/openhab/openhab2-addons/blob/master/bundles/org.openhab.binding.rfxcom/src/main/java/org/openhab/binding/rfxcom/internal/messages/RFXComThermostat3Message.java

I found an issue on github dealing with the same issue: https://github.com/openhab/openhab2-addons/issues/4633
Seems like the binding need to be updated first…

A pull-request for the binding has just been opened, please test it and report back: