diff --git a/source/_integrations/garadget.markdown b/source/_integrations/garadget.markdown index 353fece165e..75a0daacbaa 100644 --- a/source/_integrations/garadget.markdown +++ b/source/_integrations/garadget.markdown @@ -15,7 +15,7 @@ related: ha_quality_scale: legacy --- -The `garadget` cover {% term integration %} lets you control [Garadget](https://www.garadget.com/) garage door futurizers through Home Assistant. +The **Garadget** {% term integration %} lets you control [Garadget](https://www.garadget.com/) garage door futurizers through Home Assistant. ## Configuration diff --git a/source/_integrations/gardena_bluetooth.markdown b/source/_integrations/gardena_bluetooth.markdown index e3e08a68143..2fb27fc44b9 100644 --- a/source/_integrations/gardena_bluetooth.markdown +++ b/source/_integrations/gardena_bluetooth.markdown @@ -22,7 +22,7 @@ ha_platforms: ha_integration_type: integration --- -The Gardena Bluetooth {% term integration %} allows users to integrate their Gardena Bluetooth devices into Home Assistant. +The **Gardena Bluetooth** {% term integration %} allows users to integrate their Gardena Bluetooth devices into Home Assistant. See device section for support information: [water control](#water-control), [irrigation valves](#irrigation-valves), [lawn mowers](#lawn-mowers), [garden pumps](#gard-pumps) diff --git a/source/_integrations/gdacs.markdown b/source/_integrations/gdacs.markdown index d2c35497ac8..ff8e0e612d0 100644 --- a/source/_integrations/gdacs.markdown +++ b/source/_integrations/gdacs.markdown @@ -16,7 +16,7 @@ ha_platforms: ha_integration_type: service --- -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. +The **GDACS** {% term 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. diff --git a/source/_integrations/generic.markdown b/source/_integrations/generic.markdown index 58053dcc2ad..f94da8aa721 100644 --- a/source/_integrations/generic.markdown +++ b/source/_integrations/generic.markdown @@ -15,7 +15,7 @@ ha_config_flow: true ha_integration_type: device --- -The `generic` camera platform allows you to integrate any IP camera or other URL into Home Assistant. Templates can be used to generate the URLs on the fly. +The **Generic Camera** {% term integration %} allows you to integrate any IP camera or other URL into Home Assistant. Templates can be used to generate the URLs on the fly. Home Assistant will serve the images via its server, making it possible to view your IP cameras while outside of your network. The endpoint is `/api/camera_proxy/camera.[name]`. diff --git a/source/_integrations/generic_hygrostat.markdown b/source/_integrations/generic_hygrostat.markdown index 0e0b2b62e33..dfc1411aa24 100644 --- a/source/_integrations/generic_hygrostat.markdown +++ b/source/_integrations/generic_hygrostat.markdown @@ -19,7 +19,7 @@ related: ha_config_flow: true --- -The `generic_hygrostat` humidifier {% term integration %} is a virtual hygrostat implemented in Home Assistant. It uses a sensor and a switch connected to a humidifier or dehumidifier under the hood. When in humidifier mode, if the measured humidity is less than the target humidity, the humidifier will be turned on and turned off when the required humidity is reached. When in dehumidifier mode, if the measured humidity is greater than the target humidity, the dehumidifier will be turned on and turned off when required humidity is reached. One Generic Hygrostat entity can only control one switch. If you need to activate two switches, one for a humidifier and one for a dehumidifier, you will need two Generic Hygrostat entities. +The **Generic hygrostat** {% term integration %} is a virtual hygrostat implemented in Home Assistant. It uses a sensor and a switch connected to a humidifier or dehumidifier under the hood. When in humidifier mode, if the measured humidity is less than the target humidity, the humidifier will be turned on and turned off when the required humidity is reached. When in dehumidifier mode, if the measured humidity is greater than the target humidity, the dehumidifier will be turned on and turned off when required humidity is reached. One Generic Hygrostat entity can only control one switch. If you need to activate two switches, one for a humidifier and one for a dehumidifier, you will need two Generic Hygrostat entities. {% include integrations/config_flow.md %} diff --git a/source/_integrations/generic_thermostat.markdown b/source/_integrations/generic_thermostat.markdown index 016f9fdfb0f..b7a6db136ea 100644 --- a/source/_integrations/generic_thermostat.markdown +++ b/source/_integrations/generic_thermostat.markdown @@ -17,7 +17,7 @@ ha_config_flow: true ha_quality_scale: internal --- -The `generic_thermostat` climate {% term integration %} is a thermostat implemented in Home Assistant. It uses a sensor and a switch connected to a heater or air conditioning under the hood. When in heater mode, if the measured temperature is cooler than the target temperature, the heater will be turned on and turned off when the required temperature is reached. When in air conditioning mode, if the measured temperature is hotter than the target temperature, the air conditioning will be turned on and turned off when required temperature is reached. One Generic Thermostat entity can only control one switch. If you need to activate two switches, one for a heater and one for an air conditioner, you will need two Generic Thermostat entities. +The **Generic Thermostat** {% term integration %} is a thermostat implemented in Home Assistant. It uses a sensor and a switch connected to a heater or air conditioning under the hood. When in heater mode, if the measured temperature is cooler than the target temperature, the heater will be turned on and turned off when the required temperature is reached. When in air conditioning mode, if the measured temperature is hotter than the target temperature, the air conditioning will be turned on and turned off when required temperature is reached. One Generic Thermostat entity can only control one switch. If you need to activate two switches, one for a heater and one for an air conditioner, you will need two Generic Thermostat entities. {% include integrations/config_flow.md %} diff --git a/source/_integrations/geniushub.markdown b/source/_integrations/geniushub.markdown index 8a9f6ccb1d4..e277a888ca0 100644 --- a/source/_integrations/geniushub.markdown +++ b/source/_integrations/geniushub.markdown @@ -22,7 +22,7 @@ ha_integration_type: integration ha_config_flow: true --- -The `geniushub` {% term integration %} links Home Assistant with your Genius Hub CH/DHW system, including its zones, devices, and issues. +The **Genius Hub** {% term integration %} links Home Assistant with your Genius Hub CH/DHW system, including its zones, devices, and issues. It uses the [geniushub](https://pypi.org/project/geniushub-client/) client library, which provides data compatible with the v1 API that _may not_ exactly match that of the official Web App. diff --git a/source/_integrations/geo_json_events.markdown b/source/_integrations/geo_json_events.markdown index 57b904f16ba..53a6c44bf83 100644 --- a/source/_integrations/geo_json_events.markdown +++ b/source/_integrations/geo_json_events.markdown @@ -14,7 +14,7 @@ ha_platforms: ha_integration_type: service --- -The GeoJSON {% term integration %} lets you ingest events from GeoJSON feeds. It retrieves events from a feed and shows information of those events filtered by distance to Home Assistant's location. +The **GeoJSON** {% term integration %} lets you ingest events from GeoJSON feeds. It retrieves events from a feed and shows information of those events filtered by distance to Home Assistant's location. All entries in the GeoJSON feed must define a `geometry` which typically is a point or polygon with geo coordinates. In addition, this platform will look for a `title` key in the entry's `properties` and use that as the entity's name. Entities are generated, updated and removed automatically with each update from the GeoJSON feed. Each entity defines latitude and longitude and will be shown on the map automatically. The distance in kilometers is available as the state of each entity. diff --git a/source/_integrations/geo_rss_events.markdown b/source/_integrations/geo_rss_events.markdown index 2f7484fa9d0..ab2eb2a2b1b 100644 --- a/source/_integrations/geo_rss_events.markdown +++ b/source/_integrations/geo_rss_events.markdown @@ -17,7 +17,7 @@ related: ha_quality_scale: legacy --- -The `geo_rss_events` {% term integration %} retrieves events from a GeoRSS feed and shows information of those events filtered by distance to Home Assistant's location and grouped by category. +The **GeoRSS** {% term integration %} retrieves events from a GeoRSS feed and shows information of those events filtered by distance to Home Assistant's location and grouped by category. This {% term integration %} is particularly useful if events occur unexpectedly in the vicinity of the home while the GeoRSS feed also contains many events representing distant unrelated entries. Typical examples are bush fires alerts or earthquakes. diff --git a/source/_integrations/geonetnz_quakes.markdown b/source/_integrations/geonetnz_quakes.markdown index b74ceb23c9a..18c19bd026a 100644 --- a/source/_integrations/geonetnz_quakes.markdown +++ b/source/_integrations/geonetnz_quakes.markdown @@ -16,7 +16,7 @@ ha_platforms: ha_integration_type: service --- -The `geonetnz_quakes` integration lets you use a GeoJSON feed provided by +The **GeoNet NZ Quakes** {% term integration %} lets you use a GeoJSON feed provided by New Zealand's [GeoNet](https://www.geonet.org.nz/) with information about quakes in the New Zealand region that happened within the last 7 days. It retrieves incidents from a feed and diff --git a/source/_integrations/geonetnz_volcano.markdown b/source/_integrations/geonetnz_volcano.markdown index 01ddf3a6b0e..61662eef8b0 100644 --- a/source/_integrations/geonetnz_volcano.markdown +++ b/source/_integrations/geonetnz_volcano.markdown @@ -14,7 +14,7 @@ ha_platforms: ha_integration_type: service --- -The `geonetnz_volcano` integration lets you use a GeoJSON feed provided by +The **GeoNet NZ Volcano** {% term integration %} lets you use a GeoJSON feed provided by New Zealand's [GeoNet](https://www.geonet.org.nz/) with information about volcanoes in the New Zealand region. It shows information of those volcanoes filtered by distance to Home Assistant's diff --git a/source/_integrations/gios.markdown b/source/_integrations/gios.markdown index ca06ca8ad40..3ff65e407a3 100644 --- a/source/_integrations/gios.markdown +++ b/source/_integrations/gios.markdown @@ -15,7 +15,7 @@ ha_platforms: ha_integration_type: service --- -The `gios` integration uses the [GIOŚ](http://powietrze.gios.gov.pl/pjp/current) web service as a source for air quality data for your location. +The **GIOŚ** {% term integration %} uses the [GIOŚ](http://powietrze.gios.gov.pl/pjp/current) web service as a source for air quality data for your location. {% include integrations/config_flow.md %} diff --git a/source/_integrations/github.markdown b/source/_integrations/github.markdown index 703d869d974..fe210a76e99 100644 --- a/source/_integrations/github.markdown +++ b/source/_integrations/github.markdown @@ -16,7 +16,7 @@ ha_codeowners: ha_integration_type: integration --- -The GitHub {% term integration %} allows you to monitor your favorite [GitHub](https://github.com/) public repositories. +The **GitHub** {% term integration %} allows you to monitor your favorite [GitHub](https://github.com/) public repositories. {% include integrations/config_flow.md %} diff --git a/source/_integrations/gitlab_ci.markdown b/source/_integrations/gitlab_ci.markdown index 57d4488f1fe..d545ee22d0a 100644 --- a/source/_integrations/gitlab_ci.markdown +++ b/source/_integrations/gitlab_ci.markdown @@ -15,7 +15,7 @@ related: ha_quality_scale: legacy --- -The `gitlab_ci` sensor {% term integration %} integrates results reported by CI/CD Pipeline Jobs in [GitLab](https://gitlab.com/). +The **GitLab-CI** {% term integration %} integrates results reported by CI/CD Pipeline Jobs in [GitLab](https://gitlab.com/). ## Setup diff --git a/source/_integrations/gitter.markdown b/source/_integrations/gitter.markdown index e807712c673..1dd5d391422 100644 --- a/source/_integrations/gitter.markdown +++ b/source/_integrations/gitter.markdown @@ -15,7 +15,7 @@ related: ha_quality_scale: legacy --- -This `gitter` {% term integration %} allows one to monitor a [Gitter.im](https://gitter.im) chatroom for unread messages. +This **Gitter** {% term integration %} allows one to monitor a [Gitter.im](https://gitter.im) chatroom for unread messages. ## Configuration diff --git a/source/_integrations/glances.markdown b/source/_integrations/glances.markdown index 9e31f40c68c..e598efbd830 100644 --- a/source/_integrations/glances.markdown +++ b/source/_integrations/glances.markdown @@ -14,7 +14,7 @@ ha_platforms: ha_integration_type: integration --- -The `glances` integration allows you to monitor the system information provided by the [Glances](https://github.com/nicolargo/glances) API. This enables one to track remote host and display their stats in Home Assistant. +The **Glances** {% term integration %} allows you to monitor the system information provided by the [Glances](https://github.com/nicolargo/glances) API. This enables one to track remote host and display their stats in Home Assistant. ## Setup diff --git a/source/_integrations/goalzero.markdown b/source/_integrations/goalzero.markdown index 5098b538ee7..1b5fb9c8cfb 100644 --- a/source/_integrations/goalzero.markdown +++ b/source/_integrations/goalzero.markdown @@ -17,7 +17,7 @@ ha_codeowners: ha_integration_type: device --- -This Goal Zero Yeti integration pulls data from a Wifi-enabled [Goal Zero Yeti](https://www.goalzero.com). +This **Goal Zero Yeti** {% term integration %} pulls data from a Wifi-enabled [Goal Zero Yeti](https://www.goalzero.com). {% include integrations/config_flow.md %} diff --git a/source/_integrations/gogogate2.markdown b/source/_integrations/gogogate2.markdown index abd3d79ba08..5cf99a38dea 100644 --- a/source/_integrations/gogogate2.markdown +++ b/source/_integrations/gogogate2.markdown @@ -17,7 +17,7 @@ ha_dhcp: true ha_integration_type: integration --- -The `gogogate2` cover platform lets you control Gogogate2 and iSmartGate enabled garage doors and gates through Home Assistant. Device names in Home Assistant are generated based on the names defined in the GogoGate2 or iSmartGate mobile app. +The **Gogogate2 and ismartgate** {% term integration %} lets you control Gogogate2 and iSmartGate enabled garage doors and gates through Home Assistant. Device names in Home Assistant are generated based on the names defined in the GogoGate2 or iSmartGate mobile app. {% include integrations/config_flow.md %} diff --git a/source/_integrations/goodwe.markdown b/source/_integrations/goodwe.markdown index 006b0231215..b78eeeb754b 100644 --- a/source/_integrations/goodwe.markdown +++ b/source/_integrations/goodwe.markdown @@ -20,7 +20,7 @@ ha_platforms: ha_integration_type: integration --- -The GoodWe integration will poll a [GoodWe](http://www.goodwe.com/) solar inverter over the local network and present its runtime values as sensors in Home Assistant. +The **GoodWe** {% term integration %} will poll a [GoodWe](http://www.goodwe.com/) solar inverter over the local network and present its runtime values as sensors in Home Assistant. It works with GoodWe ET, EH, BT, BH, ES, EM, DT, MS, D-NS, XS and BP families of inverters. Different inverter families/models expose different sets of sensors, the newer models have usually broader support. diff --git a/source/_integrations/google.markdown b/source/_integrations/google.markdown index 5eedafe423c..033d68d4fbe 100644 --- a/source/_integrations/google.markdown +++ b/source/_integrations/google.markdown @@ -18,7 +18,7 @@ api: Google Calendar API api_link: https://console.cloud.google.com/apis/library/calendar-json.googleapis.com --- -The *Google Calendar* {% term integration %} allows you to connect your [Google Calendar](https://calendar.google.com) to Home Assistant. The integration adds calendar entities that are shown on the *Calendar* dashboard, and can be used for automations based on any event, or limited to specific matching criteria. +The **Google Calendar** {% term integration %} allows you to connect your [Google Calendar](https://calendar.google.com) to Home Assistant. The integration adds calendar entities that are shown on the *Calendar* dashboard, and can be used for automations based on any event, or limited to specific matching criteria. ## Prerequisites diff --git a/source/_integrations/google_assistant.markdown b/source/_integrations/google_assistant.markdown index ef355f182ce..dac47858c6c 100644 --- a/source/_integrations/google_assistant.markdown +++ b/source/_integrations/google_assistant.markdown @@ -15,7 +15,7 @@ ha_platforms: - diagnostics --- -The Google Assistant {% term integration %} allows you to control your Home Assistant devices via Google Assistant on your mobile, tablet, or Google Home device. +The **Google Assistant** {% term integration %} allows you to control your Home Assistant devices via Google Assistant on your mobile, tablet, or Google Home device. If you want to send commands to Google Assistant to control devices supported by Google Assistant but not by Home Assistant, or broadcast messages to Google Assistant speakers and displays without interrupting music/video playback, take a look at the [Google Assistant SDK](/integrations/google_assistant_sdk) integration. diff --git a/source/_integrations/google_assistant_sdk.markdown b/source/_integrations/google_assistant_sdk.markdown index bb828f95c0c..fda5d6d4449 100644 --- a/source/_integrations/google_assistant_sdk.markdown +++ b/source/_integrations/google_assistant_sdk.markdown @@ -20,7 +20,7 @@ api: Google Assistant API api_link: https://console.developers.google.com/apis/api/embeddedassistant.googleapis.com/overview --- -The Google Assistant SDK {% term integration %} allows Home Assistant to interact with Google Assistant. If you want to use Google Assistant (for example, from your phone or Google Home device) to interact with your Home Assistant managed devices, then you want the [Google Assistant](/integrations/google_assistant) integration. +The **Google Assistant SDK** {% term integration %} allows Home Assistant to interact with Google Assistant. If you want to use Google Assistant (for example, from your phone or Google Home device) to interact with your Home Assistant managed devices, then you want the [Google Assistant](/integrations/google_assistant) integration. This integration allows: diff --git a/source/_integrations/google_cloud.markdown b/source/_integrations/google_cloud.markdown index 6c6ac654287..c06b3209a23 100644 --- a/source/_integrations/google_cloud.markdown +++ b/source/_integrations/google_cloud.markdown @@ -18,7 +18,7 @@ ha_platforms: ha_integration_type: service --- -The Google Cloud {% term integration %} allows you to use [Google Cloud Platform](https://cloud.google.com/) APIs and integrate them into Home Assistant. +The **Google Cloud** {% term integration %} allows you to use [Google Cloud Platform](https://cloud.google.com/) APIs and integrate them into Home Assistant. {% include integrations/config_flow.md %} diff --git a/source/_integrations/google_generative_ai_conversation.markdown b/source/_integrations/google_generative_ai_conversation.markdown index 0ffa8230732..e7dcfb1861d 100644 --- a/source/_integrations/google_generative_ai_conversation.markdown +++ b/source/_integrations/google_generative_ai_conversation.markdown @@ -30,7 +30,7 @@ related: title: Google AI --- -The Google Gemini {% term integration %} adds a conversation agent, speech-to-text, and text-to-speech entities powered by [Google Gemini](https://ai.google.dev/) to Home Assistant. The conversation agent can optionally be allowed to control Home Assistant. +The **Google Gemini** {% term integration %} adds a conversation agent, speech-to-text, and text-to-speech entities powered by [Google Gemini](https://ai.google.dev/) to Home Assistant. The conversation agent can optionally be allowed to control Home Assistant. Controlling Home Assistant is done by providing the AI access to the Assist API of Home Assistant. You can control what devices and entities it can access from the {% my voice_assistants title="exposed entities page" %}. The AI is able to provide you information about your devices and control them. diff --git a/source/_integrations/google_mail.markdown b/source/_integrations/google_mail.markdown index e574532bf7e..21f6b4585c8 100644 --- a/source/_integrations/google_mail.markdown +++ b/source/_integrations/google_mail.markdown @@ -18,7 +18,7 @@ api: Gmail API api_link: https://console.cloud.google.com/apis/library/gmail.googleapis.com --- -The Google Mail {% term integration %} allows you to connect your [Google Mail](https://mail.google.com) to Home Assistant. The integration adds an action to allow you to set an email auto-response for when you go on vacation. A `notify` action is also added, allowing you to draft or send emails in plain text. +The **Google Mail** {% term integration %} allows you to connect your [Google Mail](https://mail.google.com) to Home Assistant. The integration adds an action to allow you to set an email auto-response for when you go on vacation. A `notify` action is also added, allowing you to draft or send emails in plain text. ## Prerequisites diff --git a/source/_integrations/google_maps.markdown b/source/_integrations/google_maps.markdown index b6e29a7f761..51e493e53e3 100644 --- a/source/_integrations/google_maps.markdown +++ b/source/_integrations/google_maps.markdown @@ -15,7 +15,7 @@ related: ha_quality_scale: legacy --- -The `google_maps` {% term integration %} allows you to detect presence using the unofficial API of [Google Maps Location Sharing](https://myaccount.google.com/locationsharing). +The **Google Maps** {% term integration %} allows you to detect presence using the unofficial API of [Google Maps Location Sharing](https://myaccount.google.com/locationsharing). ## Setup diff --git a/source/_integrations/google_pubsub.markdown b/source/_integrations/google_pubsub.markdown index 12aa08a813e..ffc13fd9b29 100644 --- a/source/_integrations/google_pubsub.markdown +++ b/source/_integrations/google_pubsub.markdown @@ -13,7 +13,7 @@ related: ha_quality_scale: legacy --- -The `google_pubsub` {% term integration %} allows you to hook into the Home Assistant event bus and send events to [Google Cloud Pub/Sub](https://cloud.google.com/pubsub/docs/overview). The current [free tier](https://cloud.google.com/free/) of GCP should allow you to sync about 1 event every 2 seconds on average (2 million invocations per month). +The **Google Pub/Sub** {% term integration %} allows you to hook into the Home Assistant event bus and send events to [Google Cloud Pub/Sub](https://cloud.google.com/pubsub/docs/overview). The current [free tier](https://cloud.google.com/free/) of GCP should allow you to sync about 1 event every 2 seconds on average (2 million invocations per month). ## First time setup diff --git a/source/_integrations/google_sheets.markdown b/source/_integrations/google_sheets.markdown index ee502e7b98f..97bdb945a9f 100644 --- a/source/_integrations/google_sheets.markdown +++ b/source/_integrations/google_sheets.markdown @@ -17,7 +17,7 @@ api2: Google Sheets API api2_link: https://console.cloud.google.com/apis/enableflow?apiid=sheets.googleapis.com --- -The Google Sheets {% term integration %} allows you to connect your [Google Drive](https://drive.google.com) to Home Assistant. The integration adds an action to allow you to append rows to a Sheets document. The idea is that you can store data on there for further processing. When you set up a config entry, your drive will have a new sheet called Home Assistant. You can then rename this to whatever you like. +The **Google Sheets** {% term integration %} allows you to connect your [Google Drive](https://drive.google.com) to Home Assistant. The integration adds an action to allow you to append rows to a Sheets document. The idea is that you can store data on there for further processing. When you set up a config entry, your drive will have a new sheet called Home Assistant. You can then rename this to whatever you like. **Note**: The integration currently only has access to that one document that is created during setup. diff --git a/source/_integrations/google_translate.markdown b/source/_integrations/google_translate.markdown index b60f189fd49..da05029b5ec 100644 --- a/source/_integrations/google_translate.markdown +++ b/source/_integrations/google_translate.markdown @@ -12,7 +12,7 @@ ha_config_flow: true ha_integration_type: integration --- -The `google_translate` text-to-speech platform uses the unofficial [Google Translate text-to-speech engine](https://translate.google.com/) to read a text with natural sounding voices. Contrary to what the name suggests, the integration only does text-to-speech and does not translate messages sent to it. +The **Google Translate text-to-speech** {% term integration %} uses the unofficial [Google Translate text-to-speech engine](https://translate.google.com/) to read a text with natural sounding voices. Contrary to what the name suggests, the integration only does text-to-speech and does not translate messages sent to it. {% include integrations/config_flow.md %} diff --git a/source/_integrations/google_travel_time.markdown b/source/_integrations/google_travel_time.markdown index dc33f644534..620771fb0ff 100644 --- a/source/_integrations/google_travel_time.markdown +++ b/source/_integrations/google_travel_time.markdown @@ -14,7 +14,7 @@ ha_codeowners: ha_integration_type: integration --- -The `google_travel_time` sensor provides travel time from the [Google Maps Routes API](https://developers.google.com/maps/documentation/routes/overview). +The **Google Maps Travel Time** {% term integration %} provides travel time from the [Google Maps Routes API](https://developers.google.com/maps/documentation/routes/overview). ## Setup diff --git a/source/_integrations/google_wifi.markdown b/source/_integrations/google_wifi.markdown index 0dd86cc5b69..e2e7c7bfa5e 100644 --- a/source/_integrations/google_wifi.markdown +++ b/source/_integrations/google_wifi.markdown @@ -15,7 +15,7 @@ related: ha_quality_scale: legacy --- -The `google_wifi` sensor {% term integration %} is displaying the exposed status of a Google Wifi (or OnHub) router. +The **Google Wifi** {% term integration %} is displaying the exposed status of a Google Wifi (or OnHub) router. The {% term integration %} is able to report network status, up-time, current IP address and firmware versions. diff --git a/source/_integrations/graphite.markdown b/source/_integrations/graphite.markdown index 1f9d8deee35..ec33e259a8b 100644 --- a/source/_integrations/graphite.markdown +++ b/source/_integrations/graphite.markdown @@ -13,7 +13,7 @@ related: ha_quality_scale: legacy --- -The `graphite` {% term integration %} records all events and state changes and feeds the data to a [graphite](http://graphiteapp.org/) instance. +The **Graphite** {% term integration %} records all events and state changes and feeds the data to a [graphite](http://graphiteapp.org/) instance. To enable this {% term integration %}, add the following lines to your {% term "`configuration.yaml`" %} file. {% include integrations/restart_ha_after_config_inclusion.md %} diff --git a/source/_integrations/gree.markdown b/source/_integrations/gree.markdown index 6c84a572f20..a77ef677b68 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](https://global.gree.com/) in Home Assistant. +The **Gree** {% term 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/greenwave.markdown b/source/_integrations/greenwave.markdown index 02176e0faf3..b7a9a2f9e7c 100644 --- a/source/_integrations/greenwave.markdown +++ b/source/_integrations/greenwave.markdown @@ -12,7 +12,7 @@ ha_integration_type: integration ha_quality_scale: legacy --- -This integration communicates with the Greenwave Reality (TCP Connected) Gateway to allow control of all lights and fixtures registered to the gateway. Bulbs and Fixtures can be created and modified inside the TCP Lighting App for Android and iOS. +This {% term integration %} communicates with the Greenwave Reality (TCP Connected) Gateway to allow control of all lights and fixtures registered to the gateway. Bulbs and Fixtures can be created and modified inside the TCP Lighting App for Android and iOS. This integration has been tested on firmware revisions: diff --git a/source/_integrations/group.markdown b/source/_integrations/group.markdown index af03cb86885..af6600fbfe5 100644 --- a/source/_integrations/group.markdown +++ b/source/_integrations/group.markdown @@ -39,7 +39,7 @@ ha_platforms: ha_integration_type: helper --- -The group {% term integration %} lets you combine multiple entities into a single entity. Entities that are members of a group can be controlled and monitored as a whole. +The **Group** {% term integration %} lets you combine multiple entities into a single entity. Entities that are members of a group can be controlled and monitored as a whole. This can be useful, for example, in cases where you want to control multiple bulbs in a light fixture as a single light in Home Assistant. You also have the option of hiding the individual member entities in a group. diff --git a/source/_integrations/growatt_server.markdown b/source/_integrations/growatt_server.markdown index cfdddcd79a1..b0d3741997c 100644 --- a/source/_integrations/growatt_server.markdown +++ b/source/_integrations/growatt_server.markdown @@ -17,7 +17,7 @@ ha_codeowners: - '@johanzander' --- -The Growatt {% term integration %} enables you to retrieve data from Growatt inverters. During setup, you can choose from various regional endpoint servers: +The **Growatt** {% term integration %} enables you to retrieve data from Growatt inverters. During setup, you can choose from various regional endpoint servers: - For users in China: diff --git a/source/_integrations/gtfs.markdown b/source/_integrations/gtfs.markdown index 3b36c30d29f..e93ec24c0d8 100644 --- a/source/_integrations/gtfs.markdown +++ b/source/_integrations/gtfs.markdown @@ -15,7 +15,7 @@ related: ha_quality_scale: legacy --- -The `gtfs` {% term integration %} 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. +The **GTFS** {% term integration %} 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 [Mobility Database](https://mobilitydatabase.org/). diff --git a/source/_integrations/itach.markdown b/source/_integrations/itach.markdown index dde985063d1..036a8493b71 100644 --- a/source/_integrations/itach.markdown +++ b/source/_integrations/itach.markdown @@ -15,7 +15,7 @@ related: ha_quality_scale: legacy --- -The `itach` remote {% term integration %} allows you to control IR devices with a Global Caché iTach Device and GC-100 devices. The Global Cache IR API are similar across their product line. See API documentation links at the end of this page. +The **Global Caché iTach TCP/IP to IR** {% term integration %} allows you to control IR devices with a Global Caché iTach Device and GC-100 devices. The Global Cache IR API are similar across their product line. See API documentation links at the end of this page. In order to utilize the digital input (binary sensor) and relay (switch) features of your Global Cache device you will need to use the [gc100 integration](/integrations/gc100) and associated platforms. diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index 5ab9e7556ac..0d3b38adee7 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -25,7 +25,7 @@ ha_platforms: ha_integration_type: integration --- -The Google Nest {% term integration %} allows you to integrate a few [supported](https://developers.google.com/nest/device-access/supported-devices) Google [Nest](https://store.google.com/us/category/connected_home?) devices in Home Assistant. This integration uses the [Smart Device Management](https://developers.google.com/nest/device-access/api) API and Google's Cloud Pubsub to efficiently listen for changes in device state or other events. See [Supported Devices](https://developers.google.com/nest/device-access/supported-devices) for all devices supported by the SDM API. +The **Google Nest** {% term integration %} allows you to integrate a few [supported](https://developers.google.com/nest/device-access/supported-devices) Google [Nest](https://store.google.com/us/category/connected_home?) devices in Home Assistant. This integration uses the [Smart Device Management](https://developers.google.com/nest/device-access/api) API and Google's Cloud Pubsub to efficiently listen for changes in device state or other events. See [Supported Devices](https://developers.google.com/nest/device-access/supported-devices) for all devices supported by the SDM API. There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/zamg.markdown b/source/_integrations/zamg.markdown index b965e63eddf..adbc49a3133 100644 --- a/source/_integrations/zamg.markdown +++ b/source/_integrations/zamg.markdown @@ -16,7 +16,7 @@ ha_codeowners: - '@killer0071234' --- -The `GeoSphere Austria` platform uses meteorological details published by the Austrian weather service [GeoSphere Austria](https://www.geosphere.at). +The **GeoSphere Austria** {% term integration %} uses meteorological details published by the Austrian weather service [GeoSphere Austria](https://www.geosphere.at). With this integration, it is possible to get weather station data from up to 228 different GeoSphere stations across Austria. The integration uses the [datahub-api](https://dataset.api.hub.geosphere.at/v1/docs/index.html).