Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting in Node Red, but no response #139

Open
RicharddeCrep opened this issue Mar 17, 2024 · 6 comments
Open

Connecting in Node Red, but no response #139

RicharddeCrep opened this issue Mar 17, 2024 · 6 comments

Comments

@RicharddeCrep
Copy link

RicharddeCrep commented Mar 17, 2024

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
Copy link
Owner

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
Copy link
Author

RicharddeCrep commented Apr 29, 2024 via email

@RicharddeCrep
Copy link
Author

RicharddeCrep commented Apr 29, 2024 via email

@maxwellhadley
Copy link
Owner

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
Copy link
Owner

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
Copy link
Author

RicharddeCrep commented May 3, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants