diff --git a/source/_integrations/eafm.markdown b/source/_integrations/eafm.markdown index 4653677b5a2..0c3436fe30d 100644 --- a/source/_integrations/eafm.markdown +++ b/source/_integrations/eafm.markdown @@ -14,7 +14,7 @@ ha_platforms: ha_integration_type: integration --- -The `eafm` {% term integration %} offers integration with the [UK Environment Agency Flood Monitoring](https://environment.data.gov.uk/flood-monitoring/doc/reference) API to provide sensors for nearby water levels. Combined with Home Assistant notifications, you could give yourself a warning if a nearby river was likely to flood your local cycle path or the only road out of your village. +The **Environment Agency Flood Gauges** {% term integration %} offers integration with the [UK Environment Agency Flood Monitoring](https://environment.data.gov.uk/flood-monitoring/doc/reference) API to provide sensors for nearby water levels. Combined with Home Assistant notifications, you could give yourself a warning if a nearby river was likely to flood your local cycle path or the only road out of your village. {% important %} diff --git a/source/_integrations/ecoal_boiler.markdown b/source/_integrations/ecoal_boiler.markdown index 3c8bbeb1ca3..5967db369a8 100644 --- a/source/_integrations/ecoal_boiler.markdown +++ b/source/_integrations/ecoal_boiler.markdown @@ -16,7 +16,7 @@ related: ha_quality_scale: legacy --- -The `ecoal_boiler` {% term integration %} is the base for pumps and sensors managed by [esterownik.pl eCoal boiler controller](https://esterownik.pl/nasze-produkty/ecoal). +The **eSterownik eCoal.pl Boiler** {% term integration %} is the base for pumps and sensors managed by [esterownik.pl eCoal boiler controller](https://esterownik.pl/nasze-produkty/ecoal). ## Configuration diff --git a/source/_integrations/ecoforest.markdown b/source/_integrations/ecoforest.markdown index 716a2313347..6226acba8c0 100644 --- a/source/_integrations/ecoforest.markdown +++ b/source/_integrations/ecoforest.markdown @@ -16,7 +16,7 @@ ha_platforms: ha_integration_type: integration --- -The Ecoforest integration allows monitoring and control of local [Ecoforest](https://ecoforest.com) fireplaces in Home Assistant. +The **Ecoforest** {% term integration %} allows monitoring and control of local [Ecoforest](https://ecoforest.com) fireplaces in Home Assistant. There is currently support for the following device platforms within Home Assistant: diff --git a/source/_integrations/edimax.markdown b/source/_integrations/edimax.markdown index 5550feaeb27..5e900ee14c6 100644 --- a/source/_integrations/edimax.markdown +++ b/source/_integrations/edimax.markdown @@ -15,7 +15,7 @@ related: ha_quality_scale: legacy --- -This Edimax {% term integration %} allows you to control the state of your [Edimax](https://www.edimax.com/edimax/merchandise/merchandise_list/data/edimax/global/home_automation_smart_plug/) switches. +This **Edimax** {% term integration %} allows you to control the state of your [Edimax](https://www.edimax.com/edimax/merchandise/merchandise_list/data/edimax/global/home_automation_smart_plug/) switches. To use your Edimax switch in your installation, add the following to your {% term "`configuration.yaml`" %} file. {% include integrations/restart_ha_after_config_inclusion.md %} diff --git a/source/_integrations/edl21.markdown b/source/_integrations/edl21.markdown index 7f029506bcf..e3197c6a162 100644 --- a/source/_integrations/edl21.markdown +++ b/source/_integrations/edl21.markdown @@ -12,7 +12,7 @@ ha_integration_type: hub ha_config_flow: true --- -The `edl21` integration lets you read German EDL21 smart meters using [SML](https://de.wikipedia.org/wiki/Smart_Message_Language) from Home Assistant. +The **EDL21** {% term integration %} lets you read German EDL21 smart meters using [SML](https://de.wikipedia.org/wiki/Smart_Message_Language) from Home Assistant. In order to connect to the smart meter, an infrared transceiver is required. diff --git a/source/_integrations/elmax.markdown b/source/_integrations/elmax.markdown index e2feb8550ef..adbb51f59cd 100644 --- a/source/_integrations/elmax.markdown +++ b/source/_integrations/elmax.markdown @@ -18,7 +18,7 @@ ha_integration_type: integration ha_zeroconf: true --- -The Elmax {% term integration %} enables Home Assistant integration with +The **Elmax** {% term integration %} enables Home Assistant integration with [ELMAX](https://www.elmaxsrl.it/) control panels. Elmax panels are domotic systems focused on intrusion detection and home surveillance. diff --git a/source/_integrations/elv.markdown b/source/_integrations/elv.markdown index 8d751091b56..17c09edc73b 100644 --- a/source/_integrations/elv.markdown +++ b/source/_integrations/elv.markdown @@ -17,7 +17,7 @@ related: ha_quality_scale: legacy --- -The `pca` switch {% term integration %} allows you to control the state of your [ELV PCA 301 smart switch](https://www.elv.de/funkschaltsteckdose-fuer-energiekostenmonitor-pca-301.html). You need an 868 MHz interface like the [JeeLink](https://www.digitalsmarties.net/products/jeelink) flashed with the [pca-hex firmware](https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/firmware/JeeLink_PCA301.hex). +The **ELV PCA** {% term integration %} allows you to control the state of your [ELV PCA 301 smart switch](https://www.elv.de/funkschaltsteckdose-fuer-energiekostenmonitor-pca-301.html). You need an 868 MHz interface like the [JeeLink](https://www.digitalsmarties.net/products/jeelink) flashed with the [pca-hex firmware](https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/firmware/JeeLink_PCA301.hex). ## Configuration diff --git a/source/_integrations/elvia.markdown b/source/_integrations/elvia.markdown index 1c007eb372d..8fea80bb1e3 100644 --- a/source/_integrations/elvia.markdown +++ b/source/_integrations/elvia.markdown @@ -12,7 +12,7 @@ ha_config_flow: true ha_integration_type: integration --- -The Elvia {% term integration %} will import your historical grid consumption. +The **Elvia** {% term integration %} will import your historical grid consumption. You can use the Elvia integration, regardless of which provider you are subscribed to, as long as Elvia operates the grid. If you are unsure if this works for you, log in to [Min side](https://www.elvia.no/logg-inn/) and check. If you see a meter there, you can use it. Unlike most other integrations, this integration provides no entities. The imported data can be used in the [Energy dashboard](/docs/energy/) and with the [statistics-graph card](/dashboards/statistics-graph/). diff --git a/source/_integrations/emoncms.markdown b/source/_integrations/emoncms.markdown index a6680cf9408..6a045c39c99 100644 --- a/source/_integrations/emoncms.markdown +++ b/source/_integrations/emoncms.markdown @@ -18,7 +18,7 @@ related: ha_config_flow: true --- -The `emoncms` sensor {% term integration %} creates sensors for the feeds available in your local or cloud based version of [Emoncms](https://emoncms.org). +The **Emoncms** {% term integration %} creates sensors for the feeds available in your local or cloud based version of [Emoncms](https://emoncms.org). To write information from Home Assistant to Emoncms, you can use the [`emoncms_history`](/integrations/emoncms_history) {% term integration %}. diff --git a/source/_integrations/emoncms_history.markdown b/source/_integrations/emoncms_history.markdown index 843570f68fe..c50c58d2bc2 100644 --- a/source/_integrations/emoncms_history.markdown +++ b/source/_integrations/emoncms_history.markdown @@ -15,7 +15,7 @@ ha_codeowners: - '@alexandrecuer' --- -The `emoncms_history` {% term integration %} makes it possible to transfer (write) details collected with Home Assistant to [Emoncms.org](https://emoncms.org/) or your local running Emoncms instance. It will send the data to a specific input node on Emoncms with the entity IDs as a key. Afterwards you can create feeds and dashboards in Emoncms with the collected data. +The **Emoncms History** {% term integration %} makes it possible to transfer (write) details collected with Home Assistant to [Emoncms.org](https://emoncms.org/) or your local running Emoncms instance. It will send the data to a specific input node on Emoncms with the entity IDs as a key. Afterwards you can create feeds and dashboards in Emoncms with the collected data. To use the `emoncms_history` {% term integration %} in your installation, add the following to your {% term "`configuration.yaml`" %} file. {% include integrations/restart_ha_after_config_inclusion.md %} diff --git a/source/_integrations/emulated_hue.markdown b/source/_integrations/emulated_hue.markdown index a1a85be56aa..91e62c150ea 100644 --- a/source/_integrations/emulated_hue.markdown +++ b/source/_integrations/emulated_hue.markdown @@ -22,7 +22,7 @@ Be aware that `emulated_hue` doesn't work for new users of **Google Home** with {% endwarning %} -The `emulated_hue` {% term integration %} provides a virtual [Philips Hue](https://www.philips-hue.com) bridge, written entirely in software that allows services that work with the Hue API to interact with Home Assistant +The **Emulated Hue** {% term integration %} provides a virtual [Philips Hue](https://www.philips-hue.com) bridge, written entirely in software that allows services that work with the Hue API to interact with Home Assistant entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo or Google Home with no setup cost outside of configuration changes. The virtual bridge can turn entities on/off or change the brightness of dimmable lights. The volume level of media players can be controlled as brightness. diff --git a/source/_integrations/emulated_kasa.markdown b/source/_integrations/emulated_kasa.markdown index df28a71f5b5..20f689665a2 100644 --- a/source/_integrations/emulated_kasa.markdown +++ b/source/_integrations/emulated_kasa.markdown @@ -15,7 +15,7 @@ related: title: Configuration file --- -The Emulated Kasa {% term integration %} emulates a TP-Link Kasa smart plug and announces the power usage of configured devices to any that might request it on the local network. +The **Emulated Kasa** {% term integration %} emulates a TP-Link Kasa smart plug and announces the power usage of configured devices to any that might request it on the local network. For example, the [Sense Energy Monitor](/integrations/sense) can use this to identify power usage. diff --git a/source/_integrations/ephember.markdown b/source/_integrations/ephember.markdown index d4d9dc7cf5d..94a67ba697e 100644 --- a/source/_integrations/ephember.markdown +++ b/source/_integrations/ephember.markdown @@ -18,7 +18,7 @@ related: ha_quality_scale: legacy --- -The `ephember` {% term integration %} lets you control [EPH Controls](https://emberapp.ephcontrols.com/) thermostats. The module only works if you have a Wi-Fi gateway to control your EPH system and an account on the EMBER app. +The **EPH Controls** {% term integration %} lets you control [EPH Controls](https://emberapp.ephcontrols.com/) thermostats. The module only works if you have a Wi-Fi gateway to control your EPH system and an account on the EMBER app. To set it up, add the following information to your {% term "`configuration.yaml`" %} file: {% include integrations/restart_ha_after_config_inclusion.md %} diff --git a/source/_integrations/eq3btsmart.markdown b/source/_integrations/eq3btsmart.markdown index d90ab84b092..1112c69df4d 100644 --- a/source/_integrations/eq3btsmart.markdown +++ b/source/_integrations/eq3btsmart.markdown @@ -19,7 +19,7 @@ ha_platforms: - switch --- -The `eq3btsmart` climate platform allows you to integrate eQ-3 Bluetooth Smart Thermostats. +The **eQ-3 Bluetooth Smart Thermostats** {% term integration %} allows you to integrate eQ-3 Bluetooth Smart Thermostats. The current functionality allows setting the temperature as well as controlling the supported modes with help of the [eq3btsmart](https://github.com/eulemitkeule/eq3btsmart) library. As the device doesn't contain a temperature sensor ([read more](https://forum.fhem.de/index.php/topic,39308.15.html)), we report target temperature also as current one. diff --git a/source/_integrations/escea.markdown b/source/_integrations/escea.markdown index c2e1892cb5d..08efdfe0d2a 100644 --- a/source/_integrations/escea.markdown +++ b/source/_integrations/escea.markdown @@ -15,7 +15,7 @@ ha_platforms: ha_integration_type: integration --- -The Escea integration allows monitoring and control of local [Escea](https://escea.com/) fireplaces. These fireplaces are manufactured in New Zealand and sold throughout Australia and New Zealand. +The **Escea** {% term integration %} allows monitoring and control of local [Escea](https://escea.com/) fireplaces. These fireplaces are manufactured in New Zealand and sold throughout Australia and New Zealand. ## Supported hardware diff --git a/source/_integrations/etherscan.markdown b/source/_integrations/etherscan.markdown index f7a7f8b458a..a28b14865b5 100644 --- a/source/_integrations/etherscan.markdown +++ b/source/_integrations/etherscan.markdown @@ -15,7 +15,7 @@ related: ha_quality_scale: legacy --- -The `Etherscan` sensor platform displays Ether and ERC-20 token balances from [Etherscan.io](https://etherscan.io). +The **Etherscan** {% term integration %} displays Ether and ERC-20 token balances from [Etherscan.io](https://etherscan.io). To add the Etherscan sensor to your installation, specify an Ethereum address to watch in the {% term "`configuration.yaml`" %} file. You can also optionally provide a token name to retrieve and ERC-20 token balance. If no token is provided then the balance retrieved will be in ETH. You can also optionally provide the token contract address in case the token name is not found. {% include integrations/restart_ha_after_config_inclusion.md %} diff --git a/source/_integrations/eufylife_ble.markdown b/source/_integrations/eufylife_ble.markdown index 4029c8cdcfd..15c4d9b5089 100644 --- a/source/_integrations/eufylife_ble.markdown +++ b/source/_integrations/eufylife_ble.markdown @@ -14,7 +14,7 @@ ha_platforms: ha_integration_type: device --- -The EufyLife {% term integration %} allows you to integrate Eufy smart scales with Home Assistant. +The **EufyLife** {% term integration %} allows you to integrate Eufy smart scales with Home Assistant. ## Supported devices diff --git a/source/_integrations/evil_genius_labs.markdown b/source/_integrations/evil_genius_labs.markdown index c3374c4ffec..973fe7a9d22 100644 --- a/source/_integrations/evil_genius_labs.markdown +++ b/source/_integrations/evil_genius_labs.markdown @@ -13,7 +13,7 @@ ha_platforms: ha_integration_type: integration --- -This integration allows you to control and monitor the artworks by [Evil Genius Labs](https://www.evilgeniuslabs.org/). Tested with the Fibonacci256. +This {% term integration %} allows you to control and monitor the artworks by [Evil Genius Labs](https://www.evilgeniuslabs.org/). Tested with the Fibonacci256. If the integration is unable to connect, make sure the firmware is up to date. diff --git a/source/_integrations/ezviz.markdown b/source/_integrations/ezviz.markdown index 9760938e0e2..cdc6a83cee7 100644 --- a/source/_integrations/ezviz.markdown +++ b/source/_integrations/ezviz.markdown @@ -29,7 +29,7 @@ related: title: Controlling the camera from the dashboard --- -The `ezviz` sensor platform uses the ezvizlife.com API to interact with the devices. +The **EZVIZ** integration uses the ezvizlife.com API to interact with the devices. It also exposes an RTSP stream, by using the local camera IPs (so the device hosting Home Assistant has to be able to access the local IP of the cameras). As there is no official documentation for the API, the integration retrieves data from the API used in the EZVIZ mobile app, [hosted here](https://apiieu.ezvizlife.com). diff --git a/source/_integrations/huisbaasje.markdown b/source/_integrations/huisbaasje.markdown index 105bc34ce24..505b8f2f9d2 100644 --- a/source/_integrations/huisbaasje.markdown +++ b/source/_integrations/huisbaasje.markdown @@ -15,7 +15,7 @@ ha_platforms: ha_integration_type: integration --- -The EnergyFlip (formerly Huisbaasje) {% term integration %} allows you to track your energy consumption collected +The **EnergyFlip** (formerly Huisbaasje) {% term integration %} allows you to track your energy consumption collected by the monitoring device installed on your energy meters. {% include integrations/config_flow.md %} diff --git a/source/_integrations/kitchen_sink.markdown b/source/_integrations/kitchen_sink.markdown index 6e15886a40b..c4bea3b2891 100644 --- a/source/_integrations/kitchen_sink.markdown +++ b/source/_integrations/kitchen_sink.markdown @@ -24,7 +24,7 @@ related: title: Configuration file --- -The Kitchen Sink {% term integration %} contains demonstrations of various odds and ends. +The **Kitchen Sink** {% term integration %} contains demonstrations of various odds and ends. This sets up a demo environment of features which are obscure or which represent incorrect behavior, and are thus not wanted in the `demo` integration. diff --git a/source/_integrations/maxcube.markdown b/source/_integrations/maxcube.markdown index 7c317308856..73d9f04f943 100644 --- a/source/_integrations/maxcube.markdown +++ b/source/_integrations/maxcube.markdown @@ -17,7 +17,7 @@ related: ha_quality_scale: legacy --- -eQ-3 MAX! {% term 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. +The **eQ-3 MAX!** {% term 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: