BlindsT0 (OZRoll) not working with Node-red-contrib.rfxcom

[rkuster]

Hello,

I'm trying to integrate OZRoll Blinds with Node Red using node-red-contrib-rfxcom. Unfortunately when sending a command (open / stop / close) I always get following error back:

"RFXCOM: Command unknown or not supported by this device (4)"

It looks like that the device was recognised (BLINDS_T0).

With the rfxmgr.exe I can control the blinds without any issues.

Is there any way to find out out what the exact command is that needs to be configured in node red for the rfxtrx433xl?

I tried many combination without any success and couldn't find any documentation how to configure the correct payload in Node red.

Topic config (String): BLINDS_T0/0x0101/1
Payload config: Open (Close / Stop)

Thanks for any help.

[maxwellhadley]

Please can you provide some additional information to help sort this out:

• The RFX firmware version number (from the status message shown below the rfx-blinds-out node)
• The version number of the node-red-contrib-rfx node. New version 2.12.1 was released three weeks ago, and this did make changes to the blinds-handling code, though BLINDS_T0 should not have been affected.
• The exact byte sequence sent by Node-RED, and the response from the RFX. You can get this by enabling debug on the node configuration. all communication with the RFX is then copied to the NodeJS console:
  
  
• The byte sequence sent by RFXmgr, and the response, if this is available.

The error response you got means what it says, the RFX did not understand the command sent, or it did understand it but wasn't able to implement it because either its firmware or its hardware is the wrong version. The topic and payload you describe look OK to me though.

[rkuster]

Hi Max,

Thanks for the fast reply. I also attached the log from the rfxmgr (working) as reference. From what I see the 3rd Byte in the command is different (00 vs 14).

Node Red/JS Sent: 09,19,00,03,00,02,02,01,00,00
26.02.2023 01:18:25:195= Blinds command: 09 19 14 13 00 02 02 01 00 00

Following the requested information:

RFX Firmware Version: v1047 Unknown firmware

node-red-contrib-rfxcom version: 2.11.3

Console Log:

Feb 26 13:22:14 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:14.845 [rfxcom] on /dev/ttyUSB0 - Queued : 09,19,00,03,00,02,02,01,00,00

Feb 26 13:22:14 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:14.847 [rfxcom] on /dev/ttyUSB0 - Sent : 09,19,00,03,00,02,02,01,00,00

Feb 26 13:22:14 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:14.863 [rfxcom] on /dev/ttyUSB0 - Received: 14,01,FF,03,00,53,2F,00,40,00,00,03,00,1C,13,5A,46,58,43,4F,4D

Feb 26 13:22:14 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:14.864 [rfxcom] on /dev/ttyUSB0 - Response: Command message 03, command unknown or not supported by this device

Feb 26 13:22:14 homematic-ccu2 daemon.warn node-red[32508]: [rfx-blinds-in:ff471561.73cac] RFXCOM: Command unknown or not supported by this device (4)

Feb 26 13:22:16 homematic-ccu2 daemon.info node-red[32508]: [redmatic-homekit-bridge:RedMatic Bridge] bridge already published (36 Accessories) RedMatic Bridge CC:22:3D:A8:CC:1B on port 51826

Feb 26 13:22:17 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:17.265 [rfxcom] on /dev/ttyUSB0 - Queued : 09,19,00,04,00,02,02,01,02,00

Feb 26 13:22:17 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:17.267 [rfxcom] on /dev/ttyUSB0 - Sent : 09,19,00,04,00,02,02,01,02,00

Feb 26 13:22:17 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:17.280 [rfxcom] on /dev/ttyUSB0 - Received: 14,01,FF,04,00,53,2F,00,40,00,00,03,00,1C,13,5A,46,58,43,4F,4D

Feb 26 13:22:17 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:17.280 [rfxcom] on /dev/ttyUSB0 - Response: Command message 04, command unknown or not supported by this device

Feb 26 13:22:17 homematic-ccu2 daemon.warn node-red[32508]: [rfx-blinds-in:ff471561.73cac] RFXCOM: Command unknown or not supported by this device (4)

Feb 26 13:22:18 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:18.796 [rfxcom] on /dev/ttyUSB0 - Queued : 09,19,00,05,00,02,02,01,01,00

Feb 26 13:22:18 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:18.798 [rfxcom] on /dev/ttyUSB0 - Sent : 09,19,00,05,00,02,02,01,01,00

Feb 26 13:22:18 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:18.816 [rfxcom] on /dev/ttyUSB0 - Received: 14,01,FF,05,00,53,2F,00,40,00,00,03,00,1C,13,5A,46,58,43,4F,4D

Feb 26 13:22:18 homematic-ccu2 daemon.err node-red: 2023-02-26 13:22:18.817 [rfxcom] on /dev/ttyUSB0 - Response: Command message 05, command unknown or not supported by this device

Feb 26 13:22:18 homematic-ccu2 daemon.warn node-red[32508]: [rfx-blinds-in:ff471561.73cac] RFXCOM: Command unknown or not supported by this device (4)

RFXMgr Log:

[rkuster]

As an additional information.

The selected Type of the Blind in RFXmngr is "T20 Ozroll E-Trans". Can it be that this is not yet implemented/supported by the node-red-contrib-rfxcom?

Thanks for your help/support.

Rolf

[maxwellhadley]

Aha! If you are trying to use BLINDS_T20 subtype, you need to upgrade node-red-contrib-rfxcom to the latest version 2.12.1, as I didn't add that subtype until version 2.12.0 (which has a bug, fixed in the latest)

I'm not sure about the 'unknown firmware' but I think it is an issue with the way the XL reports its status. I don't have one here to test with, I will contact RFXCOM about it. It shouldn't matter though, it's just a status report.

[maxwellhadley]

It gets more complicated. I was testing on the same version as you, 2.11.3, and on that version when I tried to use BLINDS_T20 I got a message 'rfx-blinds-out : device type 'BLINDS_T20' is not supported'. I then upgraded to 2.12.1 and tried again. Now I get the same error message as you. There is a note in the SDK that BLINDS_T20 have some sort of remote pairing procedure, but there are no details.

Currently I'm not on my development machine: I'll take a closer look when I get a chance: likely to be a few days though!

[rkuster]

Hi Max,

Thank you for your reply/help. I was working with Bart (rfxcom) on the implementation of OZRoll (T20) in rfxtrx433xl 2 years ago. The OZRoll (BLINDS_T20) needs to be paired with the Confirm command by pressing the Stop Button on the Controller for 3 seconds. This can be done with the rfxmngr. ID and Units need to be defined before sending the Confirm Command.

Currently I'm trying to get OZRoll working on a Raspberry Pi/Rasperry Matic with Redmatic addon installed. Unfortunately Redmatic still has your old version of node-red-contrib-rfxcom and no upgrade / update available. NPM update doesn't work so I opened an issue on Redmatic to prepare an update package.

I will set up another node red instance where I can test your latest version and let you know the result.

[maxwellhadley]

Rolf,

OK back on the Big Machine. I can confirm my RFXtrx433E does not support BLINDS_T20, so that explains why I get the error message! Only ProXL2 firmware supports it. It may be that you need to pair the RFX with the given address before the RFX starts accepting commands. Send a message to the motor with a payload of confirm or pair or program and see if that gets you going.

[rkuster]

Hi Max,

I configured on my QNAP another Node red instance with your current version of node-red-contrib-rfxcom. The BLINDS_T20 is working fine now. Thanks for your help.

Redmatic does not seem to be maintained further (I don't expect any update there) - therefore I'm looking now what's the best alternative to my current setup in order to reduce dependencies.

Again thanks for your help.

[maxwellhadley]

OK that's good to hear . Did you have to 'pair' with the blinds motor at all, even using RFXmgr?

The SDK documentation I have doesn't include a firmware code value for ProXL2, but it does have code 0x11 reserved for internal use, so I assume that value is now out in the wild. When I get the new SDK update, I will be able to fix the 'Unknown firmware' issue as well as some other changes and new device types I am waiting for information about!

[rkuster]

Dear Max,

Sorry for the late reply - was on annual leave in the meantime. I have now a working setup on a Rasperry Pi 4 with Homematic (piVCCU), latest node-RED and latest node-red-contrib-rfx installed on it. This way (Homematic running in a container) gives more flexibility and independency using Node-RED together with Homematic. I connected the rfxtrx433xl to the Rasppery Pi and it was recognized/working immediately. With this setup I could bypass the CCU Addon Redmatic which seems to be dead/not maintained anymore. So far I'm happy - also thank you for your support.

Regarding your question on the OzRoll Blinds - I had to pair the blind motor with the rfxtrx433xl. I did it with the RFXmgr but it should be possible also with Node-RED. The command to send is "Confirm", that is required for pairing the rfx433xl with the motor (pressing a button on the motor and send the "Confirm" command pair it).

Please let me know if you have more questions.

I wish you a good day.

Best regards

Rolf

[maxwellhadley]

Rolf - thanks for the update. I'm still waiting to hear from RFXCOM with the SDK update, which will hopefully document all the new stuff (especially the bits I'm unclear on!)