10000 Merge branch 'current' into md-ci · home-assistant/home-assistant.io@ef2c574 · GitHub
[go: up one dir, main page]
Skip to content

Commit ef2c574

Browse files
silamonsilamon
authored
Merge branch 'current' into md-ci
2 parents c8eb61e + a6e059d commit ef2c574

File tree

5 files changed

+237
-237
lines changed

5 files changed

+237
-237
lines changed

‎source/_integrations/eafm.md renamed to ‎source/_integrations/eafm.markdown

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,27 @@
1-
---
2-
title: UK Environment Agency Flood Monitoring
3-
description: Monitor nearby water levels and be prepared for flooding with the UK Environment Agency API integration.
4-
ha_category:
5-
- Sensor
6-
ha_release: 0.115
7-
ha_iot_class: Cloud Polling
8-
ha_config_flow: true
9-
ha_codeowners:
10-
- '@Jc2k'
11-
---
12-
13-
The `eafm` 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.
14-
15-
{% important %}
16-
17-
The UK Environment Agency Flood Monitoring only provides data for England - Northern Ireland, Scotland and Wales have their own flood agencies.
18-
19-
{% endimportant %}
20-
21-
## Configuration
22-
23-
Home Assistant offers the flood monitoring integration through **Settings** -> **Devices & services** -> **Environment Agency Flood Gauges**.
24-
25-
You will be prompted to select a monitoring station. You can find the name of nearby monitoring stations on the Flood information service [website](https://check-for-flooding.service.gov.uk/river-and-sea-levels).
26-
27-
Sensors for that monitoring station should then appear in your Home Assistant instance.
1+
---
2+
title: UK Environment Agency Flood Monitoring
3+
description: Monitor nearby water levels and be prepared for flooding with the UK Environment Agency API integration.
4+
ha_category:
5+
- Sensor
6+
ha_release: 0.115
7+
ha_iot_class: Cloud Polling
8+
ha_config_flow: true
9+
ha_codeowners:
10+
- '@Jc2k'
11+
---
12+
13+
The `eafm` 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.
14+
15+
{% important %}
16+
17+
The UK Environment Agency Flood Monitoring only provides data for England - Northern Ireland, Scotland and Wales have their own flood agencies.
18+
19+
{% endimportant %}
20+
21+
## Configuration
22+
23+
Home Assistant offers the flood monitoring integration through **Settings** -> **Devices & services** -> **Environment Agency Flood Gauges**.
24+
25+
You will be prompted to select a monitoring station. You can find the name of nearby monitoring stations on the Flood information service [website](https://check-for-flooding.service.gov.uk/river-and-sea-levels).
26+
27+
Sensors for that monitoring station should then appear in your Home Assistant instance.

‎source/_integrations/ipp.md renamed to ‎source/_integrations/ipp.markdown

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
1-
---
2-
title: Internet Printing Protocol (IPP)
3-
description: Instructions on how to integrate printers that support the Internet Printing Protocol (IPP) into Home Assistant.
4-
ha_category:
5-
- System monitor
6-
ha_release: 0.108
7-
ha_iot_class: Local Polling
8-
ha_config_flow: true
9-
ha_codeowners:
10-
- '@ctalkington'
11-
ha_domain: ipp
12-
---
13-
14-
The `Internet Printing Protocol (IPP)` integration allows you to read current data from your networked printer that supports the [Internet Printing Protocol](https://www.pwg.org/ipp/everywhere.html).
15-
16-
It provides information about the printer's state and remaining ink levels.
17-
18-
{% include integrations/config_flow.md %}
1+
---
2+
title: Internet Printing Protocol (IPP)
3+
description: Instructions on how to integrate printers that support the Internet Printing Protocol (IPP) into Home Assistant.
4+
ha_category:
5+
- System monitor
6+
ha_release: 0.108
7+
ha_iot_class: Local Polling
8+
ha_config_flow: true
9+
ha_codeowners:
10+
- '@ctalkington'
11+
ha_domain: ipp
12+
---
13+
14+
The `Internet Printing Protocol (IPP)` integration allows you to read current data from your networked printer that supports the [Internet Printing Protocol](https://www.pwg.org/ipp/everywhere.html).
15+
16+
It provides information about the printer's state and remaining ink levels.
17+
18+
{% include integrations/config_flow.md %}

‎source/_integrations/linkplay.md renamed to ‎source/_integrations/linkplay.markdown

Lines changed: 54 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -1,54 +1,54 @@
1-
---
2-
title: LinkPlay
3-
description: Connect and control your LinkPlay media players using the LinkPlay integration
4-
ha_category:
5-
- Media player
6-
ha_domain: linkplay
7-
ha_zeroconf: true
8-
ha_integration_type: integration
9-
ha_release: 2024.8
10-
ha_codeowners:
11-
- '@Velleman'
12-
ha_config_flow: true
13-
ha_platforms:
14-
- media_player
15-
- button
16-
ha_iot_class: Local Polling
17-
---
18-
19-
The LinkPlay {% term integrations %} for Home Assistant allows you to control various media players based on the LinkPlay protocol. The integration supports auto-discovery on your local network through [Zeroconf](/integrations/zeroconf).
20-
21-
{% include integrations/config_flow.md %}
22-
23-
## Features
24-
25-
### Media Player
26-
27-
The media player entity offers robust controls and playback features from the media player integration and provides additionally:
28-
29-
- **Preset playback**: Play LinkPlay presets configured on the device using the action `linkplay.play_preset`.
30-
- **Multiroom**: Combine multiple LinkPlay devices in a multiroom. Use the actions `media_player.join` and `media_player.unjoin`.
31-
32-
### Buttons
33-
34-
The button entities provide some additional LinkPlay features available on the device:
35-
36-
- **Time Sync**: Synchronize the device's internal clock with the current time in Home Assistant.
37-
- **Restart Device**: Reboot the device, allowing for convenient troubleshooting and maintenance.
38-
39-
## Actions
40-
41-
The LinkPlay integration makes various custom actions available in addition to the [standard media player actions](/integrations/media_player/#actions).
42-
43-
### Action `linkplay.play_preset`
44-
45-
Play a preset on a LinkPlay media player.
46-
47-
{% note %}
48-
Companion apps, such as 4stream, allow to save music presets (for example, Spotify playlists). This action can be used to start playing these presets.
49-
{% endnote %}
50-
51-
| Data attribute | Optional | Description |
52-
| ---------------------- | -------- | ----------- |
53-
| `entity_id` | no | The speakers to target. To target all LinkPlay devices, use `all`.
54-
| `preset_number` | no | The number of the preset to play.
1+
---
2+
title: LinkPlay
3+
description: Connect and control your LinkPlay media players using the LinkPlay integration
4+
ha_category:
5+
- Media player
6+
ha_domain: linkplay
7+
ha_zeroconf: true
8+
ha_integration_type: integration
9+
ha_release: 2024.8
10+
ha_codeowners:
11+
- '@Velleman'
12+
ha_config_flow: true
13+
ha_platforms:
14+
- media_player
15+
- button
16+
ha_iot_class: Local Polling
17+
---
18+
19+
The LinkPlay {% term integrations %} for Home Assistant allows you to control various media players based on the LinkPlay protocol. The integration supports auto-discovery on your local network through [Zeroconf](/integrations/zeroconf).
20+
21+
{% include integrations/config_flow.md %}
22+
23+
## Features
24+
25+
### Media Player
26+
27+
The media player entity offers robust controls and playback features from the media player integration and provides additionally:
28+
29+
- **Preset playback**: Play LinkPlay presets configured on the device using the action `linkplay.play_preset`.
30+
- **Multiroom**: Combine multiple LinkPlay devices in a multiroom. Use the actions `media_player.join` and `media_player.unjoin`.
31+
32+
### Buttons
33+
34+
The button entities provide some additional LinkPlay features available on the device:
35+
36+
- **Time Sync**: Synchronize the device's internal clock with the current time in Home Assistant.
37+
- **Restart Device**: Reboot the device, allowing for convenient troubleshooting and maintenance.
38+
39+
## Actions
40+
41+
The LinkPlay integration makes various custom actions available in addition to the [standard media player actions](/integrations/media_player/#actions).
42+
43+
### Action `linkplay.play_preset`
44+
45+
Play a preset on a LinkPlay media player.
46+
47+
{% note %}
48+
Companion apps, such as 4stream, allow to save music presets (for example, Spotify playlists). This action can be used to start playing these presets.
49+
{% endnote %}
50+
51+
| Data attribute | Optional | Description |
52+
| ---------------------- | -------- | ----------- |
53+
| `entity_id` | no | The speakers to target. To target all LinkPlay devices, use `all`.
54+
| `preset_number` | no | The number of the preset to play.

‎source/_integrations/locative.md renamed to ‎source/_integrations/locative.markdown

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
1-
---
2-
title: "Locative"
3-
description: "Instructions on how to use Locative to track devices in Home Assistant."
4-
ha_category:
5-
- Presence detection
6-
ha_release: 0.86
7-
ha_iot_class: Cloud Push
8-
ha_domain: locative
9-
---
10-
11-
This platform allows you to detect presence using [Locative](https://www.locative.app/). Locative is an open source app for [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location.
12-
13-
Install on your smartphone:
14-
15-
- [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4)
16-
17-
To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant instance at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on its first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
18-
19-
<p class='img'>
20-
<img src='/images/screenshots/locative.png'/>
21-
</p>
22-
23-
When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".
1+
---
2+
title: "Locative"
3+
description: "Instructions on how to use Locative to track devices in Home Assistant."
4+
ha_category:
5+
- Presence detection
6+
ha_release: 0.86
7+
ha_iot_class: Cloud Push
8+
ha_domain: locative
9+
---
10+
11+
This platform allows you to detect presence using [Locative](https://www.locative.app/). Locative is an open source app for [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location.
12+
13+
Install on your smartphone:
14+
15+
- [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4)
16+
17+
To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant instance at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on its first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
18+
19+
<p class='img'>
20+
<img src='/images/screenshots/locative.png'/>
21+
</p>
22+
23+
When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".

0 commit comments

Comments
 (0)
0