diff --git a/source/_integrations/rfxtrx.markdown b/source/_integrations/rfxtrx.markdown
index d04c2784e87..4227916136e 100644
--- a/source/_integrations/rfxtrx.markdown
+++ b/source/_integrations/rfxtrx.markdown
@@ -145,6 +145,16 @@ Binary sensors have only two states - "on" and "off". Many door or window openin
 
 For those devices, use the *off_delay* parameter. It defines a delay after, which a device will go back to an "Off" state. That "Off" state will be fired internally by Home Assistant, just as if the device fired it by itself. If a motion sensor can only send signals once every 5 seconds, sets the *off_delay* parameter to *seconds: 5*.
 
+#### Venetian blind mode
+
+Available only for RFY cover devices. Enables tilt control of venetian blind slats.
+
+Venetian blind motors that control slats tilt can be configured in one of two modes - US (short press of up/down buttons opens/closes the blind, long-press controls tilt angle), or European (short press of up/down buttons controls tilt angle, long-press opens/closes the blind). You can select one of the following settings depending on your blinds:
+
+- **Unknown** - default, tilt control is not enabled. Leave if the cover is not a venetian blind.
+- **US** - tilt control enabled for blinds in US tilt mode.
+- **EU** - tilt control enabled for blinds in European tilt mode.
+
 #### Options for PT-2262 devices under the Lighting4 protocol
 
 When a data packet is transmitted by a PT-2262 device using the Lighting4 protocol, there is no way to automatically extract the device identifier and the command from the packet. Each device has its own id/command length combination and the field lengths are not included in the data. One device that sends 2 different commands will be seen as 2 devices on Home Assistant. For such cases, the following options are available in order to circumvent the problem: