mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 07:17:14 +00:00
Broken links (#24495)
This commit is contained in:
Stefan
GitHub
parent
e1d3f69f6e
commit
bdbda59e9c
@ -190,7 +190,7 @@ The tables below show the key press sequences used for arming for the different
|
||||
|
||||
<div class='note'>
|
||||
|
||||
The `chr(4)` and `chr(5)` sequences below are equivalent to pressing the <em>Stay</em> and <em>Away</em> keypad keys respectively (as outlined in the <a href='http://www.alarmdecoder.com/wiki/index.php/Protocol#Special_Keys'>AlarmDecoder documentation</a>).
|
||||
The `chr(4)` and `chr(5)` sequences below are equivalent to pressing the <em>Stay</em> and <em>Away</em> keypad keys respectively (as outlined in the <a href='https://www.alarmdecoder.com/wiki/index.php/Protocol#Special_Keys'>AlarmDecoder documentation</a>).
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -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):
|
||||
|
||||
|
||||
@ -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:
|
||||
|
||||
|
||||
@ -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" %}
|
||||
|
||||
|
||||
@ -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):
|
||||
|
||||
@ -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`:
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -67,6 +67,7 @@ ssh pi@your_raspberry_pi_ip
|
||||
```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
|
||||
@ -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/)
|
||||
|
||||
@ -25,7 +25,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
Obtain your oAuth2 Access Token from Linode account.
|
||||
|
||||
- <http://cloud.linode.com>
|
||||
- <https://cloud.linode.com>
|
||||
- Log in
|
||||
- Select API Tokens
|
||||
- Create a Personal Access Token,
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
@ -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
|
||||
|
||||
|
||||
@ -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:
|
||||
|
||||
|
||||
@ -15,20 +15,15 @@ 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 <https://www.esios.ree.es/en/pvpc>.
|
||||
|
||||
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.
|
||||
|
||||
<iframe src="https://www.esios.ree.es/en/embed/active-energy-invoicing-price-pvpc" width="100%" height="608"></iframe>
|
||||
|
||||
More information available at http://www.cnmc.es/en/ and http://www.omie.es/en/
|
||||
More information available at <https://www.cnmc.es/en/> and <https://www.omie.es/en/>
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -88,10 +83,11 @@ power_p3:
|
||||
<div class='note'>
|
||||
|
||||
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
|
||||
|
||||
</div>
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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`.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user