ElixirForge/frigate
1
0
Fork 0
mirror of https://github.com/alexhopeoconnor/frigate.git synced 2026-10-22 03:02:09 +10:00
Code Releases Activity

Docs tweaks (#23787)

Browse Source 
* docs fixes

* backend tweaks

* regenerate i18n

* tweak genai

* add config overrides section

* add common errors

* add suggestions for rebuilding a corrupt database
This commit is contained in:
Josh Hawkins
2026-07-22 11:13:58 -05:00
committed by GitHub
parent c0cf08ab4a
commit 168cbea9ea
17 changed files with 593 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/docs/integrations/home-assistant.md
+1 -1
View File
@@ -281,7 +281,7 @@ For advanced usecases, this behavior can be changed with the [RTSP URL
template](#options) option. When set, this string will override the default stream
address that is derived from the default behavior described above. This option supports
[jinja2 templates](https://jinja.palletsprojects.com/) and has the `camera` dict
variables from [Frigate API](../integrations/api)
variables from [Frigate API](/integrations/api/frigate-http-api)
available for the template. Note that no Home Assistant state is available to the
template, only the camera dict from Frigate.
docs/docs/integrations/mqtt.md
+1 -1
View File
@@ -16,7 +16,7 @@ MQTT requires a network connection to your broker. This is typically local, but
### `frigate/available`
Designed to be used as an availability topic with Home Assistant. Possible message are:
"online": published when Frigate is running (on startup)
"online": published once Frigate is running and has published its initial state. Note that this is published on every connection to the broker, so it is republished if the broker restarts or the connection drops and recovers, without Frigate itself restarting.
"stopped": published when Frigate is stopped normally
"offline": published automatically by the MQTT broker if Frigate disconnects unexpectedly (via MQTT Will Message)