diff --git a/source/_components/cover.rflink.markdown b/source/_components/cover.rflink.markdown
index 38b2cff93df..5431545d66b 100644
--- a/source/_components/cover.rflink.markdown
+++ b/source/_components/cover.rflink.markdown
@@ -1,13 +1,12 @@
 ---
 title: "RFLink Cover"
-description: "Instructions on how to integrate RFLink Somfy RTS Cover into Home Assistant."
+description: "Instructions on how to integrate RFLink Somfy RTS and KAKU ASUN-650 covers into Home Assistant."
 logo: rflink.png
 ha_category:
   - Cover
 ha_release: 0.55
 ---
 
-
 The `rflink` integration supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
 
 First, you have to set up your [RFLink hub](/components/rflink/).
@@ -124,8 +123,49 @@ devices:
           description: The `aliases` which do not respond to group commands.
           required: false
           type: [list, string]
+        type:
+          description: The option to invert (`inverted`) on/off commands sent to the RFLink device or not (`standard`).
+          required: false
+          type: string
 {% endconfiguration %}
 
+### Setting up a KAKU ASUN-650 device
+
+In RFLink, the ON and DOWN command are used to close the cover and the OFF and UP command are used to open the cover. The KAKU (COCO) ASUN-650 works the other way around, it uses the ON command to open the cover and the OFF command to close the cover.
+
+The RFLink cover device has a property named `type` that takes 2 values:
+
+- `standard`: Do not invert the on/off commands sent to the RFLink device.
+- `inverted`: Invert the on/off commands sent to the RFLink device.
+
+The following configuration example shows how to use the `type` property:
+
+```yaml
+# Example configuration.yaml entry that shows how to
+# use the type property.
+cover:
+  - platform: rflink
+    devices:
+      newkaku_xxxxxxxx_x:
+        name: kaku_inverted_by_type
+        type: inverted
+      newkaku_xxxxxxxx_y:
+        name: kaku_not_inverted_by_type
+        type: standard
+      newkaku_xxxxxxxx_z:
+        name: kaku_inverted_by_default
+      nonkaku_yyyyyyyy_x:
+        name: non_kaku_inverted_by_type
+        type: inverted
+      nonkaku_yyyyyyyy_y:
+        name: non_kaku_not_inverted_by_type
+        type: standard
+      nonkaku_yyyyyyyy_z:
+        name: non_kaku_not_inverted_by_default
+```
+
+The configuration above shows that the `type` property may be omitted. When the ID starts with `newkaku`, the component will make sure that the on and off commands are inverted. When the ID does not start with `newkaku`, the on and off commands are not inverted. 
+
 ### Device support
 
 See [device support](/components/rflink/#device-support).
@@ -157,4 +197,4 @@ cover:
       RTS_32E542_0:
         name: habitaciones
         fire_event: true
-```
\ No newline at end of file
+```