I have first tried in 1.8.1, which was my current version, but with rfxcom 1.8.2 addon - it had the same issue and then updated to OH 1.8.2. with the same result.
I have updated rfxcom firmware to latest firmware as well. I have tried various items as examples in the Wiki with the same result.
I have not rules defined yet.
Not sure if it makes a difference but I have the rfxtrx433E version.
I have the same device, though I have not updated to 1.8.2 yet.
I can tell you that when I send out signals form openHAB to the RFX unit, my log also gives me the “unknown” message. But like yours, it also gives the 2016-04-08 20:50:44.220 [DEBUG] [.rfxcom.internal.RFXComBinding] - Command successfully transmitted, 'ACK' received
I don’t know for sure, but I think the ACK response is an acknowledgment from the device, confirming that the transmission was received.
Ignoring openHAB for a second, when using RFXManager, are you able to turn the LIGHTING2 device on and off?
It looks like you are receiving the commands in openHAB but openHAB doesn’t know what to do with them.
Your item Switch ChristmasTreeLights { rfxcom=">636602.1:LIGHTING2.AC:Command" } is correct
The > in your item means that your are sending a signal OUT from openHAB to the RFXcom.
Which means the on and off command must come from a switch/rule in openHAB.
Try plopping the following in a browser 192.168.1.22:8080/CMD?ChristmasTreeLights=ON replacing the IP with yours obviously. You can replace ON with OFF, you can also use TOGGLE and every time you hit refresh it should toggle.
See how you get on with that, try just the switch at the moment, becasue although I don’t have one, I know that rollershutters are more complicated to setup.
Thanks for your feedback - it made me tackle the problem differently now knowing the log file states Subtype as UNKNOWN in a working setup as well.
I have the items defined in my sitemap as a switches.
The Switch ChristmasTreeLights { rfxcom=">636602.1:LIGHTING2.AC:Command" } was just used as an example of one of the items configured/defined in the Wiki to check if the Subtype is mentioned correctly…
I only have the Shutter now and since it was not working as described, my thought was that the output to the RFXCOM for not specifying the Sequence and Subtype correctly as it is shown as UNKNOWN.
I have taken the dirty way out, instead of transferring/calculating the values from the RFX Manager to an OH item, I have just defined the parameters in the OH and paired my receiver with the values send via OH.
I think the converting the data defined in the RFXCOM manager to the OH Items data/format might be wrong. I did what was explained in the Wiki and tried various configuration options.
Was there a specific reason for using the RFX Manager to send signals to openHAB? I think your “dirty way” is actually more like the right way
I send everything to openHAB, and let openHAB send the signals to the devices. e.g. I have some Lightwave Dimmers that “out of the box” should be controlled directly via the supplied remote. I have openHAB detect the remote transmission, do whatever logic it needs and then sends out a signal to the Dimmers. I paired the Dimmers to the signal from openHAB and they behave as if they were controlled directly with the remote. Plus it means I can use the relatively cheap remote for anything in openHAB.
The same is true for wall switches in rooms, PIRs and thermometers. All sending out RF signals, with openHAB processing them.
I was only using the RFX Manager to send signals to the RF/Shutter Control. I did this first when I got the RFX to make sure it was working I bound/linked a configured RFX Blinds1 in RFX Manager to a Shutter and that was working. My next step was to transfer the already bound configuration from RFX Manager to an OH Item and that is were I got stuck. In future - I will follow the direct way and not use RFX Manager.