Fix the remaining issues

source/_components/pilight.markdown

@@ -1,7 +1,7 @@
 ---
 layout: page
 title: "Pilight"
-description: "Instructions how to setup MQTT within Home Assistant."
+description: "Instructions how to setup Pilight within Home Assistant."
 date: 2015-08-07 18:00
 sidebar: true
 comments: false
@@ -9,8 +9,7 @@ sharing: true
 footer: true
 logo: pilight.png
 ha_category: Hub
-featured: true
-ha_release: pre 0.26
+ha_release: 0.26
 ha_iot_class: Local Push
 ---
 
@@ -25,15 +24,14 @@ To integrate pilight into Home Assistant, add the following section to your `con
 ```yaml
 # Example configuration.yaml entry
 pilight:
-  host: 127.0.0.1
-  port: 5000
-  whitelist:  # optional
-    protocol:
-      - daycom
-      - intertechno
-    id:
-      - 42
-  
+  - host: 127.0.0.1
+    port: 5000
+    whitelist:  # optional
+      protocol:
+        - daycom
+        - intertechno
+      id:
+        - 42
 ```
 
 Configuration variables:
@@ -41,12 +39,14 @@ Configuration variables:
 - **host** (*Required*): The IP address of the computer running the pilight-daemon, e.g. 192.168.1.32.
 - **port** (*Required*): The network port to connect to. The usual port is [5000](https://www.pilight.org/development/api/).
 - **whitelist** (*Optional*): You can define a whitelist to prevent that too many unwanted RF codes (e.g. the neighbours weather station) are put on your HA event bus. All defined subsections have to be matched. A subsection is matched if one of the items are true.
+
 In this example only received RF codes using a daycom or intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight [API](https://www.pilight.org/development/api/).
 
-## Troubleshooting
+## {% linkable_title Troubleshooting %}
 
 - A list of tested RF transceiver hardware is available [here](https://wiki.pilight.org/doku.php/electronics). This might be usefull before buying.
 - Sending commands is simple when the protocol is known by pilight, but receiving commands can be rather difficult. It can happend that the code is not correctly recognized due to different timings in the sending hardware or the RF receiver. If this happens follow these steps:
+
 1. [Install](https://www.pilight.org/get-started/installation/) pilight from source (do not worry that is very easy) and only activate the protocols you are expecting in the pop up menu. This reduces false positives.
 2. Check the real timings of your device + RF receiver by running `pilight-debug`. Remember the `pulslen` parameter.
-3. Go to the `libs/pilight/protocols/433.92` subfolder of the pilight source code and open the .c file of your protocol. Search for `MIN_PULSE_LENGTH`, `MAX_PULSE_LENGTH ` and `AVG_PULSE_LENGTH`. Change the pulse lengths to match your measured one. Recompile and install pilight by rerunning ```sudo ./setup.sh```
+3. Go to the `libs/pilight/protocols/433.92` subfolder of the pilight source code and open the .c file of your protocol. Search for `MIN_PULSE_LENGTH`, `MAX_PULSE_LENGTH ` and `AVG_PULSE_LENGTH`. Change the pulse lengths to match your measured one. Recompile and install pilight by re-running `$ sudo ./setup.sh`.