mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-13 12:26:50 +00:00
HTTPS-everywhere (update links in our website) (#10932)
* HTTPS-everywhere (update links in our website) * HTTPS-everywhere (round 2) * HTTPS-everywhere (round 3)
This commit is contained in:
Franck Nijhof
GitHub
parent
5417fa4f7f
commit
533bb3866f
@ -8,7 +8,7 @@ ha_iot_class: Local Polling
|
||||
ha_release: 0.19
|
||||
---
|
||||
|
||||
The `acer_projector` switch platform allows you to control the state of RS232 connected projectors from [Acer](http://www.acer.com).
|
||||
The `acer_projector` switch platform allows you to control the state of RS232 connected projectors from [Acer](https://www.acer.com/).
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_category:
|
||||
ha_release: 0.7
|
||||
---
|
||||
|
||||
This platform allows you to detect presence by looking at connected devices to an [Actiontec](http://www.actiontec.com/) device.
|
||||
This platform allows you to detect presence by looking at connected devices to an [Actiontec](https://www.actiontec.com/) device.
|
||||
|
||||
Supported devices (tested):
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ ha_release: "0.60"
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
The ADS (automation device specification) describes a device-independent and fieldbus independent interface for communication between [Beckhoff](https://www.beckhoff.com/) automation devices running [TwinCAT](http://www.beckhoff.hu/english.asp?twincat/default.htm) and other devices implementing this interface.
|
||||
The ADS (automation device specification) describes a device-independent and fieldbus independent interface for communication between [Beckhoff](https://www.beckhoff.com/) automation devices running [TwinCAT](https://www.beckhoff.hu/english.asp?twincat/default.htm) and other devices implementing this interface.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.53
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `airvisual` sensor platform queries the [AirVisual](https://airvisual.com/) API for air quality data. Data can be collected via latitude/longitude or by city/state/country. The resulting information creates sensors for the Air Quality Index (AQI), the human-friendly air quality level, and the main pollutant of that area. Sensors that conform to either/both the [U.S. and Chinese air quality standards](http://www.clm.com/publication.cfm?ID=366) can be created.
|
||||
The `airvisual` sensor platform queries the [AirVisual](https://airvisual.com/) API for air quality data. Data can be collected via latitude/longitude or by city/state/country. The resulting information creates sensors for the Air Quality Index (AQI), the human-friendly air quality level, and the main pollutant of that area. Sensors that conform to either/both the [U.S. and Chinese air quality standards](https://www.clm.com/publication.cfm?ID=366) can be created.
|
||||
|
||||
This platform requires an AirVisual API key, which can be obtained [here](https://airvisual.com/api). Note that the platform was designed using the "Community" package; the "Startup" and "Enterprise" package keys should continue to function, but actual results may vary (or not work at all).
|
||||
|
||||
|
||||
@ -78,5 +78,5 @@ Please refer to the [Amazon documentation][flash-briefing-api-docs] for more inf
|
||||
[small-icon]: /images/integrations/alexa/alexa-108x108.png
|
||||
[templates]: /topics/templating/
|
||||
[zero-three-one]: /blog/2016/10/22/flash-briefing-updater-hacktoberfest/
|
||||
[alexa-settings-site]: http://alexa.amazon.com/
|
||||
[alexa-settings-site]: https://alexa.amazon.com/
|
||||
[emulated-hue-component]: /integrations/emulated_hue/
|
||||
|
||||
@ -12,9 +12,9 @@ Polly is a paid service via Amazon Web Services. There is a [free tier](https:/
|
||||
|
||||
## Setup
|
||||
|
||||
For more information, please read the [AWS General Reference regarding Security Credentials](http://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html) to get the needed details. Also, check the [boto3 Documentation](http://boto3.readthedocs.io/en/latest/guide/configuration.html#shared-credentials-file) about the profiles and the [AWS Regions and Endpoints Reference](https://docs.aws.amazon.com/general/latest/gr/rande.html#pol_region) for available regions.
|
||||
For more information, please read the [AWS General Reference regarding Security Credentials](https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html) to get the needed details. Also, check the [boto3 Documentation](https://boto3.readthedocs.io/en/latest/guide/configuration.html#shared-credentials-file) about the profiles and the [AWS Regions and Endpoints Reference](https://docs.aws.amazon.com/general/latest/gr/rande.html#pol_region) for available regions.
|
||||
|
||||
Available voices are listed in the [Amazon Documentation](http://docs.aws.amazon.com/polly/latest/dg/voicelist.html).
|
||||
Available voices are listed in the [Amazon Documentation](https://docs.aws.amazon.com/polly/latest/dg/voicelist.html).
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_release: 0.93
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
Integrates [Ambiclimate](https://Ambiclimate.com) Air Conditioning controller into Home Assistant.
|
||||
Integrates [Ambiclimate](https://ambiclimate.com/) Air Conditioning controller into Home Assistant.
|
||||
|
||||
You must create an application [here](https://api.ambiclimate.com/clients) to obtain a `client_id` and `client_secret`.
|
||||
The `callback url` should be configured as your Home Assistant `base_url` + `/api/ambiclimate`, e.g. `https://example.com/api/ambiclimate`.
|
||||
|
||||
@ -8,7 +8,7 @@ ha_iot_class: Local Polling
|
||||
ha_release: "0.30"
|
||||
---
|
||||
|
||||
The `anel_pwrctrl` switch platform allows you to control [ANEL PwrCtrl](http://anel-elektronik.de/SITE/produkte/produkte.htm) devices.
|
||||
The `anel_pwrctrl` switch platform allows you to control [ANEL PwrCtrl](https://anel-elektronik.de/SITE/produkte/produkte.htm) devices.
|
||||
|
||||
Supported devices (tested):
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ Both [Anthem]'s current and last generation of A/V Receivers and Processors supp
|
||||
|
||||
Support is provided through the Python [anthemav] module. Older, RS-232 serial-based units like the [D2v](https://www.anthemav.com/products-current/type=av-processor/model=d2v-3d/page=overview) use a different protocol entirely and are not currently supported.
|
||||
|
||||
[Anthem]: http://www.anthemav.com/
|
||||
[Anthem]: https://www.anthemav.com/
|
||||
[anthemav]: https://github.com/nugget/python-anthemav
|
||||
|
||||
|
||||
|
||||
@ -75,7 +75,7 @@ name:
|
||||
|
||||
## Sensor
|
||||
|
||||
The `apcupsd` sensor platform allows you to monitor a UPS (battery backup) by using data from the [apcaccess](http://linux.die.net/man/8/apcaccess) command.
|
||||
The `apcupsd` sensor platform allows you to monitor a UPS (battery backup) by using data from the [apcaccess](https://linux.die.net/man/8/apcaccess) command.
|
||||
|
||||
### Configuration
|
||||
|
||||
|
||||
@ -100,7 +100,7 @@ Found Apple TVs:
|
||||
Note: You must use 'pair' with devices that have home sharing disabled
|
||||
```
|
||||
|
||||
Just copy and paste the `login_id` from the device you want to add. For more details about `atvremote`, see: [this page](http://pyatv.readthedocs.io/en/master/atvremote.html).
|
||||
Just copy and paste the `login_id` from the device you want to add. For more details about `atvremote`, see: [this page](https://pyatv.readthedocs.io/en/master/atvremote.html).
|
||||
|
||||
### Setting up device authentication
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
## Binary Sensor
|
||||
|
||||
The `arest` binary sensor platform allows you to get all data from your devices (like Arduinos with an ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework.
|
||||
The `arest` binary sensor platform allows you to get all data from your devices (like Arduinos with an ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the [aREST](https://arest.io/) RESTful framework.
|
||||
|
||||
To use your aREST binary sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -70,7 +70,7 @@ This sensor is not suitable for fast state changes because there is a high possi
|
||||
|
||||
## Sensor
|
||||
|
||||
The `arest` sensor platform allows you to get all data from your devices (like Arduinos with a Ethernet/Wifi connection, the ESP8266, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework.
|
||||
The `arest` sensor platform allows you to get all data from your devices (like Arduinos with a Ethernet/Wifi connection, the ESP8266, and the Raspberry Pi) running the [aREST](https://arest.io/) RESTful framework.
|
||||
|
||||
To use your aREST enabled device in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -173,7 +173,7 @@ The root will give you a JSON response that contains all variables and their cur
|
||||
|
||||
## Switch
|
||||
|
||||
The `arest` switch platform allows you to toggle pins of your devices (like Arduino boards with an Ethernet/Wifi connection, ESP8266 based devices, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework.
|
||||
The `arest` switch platform allows you to toggle pins of your devices (like Arduino boards with an Ethernet/Wifi connection, ESP8266 based devices, and the Raspberry Pi) running the [aREST](https://arest.io/) RESTful framework.
|
||||
|
||||
To use your aREST enabled device with pins in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.7
|
||||
---
|
||||
|
||||
|
||||
This platform allows you to detect presence by looking at connected devices to an [Aruba Instant](http://www.arubanetworks.com/products/networking/aruba-instant/) device.
|
||||
This platform allows you to detect presence by looking at connected devices to an [Aruba Instant](https://www.arubanetworks.com/products/networking/aruba-instant/) device.
|
||||
|
||||
Supported devices (tested):
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_release: 0.31
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `arwn` sensor platform is a client for the [Ambient Radio Weather Network](http://github.com/sdague/arwn) project. This collects weather station data and makes it available in an MQTT subtree.
|
||||
The `arwn` sensor platform is a client for the [Ambient Radio Weather Network](https://github.com/sdague/arwn) project. This collects weather station data and makes it available in an MQTT subtree.
|
||||
|
||||
To use your ARWN setup, you must already have configured the [MQTT](/integrations/mqtt/) platform. Then add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ha_release: 0.83
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `asuswrt` integration is the main integration to connect to a [ASUSWRT](http://event.asus.com/2013/nw/ASUSWRT/) based router.
|
||||
The `asuswrt` integration is the main integration to connect to a [ASUSWRT](https://event.asus.com/2013/nw/ASUSWRT/) based router.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ ha_iot_class: Cloud Polling
|
||||
The `atome` sensor platform is retrieving the consumption of your home from the [Direct Energy Atome electric meter](https://total.direct-energie.com/particuliers/electricite/compteur-linky/atome).
|
||||
This special little device is connected to a Linky Electric Meter, and sends live data to a cloud platform.
|
||||
|
||||
As there is no official documentation for the API, the component retrieves data from the API used in the Atome mobile app, [hosted here](http://esoftlink.esoftthings.com).
|
||||
As there is no official documentation for the API, the component retrieves data from the API used in the Atome mobile app, [hosted here](https://esoftlink.esoftthings.com/).
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ha_release: 0.64
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `august` integration allows you to integrate your [August](http://august.com) devices in Home Assistant.
|
||||
The `august` integration allows you to integrate your [August](https://august.com/) devices in Home Assistant.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -74,4 +74,4 @@ If you have August Smart Lock with DoorSense, once you have enabled the August c
|
||||
|
||||
### Camera
|
||||
|
||||
The `august` camera platform allows you to view the latest camera image (triggered by motion) by your [August](http://august.com) device in Home Assistant.
|
||||
The `august` camera platform allows you to view the latest camera image (triggered by motion) by your [August](https://august.com/) device in Home Assistant.
|
||||
|
||||
@ -7,7 +7,7 @@ ha_release: 0.39
|
||||
logo: noaa.png
|
||||
---
|
||||
|
||||
The `aurora` platform uses the [NOAA aurora forecast](http://www.swpc.noaa.gov/products/aurora-30-minute-forecast) service to let you know if an aurora might be visible at your home location in the next 30 minutes, based off of current solar flare activity.
|
||||
The `aurora` platform uses the [NOAA aurora forecast](https://www.swpc.noaa.gov/products/aurora-30-minute-forecast) service to let you know if an aurora might be visible at your home location in the next 30 minutes, based off of current solar flare activity.
|
||||
|
||||
This service gives a number 0-100 representing the current likelihood of visible auroras at your latitude/longitude. By default this sensor is set up to trigger when the reported likelihood for your location is > 75. It updates every 5 minutes.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Cloud Push
|
||||
---
|
||||
|
||||
|
||||
The `automatic` device tracker platform offers presence detection by retrieving your car's information from the [Automatic](http://automatic.com/) cloud service.
|
||||
The `automatic` device tracker platform offers presence detection by retrieving your car's information from the [Automatic](https://automatic.com/) cloud service.
|
||||
|
||||
## Setup
|
||||
|
||||
|
||||
@ -100,7 +100,7 @@ context:
|
||||
|
||||
## Lambda Notify Usage
|
||||
|
||||
AWS Lambda is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)) or a partial ARN. For more information, please see the [botocore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/lambda.html#Lambda.Client.invoke).
|
||||
AWS Lambda is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)) or a partial ARN. For more information, please see the [botocore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/lambda.html#Lambda.Client.invoke).
|
||||
|
||||
The Lambda event payload will contain everything passed in the service call payload. Here is an example payload that would be sent to Lambda:
|
||||
|
||||
@ -128,7 +128,7 @@ The context will look like this:
|
||||
|
||||
## SNS Notify Usage
|
||||
|
||||
AWS SNS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [botocore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.publish).
|
||||
AWS SNS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [botocore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.publish).
|
||||
|
||||
If one exists, the SNS Subject will be set to the title. All attributes from the payload, except the message, will be sent as stringified message attributes.
|
||||
|
||||
@ -154,14 +154,14 @@ If you do not download them, you will lose them and will have to recreate a new
|
||||
|
||||
## SQS Notify Usage
|
||||
|
||||
AWS SQS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS docs](http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/ImportantIdentifiers.html) and [bototcore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sqs.html#SQS.Client.send_message)
|
||||
AWS SQS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS docs](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/ImportantIdentifiers.html) and [bototcore docs](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sqs.html#SQS.Client.send_message)
|
||||
|
||||
The SQS event payload will contain everything passed in the service call payload. SQS payloads will be published as stringified JSON. All attributes from the payload, except message, will also be sent as stringified message attributes. Here is an example message that would be published to the SQS queue:
|
||||
|
||||
```json
|
||||
{
|
||||
"title": "Test message!",
|
||||
"target": "http://sqs.us-east-1.amazonaws.com/123456789012/queue2",
|
||||
"target": "https://sqs.us-east-1.amazonaws.com/123456789012/queue2%22,
|
||||
"data": {
|
||||
"test": "okay"
|
||||
},
|
||||
|
||||
@ -64,7 +64,7 @@ pins:
|
||||
default: UP
|
||||
{% endconfiguration %}
|
||||
|
||||
For more details about the GPIO layout, visit the [article](http://elinux.org/Beagleboard:BeagleBoneBlack) about the BeagleBone Black.
|
||||
For more details about the GPIO layout, visit the [article](https://elinux.org/Beagleboard:BeagleBoneBlack) about the BeagleBone Black.
|
||||
|
||||
## Switch
|
||||
|
||||
@ -112,4 +112,4 @@ pins:
|
||||
type: boolean
|
||||
{% endconfiguration %}
|
||||
|
||||
For more details about the GPIO layout, visit the [article](http://elinux.org/Beagleboard:BeagleBoneBlack) about the BeagleBone Black.
|
||||
For more details about the GPIO layout, visit the [article](https://elinux.org/Beagleboard:BeagleBoneBlack) about the BeagleBone Black.
|
||||
|
||||
@ -14,7 +14,7 @@ The `knx` integration must be configured correctly to use this integration, see
|
||||
|
||||
</div>
|
||||
|
||||
The `knx` sensor platform allows you to monitor [KNX](http://www.knx.org) binary sensors.
|
||||
The `knx` sensor platform allows you to monitor [KNX](https://www.knx.org/) binary sensors.
|
||||
|
||||
Binary sensors are read-only. To write to the knx-bus configure an exposure [KNX Integration - Expose](/integrations/knx/#exposing-sensor-values-or-time-to-knx-bus).
|
||||
|
||||
|
||||
@ -37,10 +37,10 @@ For more information, visit the [serial api] of MySensors.
|
||||
|
||||
```cpp
|
||||
/**
|
||||
* Documentation: http://www.mysensors.org
|
||||
* Support Forum: http://forum.mysensors.org
|
||||
* Documentation: https://www.mysensors.org
|
||||
* Support Forum: https://forum.mysensors.org
|
||||
*
|
||||
* http://www.mysensors.org/build/binary
|
||||
* https://www.mysensors.org/build/binary
|
||||
*/
|
||||
|
||||
|
||||
@ -82,4 +82,4 @@ void loop()
|
||||
```
|
||||
|
||||
[main component]: /integrations/mysensors/
|
||||
[serial api]: http://www.mysensors.org/download
|
||||
[serial api]: https://www.mysensors.org/download
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: "0.50"
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
The `xiaomi aqara` binary sensor platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) binary sensors.
|
||||
The `xiaomi aqara` binary sensor platform allows you to get data from your [Xiaomi](https://www.mi.com/en/) binary sensors.
|
||||
|
||||
The requirement is that you have setup the [`xiaomi aqara` integration](/integrations/xiaomi_aqara/).
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ha_release: 0.93
|
||||
|
||||
The `bizkaibus` sensor will give you the time until the next bus in the selected stop.
|
||||
|
||||
The next website can help to determine the id of your bus stop. You can check if this is correct by going to [next link](http://apli.bizkaia.net/APPS/DANOK/TQ/DATOS_PARADAS/DATOS_Paradas.xml) and look the PR_CODE for the STOP_ID.
|
||||
The next website can help to determine the id of your bus stop. You can check if this is correct by going to [next link](https://apli.bizkaia.net/APPS/DANOK/TQ/DATOS_PARADAS/DATOS_Paradas.xml) and look the PR_CODE for the STOP_ID.
|
||||
|
||||
For a correct use of the sensor the selected route must stop in the selected stop.
|
||||
|
||||
@ -41,4 +41,4 @@ name:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
The public RTPI information is coming from [Bizkaibus API](http://apli.bizkaia.net/APPS/DANOK/TQWS/TQ.ASMX).
|
||||
The public RTPI information is coming from [Bizkaibus API](https://apli.bizkaia.net/APPS/DANOK/TQWS/TQ.ASMX).
|
||||
|
||||
@ -12,7 +12,7 @@ ha_release: "0.40"
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `blink` integration lets you view camera images and motion events from [Blink](http://blinkforhome.com) camera and security systems.
|
||||
The `blink` integration lets you view camera images and motion events from [Blink](https://blinkforhome.com/) camera and security systems.
|
||||
|
||||
## Setup
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.51
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `bluesound` platform allows you to control your [Bluesound](http://www.bluesound.com/) HiFi wireless speakers and audio integrations from Home Assistant.
|
||||
The `bluesound` platform allows you to control your [Bluesound](https://www.bluesound.com/) HiFi wireless speakers and audio integrations from Home Assistant.
|
||||
|
||||
If you want to automatically discover new devices, just make sure you have discovery: in your configuration.yaml file. To manually add a Bluesound device to your installation, add the following to your configuration.yaml file:
|
||||
|
||||
|
||||
@ -49,7 +49,7 @@ Some BTLE devices (e.g., fitness trackers) are only visible to the devices that
|
||||
|
||||
## Rootless Setup
|
||||
|
||||
Normally accessing the Bluetooth stack is reserved for root, but running programs that are networked as root is a bad security wise. To allow non-root access to the Bluetooth stack we can give Python 3 and hcitool the missing capabilities to access the Bluetooth stack. Quite like setting the setuid bit (see [Stack Exchange](http://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root) for more information).
|
||||
Normally accessing the Bluetooth stack is reserved for root, but running programs that are networked as root is a bad security wise. To allow non-root access to the Bluetooth stack we can give Python 3 and hcitool the missing capabilities to access the Bluetooth stack. Quite like setting the setuid bit (see [Stack Exchange](https://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root) for more information).
|
||||
|
||||
```bash
|
||||
sudo apt-get install libcap2-bin
|
||||
|
||||
@ -8,9 +8,9 @@ ha_release: 0.23
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `braviatv` platform allows you to control a [Sony Bravia TV](http://www.sony.com).
|
||||
The `braviatv` platform allows you to control a [Sony Bravia TV](https://www.sony.com/).
|
||||
|
||||
Almost all [Sony Bravia TV 2013 and newer](http://info.tvsideview.sony.net/en_ww/home_device.html#bravia) are supported. A more generic method for older TVs connected to a Raspberry Pi with HDMI-CEC is explained further below.
|
||||
Almost all [Sony Bravia TV 2013 and newer](https://info.tvsideview.sony.net/en_ww/home_device.html#bravia) are supported. A more generic method for older TVs connected to a Raspberry Pi with HDMI-CEC is explained further below.
|
||||
|
||||
You will need to configure your TV to allow the Home Assistant for remote usage. To do that, ensure that your TV is turned on. Open the configuration popup on Home Assistant and enter a random PIN (for example 0000). After that, the TV will show you a PIN and Home Assistant will allow you to re-enter that PIN. Enter the PIN shown on your TV and Home Assistant will be able to control your Sony Bravia TV.
|
||||
|
||||
|
||||
@ -119,7 +119,7 @@ pip install --use-wheel --no-index --find-links=https://github.com/sfbahr/PyCryp
|
||||
|
||||
## Switch
|
||||
|
||||
This `Broadlink` switch platform allow to you control Broadlink [devices](http://www.ibroadlink.com/).
|
||||
This `Broadlink` switch platform allow to you control Broadlink [devices](https://www.ibroadlink.com/).
|
||||
|
||||
### Configuration
|
||||
|
||||
@ -357,7 +357,7 @@ First get or learn all the remotes you want to add to Home Assistant in E-Contro
|
||||
Not every code works.
|
||||
|
||||
8. Convert the HEX codes to base64.
|
||||
Use [this](http://tomeko.net/online_tools/hex_to_base64.php?lang=en1) tool to convert the hex codes to base64 for use with Home Assistant.
|
||||
Use [this](https://tomeko.net/online_tools/hex_to_base64.php?lang=en1) tool to convert the hex codes to base64 for use with Home Assistant.
|
||||
|
||||
### Using iOS and Windows to obtain codes
|
||||
|
||||
@ -367,7 +367,7 @@ First get or learn all the remotes you want to add to Home Assistant in E-Contro
|
||||
|
||||
- Download and install Python 2.7 on your windows PC.
|
||||
- Run `pip install simplejson`. You must install simplejson in the same python version you will use to run the scripts. You can ensure that the current version is installed by attempting to install again and confirming that you see "Requirement already satisfied".
|
||||
- Download and install [iBackup Viewer](http://www.imactools.com/iphonebackupviewer/).
|
||||
- Download and install [iBackup Viewer](https://www.imactools.com/iphonebackupviewer/).
|
||||
- Download [these](https://github.com/NightRang3r/Broadlink-e-control-db-dump) github files. Make sure you place them in the \Python27 path in Windows. Be sure that the getBroadlinkSharedData.py from the download is in this directory.
|
||||
|
||||
3. Plug your iphone into your windows PC, open iTunes and create a non-encrypted backup of your device.
|
||||
|
||||
@ -73,7 +73,7 @@ The weather platform is easier to configure but less customizable.
|
||||
|
||||
## Camera
|
||||
|
||||
The `buienradar` camera platform uses [buienradar.nl](http://buienradar.nl/) as a source for the last rain radar map. The overview image of the whole of the Netherlands is loaded and shown as a camera in Home Assistant.
|
||||
The `buienradar` camera platform uses [buienradar.nl](https://buienradar.nl/) as a source for the last rain radar map. The overview image of the whole of the Netherlands is loaded and shown as a camera in Home Assistant.
|
||||
|
||||
Internally this component uses the radar map image as [documented](https://www.buienradar.nl/overbuienradar/gratis-weerdata) on buienradar.nl.
|
||||
The downloaded image is cached to prevent Home Assistant from making a new request to buienradar.nl multiple times a minute when Home Assistant checks for new stills from the camera.
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.26
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `ffmpeg` platform allows you to use any video feed as a camera in Home Assistant via [FFmpeg](http://www.ffmpeg.org/). This video source must support multiple simultaneous reads, because for every concurrent Home Assistant user, a connection will be made to the source every 10 seconds. Normally this should not be a problem.
|
||||
The `ffmpeg` platform allows you to use any video feed as a camera in Home Assistant via [FFmpeg](https://www.ffmpeg.org/). This video source must support multiple simultaneous reads, because for every concurrent Home Assistant user, a connection will be made to the source every 10 seconds. Normally this should not be a problem.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_category:
|
||||
ha_release: 0.33
|
||||
---
|
||||
|
||||
This is a presence detection scanner for [Cisco](http://www.cisco.com) IOS devices.
|
||||
This is a presence detection scanner for [Cisco](https://www.cisco.com/) IOS devices.
|
||||
|
||||
<div class='note warning'>
|
||||
This device tracker needs SSH to be enabled on the router.
|
||||
|
||||
@ -42,8 +42,8 @@ For more information, visit the [serial api] of MySensors.
|
||||
|
||||
```cpp
|
||||
/*
|
||||
* Documentation: http://www.mysensors.org
|
||||
* Support Forum: http://forum.mysensors.org
|
||||
* Documentation: https://www.mysensors.org
|
||||
* Support Forum: https://forum.mysensors.org
|
||||
*/
|
||||
|
||||
#define MY_RADIO_NRF24
|
||||
@ -187,8 +187,8 @@ void sendHeatpumpCommand() {
|
||||
|
||||
```cpp
|
||||
/*
|
||||
* Documentation: http://www.mysensors.org
|
||||
* Support Forum: http://forum.mysensors.org
|
||||
* Documentation: https://www.mysensors.org
|
||||
* Support Forum: https://forum.mysensors.org
|
||||
*/
|
||||
|
||||
#include <MySensor.h>
|
||||
@ -257,4 +257,4 @@ void incomingMessage(const MyMessage &message) {
|
||||
```
|
||||
|
||||
[main component]: /integrations/mysensors/
|
||||
[serial api]: http://www.mysensors.org/download
|
||||
[serial api]: https://www.mysensors.org/download
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.87
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `co2signal` sensor platform queries the [CO2Signal](https://www.co2signal.com/) API for the CO2 intensity of a specific region. Data can be collected via latitude/longitude or by country code. This API uses the same data as https://www.electricitymap.org/. Not all countries/regions in the world are supported so please consult this website to check local availability.
|
||||
The `co2signal` sensor platform queries the [CO2Signal](https://www.co2signal.com/) API for the CO2 intensity of a specific region. Data can be collected via latitude/longitude or by country code. This API uses the same data as <https://www.electricitymap.org> Not all countries/regions in the world are supported so please consult this website to check local availability.
|
||||
|
||||
This platform requires a CO2Signal API key, which can be obtained [here](https://www.co2signal.com/). Note that this API key is for personal use only and other options exist when the data is used commercially.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
|
||||
The `coinmarketcap` sensor platform displays various details about a cryptocurrency provided by [CoinMarketCap](http://coinmarketcap.com/).
|
||||
The `coinmarketcap` sensor platform displays various details about a cryptocurrency provided by [CoinMarketCap](https://coinmarketcap.com/).
|
||||
|
||||
To add the CoinMarketCap sensor to your installation, add the following lines to your `configuration.yaml`:
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.48
|
||||
---
|
||||
|
||||
The `comfoconnect` integration lets you control Zehnder ComfoAir [Q350](https://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q350-tr)/[Q450](https://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q450-tr)/[Q600](https://www.international.zehnder-systems.com/products-and-systems/comfosystems/zehnder-comfoair-q600-st)
|
||||
ventilation units from Home Assistant. You need a [ComfoConnect LAN C](http://www.zehnder.co.uk/products-and-systems/comfortable-indoor-ventilation/ms-comfoair-q/ideal-control#node-21233)
|
||||
ventilation units from Home Assistant. You need a [ComfoConnect LAN C](https://www.zehnder.co.uk/products-and-systems/comfortable-indoor-ventilation/ms-comfoair-q/ideal-control#node-21233)
|
||||
bridge to connect the unit to your local network.
|
||||
|
||||
There is an official iPhone and Android app to configure and control your unit. This platform connects with the help of
|
||||
|
||||
@ -88,7 +88,7 @@ binary_sensor:
|
||||
|
||||
### Check RasPlex
|
||||
|
||||
Check if [RasPlex](http://www.rasplex.com/) is `online`.
|
||||
Check if [RasPlex](https://www.rasplex.com/) is `online`.
|
||||
|
||||
```yaml
|
||||
binary_sensor:
|
||||
|
||||
@ -33,8 +33,8 @@ For more information, visit the [serial api] of MySensors.
|
||||
|
||||
```cpp
|
||||
/*
|
||||
* Documentation: http://www.mysensors.org
|
||||
* Support Forum: http://forum.mysensors.org
|
||||
* Documentation: https://www.mysensors.org
|
||||
* Support Forum: https://forum.mysensors.org
|
||||
*/
|
||||
|
||||
// Enable debug prints to serial monitor
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
|
||||
The `xiaomi aqara` cover platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) covers.
|
||||
The `xiaomi aqara` cover platform allows you to get data from your [Xiaomi](https://www.mi.com/en/) covers.
|
||||
|
||||
The requirement is that you have setup [Xiaomi aqara](/integrations/xiaomi_aqara/).
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: "0.30"
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `darksky` platform uses the [Dark Sky](https://darksky.net/) web service as a source for meteorological data for your location. The location is based on the `longitude` and `latitude` coordinates configured in your `configuration.yaml` file. The coordinates are auto-detected but to take advantage of the hyper-local weather reported by Dark Sky, you can refine them down to your exact home address. GPS coordinates can be found by using [Google Maps](https://www.google.com/maps) and clicking on your home or [Openstreetmap](http://www.openstreetmap.org/).
|
||||
The `darksky` platform uses the [Dark Sky](https://darksky.net/) web service as a source for meteorological data for your location. The location is based on the `longitude` and `latitude` coordinates configured in your `configuration.yaml` file. The coordinates are auto-detected but to take advantage of the hyper-local weather reported by Dark Sky, you can refine them down to your exact home address. GPS coordinates can be found by using [Google Maps](https://www.google.com/maps) and clicking on your home or [Openstreetmap](https://www.openstreetmap.org/).
|
||||
|
||||
## Setup
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_category:
|
||||
ha_release: 0.45
|
||||
---
|
||||
|
||||
The `datadog` integration sends all state changes to [Datadog](https://www.datadoghq.com/) using a [Datadog Agent](http://docs.datadoghq.com/guides/basic_agent_usage/).
|
||||
The `datadog` integration sends all state changes to [Datadog](https://www.datadoghq.com/) using a [Datadog Agent](https://docs.datadoghq.com/guides/basic_agent_usage/).
|
||||
|
||||
Datadog allows you to analyze, monitor, cross-reference and alert upon your data. You can use it to detect statistical anomalies, see graphs across multiple sources in real-time, send critical alerts to Slack, etc.
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ ha_config_flow: true
|
||||
|
||||
[deCONZ](https://www.dresden-elektronik.de/funktechnik/products/software/pc/deconz/) by [Dresden Elektronik](https://www.dresden-elektronik.de) is a software that communicates with Conbee/Raspbee Zigbee gateways and exposes Zigbee devices that are connected to the gateway.
|
||||
|
||||
[deCONZ REST API](http://dresden-elektronik.github.io/deconz-rest-doc/).
|
||||
[deCONZ REST API](https://dresden-elektronik.github.io/deconz-rest-doc/).
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -69,7 +69,7 @@ Available services: `configure` and `deconz.device_refresh`.
|
||||
|
||||
### Service `deconz.configure`
|
||||
|
||||
Set attribute of device in deCONZ using [Rest API](http://dresden-elektronik.github.io/deconz-rest-doc/rest/).
|
||||
Set attribute of device in deCONZ using [Rest API](https://dresden-elektronik.github.io/deconz-rest-doc/rest/).
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|-----------|----------|-------------|
|
||||
|
||||
@ -8,7 +8,7 @@ logo: leviton.png
|
||||
ha_release: 0.51
|
||||
---
|
||||
|
||||
Support for [Leviton Decora Wi-Fi](http://www.leviton.com/en/products/lighting-controls/decora-smart-with-wifi) dimmers/switches via the MyLeviton API.
|
||||
Support for [Leviton Decora Wi-Fi](https://www.leviton.com/en/products/lighting-controls/decora-smart-with-wifi) dimmers/switches via the MyLeviton API.
|
||||
|
||||
Supported devices (tested):
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
## Sensor
|
||||
|
||||
The `deluge` platform allows you to monitor your downloads with [Deluge](http://deluge-torrent.org/) from within Home Assistant and setup automation based on the information.
|
||||
The `deluge` platform allows you to monitor your downloads with [Deluge](https://deluge-torrent.org/) from within Home Assistant and setup automation based on the information.
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
@ -72,7 +72,7 @@ monitored_variables:
|
||||
|
||||
## Switch
|
||||
|
||||
The `deluge` switch platform allows you to control your [Deluge](http://deluge-torrent.org/) client from within Home Assistant. The platform enables you switch all your torrents in pause, and then unpause them all.
|
||||
The `deluge` switch platform allows you to control your [Deluge](https://deluge-torrent.org/) client from within Home Assistant. The platform enables you switch all your torrents in pause, and then unpause them all.
|
||||
|
||||
To add Deluge to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_iot_class: Local Polling
|
||||
ha_release: 0.7.2
|
||||
---
|
||||
|
||||
The `denon` platform allows you to control a [Denon Network Receivers](http://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. It might be that your device is supported by the [Denon AVR] platform.
|
||||
The `denon` platform allows you to control a [Denon Network Receivers](https://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. It might be that your device is supported by the [Denon AVR] platform.
|
||||
|
||||
Supported devices:
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_iot_class: Local Polling
|
||||
ha_release: 0.7.2
|
||||
---
|
||||
|
||||
The `denonavr` platform allows you to control a [Denon Network Receivers](http://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. It might be that your device is supported by the [Denon] platform.
|
||||
The `denonavr` platform allows you to control a [Denon Network Receivers](https://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. It might be that your device is supported by the [Denon] platform.
|
||||
|
||||
Supported devices:
|
||||
|
||||
|
||||
@ -53,4 +53,4 @@ sensor:
|
||||
friendly_name: 'Next departure'
|
||||
```
|
||||
|
||||
The data is coming from the [bahn.de](http://www.bahn.de/p/view/index.shtml) website.
|
||||
The data is coming from the [bahn.de](https://www.bahn.de/p/view/index.shtml) website.
|
||||
|
||||
@ -25,10 +25,10 @@ For more information, visit the [serial api] of MySensors.
|
||||
|
||||
```cpp
|
||||
/**
|
||||
* Documentation: http://www.mysensors.org
|
||||
* Support Forum: http://forum.mysensors.org
|
||||
* Documentation: https://www.mysensors.org
|
||||
* Support Forum: https://forum.mysensors.org
|
||||
*
|
||||
* http://www.mysensors.org/build/gps
|
||||
* https://www.mysensors.org/build/gps
|
||||
*/
|
||||
|
||||
// Enable debug prints to serial monitor
|
||||
@ -97,4 +97,4 @@ void loop()
|
||||
```
|
||||
|
||||
[main component]: /integrations/mysensors/
|
||||
[serial api]: http://www.mysensors.org/download
|
||||
[serial api]: https://www.mysensors.org/download
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.35
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `digitalloggers` switch platform allows you to control the state of your [Digital Loggers](http://www.digital-loggers.com/dinfaqs.html) switches.
|
||||
The `digitalloggers` switch platform allows you to control the state of your [Digital Loggers](https://www.digital-loggers.com/dinfaqs.html) switches.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.25
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
Master [DirecTV](http://www.directv.com/) receivers (ie: those that have tuners) will be automatically discovered if you enable the [discovery integration](/integrations/discovery/) and the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery.
|
||||
Master [DirecTV](https://www.directv.com/) receivers (ie: those that have tuners) will be automatically discovered if you enable the [discovery integration](/integrations/discovery/) and the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery.
|
||||
|
||||
To ensure that your DirecTV boxes are always found and configured, they should be added into your `configuration.yaml`.
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_iot_class: Local Polling
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
The `dlink` switch platform allows you to control the state of your [D-Link Wi-Fi Smart Plugs](http://us.dlink.com/product-category/home-solutions/connected-home/smart-plugs/).
|
||||
The `dlink` switch platform allows you to control the state of your [D-Link Wi-Fi Smart Plugs](https://us.dlink.com/en/consumer/smart-plugs).
|
||||
|
||||
Supported devices (tested):
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ha_release: 0.87
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `dovado` integration manages communication with the [Dovado](http://www.dovado.com/) router.
|
||||
The `dovado` integration manages communication with the [Dovado](https://www.dovado.com/) router.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -49,7 +49,7 @@ port:
|
||||
|
||||
## Notifications
|
||||
|
||||
The `dovado` notify platform allows you to send SMS from your [Dovado](http://www.dovado.com/) router, if it supports it.
|
||||
The `dovado` notify platform allows you to send SMS from your [Dovado](https://www.dovado.com/) router, if it supports it.
|
||||
|
||||
To add the Dovado notify platform to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -79,7 +79,7 @@ automation:
|
||||
|
||||
## Sensor
|
||||
|
||||
The `dovado` sensor platform let you monitor your [Dovado](http://www.dovado.com/) router.
|
||||
The `dovado` sensor platform let you monitor your [Dovado](https://www.dovado.com/) router.
|
||||
|
||||
To add a Dovado sensor to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.34
|
||||
---
|
||||
|
||||
|
||||
The `dunehd` media player platform allows you to control a [Dune HD media player](http://dune-hd.com/eng/products/full_hd_media_players) from Home Assistant. Support is based on the official [IP protocol](http://dune-hd.com/support/ip_control/dune_ip_control_overview.txt) published by Dune.
|
||||
The `dunehd` media player platform allows you to control a [Dune HD media player](https://dune-hd.com/eng/products/full_hd_media_players) from Home Assistant. Support is based on the official [IP protocol](https://dune-hd.com/support/ip_control/dune_ip_control_overview.txt) published by Dune.
|
||||
|
||||
Devices with firmware 110127_2105_beta or above are supported. Some functions may depend on the version of the protocol (volume / mute control is only available with version 2 onwards).
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.19
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `dweet` integration makes it possible to transfer details collected with Home Assistant to [Dweet.io](http://dweet.io/) and visualize them with [freeboard.io](https://freeboard.io). Keep in mind that your information will be public!
|
||||
The `dweet` integration makes it possible to transfer details collected with Home Assistant to [Dweet.io](https://dweet.io/) and visualize them with [freeboard.io](https://freeboard.io). Keep in mind that your information will be public!
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/screenshots/dweet-freeboard.png' />
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.61
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `econet` water heater platform is consuming the information provided by a [EcoNet enabled Rheem water heater](http://www.rheem.com/EcoNet/Home). This platform allows you to set the temperature, the operation mode, and enable vacation mode.
|
||||
The `econet` water heater platform is consuming the information provided by a [EcoNet enabled Rheem water heater](https://www.rheem.com/EcoNet/Home). This platform allows you to set the temperature, the operation mode, and enable vacation mode.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `eddystone_temperature` sensor platform reads temperature information from Bluetooth LE advertisements transmitted by [Eddystone](https://en.wikipedia.org/wiki/Eddystone_(Google)) beacons. Your beacons must be configured to transmit UID frames (for identification) and TLM frames (for temperature).
|
||||
All beacons that support the Eddystone protocol, have a temperature sensor and can transmit TLM frames are compatible with this platform. For example [Gimbal](https://store.gimbal.com/collections/beacons/), [Estimote](http://estimote.com/) or [kontakt.io](https://kontakt.io/). For more manufacturers see [this overview](https://developers.google.com/beacons/eddystone#beacon_manufacturers) by Google.
|
||||
All beacons that support the Eddystone protocol, have a temperature sensor and can transmit TLM frames are compatible with this platform. For example [Gimbal](https://store.gimbal.com/collections/beacons/), [Estimote](https://estimote.com/) or [kontakt.io](https://kontakt.io/). For more manufacturers see [this overview](https://developers.google.com/beacons/eddystone#beacon_manufacturers) by Google.
|
||||
|
||||
## Requirements
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: "0.10"
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
Integrate your [ELIQ Online](http://eliq.io) smart meter information into Home Assistant. To get an [access token](https://my.eliq.io/user/settings/api) and the [Channel ID](https://my.eliq.io/user/settings/locations), log in to your account.
|
||||
Integrate your [ELIQ Online](https://eliq.io/) smart meter information into Home Assistant. To get an [access token](https://my.eliq.io/user/settings/api) and the [Channel ID](https://my.eliq.io/user/settings/locations), log in to your account.
|
||||
|
||||
To enable this sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
|
||||
The `emby` platform allows you to control a [Emby](http://emby.media/) multimedia system from Home Assistant.
|
||||
The `emby` platform allows you to control a [Emby](https://emby.media/) multimedia system from Home Assistant.
|
||||
|
||||
To add Emby to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -63,7 +63,7 @@ This can typically be one of those batteryless wall switches.
|
||||
Tested with:
|
||||
|
||||
- Eltako FT55 which uses the EnOcean PTM 215 module
|
||||
- [TRIO2SYS Wall switches](http://www.trio2sys.fr/index.php/fr/produits-enocean-sans-fil-sans-pile-interoperable/emetteur-sans-fils-sans-pile-interoperable-enocean) which uses the EnOcean PTM210 DB module
|
||||
- [TRIO2SYS Wall switches](https://www.trio2sys.fr/index.php/fr/produits-enocean-sans-fil-sans-pile-interoperable/emetteur-sans-fils-sans-pile-interoperable-enocean) which uses the EnOcean PTM210 DB module
|
||||
- Omnio WS-CH-102
|
||||
|
||||
The following [EnOcean Equipment Profiles](https://www.enocean-alliance.org/what-is-enocean/specifications/) are supported:
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
|
||||
The `ephember` climate platform lets you control [EPH Controls](http://emberapp.ephcontrols.com/) thermostats. The module only works if you have a WiFi gateway to control your EPH system and an account on the EMBER app.
|
||||
The `ephember` climate platform lets you control [EPH Controls](https://emberapp.ephcontrols.com/) thermostats. The module only works if you have a WiFi gateway to control your EPH system and an account on the EMBER app.
|
||||
|
||||
To set it up, add the following information to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ The `ffmpeg` integration allows other Home Assistant integrations to process vid
|
||||
|
||||
<div class='note'>
|
||||
|
||||
You need the `ffmpeg` binary in your system path. On Hassbian you will need to login as the `pi` user and `sudo apt install ffmpeg`. On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are available on the [FFmpeg](http://www.ffmpeg.org/) website.
|
||||
You need the `ffmpeg` binary in your system path. On Hassbian you will need to login as the `pi` user and `sudo apt install ffmpeg`. On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are available on the [FFmpeg](https://www.ffmpeg.org/) website.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_category:
|
||||
ha_release: 0.27
|
||||
---
|
||||
|
||||
The `ffmpeg` platform allows you to use any video feed with [FFmpeg](http://www.ffmpeg.org/) for motion sensors in Home Assistant.
|
||||
The `ffmpeg` platform allows you to use any video feed with [FFmpeg](https://www.ffmpeg.org/) for motion sensors in Home Assistant.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_category:
|
||||
ha_release: 0.27
|
||||
---
|
||||
|
||||
The `ffmpeg` platform allows you to use any video or audio feed with [FFmpeg](http://www.ffmpeg.org/) for various sensors in Home Assistant.
|
||||
The `ffmpeg` platform allows you to use any video or audio feed with [FFmpeg](https://www.ffmpeg.org/) for various sensors in Home Assistant.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ ha_release: 0.83
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
The [Fibaro](http://fibaro.com) hub is a controller mainly connecting to Z-Wave devices.
|
||||
The [Fibaro](https://fibaro.com/) hub is a controller mainly connecting to Z-Wave devices.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_iot_class: Cloud Polling
|
||||
ha_release: 0.19
|
||||
---
|
||||
|
||||
The Fitbit sensor allows you to expose data from [Fitbit](http://fitbit.com) to Home Assistant.
|
||||
The Fitbit sensor allows you to expose data from [Fitbit](https://fitbit.com/) to Home Assistant.
|
||||
|
||||
Enable the sensor by adding the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.23
|
||||
---
|
||||
|
||||
|
||||
The `fixer` sensor will show you the current exchange rate from [Fixer.io](http://fixer.io/) which is using data from the [European Central Bank (ECB)](https://www.ecb.europa.eu).
|
||||
The `fixer` sensor will show you the current exchange rate from [Fixer.io](https://fixer.io/) which is using data from the [European Central Bank (ECB)](https://www.ecb.europa.eu).
|
||||
|
||||
To get an overview about the available [currencies](https://fixer.io/symbols).
|
||||
|
||||
@ -31,7 +31,7 @@ sensor:
|
||||
|
||||
{% configuration %}
|
||||
api_key:
|
||||
description: Your API key for [Fixer.io](http://fixer.io/).
|
||||
description: Your API key for [Fixer.io](https://fixer.io/).
|
||||
required: true
|
||||
type: string
|
||||
target:
|
||||
|
||||
@ -12,7 +12,7 @@ The `flux_led` support is integrated into Home Assistant as a light platform. Se
|
||||
|
||||
Example of bulbs:
|
||||
|
||||
- [Flux Smart Lighting](http://www.fluxsmartlighting.com/)
|
||||
- [Flux Smart Lighting](https://www.fluxsmartlighting.com/)
|
||||
- [Flux WiFi Smart LED Light Bulb4](https://amzn.to/2X0dVwu)
|
||||
- [WIFI smart LED light Bulb1](https://amzn.to/2J2fksr)
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ha_release: 0.85
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `freebox` integration allows you to observe and control [Freebox router](http://www.free.fr/).
|
||||
The `freebox` integration allows you to observe and control [Freebox router](https://www.free.fr/).
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -70,7 +70,7 @@ Only the routers with Freebox OS are supported:
|
||||
## Presence Detection
|
||||
|
||||
This platform offers presence detection by keeping track of the
|
||||
devices connected to a [Freebox](http://www.free.fr/) router.
|
||||
devices connected to a [Freebox](https://www.free.fr/) router.
|
||||
|
||||
### Notes
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.27
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `fritzbox_callmonitor` sensor monitors the call monitor exposed by [AVM Fritz!Box](http://avm.de/produkte/fritzbox/) routers on TCP port 1012. It will assume the values `idle`, `ringing`, `dialing` or `talking` with the phone numbers involved contained in the state attributes.
|
||||
The `fritzbox_callmonitor` sensor monitors the call monitor exposed by [AVM Fritz!Box](https://avm.de/produkte/fritzbox/) routers on TCP port 1012. It will assume the values `idle`, `ringing`, `dialing` or `talking` with the phone numbers involved contained in the state attributes.
|
||||
It can also access the internal phone book of the router to look up the names corresponding to the phone numbers and store them in the state attributes.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.36
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `fritzbox_netmonitor` sensor monitors the network statistics exposed by [AVM Fritz!Box](http://avm.de/produkte/fritzbox/) routers.
|
||||
The `fritzbox_netmonitor` sensor monitors the network statistics exposed by [AVM Fritz!Box](https://avm.de/produkte/fritzbox/) routers.
|
||||
|
||||
<div class='note warning'>
|
||||
It might be necessary to install additional packages: <code>sudo apt-get install libxslt-dev libxml2-dev python3-lxml</code>
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Local Polling
|
||||
ha_release: 0.96
|
||||
---
|
||||
|
||||
The `fronius` sensor polls a [Fronius](http://www.fronius.com/) solar inverter, battery system or smart meter and present the values as sensors in Home Assistant.
|
||||
The `fronius` sensor polls a [Fronius](https://www.fronius.com/) solar inverter, battery system or smart meter and present the values as sensors in Home Assistant.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -94,13 +94,13 @@ The Frontier Silicon API does not provide a multi-user environment. There is alw
|
||||
|
||||
</div>
|
||||
|
||||
[Frontier Silicon chipset]: http://www.frontier-silicon.com/digital-radio-solutions
|
||||
[Frontier Silicon chipset]: https://www.frontier-silicon.com/digital-radio-solutions
|
||||
[Medion Radios]: http://internetradio.medion.com/
|
||||
[IR110]: https://www.hama.com/00054823/hama-ir110-internet-radio-internet-radio-multi-room-app-control
|
||||
[DIR3110]: https://www.hama.com/00054824/hama-digitalradio-dir3110-internetradio-dab+-fm-multiroom-app-steuerung
|
||||
[MD 87466]: https://www.medion.com/gb/service/start/_product.php?msn=50051273&gid=14
|
||||
[SIRD 14 C2]: https://www.silvercrest-multiroom.de/fileadmin/user_upload/pdf/handbucher/Bedienungsanleitungen/IR/279398_SIRD_14_C2_ML4_V1.1_GB_CZ_SK_DE.pdf
|
||||
[fsapi]: https://github.com/zhelev/python-fsapi
|
||||
[UNDOK]: http://www.frontier-silicon.com/undok
|
||||
[UNDOK]: https://www.frontier-silicon.com/undok
|
||||
[flammy]: https://github.com/flammy/fsapi/
|
||||
[tiwillam]: https://github.com/tiwilliam/fsapi
|
||||
|
||||
@ -7,9 +7,9 @@ ha_category:
|
||||
ha_release: 0.75
|
||||
---
|
||||
|
||||
The `futurenow` light platform allows you to use [P5](http://www.p5.hu) FutureNow relay/dimmer units as lights. Currently supported units:
|
||||
* [FutureNow FNIP-6x2AD](http://www.p5.hu/index.php/products/ethernet-modules/265-fnip-6x2ad) dimmer unit (outputs only)
|
||||
* [FutureNow FNIP-8x10A](http://www.p5.hu/index.php/products/ethernet-modules/263-fnip-8x10a) relay unit (outputs only)
|
||||
The `futurenow` light platform allows you to use [P5](https://www.p5.hu/) FutureNow relay/dimmer units as lights. Currently supported units:
|
||||
* [FutureNow FNIP-6x2AD](https://www.p5.hu/index.php/products/ethernet-modules/265-fnip-6x2ad) dimmer unit (outputs only)
|
||||
* [FutureNow FNIP-8x10A](https://www.p5.hu/index.php/products/ethernet-modules/263-fnip-8x10a) relay unit (outputs only)
|
||||
|
||||
### Configuration Sample
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
|
||||
The `garadget` cover platform lets you control [Garadget](http://www.garadget.com/) garage door futurizers through Home Assistant.
|
||||
The `garadget` cover platform lets you control [Garadget](https://www.garadget.com/) garage door futurizers through Home Assistant.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -31,7 +31,7 @@ To enable the GeoRSS events sensor, add the following lines to your `configurati
|
||||
sensor:
|
||||
- platform: geo_rss_events
|
||||
name: NSW Fire Service
|
||||
url: http://www.rfs.nsw.gov.au/feeds/majorIncidents.xml
|
||||
url: https://www.rfs.nsw.gov.au/feeds/majorIncidents.xml
|
||||
unit_of_measurement: 'Incidents'
|
||||
categories:
|
||||
- 'Emergency Warning'
|
||||
@ -95,7 +95,7 @@ sensor:
|
||||
url: https://www.emergency.wa.gov.au/data/incident_FCAD.rss
|
||||
- platform: geo_rss_events
|
||||
name: ACT Emergency Services Agency
|
||||
url: http://www.esa.act.gov.au/feeds/currentincidents.xml
|
||||
url: https://www.esa.act.gov.au/feeds/currentincidents.xml
|
||||
```
|
||||
|
||||
|
||||
@ -111,7 +111,7 @@ sensor:
|
||||
- 'Past Day'
|
||||
- platform: geo_rss_events
|
||||
name: BGS Worlwide Earthquakes
|
||||
url: http://www.bgs.ac.uk/feeds/worldSeismology.xml
|
||||
url: https://www.bgs.ac.uk/feeds/worldSeismology.xml
|
||||
categories:
|
||||
- 'EQMH'
|
||||
- platform: geo_rss_events
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.53
|
||||
ha_iot_class: Cloud Push
|
||||
---
|
||||
|
||||
This integration sets up integration with [Geofency](http://www.geofency.com/). Geofency is a paid app for iOS that lets users to configure a request that will be sent when a geofence or iBeacon region is entered or exited. This can be configured with Home Assistant to update your location.
|
||||
This integration sets up integration with [Geofency](https://www.geofency.com/). Geofency is a paid app for iOS that lets users to configure a request that will be sent when a geofence or iBeacon region is entered or exited. This can be configured with Home Assistant to update your location.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ The data is updated every 5 minutes.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
The material used by this integration is provided under the [Creative Commons Attribution 3.0 New Zealand (CC BY 3.0 NZ) license](http://creativecommons.org/licenses/by/3.0/nz/).
|
||||
The material used by this integration is provided under the [Creative Commons Attribution 3.0 New Zealand (CC BY 3.0 NZ) license](https://creativecommons.org/licenses/by/3.0/nz/).
|
||||
It has only been modified for the purpose of presenting the material in Home Assistant.
|
||||
Please refer to the [creator's disclaimer notice](https://www.geonet.org.nz/disclaimer) and [data policy](https://www.geonet.org.nz/policy) for more information.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: "0.20"
|
||||
---
|
||||
|
||||
|
||||
The `gpmdp` media player platform allows you to control a [GPMDP](http://www.googleplaymusicdesktopplayer.com/) instance running on a computer from Home Assistant.
|
||||
The `gpmdp` media player platform allows you to control a [GPMDP](https://www.googleplaymusicdesktopplayer.com/) instance running on a computer from Home Assistant.
|
||||
|
||||
You will have first have to check "Enable playback API" in GPMDP's settings and then add an inbound rule to the firewall to allow access to port 5672 on the computer running GPMDP.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.82
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
The [GreenEye Monitor (GEM)](http://www.brultech.com/greeneye/) integration for Home Assistant allows you to create sensors for the various data channels of the GEM. Each current transformer (CT) channel, pulse counter, and temperature sensor appears in Home Assistant as a sensor, and can be used in automations.
|
||||
The [GreenEye Monitor (GEM)](https://www.brultech.com/greeneye/) integration for Home Assistant allows you to create sensors for the various data channels of the GEM. Each current transformer (CT) channel, pulse counter, and temperature sensor appears in Home Assistant as a sensor, and can be used in automations.
|
||||
|
||||
Configure your GEM(s) to produce binary-format packets (for example, "Bin32 NET" for a 32-channel GEM with some channels configured for net metering) and send them to an unused port on your Home Assistant machine. (These settings are in the "Packet Send" and "Network" pages of the GEM UI.) Then specify that port and information about your monitor(s) and the data channels you wish to monitor in your `configuration.yaml`:
|
||||
|
||||
|
||||
@ -10,11 +10,11 @@ ha_release: 0.17
|
||||
|
||||
The `gtfs` sensor will give you the next departure time and associated data from your public transit station/stop. The data comes from your chosen public transit authority and is formatted as [General Transit Feed Specification](https://developers.google.com/transit/gtfs/) data, commonly known as GTFS.
|
||||
|
||||
You need to find a valid GTFS data set, which you can usually find just by searching the internet. Most public transit authorities have GTFS available somewhere, as Google requires public transit authorities to provide the data if they wish to appear on Google Maps. You may also be able to find data at [TransitFeeds](http://transitfeeds.com/feeds).
|
||||
You need to find a valid GTFS data set, which you can usually find just by searching the internet. Most public transit authorities have GTFS available somewhere, as Google requires public transit authorities to provide the data if they wish to appear on Google Maps. You may also be able to find data at [TransitFeeds](https://transitfeeds.com/feeds).
|
||||
|
||||
Here are some examples:
|
||||
|
||||
- [Bay Area Rapid Transit (BART)](http://www.bart.gov/schedules/developers/gtfs) - The light rail system for the San Francisco Bay Area.
|
||||
- [Bay Area Rapid Transit (BART)](https://www.bart.gov/schedules/developers/gtfs) - The light rail system for the San Francisco Bay Area.
|
||||
- [Metropolitan Transit Authority of New York City (MTA)](http://web.mta.info/developers/) - Provides separate data feeds for subway, bus, LIRR and Metro-North of the greater New York City metropolitan region.
|
||||
- [Official Timetable Switzerland](https://opentransportdata.swiss/en/dataset/timetable-2019-gtfs) - The official timetable data for Switzerland in 2019.
|
||||
|
||||
|
||||
@ -234,7 +234,7 @@ The hangouts integration can't detect if your IP address changes, so it can't au
|
||||
```yaml
|
||||
sensor:
|
||||
- platform: rest
|
||||
resource: https://api.ipify.org?format=json
|
||||
resource: https://api.ipify.org/?format=json
|
||||
name: External IP
|
||||
value_template: '{{ value_json.ip }}'
|
||||
scan_interval: 10
|
||||
@ -257,7 +257,7 @@ automation:
|
||||
|
||||
## Notifications
|
||||
|
||||
The `hangouts` platform allows you to deliver notifications from Home Assistant to [Google Hangouts](http://hangouts.google.com) conversations. Conversations can be both direct as well as group chats.
|
||||
The `hangouts` platform allows you to deliver notifications from Home Assistant to [Google Hangouts](https://hangouts.google.com/) conversations. Conversations can be both direct as well as group chats.
|
||||
|
||||
To enable Hangouts notifications in your installation, you first need to configure the Hangouts component. Then, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_iot_class: Local Push
|
||||
ha_release: 0.34
|
||||
---
|
||||
|
||||
The `harmony` remote platform allows you to control the state of your [Harmony Hub Device](http://www.logitech.com/en-us/product/harmony-hub).
|
||||
The `harmony` remote platform allows you to control the state of your [Harmony Hub Device](https://www.logitech.com/en-us/product/harmony-hub).
|
||||
|
||||
Supported units:
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_release: 0.32
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `hddtemp` sensor platform is using the data provided by [HDDTemp](http://savannah.nongnu.org/projects/hddtemp).
|
||||
The `hddtemp` sensor platform is using the data provided by [HDDTemp](https://savannah.nongnu.org/projects/hddtemp).
|
||||
|
||||
It required that `hddtemp` is started or running in daemon mode on a local or remote system.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
The Hikvision Binary Sensor is a platform that parses the event stream of a
|
||||
[Hikvision IP Camera or NVR](http://www.hikvision.com/) and presents the
|
||||
[Hikvision IP Camera or NVR](https://www.hikvision.com/) and presents the
|
||||
camera/nvr events to Home Assistant as binary sensors with either an "off" or
|
||||
"on" state.
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_category:
|
||||
ha_release: pre 0.7
|
||||
---
|
||||
|
||||
This `hikvisioncam` switch platform allows you to control your motion detection setting on your [Hikvision](http://www.hikvision.com/) camera.
|
||||
This `hikvisioncam` switch platform allows you to control your motion detection setting on your [Hikvision](https://www.hikvision.com/) camera.
|
||||
|
||||
<div class='note warning'>
|
||||
Currently works using default https port only.
|
||||
|
||||
@ -16,8 +16,8 @@ ha_iot_class: Local Push
|
||||
ha_release: 0.23
|
||||
---
|
||||
|
||||
The [Homematic](http://www.homematic.com/) integration provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit.
|
||||
If you are using Homegear with paired [Intertechno](http://intertechno.at/) devices, uni-directional communication is possible as well.
|
||||
The [Homematic](https://www.homematic.com/) integration provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit.
|
||||
If you are using Homegear with paired [Intertechno](https://intertechno.at/) devices, uni-directional communication is possible as well.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ ha_iot_class: Cloud Push
|
||||
ha_release: 0.66
|
||||
---
|
||||
|
||||
The [HomematicIP](http://www.homematic-ip.com) integration platform is used as an interface to the cloud server. Since there is no official documentation about this API, everything was done via reverse engineering. The [homematicip-rest-api](https://github.com/coreGreenberet/homematicip-rest-api) is used for communicating. Use at your own risk.
|
||||
The [HomematicIP](https://www.homematic-ip.com/) integration platform is used as an interface to the cloud server. Since there is no official documentation about this API, everything was done via reverse engineering. The [homematicip-rest-api](https://github.com/coreGreenberet/homematicip-rest-api) is used for communicating. Use at your own risk.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ The `hp_ilo` platform allows you to do an API call to the HP ILO (Integrated Lig
|
||||
|
||||
If the ILO or specified jsonpath query returns only a single value (e.g., a temperature or state), it will be put in the state field. If a data structure is returned, it will be placed in the `ilo_data` attribute.
|
||||
|
||||
Some more details about what can be retrieved from these sensors is available in the [python-hpilo documentation](http://seveas.github.io/python-hpilo/).
|
||||
Some more details about what can be retrieved from these sensors is available in the [python-hpilo documentation](https://seveas.github.io/python-hpilo/).
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/screenshots/hp_ilo.png' />
|
||||
|
||||
@ -7,7 +7,7 @@ ha_category:
|
||||
ha_release: 0.15
|
||||
---
|
||||
|
||||
Implements the [Hunter Douglas PowerView](http://www.hunterdouglas.com/operating-systems/powerview-motorization/support) platform scene control. It queries the PowerView Hub and Home Assistant displays them as scenes.
|
||||
Implements the [Hunter Douglas PowerView](https://www.hunterdouglas.com/operating-systems/powerview-motorization/support) platform scene control. It queries the PowerView Hub and Home Assistant displays them as scenes.
|
||||
|
||||
Scenes can be activated using the service `scene.turn_on`.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.92
|
||||
---
|
||||
|
||||
The `ign_sismologia` platform lets you integrate a GeoRSS feed provided by the
|
||||
Spanish [Instituto Geográfico Nacional](http://www.ign.es/) with information
|
||||
Spanish [Instituto Geográfico Nacional](https://www.ign.es/) with information
|
||||
about seismic events like earthquakes on the Iberian Peninsula and Canary
|
||||
Islands. It retrieves incidents from a feed and shows information of those
|
||||
incidents filtered by distance to Home Assistant's location.
|
||||
|
||||
@ -56,7 +56,7 @@ input_select:
|
||||
|
||||
<div class='note'>
|
||||
|
||||
Because YAML defines [booleans](http://yaml.org/type/bool.html) as equivalent, any variations of 'On', 'Yes', 'Y', 'Off', 'No', or 'N' (regardless of case) used as option names will be replaced by True and False unless they are defined in quotation marks.
|
||||
Because YAML defines [booleans](https://yaml.org/type/bool.html) as equivalent, any variations of 'On', 'Yes', 'Y', 'Off', 'No', or 'N' (regardless of case) used as option names will be replaced by True and False unless they are defined in quotation marks.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -191,7 +191,7 @@ In order for any two Insteon devices to talk with one another, they must be link
|
||||
|
||||
If you are looking for more advanced options, you can use the [insteonplm_interactive] command line tool that is distributed with the [insteonplm] Python module. Please see the documentation on the [insteonplm] GitHub site. Alternatively, you can download [HouseLinc] which runs on any Windows PC, or you can use [Insteon Terminal] which is open source and runs on most platforms. SmartHome no longer supports HouseLinc, but it still works. Insteon Terminal is a very useful tool but please read the disclaimers carefully, they are important.
|
||||
|
||||
[understanding linking]: http://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking
|
||||
[understanding linking]: https://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking
|
||||
[Development Tools]: /docs/tools/dev-tools/
|
||||
[HouseLinc]: https://www.smarthome.com/houselinc.html
|
||||
[Insteon Terminal]: https://github.com/pfrommerd/insteon-terminal
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.62
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
[IOTA](http://iota.org/) is a new blockless distributed ledger which is scalable, lightweight and makes it possible to transfer value without any fees.
|
||||
[IOTA](https://iota.org/) is a new blockless distributed ledger which is scalable, lightweight and makes it possible to transfer value without any fees.
|
||||
|
||||
The `iota` integration displays various details (e.g., the balance, node attributes) of IOTA wallets.
|
||||
|
||||
|
||||
@ -9,13 +9,13 @@ ha_release: 0.71
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `iperf3` sensor integration allows you to measure network bandwidth performance against a private or public [Iperf3](http://software.es.net/iperf/index.html) server.
|
||||
The `iperf3` sensor integration allows you to measure network bandwidth performance against a private or public [Iperf3](https://software.es.net/iperf/index.html) server.
|
||||
|
||||
Enabling this integration will automatically create the Iperf3 sensors for the monitored conditions (below). By default, it will run every hour. The user can change the update frequency in the config by defining the `scan_interval` for a Iperf3 test to run.
|
||||
|
||||
## Setup
|
||||
|
||||
This integration requires the `iperf3` command to be installed on your OS. Please, refer to the [official Iperf3 documentation](http://software.es.net/iperf/obtaining.html) for installation instructions.
|
||||
This integration requires the `iperf3` command to be installed on your OS. Please, refer to the [official Iperf3 documentation](https://software.es.net/iperf/obtaining.html) for installation instructions.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.72
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `ipma` weather platform uses the [Instituto Português do Mar e Atmosfera](http://www.ipma.pt) as a source for current and forecast meteorological data.
|
||||
The `ipma` weather platform uses the [Instituto Português do Mar e Atmosfera](https://www.ipma.pt/) as a source for current and forecast meteorological data.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -79,4 +79,4 @@ Note: Global Cache devices expect data in their own format of "sendir...". This
|
||||
API Docs:
|
||||
|
||||
- [iTach](https://www.globalcache.com/files/docs/API-iTach.pdf)
|
||||
- [GC-100](http://www.globalcache.com/files/docs/API-GC-100.pdf)
|
||||
- [GC-100](https://www.globalcache.com/files/docs/API-GC-100.pdf)
|
||||
|
||||
@ -9,7 +9,7 @@ ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
|
||||
The `itunes` media player platform allows you to control [iTunes](http://apple.com/itunes/) from Home Assistant. It uses a 3rd party server that you run on your Mac called [itunes-api](https://github.com/maddox/itunes-api). Play, pause or skip songs remotely on iTunes running on your Mac.
|
||||
The `itunes` media player platform allows you to control [iTunes](https://apple.com/itunes/) from Home Assistant. It uses a 3rd party server that you run on your Mac called [itunes-api](https://github.com/maddox/itunes-api). Play, pause or skip songs remotely on iTunes running on your Mac.
|
||||
|
||||
In addition to controlling iTunes, your available AirPlay endpoints will be added as media players as well. You can then individually address them and turn them on, turn them off or adjust their volume.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.24
|
||||
---
|
||||
|
||||
The `joaoapps_join` integration exposes services from
|
||||
[Join](http://joaoapps.com/join). In Home Assistant, the Join features are
|
||||
[Join](https://joaoapps.com/join). In Home Assistant, the Join features are
|
||||
divided up in two locations, the Join component, and the Join notify platform.
|
||||
The notify platform allows us to send messages to Join devices, the component
|
||||
allows us to access the other special features that Join offers. When in doubt, you can reference the [API documentation](https://joaoapps.com/join/api/) this is based on.
|
||||
@ -53,7 +53,7 @@ device_names:
|
||||
required: false
|
||||
type: string
|
||||
name:
|
||||
description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.<name>`. The name will defailt to `notify` if not supplied. See the [Notifications Component](http://www.home-assistant.io/integrations/notify) for more details.
|
||||
description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.<name>`. The name will defailt to `notify` if not supplied. See the [Notifications Component](/integrations/notify) for more details.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -32,6 +32,6 @@ pip3 install [package name]
|
||||
|
||||
### Windows
|
||||
|
||||
x64 Windows users may have trouble installing pywin through pip. Using an [executable installer](http://sourceforge.net/projects/pywin32/files/pywin32/) should work around this issue.
|
||||
x64 Windows users may have trouble installing pywin through pip. Using an [executable installer](https://sourceforge.net/projects/pywin32/files/pywin32/) should work around this issue.
|
||||
|
||||
[Similar installers](http://www.lfd.uci.edu/~gohlke/pythonlibs/#pyhook) (unofficial) for pyhook have been ported to python 3.4 and should help with x64 pip issues with pyhook.
|
||||
[Similar installers](https://www.lfd.uci.edu/~gohlke/pythonlibs/#pyhook) (unofficial) for pyhook have been ported to python 3.4 and should help with x64 pip issues with pyhook.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user