search

maxwellhadley / node-red-contrib-rfxcom

node-RED nodes to access an RFXtrx433 transceiver
BSD 2-Clause "Simplified" License
22 stars 13 forks source link

Connecting in Node Red, but no response #139

Open RicharddeCrep opened 3 months ago

RicharddeCrep commented 3 months ago

Hi Maxwell,

I'm having trouble getting **node-red-contrib-rfxcom 2.13.0 to work with the rfx-blinds-in and rfx-blinds-out nodes in Node Red (versions 3.0.2 or 3.1.7) on a Pi4.

  1. Bert Weijenberg at RTX now only sells the "RFX433SL-USB" that replaces the "RFXtrx433E" that is now discontinued.

So I'm working with the RFX433SL-USB, that works perfectly via "RFXmngr.exe" inside a Windows 11 box . I can see data in the terminal window when pressing the Somfy remote button, when I enable the "undec" receiver option. (This remote correctly commands the blinds to move).

But on the Pi 4 ....

1. The RFX433SL-USB corrrectly shows connecting/disconnecting.

The "Rx & USB" led on the "RFX433SL-USB" is permanently illuminated when connected.

When I connect plug in the USB cable, the Raspberry Pi 4 Console displays:

17 Mar 13:20:03 - [info] [rfx-blinds-in:01392c2a70be68da] connecting to /dev/ttyUSB0 2024-03-17 13:20:08.693 [rfxcom] on /dev/ttyUSB0 - Sent : 0D,00,00,00,00,00,00,00,00,00,00,00,00,00 2024-03-17 13:20:09.196 [rfxcom] on /dev/ttyUSB0 - Sent : 0D,00,00,01,02,00,00,00,00,00,00,00,00,00 2024-03-17 13:20:09.315 [rfxcom] on /dev/ttyUSB0 - Received: 14,01,00,01,02,53,1D,00,00,00,00,03,03,23,14,54,00,00,24,00,00 2024-03-17 13:20:09.318 [rfxcom] on /dev/ttyUSB0 - Sent : 0D,00,00,02,07,00,00,00,00,00,00,00,00,00 2024-03-17 13:20:09.940 [rfxcom] on /dev/ttyUSB0 - Received: 14,01,07,02,07,43,6F,70,79,72,69,67,68,74,20,52,46,58,43,4F,4D 2024-03-17 13:20:09.941 [rfxcom] on /dev/ttyUSB0 - Copyright RFXCOM 2024-03-17 13:20:09.942 [rfxcom] on /dev/ttyUSB0 - Started command message queue 17 Mar 13:20:09 - [info] [rfx-blinds-in:01392c2a70be68da] connected: Serial port /dev/ttyUSB0 17 Mar 13:20:03 - [info] [rfx-blinds-in:01392c2a70be68da] connecting to /dev/ttyUSB0 2024-03-17 13:20:08.693 [rfxcom] on /dev/ttyUSB0 - Sent : 0D,00,00,00,00,00,00,00,00,00,00,00,00,00 2024-03-17 13:20:09.196 [rfxcom] on /dev/ttyUSB0 - Sent : 0D,00,00,01,02,00,00,00,00,00,00,00,00,00 2024-03-17 13:20:09.315 [rfxcom] on /dev/ttyUSB0 - Received: 14,01,00,01,02,53,1D,00,00,00,00,03,03,23,14,54,00,00,24,00,00 2024-03-17 13:20:09.318 [rfxcom] on /dev/ttyUSB0 - Sent : 0D,00,00,02,07,00,00,00,00,00,00,00,00,00 2024-03-17 13:20:09.940 [rfxcom] on /dev/ttyUSB0 - Received: 14,01,07,02,07,43,6F,70,79,72,69,67,68,74,20,52,46,58,43,4F,4D 2024-03-17 13:20:09.941 [rfxcom] on /dev/ttyUSB0 - Copyright RFXCOM 2024-03-17 13:20:09.942 [rfxcom] on /dev/ttyUSB0 - Started command message queue 17 Mar 13:20:09 - [info] [rfx-blinds-in:01392c2a70be68da] connected: Serial port /dev/ttyUSB0

image

  1. But the "rfx-blinds-in" does not receive signals from a Somfy remote. No Node-Red debugger or console messages appear even when I select "Show debug messages on the console".

image

image

  1. The "rfx-blinds-out" also shows connected, but fails to illuminate the Tx LED on the "RFX433SL-USB".

I'd love to get the Tx/Rx working with lots of systems with your node, so I welcome any/all suggestions.

Rich

maxwellhadley commented 3 months ago

As Bert has told you in his email, the RFX transceivers do not receive/decode the Somfy RFY remote controls.

To pair your RFX device with a Somfy blind motor:

  1. Choose a random (but valid) address and unit code to associate with the motor. If you have more than one motor it would make sense to use the same address with different unit codes. From this choice, you construct the topic to control the motor. For example, address = 0x123a, unit code 1 would give a topi of RFY/0x123a/1
  2. Connect an inject node to the rfx-blinds-out node: set the topic of the inject node to your chosen topic, and the payload to program. Ensure your rfx-blinds-out node is set to get address from message topic.
  3. Disconnect power from all Somfy RTS devices controlled by the original remote except the device to pair, then press the Program button for 2 seconds or longer on the original Somfy remote until the Somfy RTS device responds (usually with a 'jog' motion).
  4. Trigger the inject node to send the program message. The Somfy motor should respond, again usually with a 'jog' motion.

The blind motor should then respond to normal command messages (up/down etc.,) sent to the address in your chosen topic. You wont need the inject node any more, so it can be deleted.

RicharddeCrep commented 2 months ago

Hi Max,

I’ve been busy so have only now had time to finish installation of the RFX transceiver for Somfy blinds.

I think the text you provided below was very helpful, but could be improved for use in the manual. Web site etc. I include the amended text, below. I hope these edits help the next person.

So all is good now. Thanks for your help and great product.

Rich

Richard de Crespigny

RFX transceivers do not receive/decode the Somfy RFY remote controls. To pair your RFX device with a Somfy blind motor:

  1. Choose a random (but valid) address and unit code to associate with the motor. If you have more than one motor it would make sense to use the same address with different unit codes.

  2. From this choice, you construct the topic to control the motor. For example, address = 0x123a, unit code 1 would give a msg.topic of RFY/0x123a/1

  3. Create a new inject node (called “Programming”) to the rfx-blinds-out node:

a. set the msg.topic of the inject node to your chosen topic (i.e. "RFY/0x123a/1"),

b. set the msg.payload to "program".

c. Set the rfx-blinds-out node “Address” field to "get address from message topic”.

  1. Disconnect power from all Somfy RTS devices controlled by the original Somfy remote control except the device to pair. Then press the Program button (located on the rear surface of the Somfy remote control) for 2 seconds or longer until the Somfy RTS device responds (usually with a 'jog' motion).

  2. Trigger your new inject node to send the msg.payload="program" message to the address at msg.topic.

    1. The Somfy motor should respond, again usually with a 'jog' motion.
    2. The motor should then respond to normal blind command messages (msg.topic = …, and msg.payload=up/down/stop etc).

  3. You won’t need the "Programming" inject node again until you need to reprogram the blinds.

—

From: Max Hadley @.> Sent: Monday, March 18, 2024 6:00 AM To: maxwellhadley/node-red-contrib-rfxcom @.> Cc: Richard De Crespigny @.>; Author @.> Subject: Re: [maxwellhadley/node-red-contrib-rfxcom] Connecting in Node Red, but no response (Issue #139)

As Bert has told you in his email, the RFX transceivers do not receive/decode the Somfy RFY remote controls.

To pair your RFX device with a Somfy blind motor:

  1. Choose a random (but valid) address and unit code to associate with the motor. If you have more than one motor it would make sense to use the same address with different unit codes. From this choice, you construct the topic to control the motor. For example, address = 0x123a, unit code 1 would give a topi of RFY/0x123a/1
  2. Connect an inject node to the rfx-blinds-out node: set the topic of the inject node to your chosen topic, and the payload to program. Ensure your rfx-blinds-out node is set to get address from message topic.
  3. Disconnect power from all Somfy RTS devices controlled by the original remote except the device to pair, then press the Program button for 2 seconds or longer on the original Somfy remote until the Somfy RTS device responds (usually with a 'jog' motion).
  4. Trigger the inject node to send the program message. The Somfy motor should respond, again usually with a 'jog' motion.

The blind motor should then respond to normal command messages (up/down etc.,) sent to the address in your chosen topic. You wont need the inject node any more, so it can be deleted.

— Reply to this email directly, view it on GitHubhttps://github.com/maxwellhadley/node-red-contrib-rfxcom/issues/139#issuecomment-2002579512, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APAORYPHXTWHV22B2MOQTLTYYXR3BAVCNFSM6AAAAABEZW2HW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGU3TSNJRGI. You are receiving this because you authored the thread.Message ID: @.**@.>>

RicharddeCrep commented 2 months ago

Max, one last thing.

Regardless of the success in sending messages to the Somfy blinds, and the setting of the “Show debug messages on the console” in the config node, I always get an annoying "RFXCOM: Timed out waiting for response (6)" message after sending a message.

If the RFX does not Receive Somfy signals (that are not sent), then it should not give an error message when no reply is received.

Cheers again

Rich

From: Richard De Crespigny Sent: Monday, April 29, 2024 6:17 PM To: maxwellhadley/node-red-contrib-rfxcom @.***> Subject: RE: [maxwellhadley/node-red-contrib-rfxcom] Connecting in Node Red, but no response (Issue #139)

Hi Max,

I’ve been busy so have only now had time to finish installation of the RFX transceiver for Somfy blinds.

I think the text you provided below was very helpful, but could be improved for use in the manual. Web site etc. I include the amended text, below. I hope these edits help the next person.

So all is good now. Thanks for your help and great product.

Rich

Richard de Crespigny

RFX transceivers do not receive/decode the Somfy RFY remote controls. To pair your RFX device with a Somfy blind motor:

  1. Choose a random (but valid) address and unit code to associate with the motor. If you have more than one motor it would make sense to use the same address with different unit codes.

  2. From this choice, you construct the topic to control the motor. For example, address = 0x123a, unit code 1 would give a msg.topic of RFY/0x123a/1

  3. Create a new inject node (called “Programming”) to the rfx-blinds-out node:

a. set the msg.topic of the inject node to your chosen topic (i.e. "RFY/0x123a/1"),

b. set the msg.payload to "program".

c. Set the rfx-blinds-out node “Address” field to "get address from message topic”.

  1. Disconnect power from all Somfy RTS devices controlled by the original Somfy remote control except the device to pair. Then press the Program button (located on the rear surface of the Somfy remote control) for 2 seconds or longer until the Somfy RTS device responds (usually with a 'jog' motion).

  2. Trigger your new inject node to send the msg.payload="program" message to the address at msg.topic.

    1. The Somfy motor should respond, again usually with a 'jog' motion.
    2. The motor should then respond to normal blind command messages (msg.topic = …, and msg.payload=up/down/stop etc).

  3. You won’t need the "Programming" inject node again until you need to reprogram the blinds.

—

From: Max Hadley @.**@.>> Sent: Monday, March 18, 2024 6:00 AM To: maxwellhadley/node-red-contrib-rfxcom @.**@.>> Cc: Richard De Crespigny @.**@.>>; Author @.**@.>> Subject: Re: [maxwellhadley/node-red-contrib-rfxcom] Connecting in Node Red, but no response (Issue #139)

As Bert has told you in his email, the RFX transceivers do not receive/decode the Somfy RFY remote controls.

To pair your RFX device with a Somfy blind motor:

  1. Choose a random (but valid) address and unit code to associate with the motor. If you have more than one motor it would make sense to use the same address with different unit codes. From this choice, you construct the topic to control the motor. For example, address = 0x123a, unit code 1 would give a topi of RFY/0x123a/1
  2. Connect an inject node to the rfx-blinds-out node: set the topic of the inject node to your chosen topic, and the payload to program. Ensure your rfx-blinds-out node is set to get address from message topic.
  3. Disconnect power from all Somfy RTS devices controlled by the original remote except the device to pair, then press the Program button for 2 seconds or longer on the original Somfy remote until the Somfy RTS device responds (usually with a 'jog' motion).
  4. Trigger the inject node to send the program message. The Somfy motor should respond, again usually with a 'jog' motion.

The blind motor should then respond to normal command messages (up/down etc.,) sent to the address in your chosen topic. You wont need the inject node any more, so it can be deleted.

— Reply to this email directly, view it on GitHubhttps://github.com/maxwellhadley/node-red-contrib-rfxcom/issues/139#issuecomment-2002579512, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APAORYPHXTWHV22B2MOQTLTYYXR3BAVCNFSM6AAAAABEZW2HW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGU3TSNJRGI. You are receiving this because you authored the thread.Message ID: @.**@.>>

maxwellhadley commented 1 month ago

Thanks for your input, much appreciated! I see that in firmware version 2031, Bert has added receive mode for the RFY protocol. I have no further information (yet) but if/when I get an update I will look at adding it to the node.

maxwellhadley commented 1 month ago

Regardless of the success in sending messages to the Somfy blinds, and the setting of the “Show debug messages on the console” in the config node, I always get an annoying "RFXCOM: Timed out waiting for response (6)" message after sending a message.

That sounds like a problem I came across, caused by a firmware issue in the RFX. Firmware version 2030 fixes this, among other things.

RicharddeCrep commented 1 month ago

All great news Max. Thanks for all your efforts.

Nest wishes

Rich

From: Max Hadley @.> Sent: Friday, May 3, 2024 6:24 PM To: maxwellhadley/node-red-contrib-rfxcom @.> Cc: Richard De Crespigny @.>; Author @.> Subject: Re: [maxwellhadley/node-red-contrib-rfxcom] Connecting in Node Red, but no response (Issue #139)

Thanks for your input, much appreciated! I see that in firmware version 2031, Bert has added receive mode for the RFY protocol. I have no further information (yet) but if/when I get an update I will look at adding it to the node.

- Reply to this email directly, view it on GitHubhttps://github.com/maxwellhadley/node-red-contrib-rfxcom/issues/139#issuecomment-2092541273, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APAORYPIDPKVSNHU2YDGWR3ZANCQZAVCNFSM6AAAAABEZW2HW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJSGU2DCMRXGM. You are receiving this because you authored the thread.Message ID: @.**@.>>