jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-24 01:37:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Integrations - move related topics to meta data (#32414)

Browse Source
This commit is contained in:
c0ffeeca7 2024-04-22 16:52:33 +02:00 committed by GitHub
parent 6d58f9cea0
commit 936ec1e060
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
7 changed files with 74 additions and 64 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

61
source/_integrations/ezviz.markdown
View File

@ -25,6 +25,9 @@ ha_platforms:
- switch
- update
ha_integration_type: integration
related:
- docs: /dashboards/picture-glance/#creating-a-card-to-control-the-camera
title: Controlling the camera from the dashboard
---
The `ezviz` sensor platform uses the ezvizlife.com API to interact with the devices.
@ -74,61 +77,61 @@ You can also change the camera options should you need to access a high or low r
If your EZVIZ camera supports warning sounds, you can use this service to set the intensity.
| Service data attribute | Description |
| -----------------------| ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| `level` | Set the sound level to 0 for Soft, 1 for Intensive or 2 to disable |
| Service data attribute | Description |
| ---------------------- | ---------------------------------------------------------------------------------------------------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| `level` | Set the sound level to 0 for Soft, 1 for Intensive or 2 to disable |
### Service `ezviz.ptz`
If your EZVIZ camera supports <abbr title="pan, tilt, and zoom">PTZ</abbr>, you will be able to pan or tilt your camera.
| Service data attribute | Description |
| -----------------------| ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| `direction` | Direction of the movement. Allowed values: `up`, `down`, `left`, `right` |
| `speed` | (Optional) Speed to in which to move the camera. Allowed values: int from 1 to 9. Default: 5 |
| Service data attribute | Description |
| ---------------------- | ---------------------------------------------------------------------------------------------------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| `direction` | Direction of the movement. Allowed values: `up`, `down`, `left`, `right` |
| `speed` | (Optional) Speed to in which to move the camera. Allowed values: int from 1 to 9. Default: 5 |
### Service `ezviz.set_alarm_detection_sensibility`
If your EZVIZ camera supports motion detection, you will be able to set the sensitivity level using this service.
| Service data attribute | Description |
| -----------------------| ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| `level` | Sensibility level (1-6) for type 0 (Normal camera) or (1-100) for type 3 (PIR sensor camera). |
| `type_value` | Type of detection. Options : 0 - Camera or 3 - PIR Sensor Camera. |
| Service data attribute | Description |
| ---------------------- | ---------------------------------------------------------------------------------------------------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| `level` | Sensibility level (1-6) for type 0 (Normal camera) or (1-100) for type 3 (PIR sensor camera). |
| `type_value` | Type of detection. Options : 0 - Camera or 3 - PIR Sensor Camera. |
### Service `ezviz.sound_alarm`
If your EZVIZ camera has a built-in siren, you can use this service to make a noise.
| Service data attribute | Description |
| -----------------------| ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| `enable` | Sound the alarm by setting this to 1 or stop the siren by setting this to 0. |
| Service data attribute | Description |
| ---------------------- | ---------------------------------------------------------------------------------------------------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| `enable` | Sound the alarm by setting this to 1 or stop the siren by setting this to 0. |
### Service `ezviz.wake_device`
If you have "sleep" mode enabled on your camera, you can use this service to wake it. Especially useful for battery cameras.
| Service data attribute | Description |
| -----------------------| ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| Service data attribute | Description |
| ---------------------- | ---------------------------------------------------------------------------------------------------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
To enable/disable motion detection, use the Home Assistant built in services.
### Service `camera.enable_motion_detection`
| Service data attribute | Description |
| -----------------------| ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| Service data attribute | Description |
| ---------------------- | ---------------------------------------------------------------------------------------------------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
### Service `camera.disable_motion_detection`
| Service data attribute | Description |
| -----------------------| ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
| Service data attribute | Description |
| ---------------------- | ---------------------------------------------------------------------------------------------------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
### Alarm control panel entity
@ -166,7 +169,3 @@ The image entity represents the last detected event from a camera and visually r
## Troubleshooting
- `authentication failed`: The authentication requires an EZVIZ account with two-step verification disabled. Google, Facebook, TikTok, or other Oauth-based accounts will not work.
## Related topics
- [Controlling the camera from the dashboard](/dashboards/picture-glance/#creating-a-card-to-control-the-camera)

5
source/_integrations/history.markdown
View File

@ -9,6 +9,11 @@ ha_codeowners:
- '@home-assistant/core'
ha_domain: history
ha_integration_type: system
related:
- docs: /integrations/recorder/
title: Recorder integration
- url: https://data.home-assistant.io
title: Home Assistant Data Science Portal
---
The **History** integration tracks everything that is going on within Home

18
source/_integrations/matter.markdown
View File

@ -26,6 +26,13 @@ ha_platforms:
- sensor
- switch
ha_integration_type: integration
related:
- docs: /integrations/thread/
title: Thread
- docs: /integrations/homekit_controller/
title: HomeKit
- docs: /integrations/homekit_controller/#adding-a-homekit-device-through-thread
title: Adding an Apple HomeKit device through Thread
---
The Matter integration allows you to control Matter devices on your local Wi-Fi or {% term Thread %} network.
@ -356,14 +363,3 @@ Also see this [extended troubleshooting guide](https://developers.home.google.co
The Matter protocol relies on (local) IPv6 and mDNS (multicast traffic) which should be able to travel freely in your network. Matter devices that use Wi-Fi (including Thread border routers) must be on the same LAN/VLAN as Home Assistant. Matter devices that only use {% term Thread %} must be joined to {% term Thread %} networks for which there is at least one border router connected to the Home Assistant LAN.
If you experience any issues with discovering devices (for example, if the initial {% term commissioning %} keeps failing or if devices become unavailable randomly), investigate your network topology. For instance, a setting on your router or Wi-Fi access point to "optimize" multicast traffic can harm the (discovery) traffic from Matter devices. Keep this in mind when you experience issues trying to add or control Matter devices. Protocols like Matter are designed for regular residential network setups and may not integrate well with enterprise networking solutions like VLANs, Multicast filtering, and (malfunctioning) IGMP snooping. To avoid issues, try to keep your network topology as simple and flat as possible.
## Related topics
### Related integrations
- [Thread](/integrations/thread/)
- [HomeKit](/integrations/homekit_controller/)
### Related guides
- [Adding an Apple HomeKit device through Thread](/integrations/homekit_controller/#adding-a-homekit-device-through-thread)

5
source/_integrations/ollama.markdown
View File

@ -10,6 +10,11 @@ ha_codeowners:
- '@synesthesiam'
ha_domain: ollama
ha_integration_type: service
related:
- docs: /docs/configuration/templating/
title: Home Assistant Templating
- docs: /docs/automation/trigger/#sentence-trigger
title: Sentence trigger
---
The **Ollama** {% term integration %} adds a conversation agent in Home Assistant powered by a local [Ollama](https://ollama.com/) server.

7
source/_integrations/prusalink.markdown
View File

@ -16,6 +16,13 @@ ha_platforms:
- camera
- sensor
ha_dhcp: true
related:
- url: https://help.prusa3d.com/article/prusa-connect-and-prusalink-explained_302608
title: PrusaLink documentation
- url: https://help.prusa3d.com/guide/prusalink-and-prusa-connect-setup-mk3-s-_221744
title: PrusaLink installation guide for Prusa MK3 with Raspberry Pi Zero W
- url: https://help.prusa3d.com/guide/prusalink-prusa-connect-with-rpi-3-4-usb-mk2-5-s-mk3-s-_469341
title: Sentence trigger
---
The **PrusaLink** {% term integration %} allows you to monitor your [Prusa 3D printer](https://www.prusa3d.com) and its progress with your Home Assistant installation. This integration works with Prusa MINI/MINI+, Prusa MK3.9/MK4, Prusa XL, and with the older Raspberry Pi-based Prusa MK2.5/MK3.

7
source/_integrations/recovery_mode.markdown
View File

@ -8,6 +8,9 @@ ha_codeowners:
ha_domain: recovery_mode
ha_quality_scale: internal
ha_integration_type: system
related:
- docs: /docs/troubleshooting_general/
title: General troubleshooting
---
The **Recovery mode** integration is an internal integration used by the
@ -26,7 +29,3 @@ the Home Assistant frontend, settings and add-ons.
This gives you the possibility to correct the issue and restart Home Assistant
to re-try.
## Related topics
- [General troubleshooting](/docs/troubleshooting_general/)

35
source/_integrations/thread.markdown
View File

@ -12,6 +12,23 @@ ha_config_flow: true
ha_platforms:
- diagnostics
ha_zeroconf: true
related:
- docs: /yellow/
title: Home Assistant Yellow - hub
- docs: /skyconnect/
title: Home Assistant SkyConnect - Zigbee/Thread USB stick
- docs: /integrations/matter/
title: Matter
- docs: /integrations/homekit_controller/
title: HomeKit
- docs: /integrations/matter/#adding-a-matter-device-to-home-assistant
title: Adding a Matter device to Home Assistant
- docs: /integrations/homekit_controller/#adding-a-homekit-device-through-thread
title: Adding an Apple HomeKit device through Thread
- url: https://skyconnect.home-assistant.io/procedures/enable-thread/
title: Enabling Thread on SkyConnect
- url: https://yellow.home-assistant.io/procedures/enable-thread/
title: Enabling Thread on Yellow
---
The Thread integration helps you track the different Thread networks in your home and store the Thread network credentials (similar to a Wi-Fi password). The Thread integration in Home Assistant is currently still a work in progress.
@ -226,21 +243,3 @@ You can only set a Thread network as preferred if the credentials are known.
In the current implementation, having multiple <abbr title="Thread border routers">TBRs</abbr> from different vendors results in separate networks using different credentials. This prevents devices from roaming between the Thread networks. In theory, it would be better to join all Thread networks into a single network to increase the size of the mesh network. A dense mesh network should lead to better <abbr title="radio frequency">RF</abbr> coverage and better link quality, which lowers transmission latencies, making communication faster.
## Related topics
### Related hardware
- [Home Assistant Yellow](/yellow/) hub
- [Home Assistant SkyConnect](/skyconnect/) Zigbee/Thread USB stick
### Related integrations for smart home standards
- [Matter](/integrations/matter/)
- [HomeKit](/integrations/homekit_controller/)
### Related guides
- [Adding a Matter device to Home Assistant](/integrations/matter/#adding-a-matter-device-to-home-assistant)
- [Adding an Apple HomeKit device through Thread](/integrations/homekit_controller/#adding-a-homekit-device-through-thread)
- [Enabling Thread on SkyConnect](https://skyconnect.home-assistant.io/procedures/enable-thread/)
- [Enabling Thread on Yellow](https://yellow.home-assistant.io/procedures/enable-thread/)