Merge remote-tracking branch 'origin/master' into dev

This commit is contained in:
Blake Blackshear 2024-06-14 06:45:21 -05:00
commit 4078a147ef
3 changed files with 6 additions and 5 deletions

View File

@ -13,7 +13,7 @@ Depending on your system, these parameters may not be compatible. More informati
## Raspberry Pi 3/4 ## Raspberry Pi 3/4
Ensure you increase the allocated RAM for your GPU to at least 128 (`raspi-config` > Performance Options > GPU Memory). Ensure you increase the allocated RAM for your GPU to at least 128 (`raspi-config` > Performance Options > GPU Memory).
If you are using the HA addon, you may need to use the full access variant and turn off `Protection mode` for hardware acceleration. If you are using the HA addon, you may need to use the full access variant and turn off `Protection mode` for hardware acceleration.
```yaml ```yaml
@ -67,7 +67,7 @@ Or map in all the `/dev/video*` devices.
### Via VAAPI ### Via VAAPI
VAAPI supports automatic profile selection so it will work automatically with both H.264 and H.265 streams. VAAPI is recommended for all generations of Intel-based CPUs if QSV does not work. VAAPI supports automatic profile selection so it will work automatically with both H.264 and H.265 streams. VAAPI is recommended for all generations of Intel-based CPUs.
```yaml ```yaml
ffmpeg: ffmpeg:
@ -82,7 +82,7 @@ With some of the processors, like the J4125, the default driver `iHD` doesn't se
### Via Quicksync (>=10th Generation only) ### Via Quicksync (>=10th Generation only)
QSV must be set specifically based on the video encoding of the stream. If VAAPI does not work for you, you can try QSV if your processor supports it. QSV must be set specifically based on the video encoding of the stream.
#### H.264 streams #### H.264 streams

View File

@ -150,7 +150,8 @@ Home Assistant > Configuration > Integrations > Frigate > Options
| Platform | Description | | Platform | Description |
| --------------- | --------------------------------------------------------------------------------- | | --------------- | --------------------------------------------------------------------------------- |
| `camera` | Live camera stream (requires RTSP), camera for image of the last detected object. | | `camera` | Live camera stream (requires RTSP). |
| `image` | Image of the latest detected object for each camera. |
| `sensor` | States to monitor Frigate performance, object counts for all zones and cameras. | | `sensor` | States to monitor Frigate performance, object counts for all zones and cameras. |
| `switch` | Switch entities to toggle detection, recordings and snapshots. | | `switch` | Switch entities to toggle detection, recordings and snapshots. |
| `binary_sensor` | A "motion" binary sensor entity per camera/zone/object. | | `binary_sensor` | A "motion" binary sensor entity per camera/zone/object. |

View File

@ -37,7 +37,7 @@ The USB Coral can become stuck and need to be restarted, this can happen for a n
## PCIe Coral Not Detected ## PCIe Coral Not Detected
The most common reason for the PCIe coral not being detected is that the driver has not been installed. See [the coral docs(https://coral.ai/docs/m2/get-started/#2-install-the-pcie-driver-and-edge-tpu-runtime) for how to install the driver for the PCIe based coral. The most common reason for the PCIe coral not being detected is that the driver has not been installed. See [the coral docs](https://coral.ai/docs/m2/get-started/#2-install-the-pcie-driver-and-edge-tpu-runtime) for how to install the driver for the PCIe based coral.
## Only One PCIe Coral Is Detected With Coral Dual EdgeTPU ## Only One PCIe Coral Is Detected With Coral Dual EdgeTPU