update Home Assistant brand identity references

This commit is contained in:
Jason Hunter 2021-05-19 00:08:41 -04:00 committed by Blake Blackshear
parent c52782aa3f
commit e89697fab0
9 changed files with 69 additions and 67 deletions

View File

@ -62,7 +62,7 @@ Example of a finished row corresponding to the below example image:
```yaml
motion:
mask: '0,461,3,0,1919,0,1919,843,1699,492,1344,458,1346,336,973,317,869,375,866,432'
mask: "0,461,3,0,1919,0,1919,843,1699,492,1344,458,1346,336,973,317,869,375,866,432"
```
![poly](/img/example-mask-poly.png)
@ -405,12 +405,13 @@ The input and output parameters need to be adjusted for MJPEG cameras
- -fflags
- +genpts+discardcorrupt
- -r
- '3' # <---- adjust depending on your desired frame rate from the mjpeg image
- "3" # <---- adjust depending on your desired frame rate from the mjpeg image
- -use_wallclock_as_timestamps
- '1'
- "1"
```
Note that mjpeg cameras require encoding the video into h264 for clips, recording, and rtmp roles. This will use significantly more CPU than if the cameras supported h264 feeds directly.
```yaml
output_args:
record: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v libx264 -an
@ -436,7 +437,7 @@ ffmpeg:
- -fflags
- +genpts+discardcorrupt
- -use_wallclock_as_timestamps
- '1'
- "1"
```
### Reolink 410/520 (possibly others)
@ -457,9 +458,9 @@ ffmpeg:
- -fflags
- +genpts+discardcorrupt
- -rw_timeout
- '5000000'
- "5000000"
- -use_wallclock_as_timestamps
- '1'
- "1"
```
### Blue Iris RTSP Cameras
@ -480,7 +481,7 @@ ffmpeg:
- -rtsp_transport
- tcp
- -stimeout
- '5000000'
- "5000000"
- -use_wallclock_as_timestamps
- '1'
- "1"
```

View File

@ -25,5 +25,5 @@ Many people have powerful enough NAS devices or home servers to also run docker.
To install make sure you have the [community app plugin here](https://forums.unraid.net/topic/38582-plug-in-community-applications/). Then search for "Frigate" in the apps section within Unraid - you can see the online store [here](https://unraid.net/community/apps?q=frigate#r)
| Name | Inference Speed | Notes |
| ----------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| ------------------------------------ | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [M2 Coral Edge TPU](http://coral.ai) | 6.2ms | Install the Coral plugin from Unraid Community App Center [info here](https://forums.unraid.net/topic/98064-support-blakeblackshear-frigate/?do=findComment&comment=949789) |

View File

@ -25,7 +25,7 @@ HassOS users can install via the addon repository. Frigate requires an MQTT serv
Make sure you choose the right image for your architecture:
| Arch | Image Name |
|-|-|
| ----------- | ------------------------------------------ |
| amd64 | blakeblackshear/frigate:stable-amd64 |
| amd64nvidia | blakeblackshear/frigate:stable-amd64nvidia |
| armv7 | blakeblackshear/frigate:stable-armv7 |
@ -34,7 +34,7 @@ Make sure you choose the right image for your architecture:
It is recommended to run with docker-compose:
```yaml
version: '3.9'
version: "3.9"
services:
frigate:
container_name: frigate
@ -53,10 +53,10 @@ services:
tmpfs:
size: 1000000000
ports:
- '5000:5000'
- '1935:1935' # RTMP feeds
- "5000:5000"
- "1935:1935" # RTMP feeds
environment:
FRIGATE_RTSP_PASSWORD: 'password'
FRIGATE_RTSP_PASSWORD: "password"
```
If you can't use docker compose, you can run the container with something similar to this:
@ -120,5 +120,5 @@ lxc.cap.drop:
```
### ESX
For details on running Frigate under ESX, see details [here](https://github.com/blakeblackshear/frigate/issues/305).
For details on running Frigate under ESX, see details [here](https://github.com/blakeblackshear/frigate/issues/305).

View File

@ -125,26 +125,26 @@ Sample response:
"total": 1000,
"used": 700,
"free": 300,
"mnt_type": "ext4",
"mnt_type": "ext4"
},
"/media/frigate/recordings": {
"total": 1000,
"used": 700,
"free": 300,
"mnt_type": "ext4",
"mnt_type": "ext4"
},
"/tmp/cache": {
"total": 256,
"used": 100,
"free": 156,
"mnt_type": "tmpfs",
"mnt_type": "tmpfs"
},
"/dev/shm": {
"total": 256,
"used": 100,
"free": 156,
"mnt_type": "tmpfs",
},
"mnt_type": "tmpfs"
}
}
}
}

View File

@ -31,11 +31,13 @@ Frigate publishes event information in the form of a change feed via MQTT. This
Note that some people may not want to expose frigate to the web, so you can leverage the HA API that frigate custom_integration ties into (which is exposed to the web, and thus can be used for mobile notifications etc):
To load an image taken by frigate from Home Assistants API see below:
```
https://HA_URL/api/frigate/notifications/<event-id>/thumbnail.jpg
```
To load a video clip taken by frigate from Home Assistants API :
```
https://HA_URL/api/frigate/notifications/<event-id>/<camera>/clip.mp4
```
@ -57,7 +59,6 @@ automation:
tag: '{{trigger.payload_json["after"]["id"]}}'
```
```yaml
automation:
- alias: When a person enters a zone named yard
@ -106,7 +107,7 @@ automation:
action:
- service: notify.mobile_app_pixel_3
data_template:
message: 'High confidence dog detection.'
message: "High confidence dog detection."
data:
image: "https://url.com/api/frigate/notifications/{{trigger.payload_json['after']['id']}}/thumbnail.jpg"
tag: "{{trigger.payload_json['after']['id']}}"