diff --git a/source/_integrations/bluetooth.markdown b/source/_integrations/bluetooth.markdown
index 15534a16f1e..3ca8dccfe84 100644
--- a/source/_integrations/bluetooth.markdown
+++ b/source/_integrations/bluetooth.markdown
@@ -32,7 +32,7 @@ bluetooth:
For Bluetooth to function on Linux systems:
-- The [D-Bus](https://en.wikipedia.org/wiki/D-Bus) socket must be accessible to Home Assistant.
+- The [D-Bus](https://en.wikipedia.org/wiki/D-Bus) socket must be accessible to Home Assistant.
- The Bluetooth adapter must be accessible to D-Bus and running [BlueZ](http://www.bluez.org/) >= 5.43. It is highly recommended to use BlueZ >= 5.63 as older versions have been reported to be unreliable.
- The D-Bus implementation should be [dbus-broker](https://github.com/bus1/dbus-broker).
- The host system should be running Linux kernel 5.15.62 or later.
@@ -105,7 +105,7 @@ The following methods are known to work to add multiple adapters:
- Long USB Extension cables
- USB-Ethernet extenders
-- [USB/IP](http://usbip.sourceforge.net/)
+- [USB/IP](https://usbip.sourceforge.net/)
Integrations that have followed the [Best practices for library authors](https://developers.home-assistant.io/docs/bluetooth/?_highlight=Best+practices#best-practices-for-library-authors) will automatically connect via the adapter with the best signal and failover to an active adapter if one becomes unavailable.
@@ -173,7 +173,7 @@ For example, unshielded USB 3 port and their cables are especially infamously kn
- Try to place the Bluetooth adapter at some distance away from walls, ceilings, and floors.
- Try different orientations of the adapter's external antenna (or whole Bluetooth adapter).
- USB 3.0 ports/computers/peripherals are known culprits of RFI/EMI/EMF disruption. (See Ref. [1](https://www.usb.org/sites/default/files/327216.pdf) and [2](https://www.unit3compliance.co.uk/2-4ghz-intra-system-or-self-platform-interference-demonstration/)).
- - Make sure to only connect the Bluetooth USB adapter to a USB 2.0 port (and not to a USB 3.x port).
+ - Make sure to only connect the Bluetooth USB adapter to a USB 2.0 port (and not to a USB 3.x port).
- If your computer only has a USB 3.x port then connect the adapter via a powered USB 2.0 hub:
- A USB 2.0 hub will convert USB 3.0 to a USB 2.0 port and avoid USB 3.0 EMF.
- A USB 2.0 hub that uses an external power supply will ensure power requirements are fulfilled.
diff --git a/source/_integrations/clicksend_tts.markdown b/source/_integrations/clicksend_tts.markdown
index 7dc90e36cf9..cbb815c4a5f 100644
--- a/source/_integrations/clicksend_tts.markdown
+++ b/source/_integrations/clicksend_tts.markdown
@@ -48,7 +48,7 @@ caller:
required: false
type: string
language:
- description: The language you want to use to convert the message to audio. Accepted values are found in the [ClickSend Documentation](http://docs.clicksend.apiary.io/#reference/voice/voice-languages).
+ description: The language you want to use to convert the message to audio. Accepted values are found in the [ClickSend Documentation](https://clicksend.docs.apiary.io/#reference/voice/voice-languages).
required: false
default: en-us
type: string
diff --git a/source/_integrations/envisalink.markdown b/source/_integrations/envisalink.markdown
index a629fe4cecf..4add5376b96 100644
--- a/source/_integrations/envisalink.markdown
+++ b/source/_integrations/envisalink.markdown
@@ -20,7 +20,7 @@ ha_integration_type: integration
The `envisalink` integration will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and its sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this integration is built. Currently, the Envisalink version 4 is the latest model. This integration supports both the evl3 and the evl4.
-Please visit the [eyezon website](http://www.eyezon.com/) for further information about the evl3 and evl4 boards.
+Please visit the [eyezon website](https://www.eyezon.com/) for further information about the evl3 and evl4 boards.
There is currently support for the following device types within Home Assistant:
diff --git a/source/_integrations/gdacs.markdown b/source/_integrations/gdacs.markdown
index 77d3d799d41..5f1047a1f9a 100644
--- a/source/_integrations/gdacs.markdown
+++ b/source/_integrations/gdacs.markdown
@@ -16,18 +16,11 @@ ha_platforms:
ha_integration_type: integration
---
-The `gdacs` integration lets you use a GeoRSS feed provided by
-[GDACS](https://www.gdacs.org/) with information
-about major droughts, earthquakes, floods, tropical cyclones, tsunamis and
-volcanic activities worldwide.
-It retrieves alerts from a feed and shows information of those alerts filtered
-by distance to Home Assistant's location.
-The filter is set in the configuration as categories, radius (kilometers or miles based on unit system set in Home Assistant), latitude and longatude.
+The `gdacs` integration lets you use a GeoRSS feed provided by [GDACS](https://www.gdacs.org/) with information about major droughts, earthquakes, floods, tropical cyclones, tsunamis and volcanic activities worldwide.
+It retrieves alerts from a feed and shows information of those alerts filtered by distance to Home Assistant's location.
+The filter is set in the configuration as categories, radius (kilometers or miles based on unit system set in Home Assistant), latitude and longitude.
-Entities are generated, updated and removed automatically with each update
-from the feed. Each entity defines latitude and longitude and will be shown
-on the default map automatically, or on a map card by defining the source
-`gdacs`. The distance is available as the state of each entity converted to the configured unit system (kilometers or miles).
+Entities are generated, updated and removed automatically with each update from the feed. Each entity defines latitude and longitude and will be shown on the default map automatically, or on a map card by defining the source `gdacs`. The distance is available as the state of each entity converted to the configured unit system (kilometers or miles).
@@ -37,10 +30,7 @@ The data is updated every 5 minutes.
-The material used by this integration is provided by the [Global Disaster
-Alert and Coordination System (GDACS)](https://www.gdacs.org/) - a cooperation
-framework between the United Nations and the European Commission - under the
-[Creative Commons Attribution 4.0 International (CC BY 4.0) license](http://creativecommons.org/licenses/by/4.0/).
+The material used by this integration is provided by the [Global Disaster Alert and Coordination System (GDACS)](https://www.gdacs.org/) - a cooperation framework between the United Nations and the European Commission - under the [Creative Commons Attribution 4.0 International (CC BY 4.0) license](https://creativecommons.org/licenses/by/4.0/).
It has only been modified for the purpose of presenting the material in Home Assistant.
Please refer to the [creator's disclaimer and terms of use notice](https://www.gdacs.org/About/termofuse.aspx) for more information.
@@ -50,8 +40,7 @@ Please refer to the [creator's disclaimer and terms of use notice](https://www.g
## State Attributes
-The following state attributes are available for each entity in addition to
-the standard ones:
+The following state attributes are available for each entity in addition to the standard ones:
| Attribute | Description |
|------------------|-------------|
diff --git a/source/_integrations/geo_rss_events.markdown b/source/_integrations/geo_rss_events.markdown
index f5ca2dcf7d8..314fb06d955 100644
--- a/source/_integrations/geo_rss_events.markdown
+++ b/source/_integrations/geo_rss_events.markdown
@@ -83,7 +83,7 @@ unit_of_measurement:
## Example Feeds
-**Bush Fire Alerts**
+### Bush Fire Alerts
```yaml
sensor:
@@ -92,8 +92,8 @@ sensor:
url: https://www.qfes.qld.gov.au/data/alerts/bushfireAlert.xml
unit_of_measurement: "Alerts"
- platform: geo_rss_events
- name: Tas Fire Service
- url: http://www.fire.tas.gov.au/Show?pageId=colBushfireSummariesRss
+ name: TasALERT
+ url: https://alert.tas.gov.au/data/incidents-and-alerts.xml
unit_of_measurement: "Alerts"
- platform: geo_rss_events
name: WA Department of Fire and Emergency Services
@@ -103,8 +103,7 @@ sensor:
url: https://www.esa.act.gov.au/feeds/currentincidents.xml
```
-
-**Earthquake Alerts**
+### Earthquake Alerts
```yaml
sensor:
@@ -115,13 +114,13 @@ sensor:
- 'Past Hour'
- 'Past Day'
- platform: geo_rss_events
- name: BGS Worlwide Earthquakes
- url: https://www.bgs.ac.uk/feeds/worldSeismology.xml
+ name: BGS Worldwide Earthquakes
+ url: http://earthquakes.bgs.ac.uk/feeds/WorldSeismology.xml
categories:
- 'EQMH'
- platform: geo_rss_events
name: Recent significant earthquake reports (Canada)
- url: http://www.earthquakescanada.nrcan.gc.ca/index-en.php?tpl_region=canada&tpl_output=rss
+ url: https://www.earthquakescanada.nrcan.gc.ca/cache/earthquakes/canada-en.atom
categories:
- 'Earthquake Report'
```
diff --git a/source/_integrations/gree.markdown b/source/_integrations/gree.markdown
index 98cb099893b..7ef6a0df1aa 100644
--- a/source/_integrations/gree.markdown
+++ b/source/_integrations/gree.markdown
@@ -15,7 +15,7 @@ ha_platforms:
ha_integration_type: integration
---
-The Gree integration allows you to control a [Gree Smart HVAC](http://global.gree.com/) in Home Assistant.
+The Gree integration allows you to control a [Gree Smart HVAC](https://global.gree.com/) in Home Assistant.
There is currently support for the following device types within Home Assistant:
diff --git a/source/_integrations/homeworks.markdown b/source/_integrations/homeworks.markdown
index 4f2dffc997b..5ca1291f002 100644
--- a/source/_integrations/homeworks.markdown
+++ b/source/_integrations/homeworks.markdown
@@ -12,7 +12,7 @@ ha_platforms:
ha_integration_type: integration
---
-[Lutron](http://www.lutron.com/) is an American lighting control company. The Lutron Homeworks Series 4 & 8 systems are relatively old (~2003), and use RS-232 connections to communicate with home automation systems. The `homeworks` integration in Home Assistant is responsible for communicating with the main controller for these systems. Communication is through an ethernet to serial converter (NPort, for example).
+[Lutron](https://www.lutron.com/) is an American lighting control company. The Lutron Homeworks Series 4 & 8 systems are relatively old (~2003), and use RS-232 connections to communicate with home automation systems. The `homeworks` integration in Home Assistant is responsible for communicating with the main controller for these systems. Communication is through an ethernet to serial converter (NPort, for example).
Only a subset of the Homeworks system is supported - lights and keypads.
diff --git a/source/_integrations/idteck_prox.markdown b/source/_integrations/idteck_prox.markdown
index 8aebb7ceb55..61054068cb5 100644
--- a/source/_integrations/idteck_prox.markdown
+++ b/source/_integrations/idteck_prox.markdown
@@ -9,7 +9,7 @@ ha_domain: idteck_prox
ha_integration_type: integration
---
-[IDTECK](http://www.idteck.com) makes ID systems used to control access and identify users. This integration works with [Proximity Readers](http://www.idteck.com/en/products/proximity-reader-__-card-%26-tag-__125khz) (RFID card readers). The device is connected to Home Assistant through a serial to ethernet converter (NPort).
+[IDTECK](https://www.idteck.com/) makes ID systems used to control access and identify users. This integration works with [Proximity Readers](https://www.idteck.com/en/products/rfid-reader-__-card-%26-tag-__idteck-credential-format-(idc)) (RFID card readers). The device is connected to Home Assistant through a serial to ethernet converter (NPort).
An `idteck_prox_keycard` event is fired whenever a card or key sequence has been entered. The event contains 'card' - the card/key sequence, and the 'name' of the card reader. Checking 'card' against known card numbers can be used as the basis of an entry control system, or as part of a check-in/check-out system.