diff --git a/source/_integrations/acer_projector.markdown b/source/_integrations/acer_projector.markdown index d711e9242dc..ea66c086330 100644 --- a/source/_integrations/acer_projector.markdown +++ b/source/_integrations/acer_projector.markdown @@ -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 diff --git a/source/_integrations/actiontec.markdown b/source/_integrations/actiontec.markdown index ada052fc1dc..2ec05057621 100644 --- a/source/_integrations/actiontec.markdown +++ b/source/_integrations/actiontec.markdown @@ -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): diff --git a/source/_integrations/ads.markdown b/source/_integrations/ads.markdown index 249dd932cd6..61742c7b38e 100644 --- a/source/_integrations/ads.markdown +++ b/source/_integrations/ads.markdown @@ -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: diff --git a/source/_integrations/airvisual.markdown b/source/_integrations/airvisual.markdown index 0f56195ebf8..c95b3562d5e 100644 --- a/source/_integrations/airvisual.markdown +++ b/source/_integrations/airvisual.markdown @@ -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). diff --git a/source/_integrations/alexa.flash_briefings.markdown b/source/_integrations/alexa.flash_briefings.markdown index eb4bacd926b..e8fd786621f 100644 --- a/source/_integrations/alexa.flash_briefings.markdown +++ b/source/_integrations/alexa.flash_briefings.markdown @@ -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/ diff --git a/source/_integrations/amazon_polly.markdown b/source/_integrations/amazon_polly.markdown index 6307a57c604..7a63388dfba 100644 --- a/source/_integrations/amazon_polly.markdown +++ b/source/_integrations/amazon_polly.markdown @@ -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 diff --git a/source/_integrations/ambiclimate.markdown b/source/_integrations/ambiclimate.markdown index 7960e646ce1..a5e64074fd3 100644 --- a/source/_integrations/ambiclimate.markdown +++ b/source/_integrations/ambiclimate.markdown @@ -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`. diff --git a/source/_integrations/anel_pwrctrl.markdown b/source/_integrations/anel_pwrctrl.markdown index 193edd1b187..e146f69fb6e 100644 --- a/source/_integrations/anel_pwrctrl.markdown +++ b/source/_integrations/anel_pwrctrl.markdown @@ -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): diff --git a/source/_integrations/anthemav.markdown b/source/_integrations/anthemav.markdown index 08bcbe64910..7994f1334f4 100644 --- a/source/_integrations/anthemav.markdown +++ b/source/_integrations/anthemav.markdown @@ -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 diff --git a/source/_integrations/apcupsd.markdown b/source/_integrations/apcupsd.markdown index ffacda23099..93649d924b7 100644 --- a/source/_integrations/apcupsd.markdown +++ b/source/_integrations/apcupsd.markdown @@ -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 diff --git a/source/_integrations/apple_tv.markdown b/source/_integrations/apple_tv.markdown index f17e597a314..eeec08c3d4a 100644 --- a/source/_integrations/apple_tv.markdown +++ b/source/_integrations/apple_tv.markdown @@ -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 diff --git a/source/_integrations/arest.markdown b/source/_integrations/arest.markdown index 4cfe510e6cf..88ee5984748 100644 --- a/source/_integrations/arest.markdown +++ b/source/_integrations/arest.markdown @@ -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: diff --git a/source/_integrations/aruba.markdown b/source/_integrations/aruba.markdown index 5a5a9de25e3..723ae4765a7 100644 --- a/source/_integrations/aruba.markdown +++ b/source/_integrations/aruba.markdown @@ -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): diff --git a/source/_integrations/arwn.markdown b/source/_integrations/arwn.markdown index d1c4da78690..b1eb557a99f 100644 --- a/source/_integrations/arwn.markdown +++ b/source/_integrations/arwn.markdown @@ -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: diff --git a/source/_integrations/asuswrt.markdown b/source/_integrations/asuswrt.markdown index 7c573c94243..82aa97b7ef1 100644 --- a/source/_integrations/asuswrt.markdown +++ b/source/_integrations/asuswrt.markdown @@ -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: diff --git a/source/_integrations/atome.markdown b/source/_integrations/atome.markdown index 154340087f7..f0f71f152e5 100644 --- a/source/_integrations/atome.markdown +++ b/source/_integrations/atome.markdown @@ -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 diff --git a/source/_integrations/august.markdown b/source/_integrations/august.markdown index 06e70a946a7..a4c956714c2 100644 --- a/source/_integrations/august.markdown +++ b/source/_integrations/august.markdown @@ -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. diff --git a/source/_integrations/aurora.markdown b/source/_integrations/aurora.markdown index 57e7c5fa6f7..b4d12cacc29 100644 --- a/source/_integrations/aurora.markdown +++ b/source/_integrations/aurora.markdown @@ -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. diff --git a/source/_integrations/automatic.markdown b/source/_integrations/automatic.markdown index 8aa3063d249..fb9db70b934 100644 --- a/source/_integrations/automatic.markdown +++ b/source/_integrations/automatic.markdown @@ -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 diff --git a/source/_integrations/aws.markdown b/source/_integrations/aws.markdown index 8325a46dc5a..0c501748cea 100644 --- a/source/_integrations/aws.markdown +++ b/source/_integrations/aws.markdown @@ -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" }, diff --git a/source/_integrations/bbb_gpio.markdown b/source/_integrations/bbb_gpio.markdown index f977d033f4f..389315e7f50 100644 --- a/source/_integrations/bbb_gpio.markdown +++ b/source/_integrations/bbb_gpio.markdown @@ -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. diff --git a/source/_integrations/binary_sensor.knx.markdown b/source/_integrations/binary_sensor.knx.markdown index 47bba637991..2818ad36a1b 100644 --- a/source/_integrations/binary_sensor.knx.markdown +++ b/source/_integrations/binary_sensor.knx.markdown @@ -14,7 +14,7 @@ The `knx` integration must be configured correctly to use this integration, see -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). diff --git a/source/_integrations/binary_sensor.mysensors.markdown b/source/_integrations/binary_sensor.mysensors.markdown index a6d7cafb5c2..8b42a3c5504 100644 --- a/source/_integrations/binary_sensor.mysensors.markdown +++ b/source/_integrations/binary_sensor.mysensors.markdown @@ -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 diff --git a/source/_integrations/binary_sensor.xiaomi_aqara.markdown b/source/_integrations/binary_sensor.xiaomi_aqara.markdown index d8457fbb018..b25eb39897e 100644 --- a/source/_integrations/binary_sensor.xiaomi_aqara.markdown +++ b/source/_integrations/binary_sensor.xiaomi_aqara.markdown @@ -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/). diff --git a/source/_integrations/bizkaibus.markdown b/source/_integrations/bizkaibus.markdown index bd5b94cbe84..c2fa349ffe0 100644 --- a/source/_integrations/bizkaibus.markdown +++ b/source/_integrations/bizkaibus.markdown @@ -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). diff --git a/source/_integrations/blink.markdown b/source/_integrations/blink.markdown index 9fd9274e4e6..0639b502f63 100644 --- a/source/_integrations/blink.markdown +++ b/source/_integrations/blink.markdown @@ -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 diff --git a/source/_integrations/bluesound.markdown b/source/_integrations/bluesound.markdown index b83195ed7a8..3deaec8ce09 100644 --- a/source/_integrations/bluesound.markdown +++ b/source/_integrations/bluesound.markdown @@ -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: diff --git a/source/_integrations/bluetooth_le_tracker.markdown b/source/_integrations/bluetooth_le_tracker.markdown index 130bac4db10..3154c973979 100644 --- a/source/_integrations/bluetooth_le_tracker.markdown +++ b/source/_integrations/bluetooth_le_tracker.markdown @@ -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 diff --git a/source/_integrations/braviatv.markdown b/source/_integrations/braviatv.markdown index 6c1054e7b7b..0708f5314a7 100644 --- a/source/_integrations/braviatv.markdown +++ b/source/_integrations/braviatv.markdown @@ -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. diff --git a/source/_integrations/broadlink.markdown b/source/_integrations/broadlink.markdown index ccb7e4a7f81..28c92e02850 100644 --- a/source/_integrations/broadlink.markdown +++ b/source/_integrations/broadlink.markdown @@ -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. diff --git a/source/_integrations/buienradar.markdown b/source/_integrations/buienradar.markdown index 522e3470558..35ce1f630e8 100644 --- a/source/_integrations/buienradar.markdown +++ b/source/_integrations/buienradar.markdown @@ -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. diff --git a/source/_integrations/camera.ffmpeg.markdown b/source/_integrations/camera.ffmpeg.markdown index a3e33350977..b8f497cc3b2 100644 --- a/source/_integrations/camera.ffmpeg.markdown +++ b/source/_integrations/camera.ffmpeg.markdown @@ -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 diff --git a/source/_integrations/cisco_ios.markdown b/source/_integrations/cisco_ios.markdown index 4960c9582f1..4b6fad84935 100644 --- a/source/_integrations/cisco_ios.markdown +++ b/source/_integrations/cisco_ios.markdown @@ -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.
This device tracker needs SSH to be enabled on the router. diff --git a/source/_integrations/climate.mysensors.markdown b/source/_integrations/climate.mysensors.markdown index e5bab774b6e..542e21a4d56 100644 --- a/source/_integrations/climate.mysensors.markdown +++ b/source/_integrations/climate.mysensors.markdown @@ -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 @@ -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 diff --git a/source/_integrations/co2signal.markdown b/source/_integrations/co2signal.markdown index 260c02b7419..48808af9f26 100644 --- a/source/_integrations/co2signal.markdown +++ b/source/_integrations/co2signal.markdown @@ -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 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. diff --git a/source/_integrations/coinmarketcap.markdown b/source/_integrations/coinmarketcap.markdown index 3f143ccd8a0..a5d8d3d2e6a 100644 --- a/source/_integrations/coinmarketcap.markdown +++ b/source/_integrations/coinmarketcap.markdown @@ -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`: diff --git a/source/_integrations/comfoconnect.markdown b/source/_integrations/comfoconnect.markdown index 54a8545aa0b..476d13a786d 100644 --- a/source/_integrations/comfoconnect.markdown +++ b/source/_integrations/comfoconnect.markdown @@ -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 diff --git a/source/_integrations/command_line.markdown b/source/_integrations/command_line.markdown index 36a194af115..988422d584c 100644 --- a/source/_integrations/command_line.markdown +++ b/source/_integrations/command_line.markdown @@ -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: diff --git a/source/_integrations/cover.mysensors.markdown b/source/_integrations/cover.mysensors.markdown index 0d159b96938..075f99a2e10 100644 --- a/source/_integrations/cover.mysensors.markdown +++ b/source/_integrations/cover.mysensors.markdown @@ -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 diff --git a/source/_integrations/cover.xiaomi_aqara.markdown b/source/_integrations/cover.xiaomi_aqara.markdown index 1b39657a022..d7808d03955 100644 --- a/source/_integrations/cover.xiaomi_aqara.markdown +++ b/source/_integrations/cover.xiaomi_aqara.markdown @@ -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/). diff --git a/source/_integrations/darksky.markdown b/source/_integrations/darksky.markdown index 0e2c765c8f7..cea4581810b 100644 --- a/source/_integrations/darksky.markdown +++ b/source/_integrations/darksky.markdown @@ -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 diff --git a/source/_integrations/datadog.markdown b/source/_integrations/datadog.markdown index 1198064ad6b..7a0152f82c6 100644 --- a/source/_integrations/datadog.markdown +++ b/source/_integrations/datadog.markdown @@ -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. diff --git a/source/_integrations/deconz.markdown b/source/_integrations/deconz.markdown index abacadf5046..c7771e14040 100644 --- a/source/_integrations/deconz.markdown +++ b/source/_integrations/deconz.markdown @@ -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 | |-----------|----------|-------------| diff --git a/source/_integrations/decora_wifi.markdown b/source/_integrations/decora_wifi.markdown index aef1c6a0063..9566535d2d3 100644 --- a/source/_integrations/decora_wifi.markdown +++ b/source/_integrations/decora_wifi.markdown @@ -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): diff --git a/source/_integrations/deluge.markdown b/source/_integrations/deluge.markdown index cbabe6d717f..14993ca1416 100644 --- a/source/_integrations/deluge.markdown +++ b/source/_integrations/deluge.markdown @@ -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: diff --git a/source/_integrations/denon.markdown b/source/_integrations/denon.markdown index 6ec69f974fc..30af1e719db 100644 --- a/source/_integrations/denon.markdown +++ b/source/_integrations/denon.markdown @@ -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: diff --git a/source/_integrations/denonavr.markdown b/source/_integrations/denonavr.markdown index c294edaf491..d2cc4a62955 100644 --- a/source/_integrations/denonavr.markdown +++ b/source/_integrations/denonavr.markdown @@ -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: diff --git a/source/_integrations/deutsche_bahn.markdown b/source/_integrations/deutsche_bahn.markdown index fa956f6313e..1ce069e50b1 100644 --- a/source/_integrations/deutsche_bahn.markdown +++ b/source/_integrations/deutsche_bahn.markdown @@ -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. diff --git a/source/_integrations/device_tracker.mysensors.markdown b/source/_integrations/device_tracker.mysensors.markdown index 3e392917c9b..88d645f68b6 100644 --- a/source/_integrations/device_tracker.mysensors.markdown +++ b/source/_integrations/device_tracker.mysensors.markdown @@ -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 diff --git a/source/_integrations/digitalloggers.markdown b/source/_integrations/digitalloggers.markdown index fbbdfa510ee..c725facab7f 100644 --- a/source/_integrations/digitalloggers.markdown +++ b/source/_integrations/digitalloggers.markdown @@ -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 diff --git a/source/_integrations/directv.markdown b/source/_integrations/directv.markdown index 593c94baad4..2f28a1a3df8 100644 --- a/source/_integrations/directv.markdown +++ b/source/_integrations/directv.markdown @@ -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`. diff --git a/source/_integrations/dlink.markdown b/source/_integrations/dlink.markdown index 54e2d1192f0..e43e03c10f4 100644 --- a/source/_integrations/dlink.markdown +++ b/source/_integrations/dlink.markdown @@ -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): diff --git a/source/_integrations/dovado.markdown b/source/_integrations/dovado.markdown index 1ff6ea7ad24..2319ce09adc 100644 --- a/source/_integrations/dovado.markdown +++ b/source/_integrations/dovado.markdown @@ -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: diff --git a/source/_integrations/dunehd.markdown b/source/_integrations/dunehd.markdown index 73d41fc50b0..5357d950138 100644 --- a/source/_integrations/dunehd.markdown +++ b/source/_integrations/dunehd.markdown @@ -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). diff --git a/source/_integrations/dweet.markdown b/source/_integrations/dweet.markdown index c2ffcb58d5a..cded98a4cef 100644 --- a/source/_integrations/dweet.markdown +++ b/source/_integrations/dweet.markdown @@ -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!

diff --git a/source/_integrations/econet.markdown b/source/_integrations/econet.markdown index 8a311db2424..da50296d305 100644 --- a/source/_integrations/econet.markdown +++ b/source/_integrations/econet.markdown @@ -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 diff --git a/source/_integrations/eddystone_temperature.markdown b/source/_integrations/eddystone_temperature.markdown index d40aada885b..076b5c6b5e2 100644 --- a/source/_integrations/eddystone_temperature.markdown +++ b/source/_integrations/eddystone_temperature.markdown @@ -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 diff --git a/source/_integrations/eliqonline.markdown b/source/_integrations/eliqonline.markdown index 0c41d7551a9..c580bb41fb1 100644 --- a/source/_integrations/eliqonline.markdown +++ b/source/_integrations/eliqonline.markdown @@ -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: diff --git a/source/_integrations/emby.markdown b/source/_integrations/emby.markdown index ce768cd0490..8d3efa65613 100644 --- a/source/_integrations/emby.markdown +++ b/source/_integrations/emby.markdown @@ -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: diff --git a/source/_integrations/enocean.markdown b/source/_integrations/enocean.markdown index 038917e56a4..8ecb70d3f75 100644 --- a/source/_integrations/enocean.markdown +++ b/source/_integrations/enocean.markdown @@ -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: diff --git a/source/_integrations/ephember.markdown b/source/_integrations/ephember.markdown index 704d125dcc2..baf6765bac7 100644 --- a/source/_integrations/ephember.markdown +++ b/source/_integrations/ephember.markdown @@ -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: diff --git a/source/_integrations/ffmpeg.markdown b/source/_integrations/ffmpeg.markdown index 09c4d529ba0..47082c8b5ec 100644 --- a/source/_integrations/ffmpeg.markdown +++ b/source/_integrations/ffmpeg.markdown @@ -11,7 +11,7 @@ The `ffmpeg` integration allows other Home Assistant integrations to process vid

-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.
diff --git a/source/_integrations/ffmpeg_motion.markdown b/source/_integrations/ffmpeg_motion.markdown index cb33b0ae35f..08d0cd8a668 100644 --- a/source/_integrations/ffmpeg_motion.markdown +++ b/source/_integrations/ffmpeg_motion.markdown @@ -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.
diff --git a/source/_integrations/ffmpeg_noise.markdown b/source/_integrations/ffmpeg_noise.markdown index a80d17021af..2f269a7b509 100644 --- a/source/_integrations/ffmpeg_noise.markdown +++ b/source/_integrations/ffmpeg_noise.markdown @@ -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.
diff --git a/source/_integrations/fibaro.markdown b/source/_integrations/fibaro.markdown index 416c0c8252d..ddea890a6b7 100644 --- a/source/_integrations/fibaro.markdown +++ b/source/_integrations/fibaro.markdown @@ -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: diff --git a/source/_integrations/fitbit.markdown b/source/_integrations/fitbit.markdown index f528e41130d..579273763bf 100644 --- a/source/_integrations/fitbit.markdown +++ b/source/_integrations/fitbit.markdown @@ -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: diff --git a/source/_integrations/fixer.markdown b/source/_integrations/fixer.markdown index 2c449712e4e..0a6f9d94711 100644 --- a/source/_integrations/fixer.markdown +++ b/source/_integrations/fixer.markdown @@ -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: diff --git a/source/_integrations/flux_led.markdown b/source/_integrations/flux_led.markdown index 5627d9b881b..13ae001d4f4 100644 --- a/source/_integrations/flux_led.markdown +++ b/source/_integrations/flux_led.markdown @@ -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) diff --git a/source/_integrations/freebox.markdown b/source/_integrations/freebox.markdown index 09e0d0ba50d..b097eabb356 100644 --- a/source/_integrations/freebox.markdown +++ b/source/_integrations/freebox.markdown @@ -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 diff --git a/source/_integrations/fritzbox_callmonitor.markdown b/source/_integrations/fritzbox_callmonitor.markdown index 727c4fa81f3..f8476c7f49a 100644 --- a/source/_integrations/fritzbox_callmonitor.markdown +++ b/source/_integrations/fritzbox_callmonitor.markdown @@ -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 diff --git a/source/_integrations/fritzbox_netmonitor.markdown b/source/_integrations/fritzbox_netmonitor.markdown index bf841ec1c1c..fcb5abd7716 100644 --- a/source/_integrations/fritzbox_netmonitor.markdown +++ b/source/_integrations/fritzbox_netmonitor.markdown @@ -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.
It might be necessary to install additional packages: sudo apt-get install libxslt-dev libxml2-dev python3-lxml diff --git a/source/_integrations/fronius.markdown b/source/_integrations/fronius.markdown index d317d18af1d..abcc86f3f80 100644 --- a/source/_integrations/fronius.markdown +++ b/source/_integrations/fronius.markdown @@ -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 diff --git a/source/_integrations/frontier_silicon.markdown b/source/_integrations/frontier_silicon.markdown index 613bb19a4ed..566cc2202ef 100644 --- a/source/_integrations/frontier_silicon.markdown +++ b/source/_integrations/frontier_silicon.markdown @@ -94,13 +94,13 @@ The Frontier Silicon API does not provide a multi-user environment. There is alw
-[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 diff --git a/source/_integrations/futurenow.markdown b/source/_integrations/futurenow.markdown index b0f7938e908..5dd9375e0a3 100644 --- a/source/_integrations/futurenow.markdown +++ b/source/_integrations/futurenow.markdown @@ -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 diff --git a/source/_integrations/garadget.markdown b/source/_integrations/garadget.markdown index be20979611c..49c35416cef 100644 --- a/source/_integrations/garadget.markdown +++ b/source/_integrations/garadget.markdown @@ -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 diff --git a/source/_integrations/geo_rss_events.markdown b/source/_integrations/geo_rss_events.markdown index 25b99a57de3..6f020aa88e1 100644 --- a/source/_integrations/geo_rss_events.markdown +++ b/source/_integrations/geo_rss_events.markdown @@ -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 diff --git a/source/_integrations/geofency.markdown b/source/_integrations/geofency.markdown index d15596a9f91..02716bda083 100644 --- a/source/_integrations/geofency.markdown +++ b/source/_integrations/geofency.markdown @@ -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 diff --git a/source/_integrations/geonetnz_quakes.markdown b/source/_integrations/geonetnz_quakes.markdown index 78ccdb270a6..ba00fd528a5 100644 --- a/source/_integrations/geonetnz_quakes.markdown +++ b/source/_integrations/geonetnz_quakes.markdown @@ -29,7 +29,7 @@ The data is updated every 5 minutes.
-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. diff --git a/source/_integrations/gpmdp.markdown b/source/_integrations/gpmdp.markdown index 408413d9a4b..dcc780a8ae9 100644 --- a/source/_integrations/gpmdp.markdown +++ b/source/_integrations/gpmdp.markdown @@ -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. diff --git a/source/_integrations/greeneye_monitor.markdown b/source/_integrations/greeneye_monitor.markdown index 2562671989e..52afe90bcb9 100644 --- a/source/_integrations/greeneye_monitor.markdown +++ b/source/_integrations/greeneye_monitor.markdown @@ -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`: diff --git a/source/_integrations/gtfs.markdown b/source/_integrations/gtfs.markdown index 2a8d088a772..c6b79067dab 100644 --- a/source/_integrations/gtfs.markdown +++ b/source/_integrations/gtfs.markdown @@ -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. diff --git a/source/_integrations/hangouts.markdown b/source/_integrations/hangouts.markdown index b21e4819208..b6a1443eba4 100644 --- a/source/_integrations/hangouts.markdown +++ b/source/_integrations/hangouts.markdown @@ -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: diff --git a/source/_integrations/harmony.markdown b/source/_integrations/harmony.markdown index 37487c3e6d4..c587e6cd221 100644 --- a/source/_integrations/harmony.markdown +++ b/source/_integrations/harmony.markdown @@ -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: diff --git a/source/_integrations/hddtemp.markdown b/source/_integrations/hddtemp.markdown index 262e5f0a789..32a805b292e 100644 --- a/source/_integrations/hddtemp.markdown +++ b/source/_integrations/hddtemp.markdown @@ -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. diff --git a/source/_integrations/hikvision.markdown b/source/_integrations/hikvision.markdown index fcb8f506c43..a3bfd008d71 100644 --- a/source/_integrations/hikvision.markdown +++ b/source/_integrations/hikvision.markdown @@ -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. diff --git a/source/_integrations/hikvisioncam.markdown b/source/_integrations/hikvisioncam.markdown index 4896023bf74..28101dfa697 100644 --- a/source/_integrations/hikvisioncam.markdown +++ b/source/_integrations/hikvisioncam.markdown @@ -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.
Currently works using default https port only. diff --git a/source/_integrations/homematic.markdown b/source/_integrations/homematic.markdown index e78c30c89d9..d3b77eabf45 100644 --- a/source/_integrations/homematic.markdown +++ b/source/_integrations/homematic.markdown @@ -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: diff --git a/source/_integrations/homematicip_cloud.markdown b/source/_integrations/homematicip_cloud.markdown index c87eb1f650b..87cec0d82ef 100644 --- a/source/_integrations/homematicip_cloud.markdown +++ b/source/_integrations/homematicip_cloud.markdown @@ -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: diff --git a/source/_integrations/hp_ilo.markdown b/source/_integrations/hp_ilo.markdown index 1e885a97742..4f2cee29ede 100644 --- a/source/_integrations/hp_ilo.markdown +++ b/source/_integrations/hp_ilo.markdown @@ -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/).

diff --git a/source/_integrations/hunterdouglas_powerview.markdown b/source/_integrations/hunterdouglas_powerview.markdown index 47e5c7b6e78..6a231a79af5 100644 --- a/source/_integrations/hunterdouglas_powerview.markdown +++ b/source/_integrations/hunterdouglas_powerview.markdown @@ -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`. diff --git a/source/_integrations/ign_sismologia.markdown b/source/_integrations/ign_sismologia.markdown index a5e30c4ce33..ed9d46b4c33 100644 --- a/source/_integrations/ign_sismologia.markdown +++ b/source/_integrations/ign_sismologia.markdown @@ -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. diff --git a/source/_integrations/input_select.markdown b/source/_integrations/input_select.markdown index cd28d03e547..a666ce98c07 100644 --- a/source/_integrations/input_select.markdown +++ b/source/_integrations/input_select.markdown @@ -56,7 +56,7 @@ input_select:

-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.
diff --git a/source/_integrations/insteon.markdown b/source/_integrations/insteon.markdown index 15f96cf126d..65687710a49 100644 --- a/source/_integrations/insteon.markdown +++ b/source/_integrations/insteon.markdown @@ -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 diff --git a/source/_integrations/iota.markdown b/source/_integrations/iota.markdown index 08e2d6a9dcd..607de048798 100644 --- a/source/_integrations/iota.markdown +++ b/source/_integrations/iota.markdown @@ -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. diff --git a/source/_integrations/iperf3.markdown b/source/_integrations/iperf3.markdown index 80694beaa4b..5513ccb726b 100644 --- a/source/_integrations/iperf3.markdown +++ b/source/_integrations/iperf3.markdown @@ -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 diff --git a/source/_integrations/ipma.markdown b/source/_integrations/ipma.markdown index 4a229cf11fa..0edf8d6f9c9 100644 --- a/source/_integrations/ipma.markdown +++ b/source/_integrations/ipma.markdown @@ -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 diff --git a/source/_integrations/itach.markdown b/source/_integrations/itach.markdown index e00827df99a..df89a06320c 100644 --- a/source/_integrations/itach.markdown +++ b/source/_integrations/itach.markdown @@ -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) diff --git a/source/_integrations/itunes.markdown b/source/_integrations/itunes.markdown index 74268d14467..315d59af959 100644 --- a/source/_integrations/itunes.markdown +++ b/source/_integrations/itunes.markdown @@ -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. diff --git a/source/_integrations/joaoapps_join.markdown b/source/_integrations/joaoapps_join.markdown index 5db8e8ef688..06fbffeff2d 100644 --- a/source/_integrations/joaoapps_join.markdown +++ b/source/_integrations/joaoapps_join.markdown @@ -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.`. 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.`. The name will defailt to `notify` if not supplied. See the [Notifications Component](/integrations/notify) for more details. required: false type: string {% endconfiguration %} diff --git a/source/_integrations/keyboard.markdown b/source/_integrations/keyboard.markdown index bd7e8278cff..9443bd255fe 100644 --- a/source/_integrations/keyboard.markdown +++ b/source/_integrations/keyboard.markdown @@ -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. diff --git a/source/_integrations/kodi.markdown b/source/_integrations/kodi.markdown index 1a088a789df..01e48287370 100644 --- a/source/_integrations/kodi.markdown +++ b/source/_integrations/kodi.markdown @@ -9,7 +9,7 @@ ha_release: pre 0.7 ha_iot_class: Local Push --- -The `kodi` platform allows you to control a [Kodi](http://kodi.tv/) multimedia system from Home Assistant. +The `kodi` platform allows you to control a [Kodi](https://kodi.tv/) multimedia system from Home Assistant. The preferred way to set up the Kodi platform is by enabling the [discovery component](/integrations/discovery/) which requires enabled [web interface](https://kodi.wiki/view/Web_interface) on your Kodi installation. @@ -97,7 +97,7 @@ Add music to the default playlist (i.e. playlistid=0). #### Service `kodi.call_method` -Call a [Kodi JSONRPC API](http://kodi.wiki/?title=JSON-RPC_API) method with optional parameters. Results of the Kodi API call will be redirected in a Home Assistant event: `kodi_call_method_result`. +Call a [Kodi JSONRPC API](https://kodi.wiki/?title=JSON-RPC_API) method with optional parameters. Results of the Kodi API call will be redirected in a Home Assistant event: `kodi_call_method_result`. | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | diff --git a/source/_integrations/lametric.markdown b/source/_integrations/lametric.markdown index 7d0345b5913..18879c0155e 100644 --- a/source/_integrations/lametric.markdown +++ b/source/_integrations/lametric.markdown @@ -8,7 +8,7 @@ ha_category: ha_release: 0.49 --- -[LaMetric Time](http://lametric.com) is a smart clock that can be used to access applications, listen to web radio and display notifications. +[LaMetric Time](https://lametric.com/) is a smart clock that can be used to access applications, listen to web radio and display notifications. There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/lannouncer.markdown b/source/_integrations/lannouncer.markdown index 4f13d77d482..075a1ab45b1 100644 --- a/source/_integrations/lannouncer.markdown +++ b/source/_integrations/lannouncer.markdown @@ -7,7 +7,7 @@ ha_category: ha_release: 0.36 --- -The `lannouncer` notification platform allows you to play spoken messages (TTS) or sounds on an Android device running [Lannouncer](http://www.keybounce.com/lannouncer/). This can be useful when you have a wall mounted Android tablet, or an Android device that is permanently powered and turned on and want to use that to play notifications. +The `lannouncer` notification platform allows you to play spoken messages (TTS) or sounds on an Android device running [Lannouncer](https://www.keybounce.com/lannouncer/). This can be useful when you have a wall mounted Android tablet, or an Android device that is permanently powered and turned on and want to use that to play notifications. To enable Lannouncer notifications in your installation, add the following to your `configuration.yaml` file: @@ -42,7 +42,7 @@ You need to install the Lannouncer app and enable the *Network (TCP) Listener* a Lannouncer uses the default Android TTS voice. You can tweak that in the Android configuration, or you can install a different TTS engine from the Play Store. You might want to raise the volume in the app settings since that depends on the actual hardware device. -More information can be found [here](http://www.keybounce.com/lannouncer/configuring-lannouncer/). +More information can be found [here](https://www.keybounce.com/lannouncer/configuring-lannouncer/). ### Sending messages diff --git a/source/_integrations/lastfm.markdown b/source/_integrations/lastfm.markdown index 2ca19ba6a3d..307ace29909 100644 --- a/source/_integrations/lastfm.markdown +++ b/source/_integrations/lastfm.markdown @@ -8,11 +8,11 @@ ha_iot_class: Cloud Polling ha_release: "0.20" --- -The `lastfm` sensor platform will allow you to see whenever a user starts scrobbling, their play count, last song played, and top song played on [Last.fm](http://www.last.fm). +The `lastfm` sensor platform will allow you to see whenever a user starts scrobbling, their play count, last song played, and top song played on [Last.fm](https://www.last.fm/). ## Setup -To get an API key you need to create an [API account](http://www.last.fm/api/account/create). +To get an API key you need to create an [API account](https://www.last.fm/api/account/create). ## Configuration diff --git a/source/_integrations/launch_library.markdown b/source/_integrations/launch_library.markdown index bb7401277b1..dba4672fe7e 100644 --- a/source/_integrations/launch_library.markdown +++ b/source/_integrations/launch_library.markdown @@ -29,4 +29,4 @@ name: The data this platform presents comes from [launchlibrary.net][launchlibrary]. -[launchlibrary]: http://launchlibrary.net/ +[launchlibrary]: https://launchlibrary.net/ diff --git a/source/_integrations/lcn.markdown b/source/_integrations/lcn.markdown index 4c7d251641c..32e73f417eb 100644 --- a/source/_integrations/lcn.markdown +++ b/source/_integrations/lcn.markdown @@ -15,7 +15,7 @@ ha_release: 0.85 ha_iot_class: Local Push --- -The `lcn` integration for Home Assistant allows you to connect to [LCN](http://www.lcn.eu) hardware devices. +The `lcn` integration for Home Assistant allows you to connect to [LCN](https://www.lcn.eu/) hardware devices. The integration requires one unused license of the coupling software LCN-PCHK (version >2.8) and an LCN hardware coupler. Alternatively, an LCN-PKE coupler can be used which offers two PCHK licenses. With this setup sending and receiving commands to and from LCN modules is possible. @@ -412,7 +412,7 @@ Examples: `a1`, `a5`, `d8`. ### Binary Sensor -The `lcn` binary sensor platform allows the monitoring of the following [LCN](http://www.lcn.eu) binary data sources: +The `lcn` binary sensor platform allows the monitoring of the following [LCN](https://www.lcn.eu/) binary data sources: - Binary hardware sensors - Lock state of regulator setpoints @@ -422,7 +422,7 @@ The binary sensor can be used in automation scripts or in conjunction with `temp ### Climate -The `lcn` climate platform allows the control of the [LCN](http://www.lcn.eu) climate regulators. +The `lcn` climate platform allows the control of the [LCN](https://www.lcn.eu/) climate regulators. This platform depends on the correct configuration of the module's regulators, which has to be done in the LCN-PRO programming software. You need to specify at least the variable for the current temperature and a setpoint variable for the target temperature. If the control is set lockable, the regulator can be turned on/off. @@ -435,7 +435,7 @@ If you intend to leave the regulation to Home Assistant, you should consider usi ### Cover -The `lcn` cover platform allows the control of [LCN](http://www.lcn.eu) relays and output ports which have been configured as motor controllers. +The `lcn` cover platform allows the control of [LCN](https://www.lcn.eu/) relays and output ports which have been configured as motor controllers. Only for the module with firmware earlier than 190C:
The configuration allows the optional definition of reverse time. This is the time which is waited during the switching of the motor currents. @@ -450,18 +450,18 @@ Otherwise, the output ports are not mutually interlocked and you run the risk of ### Light -The `lcn` light platform allows the control of the following [LCN](http://www.lcn.eu) ports: +The `lcn` light platform allows the control of the following [LCN](https://www.lcn.eu/) ports: - (Dimmable) output ports - Relays ### Scene -The `lcn` scene platform allows the activation of previously programmed [LCN](http://www.lcn.eu) scenes. +The `lcn` scene platform allows the activation of previously programmed [LCN](https://www.lcn.eu/) scenes. ### Sensor -The `lcn` sensor platform allows the monitoring of the following [LCN](http://www.lcn.eu) data sources: +The `lcn` sensor platform allows the monitoring of the following [LCN](https://www.lcn.eu/) data sources: - Variables - Regulator setpoints @@ -479,7 +479,7 @@ The sensor can be used in automation scripts or in conjunction with `template` p ### Switch -The `lcn` switch platform allows the control of the following [LCN](http://www.lcn.eu) ports: +The `lcn` switch platform allows the control of the following [LCN](https://www.lcn.eu/) ports: - Output ports - Relays diff --git a/source/_integrations/light.mysensors.markdown b/source/_integrations/light.mysensors.markdown index 703fc6935b4..4cfa6de1403 100644 --- a/source/_integrations/light.mysensors.markdown +++ b/source/_integrations/light.mysensors.markdown @@ -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/dimmer + * https://www.mysensors.org/build/dimmer */ #include @@ -113,10 +113,10 @@ void incomingMessage(const MyMessage &message) { ```cpp /* * Example Dimmable Light - * Code adapted from http://github.com/mysensors/MySensors/tree/master/examples/DimmableLight + * Code adapted from https://github.com/mysensors/MySensors/tree/master/examples/DimmableLight * - * Documentation: http://www.mysensors.org - * Support Forum: http://forum.mysensors.org + * Documentation: https://www.mysensors.org + * Support Forum: https://forum.mysensors.org * */ @@ -243,4 +243,4 @@ void send_status_message() ``` [main component]: /integrations/mysensors/ -[serial api]: http://www.mysensors.org/download +[serial api]: https://www.mysensors.org/download diff --git a/source/_integrations/limitlessled.markdown b/source/_integrations/limitlessled.markdown index 1462f206c6e..b1e336b0146 100644 --- a/source/_integrations/limitlessled.markdown +++ b/source/_integrations/limitlessled.markdown @@ -8,7 +8,7 @@ ha_iot_class: Assumed State ha_release: pre 0.7 --- -`limitlessled` can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, [MiLight](http://www.milight.com/), LEDme, dekolight, or iLight. +`limitlessled` can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, [MiLight](https://www.milight.com/), LEDme, dekolight, or iLight. LimitlessLED bulbs are controlled via groups, so you can only control an individual bulb via the bridge if it is in a group by itself. diff --git a/source/_integrations/lock.xiaomi_aqara.markdown b/source/_integrations/lock.xiaomi_aqara.markdown index cf0c09e24f1..2e5773ea1d9 100644 --- a/source/_integrations/lock.xiaomi_aqara.markdown +++ b/source/_integrations/lock.xiaomi_aqara.markdown @@ -9,7 +9,7 @@ ha_iot_class: Local Push --- -The `xiaomi aqara` lock platform allows you to get data (`changed_by` property, `verified_wrong_times` attribute) from your [Xiaomi](http://www.mi.com/en/) Aqara locks. +The `xiaomi aqara` lock platform allows you to get data (`changed_by` property, `verified_wrong_times` attribute) from your [Xiaomi](https://www.mi.com/en/) Aqara locks. A Aqara lock cannot be controlled by Home Assistant. The property `changed_by` provides the user/key ID of the last successful unlock. If someone tries to unlock the device but fails more than 3 times the `verified_wrong_times` attribute will be incremented. The counter resets on a successful unlock. diff --git a/source/_integrations/london_air.markdown b/source/_integrations/london_air.markdown index 99d4d7aa774..2fc19f24c74 100644 --- a/source/_integrations/london_air.markdown +++ b/source/_integrations/london_air.markdown @@ -8,9 +8,9 @@ ha_iot_class: Cloud Polling ha_release: 0.52 --- -The `london_air` integration [queries](http://api.erg.kcl.ac.uk/AirQuality/Hourly/MonitoringIndex/GroupName=London/Json) the London air quality [data feed](https://www.londonair.org.uk/LondonAir/API/) provided by Kings College London. A single sensor will be added for each `location` ([local authority district or borough](https://en.wikipedia.org/wiki/List_of_London_boroughs)) specified in the configuration file. The state of each sensor is the overall air quality in that borough. Note that only 28 of the 32 boroughs have data available. +The `london_air` integration [queries](https://api.erg.kcl.ac.uk/AirQuality/Hourly/MonitoringIndex/GroupName=London/Json) the London air quality [data feed](https://www.londonair.org.uk/LondonAir/API/) provided by Kings College London. A single sensor will be added for each `location` ([local authority district or borough](https://en.wikipedia.org/wiki/List_of_London_boroughs)) specified in the configuration file. The state of each sensor is the overall air quality in that borough. Note that only 28 of the 32 boroughs have data available. -Boroughs can have multiple monitoring sites at different geographical positions within the borough, and each of those sites can monitor up to six different kinds of pollutant. The pollutants are described [here](http://api.erg.kcl.ac.uk/AirQuality/Information/Species/Json) and are Carbon Monoxide ([CO2](http://www.londonair.org.uk/LondonAir/guide/WhatIsCO.aspx)), Nitrogen Dioxide ([NO2](http://www.londonair.org.uk/LondonAir/guide/WhatIsNO2.aspx)), Ozone ([O3](http://www.londonair.org.uk/LondonAir/guide/WhatIsO3.aspx)), Sulfur Dioxide ([SO2](http://www.londonair.org.uk/LondonAir/guide/WhatIsSO2.aspx)), PM2.5 & PM10 [particulates](http://www.londonair.org.uk/LondonAir/guide/WhatIsPM.aspx). The `latitude` and `longitude` of each site is accessible through a `data` attribute of the sensor, as are details about the pollutants monitored at that site. The `sites` attribute of a sensor displays how many monitoring sites that sensor covers. The `updated` attribute of a sensor states when the data was last published. Nominally data is published hourly, but in my experience this can vary. To limit the number of requests made by the sensor, a single API request is made every 30 minutes. +Boroughs can have multiple monitoring sites at different geographical positions within the borough, and each of those sites can monitor up to six different kinds of pollutant. The pollutants are described [here](https://api.erg.kcl.ac.uk/AirQuality/Information/Species/Json) and are Carbon Monoxide ([CO2](https://www.londonair.org.uk/LondonAir/guide/WhatIsCO.aspx)), Nitrogen Dioxide ([NO2](https://www.londonair.org.uk/LondonAir/guide/WhatIsNO2.aspx)), Ozone ([O3](https://www.londonair.org.uk/LondonAir/guide/WhatIsO3.aspx)), Sulfur Dioxide ([SO2](https://www.londonair.org.uk/LondonAir/guide/WhatIsSO2.aspx)), PM2.5 & PM10 [particulates](https://www.londonair.org.uk/LondonAir/guide/WhatIsPM.aspx). The `latitude` and `longitude` of each site is accessible through a `data` attribute of the sensor, as are details about the pollutants monitored at that site. The `sites` attribute of a sensor displays how many monitoring sites that sensor covers. The `updated` attribute of a sensor states when the data was last published. Nominally data is published hourly, but in my experience this can vary. To limit the number of requests made by the sensor, a single API request is made every 30 minutes. To add sensors to Home-assistant for all possible areas/boroughs add the following to your `configuration.yaml` file: diff --git a/source/_integrations/luftdaten.markdown b/source/_integrations/luftdaten.markdown index 49414cc97e5..45e442ae717 100644 --- a/source/_integrations/luftdaten.markdown +++ b/source/_integrations/luftdaten.markdown @@ -10,11 +10,11 @@ ha_iot_class: Cloud Polling ha_qa_scale: gold --- -The `luftdaten` integration will query the open data API of [luftdaten.info](http://luftdaten.info) to monitor air quality and other weather data from a specific (self build) sensor station. +The `luftdaten` integration will query the open data API of [luftdaten.info](https://luftdaten.info/) to monitor air quality and other weather data from a specific (self build) sensor station. ## Setup -- To get the ID of a particle sensor you need to select it on the [Feinstaub map](http://deutschland.maps.luftdaten.info/) and find it in the sidebar (Column "Sensor ID"). +- To get the ID of a particle sensor you need to select it on the [Feinstaub map](https://deutschland.maps.luftdaten.info/) and find it in the sidebar (Column "Sensor ID"). - To get the ID of a temperature/humidity sensor you need to find it on the map hosted on [Madavi](https://www.madavi.de/sensor/feinstaub-map-dht/). ## Configuration via the frontend @@ -101,6 +101,6 @@ luftdaten: ## Sensor -The `luftdaten` sensor platform will query the open data API of [luftdaten.info](http://luftdaten.info) to monitor air quality and other weather data from a specific (self build) sensor station. +The `luftdaten` sensor platform will query the open data API of [luftdaten.info](https://luftdaten.info/) to monitor air quality and other weather data from a specific (self build) sensor station. You must have the `luftdaten` integration (from above) configured to use this platform. After configuring that component, sensors will automatically appear. diff --git a/source/_integrations/lutron_caseta.markdown b/source/_integrations/lutron_caseta.markdown index 80541db58bb..36f20244baa 100644 --- a/source/_integrations/lutron_caseta.markdown +++ b/source/_integrations/lutron_caseta.markdown @@ -12,9 +12,9 @@ ha_release: 0.41 ha_iot_class: Local Polling --- -[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches, dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` integration in Home Assistant is responsible for communicating with the Lutron Caseta Smart Bridge for the [Caseta](http://www.casetawireless.com) product line of dimmers, switches and shades. +[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches, dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` integration in Home Assistant is responsible for communicating with the Lutron Caseta Smart Bridge for the [Caseta](https://www.casetawireless.com/) product line of dimmers, switches and shades. -This integration only supports the [Caseta](http://www.casetawireless.com) line of products. Both Smart Bridge (L-BDG2-WH) and Smart Bridge PRO (L-BDGPRO2-WH) models are supported. For the RadioRA 2 product line, see the [Lutron component](/integrations/lutron/). +This integration only supports the [Caseta](https://www.casetawireless.com/) line of products. Both Smart Bridge (L-BDG2-WH) and Smart Bridge PRO (L-BDGPRO2-WH) models are supported. For the RadioRA 2 product line, see the [Lutron component](/integrations/lutron/). The currently supported Caseta devices are: diff --git a/source/_integrations/matrix.markdown b/source/_integrations/matrix.markdown index 8da71339bec..08f0877f0e3 100644 --- a/source/_integrations/matrix.markdown +++ b/source/_integrations/matrix.markdown @@ -141,7 +141,7 @@ This configuration will: ## Notifications -The `matrix` platform allows you to deliver notifications from Home Assistant to a [Matrix](http://matrix.org) room. Rooms can be both direct as well as group chats. +The `matrix` platform allows you to deliver notifications from Home Assistant to a [Matrix](https://matrix.org/) room. Rooms can be both direct as well as group chats. To enable Matrix notifications in your installation, you first need to configure the [Matrix component](#configuration). Then, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/maxcube.markdown b/source/_integrations/maxcube.markdown index 91564f6a062..5916c439820 100644 --- a/source/_integrations/maxcube.markdown +++ b/source/_integrations/maxcube.markdown @@ -9,7 +9,7 @@ ha_release: "0.40" ha_iot_class: Local Polling --- -[eQ-3 MAX!](http://www.eq-3.com/products/max.html) integration for Home Assistant allows you to connect eQ-3 MAX! components via the eQ-3 MAX! Cube. The components connects to the eQ-3 MAX! Cube via TCP and automatically makes all supported integrations available in Home Assistant. The name for each device is created by concatenating the MAX! room and device names. +[eQ-3 MAX!](https://www.eq-3.com/products/max.html) integration for Home Assistant allows you to connect eQ-3 MAX! components via the eQ-3 MAX! Cube. The components connects to the eQ-3 MAX! Cube via TCP and automatically makes all supported integrations available in Home Assistant. The name for each device is created by concatenating the MAX! room and device names. There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/melissa.markdown b/source/_integrations/melissa.markdown index cf433d86ffc..9f3303f53fe 100644 --- a/source/_integrations/melissa.markdown +++ b/source/_integrations/melissa.markdown @@ -9,7 +9,7 @@ ha_release: 0.63 ha_iot_class: Cloud Polling --- -The `melissa` integration is the main integration to connect to a [Melissa Climate](http://seemelissa.com/) A/C control. +The `melissa` integration is the main integration to connect to a [Melissa Climate](https://seemelissa.com/) A/C control. There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/meteo_france.markdown b/source/_integrations/meteo_france.markdown index 32fcf33d0ba..a412eb6c4c6 100644 --- a/source/_integrations/meteo_france.markdown +++ b/source/_integrations/meteo_france.markdown @@ -17,7 +17,7 @@ There is currently support for the following device types within Home Assistant: - Sensor - Weather -It displays the current weather along with a 4 days forecast and can create sensors based on the `monitored_conditions` set in your `configuration.yaml` file, including weather alerts from [Vigilance Météo-France](http://vigilance.meteofrance.com) +It displays the current weather along with a 4 days forecast and can create sensors based on the `monitored_conditions` set in your `configuration.yaml` file, including weather alerts from [Vigilance Météo-France](https://vigilance.meteofrance.com/) ## Configuration @@ -70,7 +70,7 @@ It works well with french postal code, city name, etc. In case your expected res It also works with international city, with mixed results. You may have to find the correct city query. For example `Montreal, Canada` will return a city in Ardèche, France, whereas `Montreal, america` works -[http://www.meteofrance.com/mf3-rpc-portlet/rest/lieu/facet/previsions/search/montreal,amerique](http://www.meteofrance.com/mf3-rpc-portlet/rest/lieu/facet/previsions/search/montreal,amerique) +[https://www.meteofrance.com/mf3-rpc-portlet/rest/lieu/facet/previsions/search/montreal,amerique](https://www.meteofrance.com/mf3-rpc-portlet/rest/lieu/facet/previsions/search/montreal,amerique) ```yaml # Example configuration.yaml entry for Montreal, Canada @@ -83,7 +83,7 @@ meteo_france:
The 1 hour rain forecast is supported for more than 75 % of metropolitan France.
- You can check if your city is covered on the [Météo-France website](http://www.meteofrance.com/previsions-meteo-france/previsions-pluie). + You can check if your city is covered on the [Météo-France website](https://www.meteofrance.com/previsions-meteo-france/previsions-pluie).
@@ -104,7 +104,7 @@ Possible value for each intervals attributes are: The weather alert is available for the metropolitan France.
-The `weather_alert` sensor value give the current weather alert status for the department linked to the city. Data is retrieve from [Météo-France vigilance website](http://vigilance.meteofrance.com/). +The `weather_alert` sensor value give the current weather alert status for the department linked to the city. Data is retrieve from [Météo-France vigilance website](https://vigilance.meteofrance.com/). The sensor attributes give access to each type of alerts and date of the bulletin emitted by Météo-France. diff --git a/source/_integrations/metoffice.markdown b/source/_integrations/metoffice.markdown index 910fe7387f0..937aecb7f32 100644 --- a/source/_integrations/metoffice.markdown +++ b/source/_integrations/metoffice.markdown @@ -8,7 +8,7 @@ ha_release: 0.42 ha_iot_class: Cloud Polling --- -The `metoffice` weather platform uses the Met Office's [DataPoint API](http://www.metoffice.gov.uk/datapoint) for weather data. +The `metoffice` weather platform uses the Met Office's [DataPoint API](https://www.metoffice.gov.uk/datapoint) for weather data. ## Configuration @@ -23,7 +23,7 @@ weather: {% configuration %} api_key: - description: "Your personal API key from the [Datapoint website](http://www.metoffice.gov.uk/datapoint)." + description: "Your personal API key from the [Datapoint website](https://www.metoffice.gov.uk/datapoint)." required: true type: string name: diff --git a/source/_integrations/microsoft.markdown b/source/_integrations/microsoft.markdown index 0a2cd4c28f6..d5bce0a8f62 100644 --- a/source/_integrations/microsoft.markdown +++ b/source/_integrations/microsoft.markdown @@ -57,7 +57,7 @@ pitch: type: string default: "`default`" contour: - description: "Change the contour of the output in percentages. This overrides the pitch setting. See the [W3 SSML specification](http://www.w3.org/TR/speech-synthesis/#pitch_contour) for what it does. Example value: `(0,0) (100,100)`." + description: "Change the contour of the output in percentages. This overrides the pitch setting. See the [W3 SSML specification](https://www.w3.org/TR/speech-synthesis/#pitch_contour) for what it does. Example value: `(0,0) (100,100)`." required: false type: string {% endconfiguration %} diff --git a/source/_integrations/mikrotik.markdown b/source/_integrations/mikrotik.markdown index 909260201a7..3f04f43c66f 100644 --- a/source/_integrations/mikrotik.markdown +++ b/source/_integrations/mikrotik.markdown @@ -8,7 +8,7 @@ ha_category: ha_release: 0.44 --- -The `mikrotik` platform offers presence detection by looking at connected devices to a [MikroTik RouterOS](http://mikrotik.com) based router. +The `mikrotik` platform offers presence detection by looking at connected devices to a [MikroTik RouterOS](https://mikrotik.com) based router. There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/mpd.markdown b/source/_integrations/mpd.markdown index 5863ad742a1..754a5f697db 100644 --- a/source/_integrations/mpd.markdown +++ b/source/_integrations/mpd.markdown @@ -9,7 +9,7 @@ ha_iot_class: Local Polling --- -The `mpd` platform allows you to control a [Music Player Daemon](http://www.musicpd.org/) from Home Assistant. Unfortunately you will not be able to manipulate the playlist (add or delete songs) or add transitions between the songs. +The `mpd` platform allows you to control a [Music Player Daemon](https://www.musicpd.org/) from Home Assistant. Unfortunately you will not be able to manipulate the playlist (add or delete songs) or add transitions between the songs. Even though no playlist manipulation is possible, it is possible to use the play_media service to load an existing saved playlist as part of an automation or scene. @@ -60,5 +60,5 @@ relaxdeck: volume_level: 0.60 ``` -This platform works with [Music Player Daemon](http://www.musicpd.org/) and [mopidy](https://www.mopidy.com/) with [Mopidy-MPD](https://docs.mopidy.com/en/latest/ext/mpd/) as used by [Pi MusicBox](http://www.pimusicbox.com/). +This platform works with [Music Player Daemon](https://www.musicpd.org/) and [mopidy](https://www.mopidy.com/) with [Mopidy-MPD](https://docs.mopidy.com/en/latest/ext/mpd/) as used by [Pi MusicBox](https://www.pimusicbox.com/). diff --git a/source/_integrations/mvglive.markdown b/source/_integrations/mvglive.markdown index e457f564d1f..27ce2cf4de0 100644 --- a/source/_integrations/mvglive.markdown +++ b/source/_integrations/mvglive.markdown @@ -24,7 +24,7 @@ sensor: {% configuration %} station: - description: Name of the stop or station. Visit [the MVG live web site](http://www.mvg-live.de) to find valid names. + description: Name of the stop or station. Visit [the MVG live web site](https://www.mvg-live.de/) to find valid names. required: true type: string destinations: diff --git a/source/_integrations/mysensors.markdown b/source/_integrations/mysensors.markdown index 9a6e632ec51..5a000985871 100644 --- a/source/_integrations/mysensors.markdown +++ b/source/_integrations/mysensors.markdown @@ -153,10 +153,10 @@ Present a MySensors sensor or actuator, by following these steps: ```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/relay + * https://www.mysensors.org/build/relay */ #define MY_DEBUG @@ -259,4 +259,4 @@ logger: Visit the [library API][MySensors library api] of MySensors for more information. -[MySensors library API]: http://www.mysensors.org/download +[MySensors library API]: https://www.mysensors.org/download diff --git a/source/_integrations/nad.markdown b/source/_integrations/nad.markdown index 9f5e806cce2..64a25c3922c 100644 --- a/source/_integrations/nad.markdown +++ b/source/_integrations/nad.markdown @@ -8,7 +8,7 @@ ha_release: 0.36 ha_iot_class: Local Polling --- -The `nad` platform allows you to control a [NAD receiver](http://nadelectronics.com) through RS232, TCP and Telnet from Home Assistant. +The `nad` platform allows you to control a [NAD receiver](https://nadelectronics.com/) through RS232, TCP and Telnet from Home Assistant. To add an NAD receiver to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/netdata.markdown b/source/_integrations/netdata.markdown index 8d9f1c93b2f..20136cdcb33 100644 --- a/source/_integrations/netdata.markdown +++ b/source/_integrations/netdata.markdown @@ -8,7 +8,7 @@ ha_release: 0.35 ha_iot_class: Local Polling --- -The `netdata` sensor platform allows you to display information collected by [Netdata](http://my-netdata.io/). +The `netdata` sensor platform allows you to display information collected by [Netdata](https://my-netdata.io/). ## Setup diff --git a/source/_integrations/netgear.markdown b/source/_integrations/netgear.markdown index 067a58efd01..bae63c3fda0 100644 --- a/source/_integrations/netgear.markdown +++ b/source/_integrations/netgear.markdown @@ -8,7 +8,7 @@ ha_iot_class: Local Polling ha_release: pre 0.7 --- -This platform allows you to detect presence by looking at connected devices to a [Netgear](http://www.netgear.com/) device. +This platform allows you to detect presence by looking at connected devices to a [Netgear](https://www.netgear.com/) device.
diff --git a/source/_integrations/netio.markdown b/source/_integrations/netio.markdown index 710e3b00993..72a54a80a1b 100644 --- a/source/_integrations/netio.markdown +++ b/source/_integrations/netio.markdown @@ -8,7 +8,7 @@ ha_iot_class: Local Polling ha_release: 0.24 --- -The `netio` switch platform allows you to control your [Netio](http://www.netio-products.com/en/overview/) Netio4, Netio4 All, and Netio 230B. These are smart outlets controllable through Ethernet and/or WiFi that reports consumptions (Netio4all). +The `netio` switch platform allows you to control your [Netio](https://www.netio-products.com/en/overview/) Netio4, Netio4 All, and Netio 230B. These are smart outlets controllable through Ethernet and/or WiFi that reports consumptions (Netio4all). To use Netio devices in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/neurio_energy.markdown b/source/_integrations/neurio_energy.markdown index cc3d721fbce..81bd24b41f9 100644 --- a/source/_integrations/neurio_energy.markdown +++ b/source/_integrations/neurio_energy.markdown @@ -8,7 +8,7 @@ ha_iot_class: Cloud Polling ha_release: 0.14 --- -Integrate your [Neurio](http://neur.io/) meter information into Home Assistant. To get an API key and secret, login to your [Neurio account](https://my.neur.io/#settings/applications/register) and register an application. Note the Homepage URL and Callback URL are optional. +Integrate your [Neurio](https://neur.io/) meter information into Home Assistant. To get an API key and secret, login to your [Neurio account](https://my.neur.io/#settings/applications/register) and register an application. Note the Homepage URL and Callback URL are optional. To enable this sensor in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/nissan_leaf.markdown b/source/_integrations/nissan_leaf.markdown index 9d2179684b7..0420bee71d5 100644 --- a/source/_integrations/nissan_leaf.markdown +++ b/source/_integrations/nissan_leaf.markdown @@ -8,7 +8,7 @@ ha_release: 0.89 ha_iot_class: Cloud Polling --- -The `nissan_leaf` integration offers integration with the [NissanConnect EV](http://youplus.nissan.co.uk/GB/en/YouPlus/ConnectedServices.html) cloud service. NissanConnect EV was previously known as Nissan Carwings. It offers: +The `nissan_leaf` integration offers integration with the [NissanConnect EV](https://youplus.nissan.co.uk/GB/en/YouPlus/ConnectedServices.html) cloud service. NissanConnect EV was previously known as Nissan Carwings. It offers: * sensors for the battery status, range and charging status * a switch to start and stop the climate control diff --git a/source/_integrations/notify.knx.markdown b/source/_integrations/notify.knx.markdown index 3be61d37e65..1d536fd88d0 100644 --- a/source/_integrations/notify.knx.markdown +++ b/source/_integrations/notify.knx.markdown @@ -14,7 +14,7 @@ The `knx` integration must be configured correctly to use this integration, see
-The `knx` notify platform allows you to send notifications to [KNX](http://www.knx.org) devices. +The `knx` notify platform allows you to send notifications to [KNX](https://www.knx.org/) devices. ## Configuration diff --git a/source/_integrations/notify.mysensors.markdown b/source/_integrations/notify.mysensors.markdown index dd6722a61a8..7dc8aeac619 100644 --- a/source/_integrations/notify.mysensors.markdown +++ b/source/_integrations/notify.mysensors.markdown @@ -38,8 +38,8 @@ For more information, visit the [api] page 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_DEBUG @@ -93,4 +93,4 @@ For more information, visit the [api] page of MySensors. ``` [main component]: /integrations/mysensors/ -[api]: http://www.mysensors.org/download/ +[api]: https://www.mysensors.org/download/ diff --git a/source/_integrations/nuheat.markdown b/source/_integrations/nuheat.markdown index 9256f6605e5..7f5de3858fb 100644 --- a/source/_integrations/nuheat.markdown +++ b/source/_integrations/nuheat.markdown @@ -8,7 +8,7 @@ ha_release: 0.61 ha_iot_class: Cloud Polling --- -The `nuheat` integration lets control your connected [NuHeat Signature](http://www.nuheat.com/products/thermostats/signature-thermostat) floor heating thermostats from [NuHeat](http://www.nuheat.com/). +The `nuheat` integration lets control your connected [NuHeat Signature](https://www.nuheat.com/products/thermostats/signature-thermostat) floor heating thermostats from [NuHeat](https://www.nuheat.com/). There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/nuimo_controller.markdown b/source/_integrations/nuimo_controller.markdown index 452926a2e1a..0f808c1fab5 100644 --- a/source/_integrations/nuimo_controller.markdown +++ b/source/_integrations/nuimo_controller.markdown @@ -8,7 +8,7 @@ ha_release: 0.29 ha_iot_class: Local Polling --- -The `nuimo_controller` integration allows you to connect to a [Nuimo](http://www.senic.com/) device for receiving input events and displaying on the LED matrix via the [Nuimo SDK for Python on Linux](https://github.com/getSenic/nuimo-linux-python). +The `nuimo_controller` integration allows you to connect to a [Nuimo](https://www.senic.com/) device for receiving input events and displaying on the LED matrix via the [Nuimo SDK for Python on Linux](https://github.com/getSenic/nuimo-linux-python). To connect to a Nuimo device add the following section to your `configuration.yaml` file: diff --git a/source/_integrations/nut.markdown b/source/_integrations/nut.markdown index 90ca6989cf7..7b7dad1e9f9 100644 --- a/source/_integrations/nut.markdown +++ b/source/_integrations/nut.markdown @@ -8,7 +8,7 @@ ha_iot_class: Local Polling ha_release: 0.34 --- -The `nut` sensor platform allows you to monitor a UPS (battery backup) by using data from a [NUT](http://networkupstools.org/) (Network UPS Tools) server. +The `nut` sensor platform allows you to monitor a UPS (battery backup) by using data from a [NUT](https://networkupstools.org/) (Network UPS Tools) server. ## Configuration diff --git a/source/_integrations/nx584.markdown b/source/_integrations/nx584.markdown index 19ad189813e..d35c93faac0 100644 --- a/source/_integrations/nx584.markdown +++ b/source/_integrations/nx584.markdown @@ -9,7 +9,7 @@ ha_release: 0.13 ha_iot_class: Local Push --- -The `nx584` platform provides integration with GE, Caddx, Interlogix (and other brands) alarm panels that support the NX584 interface module (or have it built in). Supported panels include NX4/6/8/8E. Actual integration is done through [pynx584](http://github.com/kk7ds/pynx584) which is required for this to work. +The `nx584` platform provides integration with GE, Caddx, Interlogix (and other brands) alarm panels that support the NX584 interface module (or have it built in). Supported panels include NX4/6/8/8E. Actual integration is done through [pynx584](https://github.com/kk7ds/pynx584) which is required for this to work. There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/nzbget.markdown b/source/_integrations/nzbget.markdown index d39e6530796..637acca2f3b 100644 --- a/source/_integrations/nzbget.markdown +++ b/source/_integrations/nzbget.markdown @@ -8,7 +8,7 @@ ha_iot_class: Local Polling ha_release: 0.17 --- -The `nzbget` platform will allow you to monitor and control your downloads with [NZBGet](http://NZBGet.net) from within Home Assistant and setup automation based on the information. +The `nzbget` platform will allow you to monitor and control your downloads with [NZBGet](https://nzbget.net/) from within Home Assistant and setup automation based on the information. ## Configuration diff --git a/source/_integrations/octoprint.markdown b/source/_integrations/octoprint.markdown index 39083071523..a3b3caf7c02 100644 --- a/source/_integrations/octoprint.markdown +++ b/source/_integrations/octoprint.markdown @@ -10,7 +10,7 @@ ha_release: 0.19 ha_iot_class: Local Polling --- -[OctoPrint](http://octoprint.org/) is a web interface for your 3D printer. This is the main integration to integrate OctoPrint sensors. +[OctoPrint](https://octoprint.org/) is a web interface for your 3D printer. This is the main integration to integrate OctoPrint sensors. There is currently support for the following device types within Home Assistant: @@ -23,7 +23,7 @@ You must have the OctoPrint component configured (b ## Configuration -To get started with the OctoPrint API, please follow the directions on their [site](http://docs.octoprint.org/en/master/api/general.html). Once OctoPrint is configured you will need to add your API key and host to your `configuration.yaml`. +To get started with the OctoPrint API, please follow the directions on their [site](https://docs.octoprint.org/en/master/api/general.html). Once OctoPrint is configured you will need to add your API key and host to your `configuration.yaml`. ```yaml octoprint: diff --git a/source/_integrations/oem.markdown b/source/_integrations/oem.markdown index 68d40d46253..8aca1602c56 100644 --- a/source/_integrations/oem.markdown +++ b/source/_integrations/oem.markdown @@ -8,7 +8,7 @@ ha_release: 0.39 ha_iot_class: Local Polling --- -This platform supports the ESP8266 based "WiFi MQTT Relay / Thermostat" sold by [OpenEnergyMonitor](https://shop.openenergymonitor.com/wifi-mqtt-relay-thermostat/). The underlying [library](http://oemthermostat.readthedocs.io/) only supports this single relay variant of the [original device](https://harizanov.com/2014/12/wifi-iot-3-channel-relay-board-with-mqtt-and-http-api-using-esp8266/). +This platform supports the ESP8266 based "WiFi MQTT Relay / Thermostat" sold by [OpenEnergyMonitor](https://shop.openenergymonitor.com/wifi-mqtt-relay-thermostat/). The underlying [library](https://oemthermostat.readthedocs.io/) only supports this single relay variant of the [original device](https://harizanov.com/2014/12/wifi-iot-3-channel-relay-board-with-mqtt-and-http-api-using-esp8266/). This platform controls the setpoint of the thermostat in its "manual" mode. diff --git a/source/_integrations/onewire.markdown b/source/_integrations/onewire.markdown index 6eb22f9b6f0..c2d1d1e3e5f 100644 --- a/source/_integrations/onewire.markdown +++ b/source/_integrations/onewire.markdown @@ -31,7 +31,7 @@ To edit `/boot/config.txt` on Hass.io use [this documentation](https://developer ### owfs -When an interface adapter is used, sensors can be accessed on Linux hosts via [owfs 1-Wire file system](http://owfs.org/). When using an interface adapter and the owfs, the `mount_dir` option must be configured to correspond a directory, where owfs device tree has been mounted. +When an interface adapter is used, sensors can be accessed on Linux hosts via [owfs 1-Wire file system](https://owfs.org/). When using an interface adapter and the owfs, the `mount_dir` option must be configured to correspond a directory, where owfs device tree has been mounted. ### Units with multiple sensors diff --git a/source/_integrations/openalpr_cloud.markdown b/source/_integrations/openalpr_cloud.markdown index aa0f07d0a9e..9ff8b1d2c5d 100644 --- a/source/_integrations/openalpr_cloud.markdown +++ b/source/_integrations/openalpr_cloud.markdown @@ -7,7 +7,7 @@ ha_category: ha_release: 0.36 --- -[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you +[OpenALPR](https://www.openalpr.com/) integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other [automation](/integrations/automation/). diff --git a/source/_integrations/openalpr_local.markdown b/source/_integrations/openalpr_local.markdown index fa2ec2f62c0..ece346d59ff 100644 --- a/source/_integrations/openalpr_local.markdown +++ b/source/_integrations/openalpr_local.markdown @@ -7,7 +7,7 @@ ha_category: ha_release: 0.36 --- -[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you +[OpenALPR](https://www.openalpr.com/) integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other [automation](/integrations/automation/). diff --git a/source/_integrations/opencv.markdown b/source/_integrations/opencv.markdown index d1bdd1deee6..8cff1ca6c88 100644 --- a/source/_integrations/opencv.markdown +++ b/source/_integrations/opencv.markdown @@ -7,7 +7,7 @@ ha_category: ha_release: 0.47 --- -[OpenCV](http://www.opencv.org) is an open source computer vision image and video processing library. +[OpenCV](https://www.opencv.org/) is an open source computer vision image and video processing library. Some pre-defined classifiers can be found [here](https://github.com/opencv/opencv/tree/master/data). diff --git a/source/_integrations/openhardwaremonitor.markdown b/source/_integrations/openhardwaremonitor.markdown index e4db4105182..81f0809b6df 100644 --- a/source/_integrations/openhardwaremonitor.markdown +++ b/source/_integrations/openhardwaremonitor.markdown @@ -8,7 +8,7 @@ ha_release: 0.48 ha_iot_class: Local Polling --- -The `openhardwaremonitor` platform uses your [Open Hardware Monitor](http://openhardwaremonitor.org/) installation as a source for sensors that will display system information. +The `openhardwaremonitor` platform uses your [Open Hardware Monitor](https://openhardwaremonitor.org/) installation as a source for sensors that will display system information. ## Setup diff --git a/source/_integrations/openweathermap.markdown b/source/_integrations/openweathermap.markdown index 0f8e7847bf4..e5e1ced56a2 100644 --- a/source/_integrations/openweathermap.markdown +++ b/source/_integrations/openweathermap.markdown @@ -9,14 +9,14 @@ ha_release: 0.32 ha_iot_class: Cloud Polling --- -The `openweathermap` weather platform uses [OpenWeatherMap](http://openweathermap.org/) as a source for current meteorological data for your location. +The `openweathermap` weather platform uses [OpenWeatherMap](https://openweathermap.org/) as a source for current meteorological data for your location. There is currently support for the following device types within Home Assistant: - [Sensor](#sensor) - [Weather](#weather) -You need an API key which is free but requires a [registration](http://home.openweathermap.org/users/sign_up). +You need an API key which is free but requires a [registration](https://home.openweathermap.org/users/sign_up). ## Weather @@ -31,7 +31,7 @@ weather: {% configuration %} api_key: - description: Your API key for [OpenWeatherMap](http://openweathermap.org/). + description: Your API key for [OpenWeatherMap](https://openweathermap.org/). required: true type: string name: @@ -64,7 +64,7 @@ This platform is an alternative to the [`openweathermap`](/integrations/openweat ## Sensor -The `openweathermap` platform uses [OpenWeatherMap](http://openweathermap.org/) as a source for current meteorological data for your location. The `forecast` will show you the condition in 3h. +The `openweathermap` platform uses [OpenWeatherMap](https://openweathermap.org/) as a source for current meteorological data for your location. The `forecast` will show you the condition in 3h. To add OpenWeatherMap sensor to your installation, add the following to your `configuration.yaml` file: @@ -124,4 +124,4 @@ monitored_conditions: description: The current weather condition code. {% endconfiguration %} -Details about the API are available in the [OpenWeatherMap documentation](http://openweathermap.org/api). +Details about the API are available in the [OpenWeatherMap documentation](https://openweathermap.org/api). diff --git a/source/_integrations/owntracks.markdown b/source/_integrations/owntracks.markdown index 0a27208539a..77e265ac160 100644 --- a/source/_integrations/owntracks.markdown +++ b/source/_integrations/owntracks.markdown @@ -61,7 +61,7 @@ max_gps_accuracy: required: false type: integer waypoints: - description: "Owntracks users can define [waypoints](http://owntracks.org/booklet/features/waypoints/) (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is `true`, the Owntracks users who are in `waypoint_whitelist` can export waypoints from the device and Home Assistant will import them as zone definitions." + description: "Owntracks users can define [waypoints](https://owntracks.org/booklet/features/waypoints/) (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is `true`, the Owntracks users who are in `waypoint_whitelist` can export waypoints from the device and Home Assistant will import them as zone definitions." required: false default: true type: boolean @@ -71,7 +71,7 @@ waypoint_whitelist: default: All users who are connected to Home Assistant via Owntracks. type: list secret: - description: "[Payload encryption key](http://owntracks.org/booklet/features/encrypt/). This is usable when communicating with a third-party untrusted server or a public server (where anybody can subscribe to any topic). By default the payload is assumed to be unencrypted (although the communication between Home Assistant and the server might still be encrypted). This feature requires the `libsodium` library to be present." + description: "[Payload encryption key](https://owntracks.org/booklet/features/encrypt/). This is usable when communicating with a third-party untrusted server or a public server (where anybody can subscribe to any topic). By default the payload is assumed to be unencrypted (although the communication between Home Assistant and the server might still be encrypted). This feature requires the `libsodium` library to be present." required: false type: string mqtt_topic: @@ -109,7 +109,7 @@ owntracks: ## Using Owntracks regions -Owntracks can track regions, and send region entry and exit information to Home Assistant. You set up a region in the Owntracks app which you should name the same as your Home Assistant Zone, and then make sure to turn on the `share` option for the region in the owntracks app. Please see the [owntracks documentation](http://owntracks.org/booklet/guide/waypoints/). +Owntracks can track regions, and send region entry and exit information to Home Assistant. You set up a region in the Owntracks app which you should name the same as your Home Assistant Zone, and then make sure to turn on the `share` option for the region in the owntracks app. Please see the [owntracks documentation](https://owntracks.org/booklet/guide/waypoints/). Home Assistant will use the enter and leave messages to set your zone location. Your location will be set to the center of zone when you enter. Location updates from OwnTracks will be ignored while you are inside a zone. @@ -123,7 +123,7 @@ Owntracks v2.0.0 removes support for iBeacons on Android. When run in the usual *significant changes mode* (which is kind to your phone battery), Owntracks sometimes doesn't update your location as quickly as you'd like when you arrive at a zone. This can be annoying if you want to trigger an automation when you get home. You can improve the situation using iBeacons. -iBeacons are simple Bluetooth devices that send out an "I'm here" message. They are supported by IOS and some Android devices. Owntracks explain more [here](http://owntracks.org/booklet/guide/beacons/). +iBeacons are simple Bluetooth devices that send out an "I'm here" message. They are supported by IOS and some Android devices. Owntracks explain more [here](https://owntracks.org/booklet/guide/beacons/). When you enter an iBeacon region, Owntracks will send a `region enter` message to HA as described above. So if you want to have an event triggered when you arrive home, you can put an iBeacon outside your front door. If you set up an OwnTracks iBeacon region called `home` then getting close to the beacon will trigger an update to HA that will set your zone to be `home`. diff --git a/source/_integrations/pjlink.markdown b/source/_integrations/pjlink.markdown index b9332371ea8..2e3cf757324 100644 --- a/source/_integrations/pjlink.markdown +++ b/source/_integrations/pjlink.markdown @@ -8,7 +8,7 @@ ha_release: 0.76 ha_iot_class: Local Polling --- -The `pjlink` platform allows you to control from Home Assistant, projectors with support for the [PJLink protocol](http://pjlink.jbmia.or.jp/english/index.html). +The `pjlink` platform allows you to control from Home Assistant, projectors with support for the [PJLink protocol](https://pjlink.jbmia.or.jp/english/index.html). ## Configuration diff --git a/source/_integrations/pvoutput.markdown b/source/_integrations/pvoutput.markdown index eb6b4bce08e..7aec4695b7b 100644 --- a/source/_integrations/pvoutput.markdown +++ b/source/_integrations/pvoutput.markdown @@ -8,7 +8,7 @@ ha_release: 0.33 ha_iot_class: Cloud Polling --- -The `pvoutput` sensor platform consumes information from [PVOutput](http://pvoutput.org/) which were uploaded by your solar photovoltaic (PV) system. +The `pvoutput` sensor platform consumes information from [PVOutput](https://pvoutput.org/) which were uploaded by your solar photovoltaic (PV) system. To add PVOutput details to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/qwikswitch.markdown b/source/_integrations/qwikswitch.markdown index d5acc814df9..f243a567de0 100644 --- a/source/_integrations/qwikswitch.markdown +++ b/source/_integrations/qwikswitch.markdown @@ -11,7 +11,7 @@ ha_category: ha_release: "0.20" --- -The `qwikswitch` integration is the main integration to integrate various [QwikSwitch](http://www.qwikswitch.co.za/) devices with Home Assistant. The integration requires the QSUSB Modem device and connects to the QS Mobile application. +The `qwikswitch` integration is the main integration to integrate various [QwikSwitch](https://www.qwikswitch.co.za/) devices with Home Assistant. The integration requires the QSUSB Modem device and connects to the QS Mobile application. There is currently support for the following device types within Home Assistant: @@ -137,6 +137,6 @@ qwikswitch: ### Switch -The `qwikswitch` platform allows you to control your [QwikSwitch](http://www.qwikswitch.co.za/) relays as switches from within Home Assistant. +The `qwikswitch` platform allows you to control your [QwikSwitch](https://www.qwikswitch.co.za/) relays as switches from within Home Assistant. If the device name in the QS Mobile application ends with `Switch` it will be created as a switch, otherwise as a light. diff --git a/source/_integrations/rachio.markdown b/source/_integrations/rachio.markdown index fb95a2da6bb..b590233f330 100644 --- a/source/_integrations/rachio.markdown +++ b/source/_integrations/rachio.markdown @@ -10,11 +10,11 @@ ha_iot_class: Cloud Push ha_release: 0.73 --- -The `rachio` platform allows you to control your [Rachio irrigation system](http://rachio.com/). +The `rachio` platform allows you to control your [Rachio irrigation system](https://rachio.com/). There is currently support for the following device types within Home Assistant: -- **Binary Sensor** - Allows you to view the status of your [Rachio irrigation system](http://rachio.com/). +- **Binary Sensor** - Allows you to view the status of your [Rachio irrigation system](https://rachio.com/). - [**Switch**](#switch) They will be automatically added if the Rachio integration integration is loaded. @@ -73,7 +73,7 @@ panel_iframe: ## Switch -The `rachio` switch platform allows you to toggle zones connected to your [Rachio irrigation system](http://rachio.com/) on and off. +The `rachio` switch platform allows you to toggle zones connected to your [Rachio irrigation system](https://rachio.com/) on and off. Once configured, a switch will be added for every zone that is enabled on every controller in the account provided, as well as a switch to toggle each controller's standby mode. diff --git a/source/_integrations/radiotherm.markdown b/source/_integrations/radiotherm.markdown index c87edb9bbc1..a699c331423 100644 --- a/source/_integrations/radiotherm.markdown +++ b/source/_integrations/radiotherm.markdown @@ -8,7 +8,7 @@ ha_iot_class: Local Polling ha_release: 0.7.6 --- -The `radiotherm` climate platform let you control a thermostat from [Radio Thermostat](http://www.radiothermostat.com/) or [3M Filtrete](https://www.filtrete.com/). Your thermostat must have the Wi-Fi module installed and connected to your network. +The `radiotherm` climate platform let you control a thermostat from [Radio Thermostat](https://www.radiothermostat.com/) or [3M Filtrete](https://www.filtrete.com/). Your thermostat must have the Wi-Fi module installed and connected to your network. The underlying library supports: diff --git a/source/_integrations/rainbird.markdown b/source/_integrations/rainbird.markdown index 338f5ff089a..dd240c9c20d 100644 --- a/source/_integrations/rainbird.markdown +++ b/source/_integrations/rainbird.markdown @@ -10,7 +10,7 @@ ha_release: 0.61 ha_iot_class: Local Polling --- -This `rainbird` integration allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant. +This `rainbird` integration allows interacting with [LNK WiFi](https://www.rainbird.com/products/lnk-wifi-module) module of the Rain Bird Irrigation system in Home Assistant. There is currently support for the following device types within Home Assistant: @@ -95,13 +95,13 @@ Please note that due to the implementation of the API within the LNK Module, the ## Sensor -This `rainbird` sensor allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant. +This `rainbird` sensor allows interacting with [LNK WiFi](https://www.rainbird.com/products/lnk-wifi-module) module of the Rain Bird Irrigation system in Home Assistant. The integration adds `rainsensor` and `raindelay` sensors and their `binary_sensor` alternatives. ## Switch -This `rainbird` switch platform allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant. +This `rainbird` switch platform allows interacting with [LNK WiFi](https://www.rainbird.com/products/lnk-wifi-module) module of the Rain Bird Irrigation system in Home Assistant. Switches are automatically added for all available zones of configured controllers. diff --git a/source/_integrations/rainmachine.markdown b/source/_integrations/rainmachine.markdown index b7316803f7d..c0e4eb1daba 100644 --- a/source/_integrations/rainmachine.markdown +++ b/source/_integrations/rainmachine.markdown @@ -11,7 +11,7 @@ ha_release: 0.69 ha_iot_class: Local Polling --- -The `rainmachine` integration is the main integration to integrate all platforms related to [RainMachine smart Wi-Fi sprinkler controllers](http://www.rainmachine.com/). +The `rainmachine` integration is the main integration to integrate all platforms related to [RainMachine smart Wi-Fi sprinkler controllers](https://www.rainmachine.com/). There is currently support for the following device types within Home Assistant: @@ -188,7 +188,7 @@ Unpause all watering activities. ## Switch -The `rainmachine` switch platform allows you to control programs and zones within a [RainMachine smart Wi-Fi sprinkler controller](http://www.rainmachine.com/). +The `rainmachine` switch platform allows you to control programs and zones within a [RainMachine smart Wi-Fi sprinkler controller](https://www.rainmachine.com/). ### Controlling Your Device diff --git a/source/_integrations/raspihats.markdown b/source/_integrations/raspihats.markdown index 66ea6bd0097..df01e666189 100644 --- a/source/_integrations/raspihats.markdown +++ b/source/_integrations/raspihats.markdown @@ -14,7 +14,7 @@ The `raspihats` integration is the base for all related Raspihats platforms in H ## Binary Sensor -The `raspihats` binary sensor platform allows you to read sensor values ​​using the digital inputs of the [raspihats](http://www.raspihats.com/) boards. +The `raspihats` binary sensor platform allows you to read sensor values ​​using the digital inputs of the [raspihats](https://www.raspihats.com/) boards. ## Configuration @@ -118,11 +118,11 @@ It will output a table like this: 70: -- -- -- -- -- -- -- 77 ``` -For more details about the `raspihats` add-on boards for Raspberry Pi, visit [raspihats.com](http://www.raspihats.com/). +For more details about the `raspihats` add-on boards for Raspberry Pi, visit [raspihats.com](https://www.raspihats.com/). ## Switch -The `raspihats` switch platform allows you to control the digital outputs of your [Raspihats](http://www.raspihats.com/) boards. +The `raspihats` switch platform allows you to control the digital outputs of your [Raspihats](https://www.raspihats.com/) boards. ## Configuration @@ -226,4 +226,4 @@ It will output a table like this: 70: -- -- -- -- -- -- -- 77 ``` -For more details about the Raspihats add-on boards for Raspberry Pi, visit [raspihats.com](http://www.raspihats.com/). +For more details about the Raspihats add-on boards for Raspberry Pi, visit [raspihats.com](https://www.raspihats.com/). diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown index 0bf321064f7..bb0714050b7 100644 --- a/source/_integrations/recorder.markdown +++ b/source/_integrations/recorder.markdown @@ -10,7 +10,7 @@ ha_qa_scale: internal The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history` integration](/integrations/history/). -Home Assistant uses [SQLAlchemy](http://www.sqlalchemy.org/), which is an Object Relational Mapper (ORM). This means that you can use **any** SQL backend for the recorder that is supported by SQLAlchemy, like [MySQL](https://www.mysql.com/), [MariaDB](https://mariadb.org/), [PostgreSQL](https://www.postgresql.org/), or [MS SQL Server](https://www.microsoft.com/en-us/sql-server/). +Home Assistant uses [SQLAlchemy](https://www.sqlalchemy.org/), which is an Object Relational Mapper (ORM). This means that you can use **any** SQL backend for the recorder that is supported by SQLAlchemy, like [MySQL](https://www.mysql.com/), [MariaDB](https://mariadb.org/), [PostgreSQL](https://www.postgresql.org/), or [MS SQL Server](https://www.microsoft.com/en-us/sql-server/). The default database engine is [SQLite](https://www.sqlite.org/) which doesn't require any configuration. The database is stored in your Home Assistant configuration directory (`.homeassistant` or '/config/' in HassIO) and called `home-assistant_v2.db`. diff --git a/source/_integrations/rejseplanen.markdown b/source/_integrations/rejseplanen.markdown index 8d54e29a1d6..889ce969f05 100644 --- a/source/_integrations/rejseplanen.markdown +++ b/source/_integrations/rejseplanen.markdown @@ -73,7 +73,7 @@ departure_type: ## Direction If you use the `direction` filter it's important to put correct destination or else the sensor will not work at all. -The direction has to be the destination(s) for the transport type(s) for the departure stop destination, and NOT the stop where you want to get off. Check [http://rejseplanen.dk](http://rejseplanen.dk), make a search and use the destinations from there in your configuration. Make sure you use the exact name as the destination(s). +The direction has to be the destination(s) for the transport type(s) for the departure stop destination, and NOT the stop where you want to get off. Check [https://rejseplanen.dk/](https://rejseplanen.dk/), make a search and use the destinations from there in your configuration. Make sure you use the exact name as the destination(s). A working example on how to use this sensor with direction: diff --git a/source/_integrations/rest.markdown b/source/_integrations/rest.markdown index 84bd6d59985..54b669718ce 100644 --- a/source/_integrations/rest.markdown +++ b/source/_integrations/rest.markdown @@ -103,7 +103,7 @@ force_update: Make sure that the URL exactly matches your endpoint or resource.
-`curl` can help you identify the variable you want to display in your Home Assistant frontend. The example below shows the JSON response of a device that is running with [aREST](http://arest.io/). +`curl` can help you identify the variable you want to display in your Home Assistant frontend. The example below shows the JSON response of a device that is running with [aREST](https://arest.io/). ```bash $ curl -X GET http://192.168.1.31/temperature/ @@ -116,7 +116,7 @@ In this section you find some real-life examples of how to use this sensor. ### External IP address -You can find your external IP address using the service [JSON Test](http://www.jsontest.com) at their [http://ip.jsontest.com/](http://ip.jsontest.com/) URL. +You can find your external IP address using the service [JSON Test](https://www.jsontest.com/) at their [http://ip.jsontest.com/](http://ip.jsontest.com/) URL. ```yaml sensor: @@ -217,7 +217,7 @@ sensor: ### Fetch multiple JSON values and present them as attributes -[JSON Test](http://www.jsontest.com) returns the current time, date and milliseconds since epoch from [http://date.jsontest.com/](http://date.jsontest.com/). +[JSON Test](https://www.jsontest.com/) returns the current time, date and milliseconds since epoch from [http://date.jsontest.com/](http://date.jsontest.com/). {% raw %} ```yaml @@ -240,7 +240,7 @@ sensor: ``` {% endraw %} -This sample fetches a weather report from [OpenWeatherMap](http://openweathermap.org/), maps the resulting data into attributes of the RESTful sensor and then creates a set of [template](/integrations/template) sensors that monitor the attributes and present the values in a usable form. +This sample fetches a weather report from [OpenWeatherMap](https://openweathermap.org/), maps the resulting data into attributes of the RESTful sensor and then creates a set of [template](/integrations/template) sensors that monitor the attributes and present the values in a usable form. {% raw %} ```yaml @@ -251,12 +251,12 @@ sensor: - main - weather value_template: '{{ value_json["weather"][0]["description"].title() }}' - resource: http://api.openweathermap.org/data/2.5/weather?zip=80302,us&APPID=VERYSECRETAPIKEY + resource: https://api.openweathermap.org/data/2.5/weather?zip=80302,us&APPID=VERYSECRETAPIKEY - platform: template sensors: owm_weather: value_template: '{{ state_attr('sensor.owm_report', 'weather')[0]["description"].title() }}' - entity_picture_template: '{{ "http://openweathermap.org/img/w/"+state_attr('sensor.owm_report', 'weather')[0]["icon"].lower()+".png" }}' + entity_picture_template: '{{ "https://openweathermap.org/img/w/"+state_attr('sensor.owm_report', 'weather')[0]["icon"].lower()+".png" }}' entity_id: sensor.owm_report owm_temp: friendly_name: 'Outside temp' diff --git a/source/_integrations/roku.markdown b/source/_integrations/roku.markdown index 9babb4a3f58..578e5054dda 100644 --- a/source/_integrations/roku.markdown +++ b/source/_integrations/roku.markdown @@ -10,7 +10,7 @@ ha_iot_class: Local Polling ha_release: 0.86 --- -The [Roku](http://www.roku.com/) integration allows integration of Roku, which will be automatically discovered if you enable the [discovery component](/integrations/discovery/). +The [Roku](https://www.roku.com/) integration allows integration of Roku, which will be automatically discovered if you enable the [discovery component](/integrations/discovery/). There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/roomba.markdown b/source/_integrations/roomba.markdown index 925ae07841d..c205470f74e 100644 --- a/source/_integrations/roomba.markdown +++ b/source/_integrations/roomba.markdown @@ -7,7 +7,7 @@ ha_category: ha_release: 0.51 --- -The `roomba` integration allows you to control your [iRobot Roomba](http://www.irobot.com/For-the-Home/Vacuuming/Roomba.aspx) vacuum. +The `roomba` integration allows you to control your [iRobot Roomba](https://www.irobot.com/For-the-Home/Vacuuming/Roomba.aspx) vacuum.

diff --git a/source/_integrations/rpi_gpio_pwm.markdown b/source/_integrations/rpi_gpio_pwm.markdown index 1e194632067..3fcb775584e 100644 --- a/source/_integrations/rpi_gpio_pwm.markdown +++ b/source/_integrations/rpi_gpio_pwm.markdown @@ -67,7 +67,7 @@ In this section you find some real-life examples of how to use this sensor. ### RGB LED connected to PCA9685 controller -This example uses a [PCA9685 controller](http://www.nxp.com/products/interfaces/ic-bus-portfolio/ic-led-display-control/16-channel-12-bit-pwm-fm-plus-ic-bus-led-controller:PCA9685) to control a RGB LED. +This example uses a [PCA9685 controller](https://www.nxp.com/products/interfaces/ic-bus-portfolio/ic-led-display-control/16-channel-12-bit-pwm-fm-plus-ic-bus-led-controller:PCA9685) to control a RGB LED. ```yaml # Example configuration.yaml entry @@ -82,7 +82,7 @@ light: ### RGBW LED connected to PCA9685 controller -This example uses a [PCA9685 controller](http://www.nxp.com/products/interfaces/ic-bus-portfolio/ic-led-display-control/16-channel-12-bit-pwm-fm-plus-ic-bus-led-controller:PCA9685) to interact with a RGBW LED. +This example uses a [PCA9685 controller](https://www.nxp.com/products/interfaces/ic-bus-portfolio/ic-led-display-control/16-channel-12-bit-pwm-fm-plus-ic-bus-led-controller:PCA9685) to interact with a RGBW LED. ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/samsungtv.markdown b/source/_integrations/samsungtv.markdown index 7ddde044a7d..42a4a548e20 100644 --- a/source/_integrations/samsungtv.markdown +++ b/source/_integrations/samsungtv.markdown @@ -8,7 +8,7 @@ ha_release: 0.13 ha_iot_class: Local Polling --- -The `samsungtv` platform allows you to control a [Samsung Smart TV](http://www.samsung.com/uk/consumer/tv-audio-video/televisions/). +The `samsungtv` platform allows you to control a [Samsung Smart TV](https://www.samsung.com/uk/tvs/all-tvs/). ### Setup diff --git a/source/_integrations/scene.knx.markdown b/source/_integrations/scene.knx.markdown index f0c00eb4c94..741c4e6039b 100644 --- a/source/_integrations/scene.knx.markdown +++ b/source/_integrations/scene.knx.markdown @@ -13,7 +13,7 @@ The `knx` integration must be configured correctly to use this integration, see

-The `knx` scenes platform allows you to trigger [KNX](http://www.knx.org) scenes. +The `knx` scenes platform allows you to trigger [KNX](https://www.knx.org/) scenes. ## Configuration diff --git a/source/_integrations/scrape.markdown b/source/_integrations/scrape.markdown index 4b68c7a22dd..892ba3712ca 100644 --- a/source/_integrations/scrape.markdown +++ b/source/_integrations/scrape.markdown @@ -123,13 +123,13 @@ sensor: ### IFTTT status -If you make heavy use of the [IFTTT](/integrations/ifttt/) web service for your automations and are curious about the [status of IFTTT](http://status.ifttt.com/) then you can display the current state of IFTTT in your frontend. +If you make heavy use of the [IFTTT](/integrations/ifttt/) web service for your automations and are curious about the [status of IFTTT](https://status.ifttt.com/) then you can display the current state of IFTTT in your frontend. ```yaml # Example configuration.yaml entry sensor: - platform: scrape - resource: http://status.ifttt.com/ + resource: https://status.ifttt.com/ name: IFTTT status select: '.component-status' ``` diff --git a/source/_integrations/scsgate.markdown b/source/_integrations/scsgate.markdown index 8d4a70eee34..34c3242c842 100644 --- a/source/_integrations/scsgate.markdown +++ b/source/_integrations/scsgate.markdown @@ -40,7 +40,7 @@ The SCSGate integration relies on the [scsgate](https://github.com/flavio/scsgat This module provides also a command line tool called `scs-monitor`. This program can be used to find the IDs of your lights, switches and roller shutters and produce the YAML snippet to insert into your `configuration.yaml` file. -For more information checkout [this](http://scsgate.readthedocs.org/en/latest/?badge=latest#creation-of-a-home-assistant-configuration-file) section of `scsgate`'s documentation. +For more information checkout [this](https://scsgate.readthedocs.org/en/latest/?badge=latest#creation-of-a-home-assistant-configuration-file) section of `scsgate`'s documentation. ### Cover diff --git a/source/_integrations/sensor.knx.markdown b/source/_integrations/sensor.knx.markdown index ff460640e7e..c68015799d5 100644 --- a/source/_integrations/sensor.knx.markdown +++ b/source/_integrations/sensor.knx.markdown @@ -14,7 +14,7 @@ The `knx` integration must be configured correctly to use this integration, see
-The `knx` sensor platform allows you to monitor [KNX](http://www.knx.org) sensors. +The `knx` sensor platform allows you to monitor [KNX](https://www.knx.org/) sensors. 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). diff --git a/source/_integrations/sensor.mysensors.markdown b/source/_integrations/sensor.mysensors.markdown index 24405bcfefd..6b84c8422da 100644 --- a/source/_integrations/sensor.mysensors.markdown +++ b/source/_integrations/sensor.mysensors.markdown @@ -72,10 +72,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/light + * https://www.mysensors.org/build/light */ #include @@ -120,10 +120,10 @@ void loop() ```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/light + * https://www.mysensors.org/build/light */ #define MY_DEBUG @@ -181,4 +181,4 @@ void receive(const MyMessage &message) { ``` [main component]: /integrations/mysensors/ -[serial api]: http://www.mysensors.org/download +[serial api]: https://www.mysensors.org/download diff --git a/source/_integrations/sensor.xiaomi_aqara.markdown b/source/_integrations/sensor.xiaomi_aqara.markdown index 3ba1686b9b2..d877edb9eaf 100644 --- a/source/_integrations/sensor.xiaomi_aqara.markdown +++ b/source/_integrations/sensor.xiaomi_aqara.markdown @@ -8,6 +8,6 @@ ha_release: "0.50" ha_iot_class: Local Push --- -The `xiaomi aqara` sensor platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) sensors. +The `xiaomi aqara` sensor platform allows you to get data from your [Xiaomi](https://www.mi.com/en/) sensors. The requirement is that you have setup [Xiaomi aqara](/integrations/xiaomi_aqara/). diff --git a/source/_integrations/sky_hub.markdown b/source/_integrations/sky_hub.markdown index b0937a64c19..dbd43e9fe8e 100644 --- a/source/_integrations/sky_hub.markdown +++ b/source/_integrations/sky_hub.markdown @@ -8,7 +8,7 @@ ha_release: 0.37 --- -The `sky_hub` platform offers presence detection by looking at connected devices to a [Sky Hub router](http://www.sky.com/shop/broadband-talk/sky-hub/) based router. +The `sky_hub` platform offers presence detection by looking at connected devices to a [Sky Hub router](https://www.sky.com/shop/broadband-talk/sky-hub/) based router. To use your Sky Hub device in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/skybeacon.markdown b/source/_integrations/skybeacon.markdown index c115a0b58eb..bb0563f93ef 100644 --- a/source/_integrations/skybeacon.markdown +++ b/source/_integrations/skybeacon.markdown @@ -7,7 +7,7 @@ ha_release: 0.37 ha_iot_class: Local Polling --- -The `skybeacon` sensor platform supports [CR2477](http://cnsky9.en.alibaba.com)-powered [iBeacon](https://en.wikipedia.org/wiki/IBeacon)/eddystone sensors that come with temperature/sensor module. +The `skybeacon` sensor platform supports [CR2477](https://cnsky9.en.alibaba.com/)-powered [iBeacon](https://en.wikipedia.org/wiki/IBeacon)/eddystone sensors that come with temperature/sensor module. ## Configuration diff --git a/source/_integrations/slack.markdown b/source/_integrations/slack.markdown index c873f3da9d7..7f68b1cc36e 100644 --- a/source/_integrations/slack.markdown +++ b/source/_integrations/slack.markdown @@ -59,7 +59,7 @@ username: type: string default: The user account or botname that you generated the API key as. icon: - description: Use one of the Slack emojis as an Icon for the supplied username. Slack uses the standard emoji sets used [here](http://www.webpagefx.com/tools/emoji-cheat-sheet/). + description: Use one of the Slack emojis as an Icon for the supplied username. Slack uses the standard emoji sets used [here](https://www.webpagefx.com/tools/emoji-cheat-sheet/). required: false type: string {% endconfiguration %} @@ -121,7 +121,7 @@ Example for posting formatted attachment: "attachments": [ { "title": "WHAT A HORRIBLE NIGHT TO HAVE A CURSE.", - "image_url": "http://i.imgur.com/JEExnsI.gif" + "image_url": "https://i.imgur.com/JEExnsI.gif" } ] } diff --git a/source/_integrations/sleepiq.markdown b/source/_integrations/sleepiq.markdown index 5bf4236dec6..ce55c4c9da4 100644 --- a/source/_integrations/sleepiq.markdown +++ b/source/_integrations/sleepiq.markdown @@ -10,7 +10,7 @@ ha_release: 0.29 ha_iot_class: Local Polling --- -The SleepIQ implementation lets you view sensor data from [SleepIQ by SleepNumber](http://www.sleepnumber.com/sn/en/sleepiq-sleep-tracker). In particular, it lets you see the occupancy and current SleepNumber (ie current firmness) of each side of a SleepNumber bed. +The SleepIQ implementation lets you view sensor data from [SleepIQ by SleepNumber](https://www.sleepnumber.com/sleepiq-sleep-tracker). In particular, it lets you see the occupancy and current SleepNumber (ie current firmness) of each side of a SleepNumber bed. ## Setup diff --git a/source/_integrations/sma.markdown b/source/_integrations/sma.markdown index 62cadd02f05..faccfba81d2 100644 --- a/source/_integrations/sma.markdown +++ b/source/_integrations/sma.markdown @@ -8,7 +8,7 @@ ha_iot_class: Local Polling ha_release: 0.36 --- -The `sma` sensor will poll a [SMA](http://www.sma-solar.com/) [(US)](http://www.sma-america.com/) solar inverter and present the values as sensors (or attributes of sensors) in Home Assistant. +The `sma` sensor will poll a [SMA](http://www.sma-solar.com/) [(US)](https://www.sma-america.com/) solar inverter and present the values as sensors (or attributes of sensors) in Home Assistant. This sensor uses the web interface and to use it, you have to be able to connect to the solar inverter from your favorite web browser. diff --git a/source/_integrations/smarthab.markdown b/source/_integrations/smarthab.markdown index 60e8eb98dff..e97965e6b3e 100644 --- a/source/_integrations/smarthab.markdown +++ b/source/_integrations/smarthab.markdown @@ -10,7 +10,7 @@ ha_category: ha_iot_class: Cloud Polling --- -If your home is fitted with [SmartHab](http://www.smarthab.fr/en/home/)'s +If your home is fitted with [SmartHab](https://www.smarthab.fr/en/home/)'s devices and you have access to their app-based services, you will be able to control your lights and shutters with the SmartHab integration for Home Assistant. diff --git a/source/_integrations/smhi.markdown b/source/_integrations/smhi.markdown index 207ea471ebd..a2642b3f06c 100644 --- a/source/_integrations/smhi.markdown +++ b/source/_integrations/smhi.markdown @@ -29,7 +29,7 @@ You can only add locations through the integrations page, not in configuration f
-Only location close to Sweden can be added. See [SMHI.se area](http://opendata.smhi.se/apidocs/metfcst/geographic_area.html) for more details what locations are supported. +Only location close to Sweden can be added. See [SMHI.se area](https://opendata.smhi.se/apidocs/metfcst/geographic_area.html) for more details what locations are supported.
@@ -51,4 +51,4 @@ name: default: Home {% endconfiguration %} -Details about the API are available in the [SMHI API documentation](http://opendata.smhi.se/apidocs/metfcst/index.html). +Details about the API are available in the [SMHI API documentation](https://opendata.smhi.se/apidocs/metfcst/index.html). diff --git a/source/_integrations/songpal.markdown b/source/_integrations/songpal.markdown index a9815b595b1..ac3977f1a71 100644 --- a/source/_integrations/songpal.markdown +++ b/source/_integrations/songpal.markdown @@ -10,7 +10,7 @@ ha_release: 0.65 The `songpal` platform allows you to control Sony's Songpal ("[Audio Control API](https://developer.sony.com/develop/audio-control-api/)") compatible devices such as soundbars, AV receivers and wireless speakers from Home Assistant. -Even when the API officially supports only a few devices (HT-ST5000, HT-MT500, HT-CT800, SRS-ZR5 and STR-DN1080), it has also been confirmed to work on others. [The list of supported devices](http://vssupport.sony.net/en_ww/device.html) from Sony's Songpal website lists devices which are likely to be compatible with this platform. +Even when the API officially supports only a few devices (HT-ST5000, HT-MT500, HT-CT800, SRS-ZR5 and STR-DN1080), it has also been confirmed to work on others. [The list of supported devices](https://vssupport.sony.net/en_ww/device.html) from Sony's Songpal website lists devices which are likely to be compatible with this platform. If the platform works with your non-listed device, or you encounter bugs, please feel free to [report them upstream](https://github.com/rytilahti/python-songpal). diff --git a/source/_integrations/sony_projector.markdown b/source/_integrations/sony_projector.markdown index 6659b297235..632cd71fa74 100644 --- a/source/_integrations/sony_projector.markdown +++ b/source/_integrations/sony_projector.markdown @@ -8,7 +8,7 @@ ha_iot_class: Local Polling ha_release: 0.89 --- -The `sony_projector` switch platform allows you to control the state of SDCP compatible network-connected projectors from [Sony](http://www.sony.com). +The `sony_projector` switch platform allows you to control the state of SDCP compatible network-connected projectors from [Sony](https://www.sony.com/). ## Configuration diff --git a/source/_integrations/spaceapi.markdown b/source/_integrations/spaceapi.markdown index 808e63bc6f4..719919b3952 100644 --- a/source/_integrations/spaceapi.markdown +++ b/source/_integrations/spaceapi.markdown @@ -276,7 +276,7 @@ In this section you find some real-life examples of how to use this component. ### Eastermundigen -A possible configuration entry for [Eastermundigen](http://www.eastermundigen.ch/), a Hackerspace in Switzerland, could look like this. +A possible configuration entry for [Eastermundigen](https://www.eastermundigen.ch/), a Hackerspace in Switzerland, could look like this. ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/spc.markdown b/source/_integrations/spc.markdown index ad6599ec8e7..f1caea63da4 100644 --- a/source/_integrations/spc.markdown +++ b/source/_integrations/spc.markdown @@ -12,7 +12,7 @@ ha_iot_class: Local Push Home Assistant has support to integrate your [Vanderbilt SPC](https://www.spcsupportinfo.com/SPCConnectPro/) alarm panel and any connected motion, door and smoke sensors. -Integration with SPC is done through a third-party API gateway called [SPC Web Gateway](http://www.lundix.se/smarta-losningar/) which must be installed and configured somewhere on your network. +Integration with SPC is done through a third-party API gateway called [SPC Web Gateway](https://www.lundix.se/smarta-losningar/) which must be installed and configured somewhere on your network. There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/splunk.markdown b/source/_integrations/splunk.markdown index 9aa909d2f16..d0718987d72 100644 --- a/source/_integrations/splunk.markdown +++ b/source/_integrations/splunk.markdown @@ -7,7 +7,7 @@ ha_category: ha_release: 0.13 --- -The `splunk` integration makes it possible to log all state changes to an external [Splunk](http://splunk.com/) database using Splunk's HTTP Event Collector (HEC) feature. You can either use this alone, or with the Home Assistant for Splunk [app](https://github.com/miniconfig/splunk-homeassistant). Since the HEC feature is new to Splunk, you will need to use at least version 6.3. +The `splunk` integration makes it possible to log all state changes to an external [Splunk](https://splunk.com/) database using Splunk's HTTP Event Collector (HEC) feature. You can either use this alone, or with the Home Assistant for Splunk [app](https://github.com/miniconfig/splunk-homeassistant). Since the HEC feature is new to Splunk, you will need to use at least version 6.3. ## Configuration diff --git a/source/_integrations/squeezebox.markdown b/source/_integrations/squeezebox.markdown index e9b09617c8e..c9e81bf4074 100644 --- a/source/_integrations/squeezebox.markdown +++ b/source/_integrations/squeezebox.markdown @@ -9,7 +9,7 @@ ha_iot_class: Local Polling --- -The `squeezebox` platform allows you to control a [Logitech Squeezebox](https://en.wikipedia.org/wiki/Squeezebox_%28network_music_player%29) music player from Home Assistant. This lets you control Squeezebox hardware like the Classic, Transporter, Duet, Boom, Radio and Touch and of software players like [SoftSqueeze](http://softsqueeze.sourceforge.net/), [SqueezePlayer](https://play.google.com/store/apps/details?id=de.bluegaspode.squeezeplayer) and [SqueezeSlave](http://forums.slimdevices.com/showthread.php?93607-ANNOUNCE-Squeezeslave-1-2-released). +The `squeezebox` platform allows you to control a [Logitech Squeezebox](https://en.wikipedia.org/wiki/Squeezebox_%28network_music_player%29) music player from Home Assistant. This lets you control Squeezebox hardware like the Classic, Transporter, Duet, Boom, Radio and Touch and of software players like [SoftSqueeze](http://softsqueeze.sourceforge.net/), [SqueezePlayer](https://play.google.com/store/apps/details?id=de.bluegaspode.squeezeplayer) and [SqueezeSlave](https://forums.slimdevices.com/showthread.php?93607-ANNOUNCE-Squeezeslave-1-2-released). To add your Squeezebox player to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/supla.markdown b/source/_integrations/supla.markdown index 4cd882893b7..cc2b3c4c330 100644 --- a/source/_integrations/supla.markdown +++ b/source/_integrations/supla.markdown @@ -9,7 +9,7 @@ ha_category: ha_iot_class: Cloud Polling --- -The [Supla](http://supla.org) is an Open Source home automation system for ESP8266 based devices. It has its own set of protocols, it's own firmware and commercially available devices (produced for example by [Zamel](https://supla.zamel.pl/)) +The [Supla](https://supla.org/) is an Open Source home automation system for ESP8266 based devices. It has its own set of protocols, it's own firmware and commercially available devices (produced for example by [Zamel](https://supla.zamel.pl/)) Currently only covers (shutters in Supla's lingo) and switches are supported, but, thanks to comprehensive and universal REST API, it's pretty easy to add more. diff --git a/source/_integrations/swiss_hydrological_data.markdown b/source/_integrations/swiss_hydrological_data.markdown index 799f6aa1db7..801dbaf3d34 100644 --- a/source/_integrations/swiss_hydrological_data.markdown +++ b/source/_integrations/swiss_hydrological_data.markdown @@ -57,4 +57,4 @@ Sensors are exposing additional values through their attributes for all availabl The sensors don't show the latest measurement, but those from the last hour due to the source of data. Some stations also don't provide data for certain measurements.
-The hydrological measurements are coming from the [Swiss Federal Office for the Environment (Bundesamt für Umwelt - Abt. Hydrologie)](http://www.hydrodaten.admin.ch) and are updated every 10 minutes. +The hydrological measurements are coming from the [Swiss Federal Office for the Environment (Bundesamt für Umwelt - Abt. Hydrologie)](https://www.hydrodaten.admin.ch/) and are updated every 10 minutes. diff --git a/source/_integrations/swiss_public_transport.markdown b/source/_integrations/swiss_public_transport.markdown index 4d3f73be3c5..7c07936f410 100644 --- a/source/_integrations/swiss_public_transport.markdown +++ b/source/_integrations/swiss_public_transport.markdown @@ -10,9 +10,9 @@ ha_release: pre 0.7 The `swiss_public_transport` sensor will give you the next three departure times from a given location to another one in Switzerland. -The [Swiss public transport API](http://transport.opendata.ch/) only allows 1000 requests per 24 hours. +The [Swiss public transport API](https://transport.opendata.ch/) only allows 1000 requests per 24 hours. -The [Stationboard](http://transport.opendata.ch/examples/stationboard.html) website can help to determine the exact name of the start and the end station. +The [Stationboard](https://transport.opendata.ch/examples/stationboard.html) website can help to determine the exact name of the start and the end station. Then add the data to your `configuration.yaml` file as shown in the example: @@ -40,4 +40,4 @@ name: default: Next Departure {% endconfiguration %} -The public timetables are coming from [Swiss public transport](http://transport.opendata.ch). +The public timetables are coming from [Swiss public transport](https://transport.opendata.ch/). diff --git a/source/_integrations/switch.command_line.markdown b/source/_integrations/switch.command_line.markdown index b01ae34e087..b7b9c2524e5 100644 --- a/source/_integrations/switch.command_line.markdown +++ b/source/_integrations/switch.command_line.markdown @@ -80,7 +80,7 @@ In this section you find some real-life examples of how to use this switch. The example below is doing the same as the [aREST switch](/integrations/arest#switch). -The command line tool [`curl`](http://curl.haxx.se/) is used to toggle a pin +The command line tool [`curl`](https://curl.haxx.se/) is used to toggle a pin which is controllable through REST. ```yaml diff --git a/source/_integrations/switch.mysensors.markdown b/source/_integrations/switch.mysensors.markdown index 7f212f5d937..03acee61f65 100644 --- a/source/_integrations/switch.mysensors.markdown +++ b/source/_integrations/switch.mysensors.markdown @@ -88,10 +88,10 @@ automation: ```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/relay + * https://www.mysensors.org/build/relay */ #include @@ -134,10 +134,10 @@ void incomingMessage(const MyMessage &message) ```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/ir + * https://www.mysensors.org/build/ir */ #include @@ -203,4 +203,4 @@ void incomingMessage(const MyMessage &message) { ``` [main component]: /integrations/mysensors/ -[serial api]: http://www.mysensors.org/download +[serial api]: https://www.mysensors.org/download diff --git a/source/_integrations/switch.xiaomi_aqara.markdown b/source/_integrations/switch.xiaomi_aqara.markdown index 98e9602334d..f6016df9043 100644 --- a/source/_integrations/switch.xiaomi_aqara.markdown +++ b/source/_integrations/switch.xiaomi_aqara.markdown @@ -8,6 +8,6 @@ ha_release: "0.50" ha_iot_class: Local Push --- -The `xiaomi_aqara` switch platform allows you to get data from your [Xiaomi aqara](http://www.mi.com/en/) switches. +The `xiaomi_aqara` switch platform allows you to get data from your [Xiaomi aqara](https://www.mi.com/en/) switches. The requirement is that you have set up [Xiaomi aqara](/integrations/xiaomi_aqara/). diff --git a/source/_integrations/syslog.markdown b/source/_integrations/syslog.markdown index ae22bfe656d..e61b3a9dc60 100644 --- a/source/_integrations/syslog.markdown +++ b/source/_integrations/syslog.markdown @@ -25,7 +25,7 @@ name: default: notify type: string facility: - description: Facility according to RFC 3164 (http://tools.ietf.org/html/rfc3164). Check the table below for entries. + description: Facility according to RFC 3164 (https://tools.ietf.org/html/rfc3164). Check the table below for entries. required: false default: syslog type: string @@ -64,6 +64,6 @@ The table contains values to use in your `configuration.yaml` file. | local6 | | | | local7 | | | -For details about facility, option, and priority please consult the [wikipedia article](http://en.wikipedia.org/wiki/Syslog) and [RFC 3164](http://tools.ietf.org/html/rfc3164). +For details about facility, option, and priority please consult the [wikipedia article](https://en.wikipedia.org/wiki/Syslog) and [RFC 3164](https://tools.ietf.org/html/rfc3164). To use notifications, please see the [getting started with automation page](/getting-started/automation/). diff --git a/source/_integrations/tapsaff.markdown b/source/_integrations/tapsaff.markdown index 2f3cc74b4f6..83034e963bc 100644 --- a/source/_integrations/tapsaff.markdown +++ b/source/_integrations/tapsaff.markdown @@ -8,7 +8,7 @@ ha_release: 0.47 ha_iot_class: Local Polling --- -The `tapsaff` binary sensor provides the 'Taps Aff' status for a given location within the UK using [Taps Aff](http://www.taps-aff.co.uk). +The `tapsaff` binary sensor provides the 'Taps Aff' status for a given location within the UK using [Taps Aff](https://www.taps-aff.co.uk/). ## Configuration diff --git a/source/_integrations/ted5000.markdown b/source/_integrations/ted5000.markdown index c700a1504ee..7376fd08b85 100644 --- a/source/_integrations/ted5000.markdown +++ b/source/_integrations/ted5000.markdown @@ -8,7 +8,7 @@ ha_release: "0.30" ha_iot_class: Local Polling --- -The `ted 5000` monitors electricity consumption/production by connecting to the [TED](http://www.theenergydetective.com/home) gateway, itself connected to one or several Measuring Transmitting Units (MTU). The platform creates up to two sensors per MTU, one for Wattage the other for Voltage. +The `ted 5000` monitors electricity consumption/production by connecting to the [TED](https://www.theenergydetective.com/home) gateway, itself connected to one or several Measuring Transmitting Units (MTU). The platform creates up to two sensors per MTU, one for Wattage the other for Voltage. If you want to enable the ted5000 sensor, add the following lines to your `configuration.yaml`: diff --git a/source/_integrations/thinkingcleaner.markdown b/source/_integrations/thinkingcleaner.markdown index 52bb0ec4dec..41a850b5697 100644 --- a/source/_integrations/thinkingcleaner.markdown +++ b/source/_integrations/thinkingcleaner.markdown @@ -16,7 +16,7 @@ There is currently support for the following device types within Home Assistant: ## Sensor -The `thinkingcleaner` sensor platform simple displays information about your [Thinking Cleaner](http://www.thinkingcleaner.com) add-on. +The `thinkingcleaner` sensor platform simple displays information about your [Thinking Cleaner](https://www.thinkingcleaner.com/) add-on. To enable this sensor in your installation, add the following to your `configuration.yaml` file: @@ -30,7 +30,7 @@ This will automatically add sensors for each Thinking Cleaner in your network. ## switch -The `thinkingcleaner` switch platform allows you to control your [Thinking Cleaner](http://www.thinkingcleaner.com) add-on. +The `thinkingcleaner` switch platform allows you to control your [Thinking Cleaner](https://www.thinkingcleaner.com/) add-on. To enable this switch in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/thomson.markdown b/source/_integrations/thomson.markdown index 2de9bbbaea3..9f809e8e5fb 100644 --- a/source/_integrations/thomson.markdown +++ b/source/_integrations/thomson.markdown @@ -10,7 +10,7 @@ ha_release: 0.7 Thomson produced networking equipment (under the brand name SpeedTouch) till 2010 and was then renamed to Technicolor. -This platform allows you to detect presence by looking at connected devices to a [Thomson](http://www.technicolor.com) device. +This platform allows you to detect presence by looking at connected devices to a [Thomson](https://www.technicolor.com/) device. To use this device tracker in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/tikteck.markdown b/source/_integrations/tikteck.markdown index 5249dc15171..b92b1927bb9 100644 --- a/source/_integrations/tikteck.markdown +++ b/source/_integrations/tikteck.markdown @@ -8,7 +8,7 @@ logo: tikteck.png ha_release: 0.36 --- -Support for the Bluetooth smart bulb from [Tikteck](http://www.tikteck.com). To enable these lights, add the following lines to your `configuration.yaml` file: +Support for the Bluetooth smart bulb from [Tikteck](https://www.tikteck.com/). To enable these lights, add the following lines to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/time_date.markdown b/source/_integrations/time_date.markdown index c8d24539e9c..31563206955 100644 --- a/source/_integrations/time_date.markdown +++ b/source/_integrations/time_date.markdown @@ -27,7 +27,7 @@ sensor: - 'beat' ``` -- **display_options** array (*Required*): The option to display. The types *date_time*, *time_date*, and *date_time_iso* shows the date and the time. The other types just the time or the date. *beat* shows the [Swatch Internet Time](http://www.swatch.com/en_us/internet-time). +- **display_options** array (*Required*): The option to display. The types *date_time*, *time_date*, and *date_time_iso* shows the date and the time. The other types just the time or the date. *beat* shows the [Swatch Internet Time](https://www.swatch.com/en_us/internet-time).

diff --git a/source/_integrations/tomato.markdown b/source/_integrations/tomato.markdown index 06f62d6c4d2..8bea2170380 100644 --- a/source/_integrations/tomato.markdown +++ b/source/_integrations/tomato.markdown @@ -66,7 +66,7 @@ See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked. A description of the API s available in this -[Tomato API](http://paulusschoutsen.nl/blog/2013/10/tomato-api-documentation/) +[Tomato API](https://paulusschoutsen.nl/blog/2013/10/tomato-api-documentation/) blog post. SSL Certificate: diff --git a/source/_integrations/torque.markdown b/source/_integrations/torque.markdown index d803e2c6283..b4403d7f0e9 100644 --- a/source/_integrations/torque.markdown +++ b/source/_integrations/torque.markdown @@ -8,7 +8,7 @@ ha_release: "0.10" ha_iot_class: Cloud Polling --- -The `torque` platform will allow you to monitor [Torque](http://torque-bhp.com/) data relayed from a Bluetooth OBD2 stick via the Torque mobile application. +The `torque` platform will allow you to monitor [Torque](https://torque-bhp.com/) data relayed from a Bluetooth OBD2 stick via the Torque mobile application. ## Setup diff --git a/source/_integrations/transmission.markdown b/source/_integrations/transmission.markdown index 0c0f62080db..c4e1f554849 100644 --- a/source/_integrations/transmission.markdown +++ b/source/_integrations/transmission.markdown @@ -10,7 +10,7 @@ ha_release: 0.87 ha_iot_class: Local Polling --- -The `transmission` integration allows you to monitor your downloads with [Transmission](http://www.transmissionbt.com/) from within Home Assistant and setup automation based on the information. +The `transmission` integration allows you to monitor your downloads with [Transmission](https://www.transmissionbt.com/) from within Home Assistant and setup automation based on the information. ## Setup diff --git a/source/_integrations/twitch.markdown b/source/_integrations/twitch.markdown index 2663cb79f81..af97ab66266 100644 --- a/source/_integrations/twitch.markdown +++ b/source/_integrations/twitch.markdown @@ -8,7 +8,7 @@ ha_release: "0.10" ha_iot_class: Cloud Polling --- -The `twitch` platform will allow you to monitor [Twitch](http://www.twitch.tv/) channel status from within Home Assistant and setup automation based on the information. +The `twitch` platform will allow you to monitor [Twitch](https://www.twitch.tv/) channel status from within Home Assistant and setup automation based on the information. ## Setup diff --git a/source/_integrations/ubee.markdown b/source/_integrations/ubee.markdown index 18bcc86353c..fa0ad03bd25 100644 --- a/source/_integrations/ubee.markdown +++ b/source/_integrations/ubee.markdown @@ -7,7 +7,7 @@ ha_category: ha_release: 0.89 --- -This platform offers presence detection by looking at connected devices to a [Ubee Router](http://www.ubeeinteractive.com/). +This platform offers presence detection by looking at connected devices to a [Ubee Router](https://www.ubeeinteractive.com/). To use a Ubee router in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/ubus.markdown b/source/_integrations/ubus.markdown index 320ba0e6850..e2ced94e075 100644 --- a/source/_integrations/ubus.markdown +++ b/source/_integrations/ubus.markdown @@ -9,7 +9,7 @@ ha_release: 0.7.6 _This is one of multiple ways we support OpenWRT. For an overview, see [openwrt](/integrations/openwrt)._ -This is a presence detection scanner for [OpenWRT](https://openwrt.org/) using [ubus](http://wiki.openwrt.org/doc/techref/ubus). It scans for changes in `hostapd.*`, which will detect and report changes in devices connected to the access point on the router. +This is a presence detection scanner for [OpenWRT](https://openwrt.org/) using [ubus](https://wiki.openwrt.org/doc/techref/ubus). It scans for changes in `hostapd.*`, which will detect and report changes in devices connected to the access point on the router. Before this scanner can be used you have to install the ubus RPC package on OpenWRT: diff --git a/source/_integrations/uk_transport.markdown b/source/_integrations/uk_transport.markdown index efa202ce89f..3c2d68650ec 100644 --- a/source/_integrations/uk_transport.markdown +++ b/source/_integrations/uk_transport.markdown @@ -8,7 +8,7 @@ ha_iot_class: Cloud Polling ha_release: "0.50" --- -The `uk_transport` sensor will display the time in minutes until the next departure in a specified direction from of a configured train station or bus stop. The sensor uses [transportAPI](http://www.transportapi.com/) to query live departure data and requires a developer application ID and key which can be obtained [here](https://developer.transportapi.com/). The [free tier](http://www.transportapi.com/plans/) allows 1000 requests daily, which is sufficient for a single sensor refreshing every 87 seconds. +The `uk_transport` sensor will display the time in minutes until the next departure in a specified direction from of a configured train station or bus stop. The sensor uses [transportAPI](https://www.transportapi.com/) to query live departure data and requires a developer application ID and key which can be obtained [here](https://developer.transportapi.com/). The [free tier](https://www.transportapi.com/plans/) allows 1000 requests daily, which is sufficient for a single sensor refreshing every 87 seconds.

@@ -18,7 +18,7 @@ Additional sensors can be added but at the expense of a reduced refresh rate. 2 Queries are entered as a list, with the two transport modes available being `bus` and `train`. -Train departure sensors require three character long `origin` and `destination` station codes which are searchable on the [National Rail enquiries](http://www.nationalrail.co.uk/times_fares/ldb.aspx) website (e.g., `WAT` is London Waterloo). The validity of a route can be checked by performing a GET request to `/uk/train/station/{station_code}/live.json` in the [API reference webpage](https://developer.transportapi.com/docs?raml=https://transportapi.com/v3/raml/transportapi.raml##request_uk_train_station_station_code_live_json). +Train departure sensors require three character long `origin` and `destination` station codes which are searchable on the [National Rail enquiries](https://www.nationalrail.co.uk/times_fares/ldb.aspx) website (e.g., `WAT` is London Waterloo). The validity of a route can be checked by performing a GET request to `/uk/train/station/{station_code}/live.json` in the [API reference webpage](https://developer.transportapi.com/docs?raml=https://transportapi.com/v3/raml/transportapi.raml#request_uk_train_station_station_code_live_json). To add a single train departure sensor add the following to your `configuration.yaml` file: @@ -102,7 +102,7 @@ Attributes can be accessed using the [template sensor](/integrations/template) a Bus sensors require as their `origin` a bus stop ATCO code which can be found by browsing OpenStreetMap data as follows: -1. On [OpenStreetMap.org](http://www.openstreetmap.org/) zoom right in on a bus stop you're interested in. +1. On [OpenStreetMap.org](https://www.openstreetmap.org/) zoom right in on a bus stop you're interested in. 2. Click the layers picker button on the right hand side. 3. Tick the 'map data' layer, and wait for clickable objects to load. 4. Click the bus stop node to reveal its tags on the left. @@ -148,4 +148,4 @@ And the template sensor for viewing the next bus attributes. If you wish to manage the rate of API requests (e.g., to disable requests when you aren't interested in travel, so that you can request updates more frequently when you do travel) set a really long `scan_interval` in the config options, and use the service `homeassistant.update_entity` to request the update of an entity, rather than waiting for the next scheduled update. -Powered by [transportAPI](http://www.transportapi.com/) +Powered by [transportAPI](https://www.transportapi.com/) diff --git a/source/_integrations/unifi.markdown b/source/_integrations/unifi.markdown index 7082fbce7d4..78126ea1664 100644 --- a/source/_integrations/unifi.markdown +++ b/source/_integrations/unifi.markdown @@ -94,7 +94,7 @@ It is recommended that you run the Unifi controller in a dedicated virtual machi ## Presence detection -This platform allows you to detect presence by looking at devices connected to a [Ubiquiti](http://ubnt.com/) [UniFi](https://www.ubnt.com/enterprise/#unifi) controller. +This platform allows you to detect presence by looking at devices connected to a [Ubiquiti](https://ubnt.com/) [UniFi](https://www.ubnt.com/enterprise/#unifi) controller. ### Troubleshooting and Time Synchronization diff --git a/source/_integrations/velux.markdown b/source/_integrations/velux.markdown index f2bac21439a..be1a433f9ea 100644 --- a/source/_integrations/velux.markdown +++ b/source/_integrations/velux.markdown @@ -9,7 +9,7 @@ ha_release: 0.49 ha_iot_class: Local Polling --- -[Velux](http://www.velux.com) integration for Home Assistant allows you to connect to a Velux KLF 200 interface, to control [io-homecontrol](http://www.io-homecontrol.com) devices like windows and blinds. The module allows you to start scenes configured within KLF 200. +[Velux](https://www.velux.com/) integration for Home Assistant allows you to connect to a Velux KLF 200 interface, to control [io-homecontrol](http://www.io-homecontrol.com) devices like windows and blinds. The module allows you to start scenes configured within KLF 200. At least firmware version > 2.0.0.0 is required on the KLF 200 device. The firmware images may be obtained [here](https://www.velux.com/api/klf200) and may be imported via the webinterface of your KLF 200. diff --git a/source/_integrations/venstar.markdown b/source/_integrations/venstar.markdown index c589a30d121..701df65acc5 100644 --- a/source/_integrations/venstar.markdown +++ b/source/_integrations/venstar.markdown @@ -9,7 +9,7 @@ ha_iot_class: Local Polling --- -The `venstar` climate platform allows you to control [Venstar](http://www.venstar.com) thermostats from Home Assistant. +The `venstar` climate platform allows you to control [Venstar](https://www.venstar.com/) thermostats from Home Assistant. Venstar thermostats feature a local API that allows for automation without the need for a cloud service. Currently supported and tested thermostats: diff --git a/source/_integrations/vera.markdown b/source/_integrations/vera.markdown index efd4870adb3..a2611442c4f 100644 --- a/source/_integrations/vera.markdown +++ b/source/_integrations/vera.markdown @@ -15,7 +15,7 @@ ha_category: ha_release: pre 0.7 --- -The [Vera](http://getvera.com) hub is a controller mainly connecting to Z-Wave devices. +The [Vera](https://getvera.com/) hub is a controller mainly connecting to Z-Wave devices. There is currently support for the following device types within Home Assistant: @@ -75,7 +75,7 @@ If you want to use a Z-Wave device from the Vera controller in Home Assistant au ### Sensor -The `vera` platform allows you to get data from your [Vera](http://getvera.com/) sensors from within Home Assistant. +The `vera` platform allows you to get data from your [Vera](https://getvera.com/) sensors from within Home Assistant. Please note that some vera sensors (such as _motion_ and _flood_ sensors) are _armable_ which means that vera will send alerts (email messages to txts) when they are _armed_ and change state. diff --git a/source/_integrations/vlc.markdown b/source/_integrations/vlc.markdown index 6569acaa279..bd1b7dd0add 100644 --- a/source/_integrations/vlc.markdown +++ b/source/_integrations/vlc.markdown @@ -8,7 +8,7 @@ ha_release: 0.35 ha_iot_class: Local Polling --- -The `vlc` platform allows you to control [VLC media player](http://www.videolan.org/vlc/index.html). +The `vlc` platform allows you to control [VLC media player](https://www.videolan.org/vlc/index.html). To add a VLC media player to your installation, add the following to your `configuration.yaml` file: @@ -63,4 +63,4 @@ sudo usermod -a -G audio homeassistant ##### VLC currently not supported with Hass.io -According to the forum topic ["How to add VLC into my Hassio"](http://community.home-assistant.io/t/how-to-add-vlc-into-my-hassio/23000/5), it is not possible to install packages like VLC on Hass.io. +According to the forum topic ["How to add VLC into my Hassio"](https://community.home-assistant.io/t/how-to-add-vlc-into-my-hassio/23000/5), it is not possible to install packages like VLC on Hass.io. diff --git a/source/_integrations/vlc_telnet.markdown b/source/_integrations/vlc_telnet.markdown index 7bef2182ebd..be761f1c8f4 100644 --- a/source/_integrations/vlc_telnet.markdown +++ b/source/_integrations/vlc_telnet.markdown @@ -8,7 +8,7 @@ ha_release: 0.95 ha_iot_class: Local Polling --- -The `vlc_telnet` platform allows you to control a [VLC media player](http://www.videolan.org/vlc/index.html) using the built in telnet interface. +The `vlc_telnet` platform allows you to control a [VLC media player](https://www.videolan.org/vlc/index.html) using the built in telnet interface. To add a VLC media player to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/volumio.markdown b/source/_integrations/volumio.markdown index 237e329b1ab..7c8ffc360d9 100644 --- a/source/_integrations/volumio.markdown +++ b/source/_integrations/volumio.markdown @@ -7,7 +7,7 @@ ha_category: ha_release: 0.41 --- -The `Volumio` platform allows you to control a [Volumio](http://volumio.org) media player from Home Assistant. +The `Volumio` platform allows you to control a [Volumio](https://volumio.org/) media player from Home Assistant. The preferred way to set up the Volumio platform is by enabling the [discovery component](/integrations/discovery/). diff --git a/source/_integrations/volvooncall.markdown b/source/_integrations/volvooncall.markdown index c524d44812d..ce169746f6b 100644 --- a/source/_integrations/volvooncall.markdown +++ b/source/_integrations/volvooncall.markdown @@ -8,7 +8,7 @@ ha_release: 0.39 ha_iot_class: Cloud Polling --- -The `volvooncall` integration offers integration with the [Volvo On Call](http://www.volvocars.com/intl/own/connectivity/volvo-on-call) cloud service and offers presence detection as well as sensors such as odometer and fuel level. +The `volvooncall` integration offers integration with the [Volvo On Call](https://www.volvocars.com/intl/why-volvo/human-innovation/future-of-driving/connectivity/volvo-on-call) cloud service and offers presence detection as well as sensors such as odometer and fuel level. ## Configuration diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown index 3b91080b689..9dde34ff73a 100644 --- a/source/_integrations/webostv.markdown +++ b/source/_integrations/webostv.markdown @@ -9,7 +9,7 @@ ha_iot_class: Local Polling ha_release: 0.18 --- -The `webostv` platform allows you to control a [LG](http://www.lg.com/) webOS Smart TV. +The `webostv` platform allows you to control a [LG](https://www.lg.com/) webOS Smart TV. There is currently support for the following device types within Home Assistant: @@ -18,7 +18,7 @@ There is currently support for the following device types within Home Assistant: ## Media Player -To begin with enable *LG Connect Apps* feature in *Network* settings of the TV [instructions](http://www.lg.com/uk/support/product-help/CT00008334-1437131798537-others). +To begin with enable *LG Connect Apps* feature in *Network* settings of the TV [instructions](https://www.lg.com/uk/support/product-help/CT00008334-1437131798537-others). Once basic configuration is added to your `configuration.yaml` file. A notification should be visible in the frontend's **Notification** section. Follow the instructions and accept the pairing request on your TV. @@ -99,7 +99,7 @@ Avoid using `[ ]` in the `name:` of your device. Home Assistant is able to turn on a LG webOS Smart TV if you specify an action, like HDMI-CEC or WakeOnLan. -Common for webOS 3.0 and higher would be to use WakeOnLan feature. To use this feature your TV should be connected to your network via Ethernet rather than Wireless and you should enable *LG Connect Apps* feature in *Network* settings of the TV [instructions](http://www.lg.com/uk/support/product-help/CT00008334-1437131798537-others) (or *Mobile App* in *General* settings for older models) (*may vary by version). +Common for webOS 3.0 and higher would be to use WakeOnLan feature. To use this feature your TV should be connected to your network via Ethernet rather than Wireless and you should enable *LG Connect Apps* feature in *Network* settings of the TV [instructions](https://www.lg.com/uk/support/product-help/CT00008334-1437131798537-others) (or *Mobile App* in *General* settings for older models) (*may vary by version). On newer models (2017+), WakeOnLan may need to be enabled in the TV settings by going to Settings > General > Mobile TV On > Turn On Via WiFi [instructions](https://support.quanticapps.com/hc/en-us/articles/115005985729-How-to-turn-on-my-LG-Smart-TV-using-the-App-WebOS-). diff --git a/source/_integrations/wemo.markdown b/source/_integrations/wemo.markdown index e14a970ad19..b1227ef4863 100644 --- a/source/_integrations/wemo.markdown +++ b/source/_integrations/wemo.markdown @@ -12,14 +12,14 @@ featured: true ha_release: pre 0.7 --- -The `wemo` integration is the main integration to integrate various [Belkin WeMo](http://www.belkin.com/us/Products/home-automation/c/wemo-home-automation/) devices with Home Assistant. +The `wemo` integration is the main integration to integrate various [Belkin WeMo](https://www.belkin.com/us/Products/home-automation/c/wemo-home-automation/) devices with Home Assistant. There is currently support for the following device types within Home Assistant: - Binary Sensor - Fan (Belkin WeMo (Holmes) Smart Humidifier) -- Light (Belkin WeMo LED lights and [Smart Dimmer Switch](http://www.belkin.com/us/F7C059-Belkin/p/P-F7C059/)) -- Switch ([Belkin WeMo Switches](https://www.belkin.com/us/Products/home-automation/c/wemo-home-automation/) and includes support for Wemo enabled [Mr. Coffee](http://www.mrcoffee.com/wemo-landing-page.html) smart coffee makers.) +- Light (Belkin WeMo LED lights and [Smart Dimmer Switch](https://www.belkin.com/us/F7C059-Belkin/p/P-F7C059/)) +- Switch ([Belkin WeMo Switches](https://www.belkin.com/us/Products/home-automation/c/wemo-home-automation/) and includes support for Wemo enabled [Mr. Coffee](https://www.mrcoffee.com/wemo-landing-page.html) smart coffee makers.) ## Configuration diff --git a/source/_integrations/wink.markdown b/source/_integrations/wink.markdown index e0f2978030a..156359cb467 100644 --- a/source/_integrations/wink.markdown +++ b/source/_integrations/wink.markdown @@ -20,7 +20,7 @@ ha_iot_class: Cloud Polling ha_release: pre 0.7 --- -[Wink](http://www.wink.com/) is a home automation hub that can control a whole wide range of devices on the market. Or, as they say in their own words: +[Wink](https://www.wink.com/) is a home automation hub that can control a whole wide range of devices on the market. Or, as they say in their own words:
Wink offers one, quick and simple way to connect people with the products they rely on every day in their home. @@ -373,7 +373,7 @@ script: ## Alarm Control Panel -The Wink alarm platform allows you to control your [Wink](http://www.wink.com/) Canary all-in-one security camera. +The Wink alarm platform allows you to control your [Wink](https://www.wink.com/) Canary all-in-one security camera. The requirement is that you have setup [Wink](/integrations/wink/) from above. @@ -387,7 +387,7 @@ The above devices are confirmed to work, but others may work as well. ## Binary Sensor -The Wink binary sensor platform allows you to get data from your [Wink](http://www.wink.com/) binary sensors. +The Wink binary sensor platform allows you to get data from your [Wink](https://www.wink.com/) binary sensors. The requirement is that you have setup [Wink](/integrations/wink/) from above. @@ -411,7 +411,7 @@ The above devices are confirmed to work, but others may work as well. ## Climate -The Wink climate platform allows you to get data from your [Wink](http://www.wink.com/) thermostats and air conditioners. +The Wink climate platform allows you to get data from your [Wink](https://www.wink.com/) thermostats and air conditioners. The requirement is that you have setup [Wink](/integrations/wink/) from above. @@ -451,7 +451,7 @@ The above devices are confirmed to work, but others may work as well. ## Fan -The Wink fan platform allows you to control your [Wink](http://www.wink.com/) fans. +The Wink fan platform allows you to control your [Wink](https://www.wink.com/) fans. The requirement is that you have setup [Wink](/integrations/wink/) from above. @@ -466,7 +466,7 @@ The above devices are confirmed to work, but others may work as well. ## Light -The `wink` light platform allows you to use your [Wink](http://www.wink.com/) lights. +The `wink` light platform allows you to use your [Wink](https://www.wink.com/) lights. The requirement is that you have setup [Wink](/integrations/wink/) from above. @@ -484,7 +484,7 @@ The above devices are confirmed to work, but others may work as well. ## Lock -The Wink lock platform allows you to control your [Wink](http://www.wink.com/) locks. +The Wink lock platform allows you to control your [Wink](https://www.wink.com/) locks. The requirement is that you have setup [Wink](/integrations/wink/) from above. @@ -619,7 +619,7 @@ If supported by your lock, a binary sensor will be created for each user key cod ## Sensor -The Wink sensor platform allows you to get data from your [Wink](http://www.wink.com/) sensors. +The Wink sensor platform allows you to get data from your [Wink](https://www.wink.com/) sensors. The requirement is that you have setup [Wink](/integrations/wink/) from above. @@ -639,7 +639,7 @@ The above devices are confirmed to work, but others may work as well. ## Switch -The Wink switch platform allows you to control your [Wink](http://www.wink.com/) switches. +The Wink switch platform allows you to control your [Wink](https://www.wink.com/) switches. The requirement is that you have set up [Wink](/integrations/wink/) from above. @@ -654,7 +654,7 @@ The requirement is that you have set up [Wink](/integrations/wink/) from above. ## Water heater -The Wink water heater platform allows you to get data from your [Wink](http://www.wink.com/) Water Heaters. +The Wink water heater platform allows you to get data from your [Wink](https://www.wink.com/) Water Heaters. The requirement is that you have set up [Wink](/integrations/wink/) from above. diff --git a/source/_integrations/wirelesstag.markdown b/source/_integrations/wirelesstag.markdown index d2b908cf76b..df591737665 100644 --- a/source/_integrations/wirelesstag.markdown +++ b/source/_integrations/wirelesstag.markdown @@ -11,7 +11,7 @@ ha_iot_class: Cloud Polling and Local Push ha_release: 0.68 --- -The `wirelesstag` implementation allows you to integrate your [wirelesstag.net](http://wirelesstag.net) sensors tags in Home Assistant. +The `wirelesstag` implementation allows you to integrate your [wirelesstag.net](https://wirelesstag.net/) sensors tags in Home Assistant. There is currently support for the following device types within Home Assistant: @@ -21,7 +21,7 @@ There is currently support for the following device types within Home Assistant: ## Configuration -To enable tags set up with your [wirelesstag.net](http://wirelesstag.net) account, add the following to your `configuration.yaml` file: +To enable tags set up with your [wirelesstag.net](https://wirelesstag.net/) account, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry @@ -59,7 +59,7 @@ Tags Manager supports local push notifications for `http` schema only. So if you ## Binary Sensor -To enable the binary sensor platform for your tags, set up with your [wirelesstag.net](http://wirelesstag.net) account. Add the following to your `configuration.yaml` file: +To enable the binary sensor platform for your tags, set up with your [wirelesstag.net](https://wirelesstag.net/) account. Add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry @@ -101,7 +101,7 @@ monitored_conditions: ## Sensor -To enable the sensor platform for your tags, set up with your [wirelesstag.net](http://wirelesstag.net) account. Add the following to your `configuration.yaml` file: +To enable the sensor platform for your tags, set up with your [wirelesstag.net](https://wirelesstag.net/) account. Add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry @@ -130,7 +130,7 @@ monitored_conditions: ## Switch -To enable the switch platform for your tags, set up with your [wirelesstag.net](http://wirelesstag.net) account. Add the following to your `configuration.yaml` file: +To enable the switch platform for your tags, set up with your [wirelesstag.net](https://wirelesstag.net/) account. Add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/wsdot.markdown b/source/_integrations/wsdot.markdown index 555c6bf00f9..b463e0685ff 100644 --- a/source/_integrations/wsdot.markdown +++ b/source/_integrations/wsdot.markdown @@ -8,11 +8,11 @@ ha_iot_class: Cloud Polling ha_release: 0.37 --- -The `wsdot` sensor will give you travel time information from the [Washington State Department of Transportation (WSDOT)](http://wsdot.com/). +The `wsdot` sensor will give you travel time information from the [Washington State Department of Transportation (WSDOT)](https://wsdot.com/). ## Setup -First, you need to get a free Traveler Information `api_key` from the [WSDOT API webpage](http://wsdot.com/traffic/api/). Just enter your email address to instantly get the key. +First, you need to get a free Traveler Information `api_key` from the [WSDOT API webpage](https://wsdot.com/traffic/api/). Just enter your email address to instantly get the key. ## Configuration @@ -49,7 +49,7 @@ travel_time: type: string {% endconfiguration %} -Figuring out which Travel Time ID (`id`) is associated with your routes is a bit of a challenge. If you visit `http://wsdot.com/Traffic/api/TravelTimes/TravelTimesREST.svc/GetTravelTimesAsJson?AccessCode=[your_api_key_here]` substituting your `api_key`, you will get a list of all available routes. Search through it and then find the key `TravelTimeID`. That tells you the number you need. +Figuring out which Travel Time ID (`id`) is associated with your routes is a bit of a challenge. If you visit `https://wsdot.com/Traffic/api/TravelTimes/TravelTimesREST.svc/GetTravelTimesAsJson?AccessCode=[your_api_key_here]` substituting your `api_key`, you will get a list of all available routes. Search through it and then find the key `TravelTimeID`. That tells you the number you need. Some common examples include: diff --git a/source/_integrations/wunderground.markdown b/source/_integrations/wunderground.markdown index 0dbe5d5d2ea..abc4df68b4f 100644 --- a/source/_integrations/wunderground.markdown +++ b/source/_integrations/wunderground.markdown @@ -8,7 +8,7 @@ ha_release: 0.27 ha_iot_class: Cloud Polling --- -The `wunderground` platform uses [Weather Underground](http://www.wunderground.com) as a source for current weather information. +The `wunderground` platform uses [Weather Underground](https://www.wunderground.com/) as a source for current weather information.
diff --git a/source/_integrations/wwlln.markdown b/source/_integrations/wwlln.markdown index 90c022d43a6..e9ef0048341 100644 --- a/source/_integrations/wwlln.markdown +++ b/source/_integrations/wwlln.markdown @@ -9,7 +9,7 @@ ha_config_flow: true --- The `wwlln` integration displays lightning strike information from the -[World Wide Lightning Location Network (WWLLN)](http://wwlln.net). +[World Wide Lightning Location Network (WWLLN)](https://wwlln.net/). Entities are generated, updated and removed automatically with each update from the feed. Each entity defines latitude and longitude and will be shown diff --git a/source/_integrations/x10.markdown b/source/_integrations/x10.markdown index d045d4025e6..8127de694b4 100644 --- a/source/_integrations/x10.markdown +++ b/source/_integrations/x10.markdown @@ -10,7 +10,7 @@ ha_release: 0.25 The `x10` light platform allows you to control your X10 based lights with Home Assistant. -Requires [Heyu x10](http://www.heyu.org) and a CM11A or a CM17A "FireCracker" interface. +Requires [Heyu x10](https://www.heyu.org/) and a CM11A or a CM17A "FireCracker" interface. To enable those lights, add the following lines to your `configuration.yaml` file: diff --git a/source/_integrations/xbox_live.markdown b/source/_integrations/xbox_live.markdown index d81a71cf320..da9419bcd2a 100644 --- a/source/_integrations/xbox_live.markdown +++ b/source/_integrations/xbox_live.markdown @@ -8,14 +8,14 @@ ha_iot_class: Cloud Polling ha_release: 0.28 --- -The Xbox Live integration is able to track [Xbox](http://xbox.com/) profiles. +The Xbox Live integration is able to track [Xbox](https://xbox.com/) profiles. To use this sensor you need a free API key from -[XboxAPI.com](http://xboxapi.com). +[XboxAPI.com](https://xboxapi.com/). Please also make sure to connect your Xbox account on that site. The configuration requires you to specify XUIDs which are the unique identifiers -for profiles. These can be determined on [XboxAPI.com](http://xboxapi.com) by +for profiles. These can be determined on [XboxAPI.com](https://xboxapi.com/) by either looking at your own profile page or using their interactive documentation to search for gamertags. @@ -34,7 +34,7 @@ sensor: {% configuration %} api_key: - description: Your API key from [XboxAPI.com](http://xboxapi.com). + description: Your API key from [XboxAPI.com](https://xboxapi.com/). required: true type: string xuid: diff --git a/source/_integrations/xeoma.markdown b/source/_integrations/xeoma.markdown index 8b3d3caa646..4017f37c8fb 100644 --- a/source/_integrations/xeoma.markdown +++ b/source/_integrations/xeoma.markdown @@ -8,7 +8,7 @@ ha_iot_class: Local Polling ha_release: 0.62 --- -The `Xeoma` camera platform allows you to view the video feeds from a [Xeoma](http://felenasoft.com/xeoma) video surveillance server. +The `Xeoma` camera platform allows you to view the video feeds from a [Xeoma](https://felenasoft.com/xeoma) video surveillance server. ## Configuration diff --git a/source/_integrations/xiaomi_aqara.markdown b/source/_integrations/xiaomi_aqara.markdown index 4206740b97c..6714f6e0fae 100644 --- a/source/_integrations/xiaomi_aqara.markdown +++ b/source/_integrations/xiaomi_aqara.markdown @@ -8,7 +8,7 @@ ha_release: 0.57 ha_iot_class: Local Push --- -The `xiaomi_aqara` integration allows you to integrate [Xiaomi](http://www.mi.com/en/) Aqara-compatible devices into Home Assistant. +The `xiaomi_aqara` integration allows you to integrate [Xiaomi](https://www.mi.com/en/) Aqara-compatible devices into Home Assistant. Please note, there are two versions of the hub: v1 and v2. v1 can be used with Home Assistant without any problems, however, v2 might be less straight forward when it comes to enabling the local API, and might even require you to open up your device in order to do so. Xiaomi has suggested this is in the pipeline. @@ -276,7 +276,7 @@ That means that Home Assistant is not getting any response from your Xiaomi gate - If your gateway's MAC address starts with `04:CF:8C`, there is a good chance that the required port `9898` is closed on your gateway (you can check it with the Nmap utility, using the command `sudo nmap - sU {gateway_ip} -p 9898`). To fix that issue, you need to do these steps: - Find a specific screw bit (like a fork) to open the gateway case. - Find a USB-UART cable/module and connect it to your computer. - - Solder 3 wires - RX, TX and GND like [here](http://cs5-3.4pda.to/14176168/IMG_20181020_201150.jpg). + - Solder 3 wires - RX, TX and GND like [here](https://cs5-3.4pda.to/14176168/IMG_20181020_201150.jpg). - Turn on the gateway (220V). - Open a serial terminal application (e.g. PuTTY) and connect to the serial port assigned to the USB-UART module (baudrate: 115200). - Wait until the gateway is booted up, connect the RX, TX and GND wires to the UART module (don't connect the Vcc (power) wire!). diff --git a/source/_integrations/xiaomi_tv.markdown b/source/_integrations/xiaomi_tv.markdown index 7ebb093a53f..083113d7f6e 100644 --- a/source/_integrations/xiaomi_tv.markdown +++ b/source/_integrations/xiaomi_tv.markdown @@ -8,7 +8,7 @@ ha_release: 0.64 ha_iot_class: Assumed State --- -The `xiaomi_tv` platform allows you to control a [Xiaomi TV](http://www.mi.com/en/mitv3s/65flat/). +The `xiaomi_tv` platform allows you to control a [Xiaomi TV](https://www.mi.com/en/mitv3s/65flat/). You need to make sure the TV is connected to the internet, and that your Home Assistant instance is on the same network. diff --git a/source/_integrations/xmpp.markdown b/source/_integrations/xmpp.markdown index bdb62d62312..9c0083da870 100644 --- a/source/_integrations/xmpp.markdown +++ b/source/_integrations/xmpp.markdown @@ -8,7 +8,7 @@ ha_release: pre 0.7 --- -The `xmpp` notification platform allows you to deliver notifications from Home Assistant to a [Jabber (XMPP)](http://xmpp.org) account. +The `xmpp` notification platform allows you to deliver notifications from Home Assistant to a [Jabber (XMPP)](https://xmpp.org/) account. ## Configuration diff --git a/source/_integrations/yamaha.markdown b/source/_integrations/yamaha.markdown index ce8c04b7ebc..400f94a220b 100644 --- a/source/_integrations/yamaha.markdown +++ b/source/_integrations/yamaha.markdown @@ -7,11 +7,11 @@ ha_category: ha_release: 0.16 --- -The `yamaha` platform allows you to control [Yamaha Network Receivers](http://usa.yamaha.com/products/audio-visual/av-receivers-amps/rx) from Home Assistant. +The `yamaha` platform allows you to control [Yamaha Network Receivers](https://usa.yamaha.com/products/audio-visual/av-receivers-amps/rx) from Home Assistant. Supported devices: -- [HTR-4065](http://www.yamaha.com/cchtr4065/) +- [HTR-4065](https://www.yamaha.com/cchtr4065/) - [RX-V473](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v473/specs.html) - [RX-V573](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v573/specs.html) - [RX-V673](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v673/specs.html) diff --git a/source/_integrations/yr.markdown b/source/_integrations/yr.markdown index 7fc3e187610..f266364f81c 100644 --- a/source/_integrations/yr.markdown +++ b/source/_integrations/yr.markdown @@ -8,7 +8,7 @@ ha_release: 0.11 ha_iot_class: Cloud Polling --- -The `yr` platform uses [YR.no](http://www.yr.no/) as a source for current +The `yr` platform uses [YR.no](https://www.yr.no/) as a source for current meteorological data for your location. The weather forecast is delivered by the Norwegian Meteorological Institute and the NRK. diff --git a/source/_integrations/zabbix.markdown b/source/_integrations/zabbix.markdown index 3797b7a65b4..a7cbae866ce 100644 --- a/source/_integrations/zabbix.markdown +++ b/source/_integrations/zabbix.markdown @@ -9,7 +9,7 @@ ha_release: 0.37 ha_iot_class: Local Polling --- -The `zabbix` integration is the main integration to connect to a [Zabbix](http://www.zabbix.com/) monitoring instance via the Zabbix API. +The `zabbix` integration is the main integration to connect to a [Zabbix](https://www.zabbix.com/) monitoring instance via the Zabbix API. There is currently support for the following device types within Home Assistant: @@ -64,7 +64,7 @@ zabbix: ## Sensor -The `zabbix` sensor platform let you monitor the current count of active triggers for your [Zabbix](http://www.zabbix.com/) monitoring instance. +The `zabbix` sensor platform let you monitor the current count of active triggers for your [Zabbix](https://www.zabbix.com/) monitoring instance.
You must have the Zabbix component configured to use those sensors. diff --git a/source/_integrations/zamg.markdown b/source/_integrations/zamg.markdown index 9141f2ae5df..3fda67db4b5 100644 --- a/source/_integrations/zamg.markdown +++ b/source/_integrations/zamg.markdown @@ -11,7 +11,7 @@ ha_iot_class: Cloud Polling The `zamg` platform uses meteorological details published by the Austrian weather service [Zentralanstalt für Meteorologie und Geodynamik (ZAMG)](https://www.zamg.ac.at). -Only observations for capital cities are publicly available. You can check the list of stations in [CSV format](http://www.zamg.ac.at/ogd). +Only observations for capital cities are publicly available. You can check the list of stations in [CSV format](https://www.zamg.ac.at/ogd). There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index dc67736d031..768978d3992 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -15,7 +15,7 @@ ha_iot_class: Local Polling featured: true --- -[Zigbee Home Automation](http://www.zigbee.org/zigbee-for-developers/applicationstandards/zigbeehomeautomation/) +[Zigbee Home Automation](https://zigbee.org/zigbee-for-developers/applicationstandards/zigbeehomeautomation/) integration for Home Assistant allows you to connect many off-the-shelf Zigbee based devices to Home Assistant, using one of the available Zigbee radio modules compatible with [zigpy](https://github.com/zigpy/zigpy) (an open source Python library implementing a Zigbee stack, which in turn relies on separate libraries which can each interface a with Zigbee radio module a different manufacturer). There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/zigbee.markdown b/source/_integrations/zigbee.markdown index 62c4d6603a7..9424890bad2 100644 --- a/source/_integrations/zigbee.markdown +++ b/source/_integrations/zigbee.markdown @@ -11,7 +11,7 @@ ha_release: 0.12 ha_iot_class: Local Polling --- -[Zigbee](http://www.zigbee.org/what-is-zigbee/) integration for Home Assistant allows you to utilize modules such as the [XBee](http://www.digi.com/lp/xbee) as wireless General Purpose Input/Output (GPIO) devices. The integration requires a local Zigbee device to be connected to a serial port. Through this, it will send and receive commands to and from other devices on the Zigbee mesh network. +[Zigbee](https://zigbee.org/what-is-zigbee/) integration for Home Assistant allows you to utilize modules such as the [XBee](https://www.digi.com/xbee) as wireless General Purpose Input/Output (GPIO) devices. The integration requires a local Zigbee device to be connected to a serial port. Through this, it will send and receive commands to and from other devices on the Zigbee mesh network. There is currently support for the following device types within Home Assistant: @@ -65,7 +65,7 @@ zigbee: ## Binary Sensor -A `zigbee` binary sensor in this context is a device connected to one of the digital input pins on a [Zigbee](http://www.zigbee.org/) module. The states reported by such a device are limited to `on` or `off`. By default, a binary sensor is considered `on` when the Zigbee device's digital input pin is held 'high' and considered `off` when it is held `low`. This behavior can be inverted by setting the `on_state` configuration variable to `low`. +A `zigbee` binary sensor in this context is a device connected to one of the digital input pins on a [Zigbee](https://zigbee.org/) module. The states reported by such a device are limited to `on` or `off`. By default, a binary sensor is considered `on` when the Zigbee device's digital input pin is held 'high' and considered `off` when it is held `low`. This behavior can be inverted by setting the `on_state` configuration variable to `low`. ### Configuration @@ -134,7 +134,7 @@ on_state: ## Sensor -There are two types of [Zigbee](http://www.zigbee.org/) sensor available to Home Assistant: +There are two types of [Zigbee](https://zigbee.org/) sensor available to Home Assistant: - [Analog input pin](#analog-input-pin) - [Temperature sensor](#temperature-sensor) (XBee Pro) diff --git a/source/_integrations/zwave.markdown b/source/_integrations/zwave.markdown index 2a377119179..03b7fce9a06 100644 --- a/source/_integrations/zwave.markdown +++ b/source/_integrations/zwave.markdown @@ -17,7 +17,7 @@ ha_iot_class: Local Push ha_release: 0.7 --- -The [Z-Wave](http://www.z-wave.com/) integration for Home Assistant allows you to observe and control connected Z-Wave devices. Please see the [Z-Wave getting started section](/docs/z-wave/) for in-depth documentation on how to use and setup the Z-Wave component. +The [Z-Wave](https://www.z-wave.com/) integration for Home Assistant allows you to observe and control connected Z-Wave devices. Please see the [Z-Wave getting started section](/docs/z-wave/) for in-depth documentation on how to use and setup the Z-Wave component. There is currently support for the following device types within Home Assistant: