jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-14 21:06:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update default Pilight port number (#4976)

Browse Source 
* 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.

* 🚑 Host and port variables are optional

* 🚀 Trigger rebuild

* Remove optional configuration variables

* 🚀 Trigger rebuild
This commit is contained in:
Ettienne Gous 2018-03-24 19:39:13 +11:00 committed by Franck Nijhof
parent 0ead042087
commit 63746ddee5
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/_components/pilight.markdown
View File

@ -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.