Integration - RFplayer

Hello everyone,

I’m working on an external Gladys integration for the RFPlayer RFP1000 key (Ziblue / GCE Electronics, 433 and 868 MHz).

:backhand_index_pointing_right: Code: GitHub - prohand/gladys-rfplayer: Gladys external integration to connect rfplayer devices in Gladys · GitHub

What it does

  • Sensors heard, proposed in the Discovery tab: Oregon probes (temperature, humidity, pressure, wind, rain, UV) and OWL meters.
  • Detectors Visonic, X2D, and KD101: alarm, self-protection, low battery.
  • Remotes: Chacon/DiO, X10, Somfy RTS, Blyss, X2D, Visonic key fobs…
  • Actuators controlled by the key: outlets, switches, dimmable lamps, Somfy RTS blinds (the « my » button serves as a stop) and gates.
  • One-click pairing: the « Pair an actuator » button sends the pairing frame and adds the device to the configuration.
  • Radio jamming detection of the key, useful for a wireless alarm.
  • Scene triggers (Gladys 5.1): remote button pressed, detector triggered, low battery, jamming.
  • Scene actions (Gladys 5.1): send a radio command, simulate jamming.
  • Widget « RFPlayer Radio » on the dashboard.
  • 100 % local, no cloud.

:warning: The problem: the integration cannot access the USB

External integrations run in an isolated container, and this container receives no serial port: neither /dev/ttyUSB*, nor /dev/ttyACM*.

In the manifest, the only hardware classes we can request are coral-usb, coral-pcie, gpu, and video. And even then: only for sub-containers, not for the main container.

Result: impossible to plug a serial USB key directly into an external integration.

I had the same problem with a Téléinfo integration. It will also affect Zigbee and Z-Wave keys, RFXtrx, EnOcean, Arduino…

Current workaround

We expose the key’s serial port as TCP with ser2net (or socat) on the machine where it is plugged in. The integration then connects to IP:port.

Example of /etc/ser2net.yaml:

connection: &rfplayer
  accepter: tcp,4000
  enable: on
  options:
    kickolduser: true
  connector: serialdev,/dev/serial/by-id/usb-XXXX-if00-port0,115200n81,local

Then, in the integration configuration: host = local IP of the machine (not localhost), port = 4000.

It works, but it’s not ideal:

  • One more technical step for the user: install and configure ser2net. This is not the « one-click » spirit of the store.
  • No password on the TCP port: anyone on the local network can control the radio devices. You need to limit listening to an IP or filter with the firewall.
  • One more service to monitor on the host machine.

The request is made :bullseye:

I proposed a serial hardware class: the integration requests it, the user chooses which key to give it, and Gladys mounts only that port in the container. The sandbox remains secure.

Changes are needed in 3 places, one issue for each:

:backhand_index_pointing_right: If you are concerned (RFPlayer, Téléinfo, Zigbee, Z-Wave…), put a :+1: on these issues or add your case in a comment. It helps to prioritize.

@pierre-gilles, I can help test as soon as there is something.

Call for testers

The integration follows the official RFPlayer API specification and is covered by automated tests. However, I haven’t tested it on a real key yet.

If you have an RFPlayer, your feedback helps a lot, especially on:

  • Somfy RTS blinds: the « my » function and pairing;
  • Chacon/DiO outlets: pairing;
  • Oregon probes and Visonic detectors.

The complete installation documentation is in French, including ser2net: gladys-rfplayer/docs/fr.md at main · prohand/gladys-rfplayer · GitHub

Thanks! :slightly_smiling_face:

@prohand I think the message is cut off, or I just don’t get it at all ^^

Thank you :slight_smile:
It’s fixed

Hello,

I just installed RFPLAYER 1000 to control my two SOMFY RTS outdoor shutters and my roller shutters via TYXIA 463 modules (old installation with a Pi and Domoticz). The small issue is with the pairing. I fiddled around to finally understand that no address should be entered in the Actuator field! The shutters worked fine until I tried to integrate the roller shutters into X2DSHUTTER. Some worked, but others didn’t, and especially, I no longer had control over the shutters. I deleted everything and tried to re-pair the shutters. But randomly, one works but not the other! I gave up on the TYXIA and switched to SONOFF Zigbee, and everything works fine.

Could you help me connect the SOMFY shutters (I also have a SOMFY garage door)?

Is RFPLAYER stable? Or should I switch to ESPSOMFY? I wonder if there isn’t an address issue during pairing for RFPLAYER as I fiddled a lot during the tests. Is there a memory that stores these values? And can it be erased to start fresh?

Otherwise, Gladys Plus is great!

Hello @Hebert_SALLEE,

Thank you for this detailed feedback, it allowed me to complete the documentation. What you saw is well explained.

Why one shutter works and the other doesn’t

  • In Somfy RTS, the pairing frame is a toggle: a motor that already knows the address forgets it, a motor that doesn’t know it learns it. By re-pairing with the same address after deleting everything in Gladys, one shutter learned it and the other forgot it.
  • A Somfy motor only remembers a limited number of remote controls (often a dozen). After many attempts, its memory may be full: it then refuses any new pairing.
  • If you press PROG on a group remote control, all the shutters in the group learn the same address and move together.

X2DSHUTTER didn’t break anything on the Somfy side: it’s the Delta Dore protocol of your TYXIA modules, and the integration keeps them well separated.

Does the RFPlayer keep the pairing?

No, it’s the motor that keeps it. The key only retains one RTS counter per address.
:warning: Do not perform a FACTORYRESET on the key: it would forget these counters and the already paired shutters would no longer obey it.

To start fresh

  1. In Gladys: delete the devices and clear the Actuators field.
  2. To remove an old address from a motor: hold PROG on the original remote until the shutter makes a small back-and-forth movement, then in the RFPlayer Radio widget → Send a radio command: protocol RTS, the old address, command Unpair.
  3. If you don’t know which addresses are lingering in a motor: reset the motor according to its manual (be careful, this also erases the original remote, which you will need to re-pair later).
  4. Re-pair with the Pair an actuator button: a new address per shutter (e.g., 10, 11, 12), one shutter at a time, with its individual remote control.

Somfy Garage Door

Declare it as an shutter RTS (up / my / down), for example:
Garage = shutter RTS 13

For a gate, it’s button with qualifier=1:
Gate = button RTS 14 qualifier=1

RFPlayer or ESPSomfy?

ESPSomfy only does Somfy RTS. The RFPlayer also manages your Delta Dore X2D modules and the rest (Chacon, detectors, probes…). In both cases, the radio does not confirm the state: Gladys displays the last command sent.

I added all this in the “In case of problem” part of the documentation. Don’t hesitate to come back if a shutter still resists.

And thank you for the word on Gladys Plus :slightly_smiling_face:

Hi @Hebert_SALLEE and welcome to Gladys :slight_smile:

Thanks for the compliment, glad you like it :wink:

Thanks for your quick response :relieved_face: I just did the right manipulations and it works :+1::+1:

Thanks again