From 63746ddee5cf5c7c4befe8df1c8113259916399c Mon Sep 17 00:00:00 2001 From: Ettienne Gous Date: Sat, 24 Mar 2018 19:39:13 +1100 Subject: [PATCH] Update default Pilight port number (#4976) * Update default Pilight port number Based on the Pilight docs targeted the default port is 5001, As started here https://manual.pilight.org/development/api.html and in the original Home Assistant doc I think they did a big refactor late last year to the code base and docs. * :ambulance: Host and port variables are optional * :rocket: Trigger rebuild * Remove optional configuration variables * :rocket: Trigger rebuild --- source/_components/pilight.markdown | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/source/_components/pilight.markdown b/source/_components/pilight.markdown index ab841bbe834..2e7e1b0150b 100644 --- a/source/_components/pilight.markdown +++ b/source/_components/pilight.markdown @@ -24,14 +24,12 @@ 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 ``` 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://manual.pilight.org/development/api.html). +- **host** (*Optional*): The IP address of the computer running the pilight-daemon, e.g., 192.168.1.32. +- **port** (*Optional*): The network port to connect to. The usual port is [5001](https://manual.pilight.org/development/api.html). - **send_delay** (*Optional*): You can define a send delay as a fraction of seconds if you experience transmission problems when you try to switch multiple switches at once. This can happen when you use a [pilight USB Nano](https://github.com/pilight/pilight-usb-nano) as hardware and switches a whole group of multiple switches on or off. Tested values are between 0.3 and 0.8 seconds depending on the hardware. - **whitelist** (*Optional*): You can define a whitelist to prevent that too many unwanted RF codes (e.g., the neighbors 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.