From bdbda59e9c58bf15dbad66e49577fcaae9e2d2e2 Mon Sep 17 00:00:00 2001 From: Stefan <37924749+stefanroelofs@users.noreply.github.com> Date: Mon, 10 Oct 2022 17:11:18 +0200 Subject: [PATCH] Broken links (#24495) --- source/_integrations/alarmdecoder.markdown | 2 +- source/_integrations/anel_pwrctrl.markdown | 2 +- source/_integrations/balboa.markdown | 2 +- source/_integrations/caldav.markdown | 2 +- source/_integrations/dsmr.markdown | 2 +- source/_integrations/graphite.markdown | 2 +- source/_integrations/growatt_server.markdown | 2 +- source/_integrations/hdmi_cec.markdown | 16 ++++++----- source/_integrations/linode.markdown | 2 +- source/_integrations/logentries.markdown | 2 +- source/_integrations/nilu.markdown | 2 +- source/_integrations/proliphix.markdown | 2 +- .../pvpc_hourly_pricing.markdown | 28 ++++++++----------- source/_integrations/rpi_camera.markdown | 2 +- source/_integrations/scrape.markdown | 2 +- source/_integrations/serial.markdown | 2 +- 16 files changed, 35 insertions(+), 37 deletions(-) diff --git a/source/_integrations/alarmdecoder.markdown b/source/_integrations/alarmdecoder.markdown index f53cfbaa904..6783df78be4 100644 --- a/source/_integrations/alarmdecoder.markdown +++ b/source/_integrations/alarmdecoder.markdown @@ -190,7 +190,7 @@ The tables below show the key press sequences used for arming for the different
-The `chr(4)` and `chr(5)` sequences below are equivalent to pressing the Stay and Away keypad keys respectively (as outlined in the AlarmDecoder documentation). +The `chr(4)` and `chr(5)` sequences below are equivalent to pressing the Stay and Away keypad keys respectively (as outlined in the AlarmDecoder documentation).
diff --git a/source/_integrations/anel_pwrctrl.markdown b/source/_integrations/anel_pwrctrl.markdown index 8bd9975d4fb..8f808e1fca8 100644 --- a/source/_integrations/anel_pwrctrl.markdown +++ b/source/_integrations/anel_pwrctrl.markdown @@ -11,7 +11,7 @@ ha_platforms: ha_integration_type: integration --- -The `anel_pwrctrl` switch platform allows you to control [ANEL PwrCtrl](https://anel-elektronik.de/SITE/produkte/produkte.htm) devices. +The `anel_pwrctrl` switch platform allows you to control [ANEL PwrCtrl](https://en.anel.eu/index.htm?src=/produkte/produkte.htm) devices. Supported devices (tested): diff --git a/source/_integrations/balboa.markdown b/source/_integrations/balboa.markdown index 9b91e0b293a..e8ba2f788a1 100644 --- a/source/_integrations/balboa.markdown +++ b/source/_integrations/balboa.markdown @@ -16,7 +16,7 @@ ha_config_flow: true ha_integration_type: integration --- -This integration adds support for [Balboa](http://www.balboawatergroup.com/) Spa WiFi Modules to be used within Home Assistant. +This integration adds support for [Balboa](https://www.balboawatergroup.com/) Spa WiFi Modules to be used within Home Assistant. There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/caldav.markdown b/source/_integrations/caldav.markdown index 048527e6352..08b41efc457 100644 --- a/source/_integrations/caldav.markdown +++ b/source/_integrations/caldav.markdown @@ -15,7 +15,7 @@ The `caldav` platform allows you to connect to your WebDAV calendar and generate ## Prerequisites -You need to have a CalDAV server and credentials for it. This integration was tested against [Baikal](http://sabre.io/baikal/) but any integration complying with the RFC4791 should work. [Nextcloud](https://nextcloud.com/) and [Owncloud](https://owncloud.org/) work fine. +You need to have a CalDAV server and credentials for it. This integration was tested against [Baikal](https://sabre.io/baikal/) but any integration complying with the RFC4791 should work. [Nextcloud](https://nextcloud.com/) and [Owncloud](https://owncloud.org/) work fine. {% details "Notes for Home Assistant Core Installations" %} diff --git a/source/_integrations/dsmr.markdown b/source/_integrations/dsmr.markdown index 1f478c1af54..52004327f0a 100644 --- a/source/_integrations/dsmr.markdown +++ b/source/_integrations/dsmr.markdown @@ -83,7 +83,7 @@ $ docker run --device /dev/ttyUSB0:/dev/ttyUSB0 -d --name="home-assistant" -v /h #### Serial to network proxies: -- [ser2net](http://ser2net.sourceforge.net) +- [ser2net](https://ser2net.sourceforge.net) - [WIZnet WIZ110SR](https://www.wiznet.io/product-item/wiz110sr/) DIY solutions (ESP8266 based): diff --git a/source/_integrations/graphite.markdown b/source/_integrations/graphite.markdown index ef918099e1b..de9aaebe95a 100644 --- a/source/_integrations/graphite.markdown +++ b/source/_integrations/graphite.markdown @@ -9,7 +9,7 @@ ha_iot_class: Local Push ha_integration_type: integration --- -The `graphite` integration records all events and state changes and feeds the data to a [graphite](http://graphite.wikidot.com/) instance. +The `graphite` integration records all events and state changes and feeds the data to a [graphite](http://graphiteapp.org/) instance. To enable this component, add the following lines to your `configuration.yaml`: diff --git a/source/_integrations/growatt_server.markdown b/source/_integrations/growatt_server.markdown index efbd4074a51..858b7f47a85 100644 --- a/source/_integrations/growatt_server.markdown +++ b/source/_integrations/growatt_server.markdown @@ -17,7 +17,7 @@ ha_config_flow: true ha_integration_type: integration --- -This is a sensor to collect information from your Growatt inverters using [Growatt server](https://server.growatt.com/) by default. It is possible to specify an alternative endpoint server at configuration time e.g., [SMTEN](http://server.smten.com/). +This is a sensor to collect information from your Growatt inverters using [Growatt server](https://server.growatt.com/) by default. It is possible to specify an alternative endpoint server at configuration time e.g., [SMTEN](https://server.smten.com/). This will log into your Growatt account and grab the first "Plant", after which it collects the inverters on this plant and creates sensors for these inverters as well as total sensors. diff --git a/source/_integrations/hdmi_cec.markdown b/source/_integrations/hdmi_cec.markdown index b1749ea8db4..f7978b02482 100644 --- a/source/_integrations/hdmi_cec.markdown +++ b/source/_integrations/hdmi_cec.markdown @@ -38,7 +38,7 @@ ln -s /path/to/your/installation/of/_cec.so /path/to/your/venv/lib/python*/site- ``` -##### Symlinking examples: +##### Symlinking examples For the default virtual environment of a [Manual install for Raspberry Pi](/docs/installation/raspberry-pi/) the command would be as follows. @@ -56,20 +56,21 @@ If after symlinking and adding `hdmi_cec:` to your configuration you are getting ## Testing your installation -* Login to Raspberry Pi +* Login to Raspberry Pi ```bash ssh pi@your_raspberry_pi_ip ``` -* at the command line type: +* at the command line type: ```bash echo scan | cec-client -s -d 1 ``` + Note: to use this command you have to install cec-utils package. In Debian based should be: ```sudo apt install cec-utils``` -* This will give you the list of devices that are on the bus +* This will give you the list of devices that are on the bus ```bash opening a connection to the CEC adapter... @@ -146,7 +147,6 @@ hdmi_cec: host: 192.168.1.3 ``` - ## Services ### Select Device @@ -201,6 +201,7 @@ action: Call the `hdmi_cec.volume` service with one of following commands: #### Volume up + Increase volume three times: ```json @@ -220,6 +221,7 @@ Stop increasing volume: ``` #### Volume down + Decrease volume three times: ```json @@ -239,6 +241,7 @@ Stop decreasing volume: ``` #### Volume mute + Toggle mute: ```json @@ -247,8 +250,7 @@ Toggle mute: value is ignored. - ## Useful References * [CEC overview](https://kwikwai.com/knowledge-base/the-hdmi-cec-bus/) -* [CEC-o-matic](http://www.cec-o-matic.com/) +* [CEC-o-matic](https://www.cec-o-matic.com/) diff --git a/source/_integrations/linode.markdown b/source/_integrations/linode.markdown index f3d7eaaefb2..419386f449f 100644 --- a/source/_integrations/linode.markdown +++ b/source/_integrations/linode.markdown @@ -25,7 +25,7 @@ There is currently support for the following device types within Home Assistant: Obtain your oAuth2 Access Token from Linode account. -- +- - Log in - Select API Tokens - Create a Personal Access Token, diff --git a/source/_integrations/logentries.markdown b/source/_integrations/logentries.markdown index 5aa2f539e57..f3a4548ba0c 100644 --- a/source/_integrations/logentries.markdown +++ b/source/_integrations/logentries.markdown @@ -9,7 +9,7 @@ ha_domain: logentries ha_integration_type: integration --- -The `logentries` integration makes it possible to log all state changes to [Logentries](http://logentries.com/) using Logentries Webhook endpoint. +The `logentries` integration makes it possible to log all state changes to [Logentries](https://logentries.com) using Logentries Webhook endpoint. Open the **Add a Log** page and choose **Manual**. Enter a name for your log in **Log Name**, add a group in **Select Log Set**, set **Token TCP - logs are identified by a token.** and press **Create Log Token**. The generated token is required for the Home Assistant configuration. diff --git a/source/_integrations/nilu.markdown b/source/_integrations/nilu.markdown index 8cabd854f21..b2309e500a3 100644 --- a/source/_integrations/nilu.markdown +++ b/source/_integrations/nilu.markdown @@ -13,7 +13,7 @@ ha_platforms: ha_integration_type: integration --- -The `nilu` air quality platform shows measurements of current air quality from NILU (Norsk Institutt for luftforskning/Norwegian Institute for Air Research) sensor stations within Norway. Makes data from the open API at [luftkvalitet.info](http://luftkvalitet.info/) and [nilu.no](https://nilu.no/) available in Home Assistant. +The `nilu` air quality platform shows measurements of current air quality from NILU (Norsk Institutt for luftforskning/Norwegian Institute for Air Research) sensor stations within Norway. Makes data from the open API at [luftkvalitet.info](https://www.luftkvalitet.info) and [nilu.no](https://nilu.no/) available in Home Assistant. ## Configuration diff --git a/source/_integrations/proliphix.markdown b/source/_integrations/proliphix.markdown index 06508a43a29..500187b8f9e 100644 --- a/source/_integrations/proliphix.markdown +++ b/source/_integrations/proliphix.markdown @@ -11,7 +11,7 @@ ha_platforms: ha_integration_type: integration --- -The `proliphix` climate platform let you control [Proliphix](http://www.proliphix.com) thermostat from Home Assistant. +The `proliphix` climate platform let you control Proliphix thermostats from Home Assistant. Currently supported and tested thermostats: diff --git a/source/_integrations/pvpc_hourly_pricing.markdown b/source/_integrations/pvpc_hourly_pricing.markdown index e792b558f47..fe2187f5a63 100644 --- a/source/_integrations/pvpc_hourly_pricing.markdown +++ b/source/_integrations/pvpc_hourly_pricing.markdown @@ -15,27 +15,22 @@ ha_platforms: ha_integration_type: integration --- -This sensor uses the official API to get the hourly price of electricity in Spain from https://www.esios.ree.es/en/pvpc. +This sensor uses the official API to get the hourly price of electricity in Spain from . -Specifically, it shows the current __active energy invoicing price (FEU)__ in €/kWh, -which is the energy term hourly price applied in the consumers' electrical bill -with a contracted power not exceeding 15 kW and which are under the PVPC -(Voluntary Price for Small Consumer). +Specifically, it shows the current __active energy invoicing price (FEU)__ in €/kWh, which is the energy term hourly price applied in the consumers' electrical bill with a contracted power not exceeding 15 kW and which are under the PVPC (Voluntary Price for Small Consumer). -It includes the energy term of the access tolls, the charges and the production cost. It does not include taxes. -The hourly prices and energy periods are the same throughout the Spanish territory regardless of the time zone, -except for the cities of Ceuta and Melilla, where they are slightly different. +It includes the energy term of the access tolls, the charges and the production cost. It does not include taxes. The hourly prices and energy periods are the same throughout the Spanish territory regardless of the time zone, except for the cities of Ceuta and Melilla, where they are slightly different. -More information available at http://www.cnmc.es/en/ and http://www.omie.es/en/ +More information available at and ## Configuration To configure PVPC Hourly Pricing, set it up via the integrations panel in the configuration screen. Set a name for the price sensor (default is `sensor.pvpc`), and select one of the two available tariffs, -according to your geographic position in Spain: +according to your geographic position in Spain: - `2.0TD`, for the Peninsula, the Balearic Islands and the Canary Islands. - `2.0TD (Ceuta/Melilla)`, for the cities of Ceuta and Melilla. @@ -50,7 +45,7 @@ and you can change the sensor configuration anytime by going to the integration' ### Advanced configuration -PVPC Hourly Pricing allows manual configuration by adding a section to your `configuration.yaml`. +PVPC Hourly Pricing allows manual configuration by adding a section to your `configuration.yaml`. ```yaml # Set up electricity price sensors as a component: @@ -88,10 +83,11 @@ power_p3:
The sensor provides an hourly price for energy consumed, but the variable cost of energy is only one of the factors that add up to the electricity bill: -* Fixed cost of contracted power -* Fixed cost of energy consumed -* Variable cost of energy consumed (the sensor's value) -* Other fixed expenses, such as the rental of the electric meter -* Multiple taxes applied + +- Fixed cost of contracted power +- Fixed cost of energy consumed +- Variable cost of energy consumed (the sensor's value) +- Other fixed expenses, such as the rental of the electric meter +- Multiple taxes applied
diff --git a/source/_integrations/rpi_camera.markdown b/source/_integrations/rpi_camera.markdown index dca849a1b31..972b3dec592 100644 --- a/source/_integrations/rpi_camera.markdown +++ b/source/_integrations/rpi_camera.markdown @@ -76,7 +76,7 @@ overlay_metadata: type: integer default: none overlay_timestamp: - description: Helper to add date/time onto the picture. Format as used by [`strftime`](http://man7.org/linux/man-pages/man3/strftime.3.html). + description: Helper to add date/time onto the picture. Format as used by [`strftime`](https://man7.org/linux/man-pages/man3/strftime.3.html). required: false type: string default: none diff --git a/source/_integrations/scrape.markdown b/source/_integrations/scrape.markdown index 1d6c0744e3e..8682671a42d 100644 --- a/source/_integrations/scrape.markdown +++ b/source/_integrations/scrape.markdown @@ -137,7 +137,7 @@ sensor: ### Get a value out of a tag -The German [Federal Office for Radiation protection (Bundesamt für Strahlenschutz)](http://www.bfs.de/) is publishing various details about optical radiation including an UV index. This example is getting the index for a region in Germany. +The German [Federal Office for Radiation protection (Bundesamt für Strahlenschutz)](https://www.bfs.de/) is publishing various details about optical radiation including an UV index. This example is getting the index for a region in Germany. ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/serial.markdown b/source/_integrations/serial.markdown index 1ae0984e102..41d648a4542 100644 --- a/source/_integrations/serial.markdown +++ b/source/_integrations/serial.markdown @@ -13,7 +13,7 @@ ha_platforms: ha_integration_type: integration --- -The `serial` sensor platform is using the data provided by a device connected to the serial port of the system where Home Assistant is running. With [`ser2net`](http://ser2net.sourceforge.net/) and [`socat`](http://www.dest-unreach.org/socat/) would it also work for sensors connected to a remote system. +The `serial` sensor platform is using the data provided by a device connected to the serial port of the system where Home Assistant is running. With [`ser2net`](https://ser2net.sourceforge.net/) and [`socat`](http://www.dest-unreach.org/socat/) would it also work for sensors connected to a remote system. To check what kind of data is arriving at your serial port, use a command-line tool like `minicom` or `picocom` on Linux, on a macOS you can use `screen` or on Windows `putty`.