From f5cb4331eab83f83fe58153047421cb205d39945 Mon Sep 17 00:00:00 2001 From: Sven Serlier <85389871+wrt54g@users.noreply.github.com> Date: Mon, 12 Dec 2022 08:49:35 +0100 Subject: [PATCH] Remove index.html from pilight links (#25248) --- source/_integrations/pilight.markdown | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_integrations/pilight.markdown b/source/_integrations/pilight.markdown index b30f78bc9a8..1ea9ac9a78e 100644 --- a/source/_integrations/pilight.markdown +++ b/source/_integrations/pilight.markdown @@ -19,7 +19,7 @@ ha_platforms: ha_integration_type: integration --- -[Pilight](https://www.pilight.org/) is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common [protocols](https://manual.pilight.org/protocols/index.html) are already available. +[Pilight](https://www.pilight.org/) is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common [protocols](https://manual.pilight.org/protocols/) are already available. This pilight hub connects to the [pilight-daemon](https://manual.pilight.org/programs/daemon.html) via a socket connection to receive and send codes. Thus Home Assistant does not have to run on the computer in charge of the RF communication. @@ -48,7 +48,7 @@ host: default: 127.0.0.1 type: string port: - description: "The network port to connect to, see also: (https://manual.pilight.org/development/socket/index.html)." + description: "The network port to connect to, see also: (https://manual.pilight.org/development/socket/)." required: false default: 5001 type: integer @@ -63,7 +63,7 @@ whitelist: type: string {% endconfiguration %} -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://manual.pilight.org/development/index.html). +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://manual.pilight.org/development/). A full configuration sample could look like the sample below: @@ -274,7 +274,7 @@ Variables for the different codes (`on_code` and `off_code`): - **'off'** (*Optional*): `1` or `0` - **'on'** (*Optional*): `1` or `0` -For possible code entries, look at the [pilight API](https://manual.pilight.org/development/index.html). All commands allowed by [pilight-send](https://manual.pilight.org/programs/send.html) can be used. Which means that if, for a certain protocol, there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol, for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring. +For possible code entries, look at the [pilight API](https://manual.pilight.org/development/). All commands allowed by [pilight-send](https://manual.pilight.org/programs/send.html) can be used. Which means that if, for a certain protocol, there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol, for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring. Variables for the different receive codes (`on_code_receive` and `off_code_receive`): @@ -365,7 +365,7 @@ light: ## Troubleshooting -- A list of tested RF transceiver hardware is available [here](https://manual.pilight.org/electronics/index.html). This might be useful before buying. +- A list of tested RF transceiver hardware is available [here](https://manual.pilight.org/electronics/). This might be useful before buying. - Sending commands is simple when the protocol is known by pilight, but receiving commands can be rather difficult. It can happen 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://manual.pilight.org/installation.html) 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.