[Support]: Home Assistant Add-on: Frigate crashing Home Assistant #22090
Unanswered
wanders2
asked this question in
General Support
Replies: 13 comments
-
|
Based on the logs you've provided, the issue appears to be resource contention rather than a Frigate-specific crash. The logs show Frigate is starting and running normally - the key indicators are:
The errors you're seeing in the Home Assistant core logs ( To diagnose the actual cause of Home Assistant instability: Check Resource Usage:
Configuration Optimizations:
detect:
fps: 5
Recommendations:
The Frigate logs show normal operation - the issue is likely resource exhaustion on the Home Assistant host rather than a Frigate bug. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I don't think there is a resource issue. I'm running home assistant on an older dell laptop with 9 cpus see screen shots below. Frigate / Home Assistant crashed while I was getting the screen shotshots below. CPU was at 27% just prior to crash. Frigate is now down.
Questions
*
How do you adjust shm-size on the home assistant add-on.
*
The home assistant add-on is using frigate 16.4. Looking at the documentation it appears 16.3 is the last stable version. Is this correct?
I've attached logs and a lot of screen shots. Hope this helps
System performance - frigate not running
[cid:710c9b13-c8ec-49c8-bf1d-3d78b3d01eec]
System performance Frigate running
[cid:9a9405cb-c057-4511-9319-1ed3217e5120]
VAInfo Output
{"return_code":0,"stderr":"","stdout":"vainfo: VA-API version: 1.22 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.3.3 ()
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileVP8Version0_3 : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD"}
From <http://homeassistant.local:8123/ccab4aaf_frigate>
Frigate running
[cid:9dd7d995-df3e-4138-98ca-4672ef79abad]
Frigate running
[cid:0b53d852-3233-4c36-9045-0ddd363630a6]
[cid:63b78df0-091e-4e8a-8af7-6568a85e1b83]
System performance Frigate running
[cid:7ef2b859-8ee3-4a86-8878-4b4a2db93f9f]
…________________________________
From: inkeep-ai-assistant[bot] ***@***.***>
Sent: Sunday, February 22, 2026 6:28 PM
To: blakeblackshear/frigate ***@***.***>
Cc: wanders2 ***@***.***>; Author ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Support]: Home Assistant Add-on: Frigate crashing Home Assistant (Discussion #22090)
Based on the logs you've provided, the issue appears to be resource contention rather than a Frigate-specific crash. The logs show Frigate is starting and running normally - the key indicators are:
1. Frigate successfully starts all processes (recording, review, detection, capture processes for all cameras)(1)<https://docs.frigate.video/guides/getting_started>
2. The USB Coral TPU is detected and functioning(1)<https://docs.frigate.video/guides/getting_started>
3. go2rtc starts successfully(1)<https://docs.frigate.video/guides/getting_started>
4. API requests are being served normally(1)<https://docs.frigate.video/guides/getting_started>
The errors you're seeing in the Home Assistant core logs (RuntimeError: Session is closed) are occurring during Home Assistant shutdown/restart, not from Frigate causing the crash(2)<https://docs.frigate.video/integrations/home-assistant>. These are typical cleanup errors when Home Assistant is stopping.
To diagnose the actual cause of Home Assistant instability:
Check Resource Usage:
* Monitor CPU, memory, and disk I/O when Frigate is running
* Your configuration has 5 active cameras with recording, detection, and audio enabled
* The shm-size (shared memory) allocation may need adjustment(1)<https://docs.frigate.video/guides/getting_started>
Configuration Optimizations:
1. Reduce detection load - Your detect FPS is set to 5 globally, which is appropriate(3)<https://docs.frigate.video/configuration/reference>:
detect:
fps: 5
(3)<https://docs.frigate.video/configuration/reference>
1. Verify hardware acceleration - Your config shows VAAPI is auto-detected(4)<https://docs.frigate.video/configuration/hardware_acceleration_video>:
[2026-02-22 15:00:18] frigate.util.services INFO : Automatically detected vaapi hwaccel for video decoding
(4)<https://docs.frigate.video/configuration/hardware_acceleration_video>
1. Check storage - With 5 cameras recording continuously at high resolution, verify you have adequate disk space and I/O capacity(3)<https://docs.frigate.video/configuration/reference>
Recommendations:
1. Check Home Assistant system resources (Settings → System → Hardware)
2. Verify the Docker container has sufficient memory allocated
3. Consider reducing retention periods temporarily to see if disk I/O is the bottleneck(3)<https://docs.frigate.video/configuration/reference>
4. Review Home Assistant supervisor logs for memory/resource warnings
The Frigate logs show normal operation - the issue is likely resource exhaustion on the Home Assistant host rather than a Frigate bug.
📚 Sources:
1. Getting Started<https://docs.frigate.video/guides/getting_started>
2. Home Assistant Integration<https://docs.frigate.video/integrations/home-assistant>
3. Full Reference Config<https://docs.frigate.video/configuration/reference>
4. Video Decoding<https://docs.frigate.video/configuration/hardware_acceleration_video>
________________________________
Have another question? Just tag @inkeep<https://inkeep.com>.
—
Reply to this email directly, view it on GitHub<#22090 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFMW6YSCRFRXTDWZS7WTSQD4NJCRTAVCNFSM6AAAAACV4EMABKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOBZGIYDENI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
2026-02-23 15:55:09.570956158 [INFO] Starting NGINX...
2026-02-23 15:55:10.111434177 [INFO] No TLS certificate found. Generating a self signed certificate...
2026-02-23 15:55:23.964179436 127.0.0.1 - - [23/Feb/2026:09:55:23 -0600] "" 400 0 "-" "-" "-"
2026-02-23 15:55:24.018254618 2026/02/23 09:55:24 [error] 217#217: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2026-02-23 15:55:24.018276613 2026/02/23 09:55:24 [error] 217#217: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2026-02-23 15:55:29.068160101 2026/02/23 09:55:29 [error] 218#218: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2026-02-23 15:55:29.068171785 2026/02/23 09:55:29 [error] 218#218: *4 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2026-02-23 15:55:34.123524720 2026/02/23 09:55:34 [error] 219#219: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2026-02-23 15:55:34.123535513 2026/02/23 09:55:34 [error] 219#219: *6 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2026-02-23 15:55:39.166746425 2026/02/23 09:55:39 [error] 220#220: *8 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2026-02-23 15:55:39.166773802 2026/02/23 09:55:39 [error] 220#220: *8 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2026-02-23 15:55:44.206979801 2026/02/23 09:55:44 [error] 217#217: *10 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2026-02-23 15:55:44.206993873 2026/02/23 09:55:44 [error] 217#217: *10 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2026-02-23 15:55:49.253999411 2026/02/23 09:55:49 [error] 217#217: *12 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2026-02-23 15:55:49.254003323 2026/02/23 09:55:49 [error] 217#217: *12 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2026-02-23 15:55:54.317168692 2026/02/23 09:55:54 [error] 217#217: *14 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2026-02-23 15:55:54.317175643 2026/02/23 09:55:54 [error] 217#217: *14 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2026-02-23 15:55:59.588962773 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET // HTTP/1.1" 200 2721 "http://homeassistant.local:8123/ccab4aaf_frigate" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.763060660 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /fonts/Inter-Regular.woff2 HTTP/1.1" 200 108488 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0/assets/i18n-B4RQL4LC.css" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.771545399 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/config HTTP/1.1" 200 37811 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.772716290 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/profile HTTP/1.1" 200 39 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.792418042 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/profile HTTP/1.1" 200 39 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.877886558 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/go2rtc/streams/reolink_doorbell HTTP/1.1" 200 3270 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.889627890 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/go2rtc/streams/Garage HTTP/1.1" 200 2579 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.894625429 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/go2rtc/streams/Basement HTTP/1.1" 200 2579 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.900172985 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/go2rtc/streams/reolink_ceiling HTTP/1.1" 200 3287 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.929878076 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/review?limit=10&severity=alert HTTP/1.1" 200 2165 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.969481276 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/Garage/latest.webp?height=360&store=1&cache=1771861800 HTTP/1.1" 200 14394 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:59.972918056 172.30.32.2 - - [23/Feb/2026:09:55:59 -0600] "GET /api/Basement/latest.webp?height=360&store=1&cache=1771861800 HTTP/1.1" 200 18804 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.007179407 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Garage/latest.webp?height=351&store=1&cache=1771861800 HTTP/1.1" 200 13512 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.008577981 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Basement/latest.webp?height=351&store=1&cache=1771861800 HTTP/1.1" 200 17884 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.030670765 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/reolink_doorbell/latest.webp?height=360&store=1&cache=1771861800 HTTP/1.1" 200 3654 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.048549880 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/reolink_ceiling/latest.webp?height=360&store=1&cache=1771861800 HTTP/1.1" 200 3654 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.057516620 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/review/1771861141.716721-e2pg1o/preview?format=mp4 HTTP/1.1" 404 47 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.062273383 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/reolink_doorbell/latest.webp?height=351&store=1&cache=1771861800 HTTP/1.1" 200 3544 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.076535377 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/reolink_ceiling/latest.webp?height=351&store=1&cache=1771861800 HTTP/1.1" 200 3544 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.080577617 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/review/1771860768.155884-22j1hh/preview?format=mp4 HTTP/1.1" 404 47 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.112587521 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Garage/latest.webp?height=351&cache=1771862160168 HTTP/1.1" 200 13580 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.118384646 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/reolink_doorbell/latest.webp?height=351&cache=1771862160168 HTTP/1.1" 200 3544 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.120188928 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Basement/latest.webp?height=351&cache=1771862160168 HTTP/1.1" 200 17884 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.150766691 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/reolink_ceiling/latest.webp?height=351&cache=1771862160168 HTTP/1.1" 200 3544 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.158799337 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Garage/latest.webp?height=351&cache=1771862160426 HTTP/1.1" 200 13580 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.160154529 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Basement/latest.webp?height=351&cache=1771862160434 HTTP/1.1" 200 17884 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.476849055 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Basement/latest.webp?height=351&cache=1771862160673 HTTP/1.1" 200 17900 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.478920544 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/review/1771861137.17693-rc6scf/preview?format=mp4 HTTP/1.1" 206 9826 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.483820635 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Garage/latest.webp?height=351&cache=1771862160673 HTTP/1.1" 200 13656 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.788027854 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Garage/latest.webp?height=351&cache=1771862160998 HTTP/1.1" 200 13730 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:00.791320741 172.30.32.2 - - [23/Feb/2026:09:56:00 -0600] "GET /api/Basement/latest.webp?height=351&cache=1771862160991 HTTP/1.1" 200 17928 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:01.070829313 172.30.32.2 - - [23/Feb/2026:09:56:01 -0600] "GET /api/Basement/latest.webp?height=351&cache=1771862161306 HTTP/1.1" 200 17756 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:01.072073567 172.30.32.2 - - [23/Feb/2026:09:56:01 -0600] "GET /api/Garage/latest.webp?height=351&cache=1771862161303 HTTP/1.1" 200 13748 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:01.369399612 172.30.32.2 - - [23/Feb/2026:09:56:01 -0600] "GET /api/Basement/latest.webp?height=351&cache=1771862161584 HTTP/1.1" 200 17842 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:01.374742139 172.30.32.2 - - [23/Feb/2026:09:56:01 -0600] "GET /api/Garage/latest.webp?height=351&cache=1771862161587 HTTP/1.1" 200 13762 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:01.567683018 172.30.32.2 - - [23/Feb/2026:09:56:01 -0600] "GET /api/Garage/latest.webp?height=351&cache=1771862161842 HTTP/1.1" 200 13752 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:01.595375836 172.30.32.2 - - [23/Feb/2026:09:56:01 -0600] "GET /api/Basement/latest.webp?height=351&cache=1771862161875 HTTP/1.1" 200 17840 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:01.766659819 172.30.32.2 - - [23/Feb/2026:09:56:01 -0600] "GET /api/go2rtc/streams/reolink_spare HTTP/1.1" 200 2217 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:01.965515346 172.30.32.2 - - [23/Feb/2026:09:56:01 -0600] "GET /api/reolink_ceiling/latest.webp?height=351&cache=1771862162245 HTTP/1.1" 200 12576 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:02.241373011 172.30.32.2 - - [23/Feb/2026:09:56:02 -0600] "GET /api/reolink_ceiling/latest.webp?height=351&cache=1771862162480 HTTP/1.1" 200 12520 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:02.509433783 172.30.32.2 - - [23/Feb/2026:09:56:02 -0600] "GET /api/reolink_ceiling/latest.webp?height=351&cache=1771862162755 HTTP/1.1" 200 12544 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:02.762363788 172.30.32.2 - - [23/Feb/2026:09:56:02 -0600] "GET /api/reolink_ceiling/latest.webp?height=351&cache=1771862163022 HTTP/1.1" 200 12544 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:02.834370389 172.30.32.2 - - [23/Feb/2026:09:56:02 -0600] "GET /api/reolink_doorbell/latest.webp?height=351&cache=1771862163110 HTTP/1.1" 200 15626 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:02.871751962 172.30.32.2 - - [23/Feb/2026:09:56:02 -0600] "GET /api/reolink_ceiling/latest.webp?height=351&cache=1771862163156 HTTP/1.1" 200 12488 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:03.079888706 172.30.32.2 - - [23/Feb/2026:09:56:03 -0600] "GET /api/reolink_doorbell/latest.webp?height=351&cache=1771862163347 HTTP/1.1" 200 15642 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:03.341957513 172.30.32.2 - - [23/Feb/2026:09:56:03 -0600] "GET /api/reolink_doorbell/latest.webp?height=351&cache=1771862163592 HTTP/1.1" 200 15638 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:03.638061290 172.30.32.2 - - [23/Feb/2026:09:56:03 -0600] "GET /api/reolink_doorbell/latest.webp?height=351&cache=1771862163854 HTTP/1.1" 200 15664 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:03.838132303 172.30.32.2 - - [23/Feb/2026:09:56:03 -0600] "GET /api/reolink_doorbell/latest.webp?height=351&cache=1771862164058 HTTP/1.1" 200 15606 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:05.469953089 172.30.32.2 - - [23/Feb/2026:09:56:05 -0600] "GET /fonts/Inter-SemiBold.woff2 HTTP/1.1" 200 111588 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0/assets/i18n-B4RQL4LC.css" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:05.492555648 172.30.32.2 - - [23/Feb/2026:09:56:05 -0600] "GET /api/config HTTP/1.1" 200 37811 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:05.497488110 172.30.32.2 - - [23/Feb/2026:09:56:05 -0600] "GET /api/review?limit=10&severity=alert HTTP/1.1" 200 2165 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:05.497755271 172.30.32.2 - - [23/Feb/2026:09:56:05 -0600] "GET /api/profile HTTP/1.1" 200 39 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:09.044088800 172.30.32.2 - - [23/Feb/2026:09:56:09 -0600] "GET /live/mse/api/ws?src=Garage HTTP/1.1" 101 621087 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:09.044205198 172.30.32.2 - - [23/Feb/2026:09:56:09 -0600] "GET /live/mse/api/ws?src=Basement HTTP/1.1" 101 589960 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:09.044437472 172.30.32.2 - - [23/Feb/2026:09:56:09 -0600] "GET /live/mse/api/ws?src=reolink_doorbell HTTP/1.1" 101 1600995 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:09.044720857 172.30.32.2 - - [23/Feb/2026:09:56:09 -0600] "GET /live/mse/api/ws?src=reolink_ceiling HTTP/1.1" 101 1537973 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:09.091974926 172.30.32.2 - - [23/Feb/2026:09:56:09 -0600] "GET /fonts/Inter-Medium.woff2 HTTP/1.1" 200 111380 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0/assets/i18n-B4RQL4LC.css" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:09.091985221 172.30.32.2 - - [23/Feb/2026:09:56:09 -0600] "GET /api/config HTTP/1.1" 200 37811 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0/settings" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:15.614174906 172.30.32.2 - - [23/Feb/2026:09:56:15 -0600] "GET /api/config/raw HTTP/1.1" 200 14520 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0/config" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:23.405687571 172.30.32.2 - - [23/Feb/2026:09:56:23 -0600] "GET /api/logs/frigate?start=-100 HTTP/1.1" 200 4335 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0/logs" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:24.039988439 127.0.0.1 - - [23/Feb/2026:09:56:24 -0600] "" 400 0 "-" "-" "-"
2026-02-23 15:56:25.175524336 172.30.32.2 - - [23/Feb/2026:09:56:25 -0600] "GET /api/logs/go2rtc?start=-100 HTTP/1.1" 200 817 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0/logs" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:27.580234309 172.30.32.2 - - [23/Feb/2026:09:56:27 -0600] "GET /api/logs/go2rtc?download=true HTTP/1.1" 200 782 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0/logs" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:56:30.376563143 172.30.32.2 - - [23/Feb/2026:09:56:30 -0600] "GET /api/logs/nginx?start=-100 HTTP/1.1" 200 29102 "http://homeassistant.local:8123/api/hassio_ingress/gqXcFN8kk8gkvBEWhUM0bJA2kLN1wMM5k6HYjBER-y0/logs" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0" "192.168.1.202, 172.30.32.1"
2026-02-23 15:55:19.591025830 [INFO] Starting go2rtc healthcheck service...
2026-02-23 15:55:23.414656986 [INFO] Preparing new go2rtc config...
2026-02-23 15:55:23.614149108 [INFO] Got IP address from supervisor: 192.168.7.60
2026-02-23 15:55:23.643388262 [INFO] Got WebRTC port from supervisor: 8555
2026-02-23 15:55:24.071302929 [INFO] Starting go2rtc...
2026-02-23 15:55:24.657634705 09:55:24.657 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
2026-02-23 15:55:24.657689255 09:55:24.657 INF config path=/dev/shm/go2rtc.yaml
2026-02-23 15:55:24.658718058 09:55:24.658 INF [api] listen addr=:1984
2026-02-23 15:55:24.658850496 09:55:24.658 INF [rtsp] listen addr=:8554
2026-02-23 15:55:24.659336698 09:55:24.659 INF [webrtc] listen addr=:8555
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Based on your follow-up information, I can address your questions: Regarding shm-size for Home Assistant Add-on: For Home Assistant OS users, the shared memory allocation is handled differently than standalone Docker installations(1). Home Assistant Supervisor automatically allocates The shm-size cannot be set per container for Home Assistant add-ons(1). This is managed at the supervisor level, not within the add-on configuration. Regarding Frigate version 0.16.4: The logs show you're running Frigate 0.16.4-4131252(2). Frigate uses semantic versioning where stable releases are tagged as Analysis of your situation: Your logs from February 23, 2026 show Frigate starting successfully(3):
However, I notice your Frigate logs are incomplete - they only show the startup sequence and NGINX/go2rtc logs, not the full Frigate application logs that would show camera processing, detection activity, or any errors leading to the crash. What's missing to diagnose this properly:
The fact that Frigate appears to start successfully each time, combined with Home Assistant crashing hours later, suggests this could be a memory leak, disk I/O saturation, or database growth issue rather than a Frigate configuration problem. Recommended next steps:
📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Attached are the supervisor logs not seeing anything to indicate the source of the problem
…________________________________
From: Bill Anderson ***@***.***>
Sent: Monday, February 23, 2026 12:54 PM
To: blakeblackshear/frigate ***@***.***>; blakeblackshear/frigate ***@***.***>
Cc: Author ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Support]: Home Assistant Add-on: Frigate crashing Home Assistant (Discussion #22090)
I don't think there is a resource issue. I'm running home assistant on an older dell laptop with 9 cpus see screen shots below. Frigate / Home Assistant crashed while I was getting the screen shotshots below. CPU was at 27% just prior to crash. Frigate is now down.
Questions
*
How do you adjust shm-size on the home assistant add-on.
*
The home assistant add-on is using frigate 16.4. Looking at the documentation it appears 16.3 is the last stable version. Is this correct?
I've attached logs and a lot of screen shots. Hope this helps
System performance - frigate not running
[cid:710c9b13-c8ec-49c8-bf1d-3d78b3d01eec]
System performance Frigate running
[cid:9a9405cb-c057-4511-9319-1ed3217e5120]
VAInfo Output
{"return_code":0,"stderr":"","stdout":"vainfo: VA-API version: 1.22 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.3.3 ()
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileVP8Version0_3 : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD"}
From <http://homeassistant.local:8123/ccab4aaf_frigate>
Frigate running
[cid:9dd7d995-df3e-4138-98ca-4672ef79abad]
Frigate running
[cid:0b53d852-3233-4c36-9045-0ddd363630a6]
[cid:63b78df0-091e-4e8a-8af7-6568a85e1b83]
System performance Frigate running
[cid:7ef2b859-8ee3-4a86-8878-4b4a2db93f9f]
________________________________
From: inkeep-ai-assistant[bot] ***@***.***>
Sent: Sunday, February 22, 2026 6:28 PM
To: blakeblackshear/frigate ***@***.***>
Cc: wanders2 ***@***.***>; Author ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Support]: Home Assistant Add-on: Frigate crashing Home Assistant (Discussion #22090)
Based on the logs you've provided, the issue appears to be resource contention rather than a Frigate-specific crash. The logs show Frigate is starting and running normally - the key indicators are:
1. Frigate successfully starts all processes (recording, review, detection, capture processes for all cameras)(1)<https://docs.frigate.video/guides/getting_started>
2. The USB Coral TPU is detected and functioning(1)<https://docs.frigate.video/guides/getting_started>
3. go2rtc starts successfully(1)<https://docs.frigate.video/guides/getting_started>
4. API requests are being served normally(1)<https://docs.frigate.video/guides/getting_started>
The errors you're seeing in the Home Assistant core logs (RuntimeError: Session is closed) are occurring during Home Assistant shutdown/restart, not from Frigate causing the crash(2)<https://docs.frigate.video/integrations/home-assistant>. These are typical cleanup errors when Home Assistant is stopping.
To diagnose the actual cause of Home Assistant instability:
Check Resource Usage:
* Monitor CPU, memory, and disk I/O when Frigate is running
* Your configuration has 5 active cameras with recording, detection, and audio enabled
* The shm-size (shared memory) allocation may need adjustment(1)<https://docs.frigate.video/guides/getting_started>
Configuration Optimizations:
1. Reduce detection load - Your detect FPS is set to 5 globally, which is appropriate(3)<https://docs.frigate.video/configuration/reference>:
detect:
fps: 5
(3)<https://docs.frigate.video/configuration/reference>
1. Verify hardware acceleration - Your config shows VAAPI is auto-detected(4)<https://docs.frigate.video/configuration/hardware_acceleration_video>:
[2026-02-22 15:00:18] frigate.util.services INFO : Automatically detected vaapi hwaccel for video decoding
(4)<https://docs.frigate.video/configuration/hardware_acceleration_video>
1. Check storage - With 5 cameras recording continuously at high resolution, verify you have adequate disk space and I/O capacity(3)<https://docs.frigate.video/configuration/reference>
Recommendations:
1. Check Home Assistant system resources (Settings → System → Hardware)
2. Verify the Docker container has sufficient memory allocated
3. Consider reducing retention periods temporarily to see if disk I/O is the bottleneck(3)<https://docs.frigate.video/configuration/reference>
4. Review Home Assistant supervisor logs for memory/resource warnings
The Frigate logs show normal operation - the issue is likely resource exhaustion on the Home Assistant host rather than a Frigate bug.
📚 Sources:
1. Getting Started<https://docs.frigate.video/guides/getting_started>
2. Home Assistant Integration<https://docs.frigate.video/integrations/home-assistant>
3. Full Reference Config<https://docs.frigate.video/configuration/reference>
4. Video Decoding<https://docs.frigate.video/configuration/hardware_acceleration_video>
________________________________
Have another question? Just tag @inkeep<https://inkeep.com>.
—
Reply to this email directly, view it on GitHub<#22090 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFMW6YSCRFRXTDWZS7WTSQD4NJCRTAVCNFSM6AAAAACV4EMABKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOBZGIYDENI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Based on the information provided, I can see that you're experiencing Home Assistant crashes when Frigate is running. Without access to the actual supervisor logs you mentioned attaching (they don't appear in the message), I can provide guidance based on what's typically needed to diagnose this type of issue(1). Regarding your questions:
Key observations from your logs: Your Frigate installation appears to start successfully with:
To properly diagnose the crash, you would need to check:
Recommended troubleshooting steps:
Since the supervisor logs you mentioned aren't visible in the message, those would be critical for identifying the root cause of the Home Assistant crashes. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'd like to downgrade to version 16.3. Which version of the home assistant addon is that ? I'm planning to us HACS to do this. Just don't know what version to select
…________________________________
From: inkeep-ai-assistant[bot] ***@***.***>
Sent: Monday, February 23, 2026 1:11 PM
To: blakeblackshear/frigate ***@***.***>
Cc: wanders2 ***@***.***>; Author ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Support]: Home Assistant Add-on: Frigate crashing Home Assistant (Discussion #22090)
Based on the information provided, I can see that you're experiencing Home Assistant crashes when Frigate is running. Without access to the actual supervisor logs you mentioned attaching (they don't appear in the message), I can provide guidance based on what's typically needed to diagnose this type of issue(1)<https://docs.frigate.video/frigate/installation>.
Regarding your questions:
1. shm-size adjustment for Home Assistant Add-on: For Home Assistant OS users, the shared memory allocation is handled automatically by Home Assistant Supervisor, which allocates /dev/shm with half the size of your total memory(1)<https://docs.frigate.video/frigate/installation>. The shm-size cannot be set per container for Home Assistant add-ons(1)<https://docs.frigate.video/frigate/installation>. This is managed at the supervisor level, not within the add-on configuration.
2. Frigate version 0.16.4 vs 0.16.3: The current stable version of Frigate is 0.16.3(2)<https://docs.frigate.video/frigate/updating>. Your logs show you're running 0.16.4-4131252, which appears to be a development or pre-release version. The official documentation states: "The current stable version of Frigate is 0.16.3"(2)<https://docs.frigate.video/frigate/updating>.
Key observations from your logs:
Your Frigate installation appears to start successfully with:
* go2rtc starting properly (version 1.9.9)(3)<https://docs.frigate.video/guides/getting_started>
* VAAPI hardware acceleration detected(4)<https://docs.frigate.video/configuration/hardware_acceleration_video>
* All camera processes initializing(3)<https://docs.frigate.video/guides/getting_started>
* Coral TPU detection(3)<https://docs.frigate.video/guides/getting_started>
To properly diagnose the crash, you would need to check:
1. Home Assistant Supervisor logs - Look for out-of-memory (OOM) events, watchdog timeouts, or other system-level failures
2. Complete Frigate application logs - Not just NGINX/go2rtc logs, but the full Frigate process logs showing camera processing and any errors
3. System resource metrics - Memory usage, disk I/O, and CPU over time when Frigate is running
4. Database growth - Check if the Frigate database (frigate.db) is growing excessively
Recommended troubleshooting steps:
1. Consider downgrading to the stable version 0.16.3(2)<https://docs.frigate.video/frigate/updating>
2. Monitor disk I/O and memory usage over extended periods
3. Check available disk space for recordings(3)<https://docs.frigate.video/guides/getting_started>
4. Review retention settings to ensure they're not causing excessive storage usage(3)<https://docs.frigate.video/guides/getting_started>
Since the supervisor logs you mentioned aren't visible in the message, those would be critical for identifying the root cause of the Home Assistant crashes.
📚 Sources:
1. Installation<https://docs.frigate.video/frigate/installation>
2. Updating Frigate<https://docs.frigate.video/frigate/updating>
3. Getting Started<https://docs.frigate.video/guides/getting_started>
4. Video Decoding<https://docs.frigate.video/configuration/hardware_acceleration_video>
________________________________
Have another question? Just tag @inkeep<https://inkeep.com/>.
—
Reply to this email directly, view it on GitHub<#22090 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFMW6YR5JIME5LZ6QASYIEL4NNGFRAVCNFSM6AAAAACV4EMABKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJQGA4TCNA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
For the Home Assistant Add-on, you should select the Frigate add-on version that corresponds to Frigate 0.16.3(1). The Home Assistant Add-on version numbers typically match the Frigate version numbers directly(2). To downgrade the Frigate Home Assistant Add-on to version 0.16.3:
Important clarification about HACS: HACS (Home Assistant Community Store) is used for the Frigate Home Assistant Integration, not the Frigate Add-on itself(2). These are two separate components:
The Frigate Add-on (the NVR software itself) should be updated/downgraded through the Home Assistant Add-on Store, not through HACS(2). After downgrading:
If you're unable to find version 0.16.3 in the dropdown, you may need to check the addon repository settings or manually specify the version in the addon configuration. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm running version 2026.2.3. I'm not seeing the option to downgrade to a specific version. When I tried the CLI I received the following
➜ ~ ha apps update -h
This command can upgrade a Home Assistant app to its latest version.
It is currently not possible to upgrade/downgrade to a specific version.
Can you double check to see if it's possible to downgrade a specific app in home assistant? If not what is the process to uninstall and reinstall. Is there any cleanup that needs to happen beside clicking the uninstall button?
…________________________________
From: inkeep-ai-assistant[bot] ***@***.***>
Sent: Monday, February 23, 2026 1:25 PM
To: blakeblackshear/frigate ***@***.***>
Cc: wanders2 ***@***.***>; Author ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Support]: Home Assistant Add-on: Frigate crashing Home Assistant (Discussion #22090)
For the Home Assistant Add-on, you should select the Frigate add-on version that corresponds to Frigate 0.16.3(1)<https://docs.frigate.video/frigate/updating>. The Home Assistant Add-on version numbers typically match the Frigate version numbers directly(2)<https://docs.frigate.video/frigate/installation>.
To downgrade the Frigate Home Assistant Add-on to version 0.16.3:
1. Navigate to Settings > Add-ons in Home Assistant(1)<https://docs.frigate.video/frigate/updating>
2. Find your installed Frigate addon (e.g., "Frigate NVR" or "Frigate NVR (Full Access)")(1)<https://docs.frigate.video/frigate/updating>
3. Click on the addon to open its details page
4. Look for the version dropdown or update section
5. Select version 0.16.3 from the available versions
6. Click "Install" or "Update" to apply the version change(1)<https://docs.frigate.video/frigate/updating>
7. After the installation completes, restart the addon(1)<https://docs.frigate.video/frigate/updating>
Important clarification about HACS:
HACS (Home Assistant Community Store) is used for the Frigate Home Assistant Integration, not the Frigate Add-on itself(2)<https://docs.frigate.video/frigate/installation>. These are two separate components:
* Frigate Add-on: Installed through Home Assistant's Add-on Store (Settings > Add-ons)(2)<https://docs.frigate.video/frigate/installation>
* Frigate Integration: Installed through HACS to connect Home Assistant to Frigate(2)<https://docs.frigate.video/frigate/installation>
The Frigate Add-on (the NVR software itself) should be updated/downgraded through the Home Assistant Add-on Store, not through HACS(2)<https://docs.frigate.video/frigate/installation>.
After downgrading:
1. Check the addon logs to ensure Frigate starts successfully(1)<https://docs.frigate.video/frigate/updating>
2. Access the Frigate Web UI to confirm the version is 0.16.3(1)<https://docs.frigate.video/frigate/updating>
3. Monitor your system for stability improvements
If you're unable to find version 0.16.3 in the dropdown, you may need to check the addon repository settings or manually specify the version in the addon configuration.
📚 Sources:
1. Updating Frigate<https://docs.frigate.video/frigate/updating>
2. Installation<https://docs.frigate.video/frigate/installation>
________________________________
Have another question? Just tag @inkeep<https://inkeep.com/>.
—
Reply to this email directly, view it on GitHub<#22090 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFMW6YQ225XU2JSYFQZEXPD4NNH4DAVCNFSM6AAAAACV4EMABKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJQGEYDGMA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
You're correct - Home Assistant does not currently support downgrading add-ons to specific versions through the UI or CLI(1). The documentation for updating the Home Assistant Addon states you can update to newer versions, but doesn't provide a built-in downgrade mechanism(1). To install a specific version of the Frigate add-on, you'll need to uninstall and reinstall: Uninstall Process:
What Gets Preserved: With Frigate 0.16+, the addon configuration directory location changed(2). Your Frigate config file and database are now stored in Reinstall Process:
Cleanup Notes: No additional cleanup should be necessary beyond the uninstall button, as long as you preserve the addon data(2). Your configuration file ( Alternative Approach: If you're unable to install a specific version through the standard add-on store, you may need to:
After reinstalling, verify the version by checking the Frigate Web UI or logs to confirm you're running 0.16.3(1). 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Couldn't work on this for a few days. Went to do a downgrade and found out that version 0.17.0 is released and the latest stable version. I've upgrade to version 0.17.0. Lets give this a few days and see how it runs
…________________________________
From: inkeep-ai-assistant[bot] ***@***.***>
Sent: Monday, February 23, 2026 6:46 PM
To: blakeblackshear/frigate ***@***.***>
Cc: wanders2 ***@***.***>; Author ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Support]: Home Assistant Add-on: Frigate crashing Home Assistant (Discussion #22090)
You're correct - Home Assistant does not currently support downgrading add-ons to specific versions through the UI or CLI(1)<https://docs.frigate.video/frigate/updating>. The documentation for updating the Home Assistant Addon states you can update to newer versions, but doesn't provide a built-in downgrade mechanism(1)<https://docs.frigate.video/frigate/updating>.
To install a specific version of the Frigate add-on, you'll need to uninstall and reinstall:
Uninstall Process:
1. Navigate to Settings > Add-ons in Home Assistant(1)<https://docs.frigate.video/frigate/updating>
2. Find your Frigate addon (e.g., "Frigate NVR" or "Frigate NVR (Full Access)")(1)<https://docs.frigate.video/frigate/updating>
3. Click on the addon
4. Click "Uninstall"
5. Important: When uninstalling, you'll see an option "Also permanently delete this addon's data" - do NOT check this box if you want to preserve your configuration and database(2)<#16334>
What Gets Preserved:
With Frigate 0.16+, the addon configuration directory location changed(2)<#16334>. Your Frigate config file and database are now stored in /addon_configs/ccab4aaf_frigate (or similar, depending on your addon variant)(2)<#16334>. As long as you don't check the "permanently delete" option during uninstall, this directory and all its contents will be preserved(2)<#16334>.
Reinstall Process:
1. Go back to Settings > Add-ons(1)<https://docs.frigate.video/frigate/updating>
2. Click "Add-on Store"
3. Find the Frigate addon repository
4. Before installing, check if there's a way to specify the version (this may require adding a specific repository URL for the 0.16.3 release)
5. Install the addon
6. After installation, restart the addon(1)<https://docs.frigate.video/frigate/updating>
Cleanup Notes:
No additional cleanup should be necessary beyond the uninstall button, as long as you preserve the addon data(2)<#16334>. Your configuration file (config.yaml), database (frigate.db), and recordings should all remain intact in the /addon_configs directory(2)<#16334>.
Alternative Approach:
If you're unable to install a specific version through the standard add-on store, you may need to:
* Check if there's a beta or development repository that allows version selection
* Consider temporarily switching between the stable and beta addon variants (they use different addon slugs)(2)<#16334>
After reinstalling, verify the version by checking the Frigate Web UI or logs to confirm you're running 0.16.3(1)<https://docs.frigate.video/frigate/updating>.
📚 Sources:
1. Updating Frigate<https://docs.frigate.video/frigate/updating>
2. Migrate database and config from Home Assistant /config to addon's /config<#16334>
________________________________
Have another question? Just tag @inkeep<https://inkeep.com/>.
—
Reply to this email directly, view it on GitHub<#22090 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFMW6YSQJO5LUNTBTQVRMPD4NONMRAVCNFSM6AAAAACV4EMABKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJQGMYTONI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
\Great approach! Upgrading to Frigate 0.17.0 is a good step forward. To update your Home Assistant Add-on to version 0.17.0, you should:(1)
After upgrading to 0.17.0: Monitor your system over the next few days for:
Important notes about version 0.17.0: The documentation for updating Frigate states that you should ensure your If you continue to experience crashes after a few days on 0.17.0, the issue is likely environmental (resource constraints, disk I/O, or memory) rather than a Frigate version-specific bug. In that case, you may want to:
Feel free to report back after a few days of testing with 0.17.0! 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Well that didn't take long frigate crashed between 9:13 and 9:17. I do have CPU and memory metrics this time. While there are spikes, there still appears to be plenty of resources. Frigate Add-on is throwing errors with Frigate down. I think this is to be expected but wanted to check. I'm going to disable all but one camera see if that makes things stable. Let me know if you have any ideas.
[cid:657d8ca0-b40e-46a9-910c-930ef6e5e975]
[cid:7d84ffae-ad66-4509-974f-cb48d0ec13a4]
[cid:df149cb9-4a36-491d-aa21-856d3b650fd8]
…________________________________
From: inkeep-ai-assistant[bot] ***@***.***>
Sent: Friday, February 27, 2026 9:13 AM
To: blakeblackshear/frigate ***@***.***>
Cc: wanders2 ***@***.***>; Author ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Support]: Home Assistant Add-on: Frigate crashing Home Assistant (Discussion #22090)
\Great approach! Upgrading to Frigate 0.17.0 is a good step forward. To update your Home Assistant Add-on to version 0.17.0, you should:(1)<https://docs.frigate.video/frigate/updating>
1. Navigate to Settings → Add-ons in Home Assistant(1)<https://docs.frigate.video/frigate/updating>
2. Find your Frigate addon (e.g., "Frigate NVR" or "Frigate NVR (Full Access)")(1)<https://docs.frigate.video/frigate/updating>
3. If an update is available, you'll see an "Update" button(1)<https://docs.frigate.video/frigate/updating>
4. Click the "Update" button next to the Frigate addon(1)<https://docs.frigate.video/frigate/updating>
5. Wait for the process to complete(1)<https://docs.frigate.video/frigate/updating>
6. After updating, restart the addon by clicking "Restart"(1)<https://docs.frigate.video/frigate/updating>
7. Check the addon logs to ensure Frigate starts without errors(1)<https://docs.frigate.video/frigate/updating>
8. Access the Frigate Web UI to confirm the new version is running(1)<https://docs.frigate.video/frigate/updating>
After upgrading to 0.17.0:
Monitor your system over the next few days for:
* Home Assistant stability (no unexpected restarts)
* Memory usage trends
* Disk I/O patterns
* Any errors in the Frigate or Home Assistant logs
Important notes about version 0.17.0:
The documentation for updating Frigate states that you should ensure your /config/frigate.yml is compatible with the new version by reviewing the Release notes.(1)<https://docs.frigate.video/frigate/updating> Since you're jumping from 0.16.4 to 0.17.0, there may be configuration changes or new features to be aware of.
If you continue to experience crashes after a few days on 0.17.0, the issue is likely environmental (resource constraints, disk I/O, or memory) rather than a Frigate version-specific bug. In that case, you may want to:
1. Review your retention settings to reduce storage load(2)<https://docs.frigate.video/guides/getting_started>
2. Consider reducing the number of active cameras temporarily
3. Monitor system resources more closely during operation
Feel free to report back after a few days of testing with 0.17.0!
📚 Sources:
1. Updating Frigate<https://docs.frigate.video/frigate/updating>
2. Getting Started<https://docs.frigate.video/guides/getting_started>
________________________________
Have another question? Just tag @inkeep<https://inkeep.com/>.
—
Reply to this email directly, view it on GitHub<#22090 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFMW6YSWILD24VFL5KZJPVT4OBNIXAVCNFSM6AAAAACV4EMABKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJUG44TSOI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Based on the crash pattern you're experiencing (crashes within minutes of starting Frigate), combined with resource metrics showing available capacity, this points to a more specific issue than general resource exhaustion(1). The errors from the Frigate integration when Frigate is down are expected behavior - the integration cannot connect to the stopped Frigate service(1). Diagnostic Steps: Your plan to disable cameras is a good troubleshooting approach(1). However, given the rapid crash timeline (4 minutes), I recommend collecting more specific diagnostic information first:
Configuration Review: Looking at your configuration from the earlier messages, several areas could be optimized: Your birdseye:
enabled: true
mode: continuousConsider temporarily changing this to birdseye:
enabled: true
mode: objectsYour audio detection is enabled on multiple cameras with multiple listen types(2): audio:
enabled: true
max_not_heard: 30
min_volume: 500
listen:
- bark
- fire_alarm
- scream
- speech
- yellAudio detection adds processing overhead(2). Consider temporarily disabling it to test stability: audio:
enabled: falseRecommended Testing Sequence:
Critical Question: Are you seeing any specific error messages in the Frigate logs right before the crash? The logs you've shared show successful startup but don't include the period leading up to the crash. Those final log entries would be crucial for diagnosis. The rapid crash pattern (minutes rather than hours) suggests a specific trigger rather than gradual resource exhaustion. This could be:
📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
I'm running the Frigate Addon. It has been stable for several years but about a month ago it started crashing home assistant. I was able to verify this by stopping Frigate for a week. Home Assistant stayed stable. after starting frigate Home assistant crashed within a few hours. the last restart happened some time before 4:23 2/22. (time stamp comes from an automation triggered by a home assistant restart event)
Version
Frigate Addon version
What browser(s) are you using?
Edge / Chrome /firefox
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
No response
Install method
Home Assistant Add-on
docker-compose file or Docker CLI command
N/AObject Detector
Coral
Network connection
Mixed
Camera make and model
Amcrest and Reolink
Screenshots of the Frigate UI's System metrics pages
Frigate crashed
Any other information that may be helpful
This has been happening for some time know. If Frigate is stopped home assistant is stable. if Frigate is started home assistant reboots within a few hours
core logs below
�[33m2026-02-22 14:15:31.290 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.thermostat is taking over 10 seconds�[0m
�[31m2026-02-22 14:15:53.250 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[33m2026-02-22 14:16:01.291 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.thermostat is taking over 10 seconds�[0m
�[33m2026-02-22 14:16:21.291 WARNING (MainThread) [homeassistant.components.climate] Updating honeywell climate took longer than the scheduled update interval 0:00:30�[0m
�[31m2026-02-22 14:17:15.024 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:18:36.960 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:19:58.970 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:21:20.765 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:22:42.616 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[33m2026-02-22 14:24:01.304 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.thermostat is taking over 10 seconds�[0m
�[31m2026-02-22 14:24:04.188 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[33m2026-02-22 14:24:21.305 WARNING (MainThread) [homeassistant.components.climate] Updating honeywell climate took longer than the scheduled update interval 0:00:30�[0m
�[31m2026-02-22 14:25:25.720 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:26:47.553 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:28:09.442 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:29:31.053 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:30:52.634 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:31:30.647 ERROR (MainThread) [frontend.js.modern.202601286] Uncaught error from Edge 145.0.0.0 on Windows 10
Error: Failed to execute 'define' on 'CustomElementRegistry': the name "focus-trap" has already been used with this registry
S.define (node_modules/@webcomponents/scoped-custom-element-registry/src/scoped-custom-element-registry.ts:180:12)
/hacsfiles/advanced-camera-card/card-ab1f0025.js:70:3686�[0m
�[31m2026-02-22 14:32:14.015 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[33m2026-02-22 14:33:01.315 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.thermostat is taking over 10 seconds�[0m
�[33m2026-02-22 14:33:21.315 WARNING (MainThread) [homeassistant.components.climate] Updating honeywell climate took longer than the scheduled update interval 0:00:30�[0m
�[31m2026-02-22 14:33:35.864 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:34:57.306 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[31m2026-02-22 14:36:19.043 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]�[0m
�[33m2026-02-22 14:36:26.597 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration presence_simulation which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m
�[33m2026-02-22 14:36:26.599 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m
�[33m2026-02-22 14:36:26.600 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration battery_notes which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m
�[33m2026-02-22 14:36:26.601 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m
�[33m2026-02-22 14:36:26.602 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration alarmo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m
�[33m2026-02-22 14:36:26.603 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration watchman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m
�[33m2026-02-22 14:36:26.604 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration spook_inverse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m
�[33m2026-02-22 14:36:26.605 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration spook which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m
�[33m2026-02-22 14:36:26.607 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration webrtc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m
�[31m2026-02-22 14:37:39.272 ERROR (MainThread) [custom_components.frigate.api] Client response error (500) for URL http://ccab4aaf-frigate:5000/api/stats: Internal Server Error�[0m
s6-rc: info: service legacy-services: stopping
�[33m2026-02-22 14:40:02.870 WARNING (MainThread) [homeassistant.core] Task <Task pending name='service homeassistant.restart' coro=<_async_admin_handler() running at /usr/src/homeassistant/homeassistant/helpers/service.py:941> wait_for=<Task pending name='admin service homeassistant.restart' coro=<async_setup..async_handle_core_service() running at /usr/src/homeassistant/homeassistant/components/homeassistant/init.py:238> wait_for= cb=[set.remove(), Task.task_wakeup()]> cb=[set.remove()]> was still running after final writes shutdown stage; Integrations should cancel non-critical tasks when receiving the stop event to prevent delaying shutdown�[0m
�[31m2026-02-22 14:40:03.019 ERROR (MainThread) [reolink_aio.api] Host 192.168.7.55:443: RuntimeError "Session is closed" occurred, traceback:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5943, in send_chunk
response = await self._aiohttp_session.post(url=self._url, json=filtered_body, params=param, allow_redirects=False, timeout=self._timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 529, in _request
raise RuntimeError("Session is closed")
RuntimeError: Session is closed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5943, in send_chunk
response = await self._aiohttp_session.post(url=self._url, json=filtered_body, params=param, allow_redirects=False, timeout=self._timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 529, in _request
raise RuntimeError("Session is closed")
RuntimeError: Session is closed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5943, in send_chunk
response = await self._aiohttp_session.post(url=self._url, json=filtered_body, params=param, allow_redirects=False, timeout=self._timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 529, in _request
raise RuntimeError("Session is closed")
RuntimeError: Session is closed
�[0m
�[31m2026-02-22 14:40:03.019 ERROR (MainThread) [homeassistant.components.reolink] Unexpected error fetching reolink.Reolink Video Doorbell WiFi data
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5943, in send_chunk
response = await self._aiohttp_session.post(url=self._url, json=filtered_body, params=param, allow_redirects=False, timeout=self._timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 529, in _request
raise RuntimeError("Session is closed")
RuntimeError: Session is closed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5943, in send_chunk
response = await self._aiohttp_session.post(url=self._url, json=filtered_body, params=param, allow_redirects=False, timeout=self._timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 529, in _request
raise RuntimeError("Session is closed")
RuntimeError: Session is closed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 416, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 307, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/reolink/init.py", line 150, in async_device_config_update
await host.update_states()
File "/usr/src/homeassistant/homeassistant/components/reolink/host.py", line 509, in update_states
await self._api.get_states(cmd_list=self.update_cmd, wake=wake)
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 2347, in get_states
json_data = await self.send(body, expected_response_type="json")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5809, in send
return await self.send_chunk(body, param, expected_response_type, retry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5878, in send_chunk
await self._login_open_port()
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 1489, in _login_open_port
await self.login()
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 1321, in login
json_data = await self.send(body, param, expected_response_type="json")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5809, in send
return await self.send_chunk(body, param, expected_response_type, retry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 6091, in send_chunk
return await self.send(body, param, expected_response_type, retry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5809, in send
return await self.send_chunk(body, param, expected_response_type, retry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 6091, in send_chunk
return await self.send(body, param, expected_response_type, retry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5809, in send
return await self.send_chunk(body, param, expected_response_type, retry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 6094, in send_chunk
raise err
File "/usr/local/lib/python3.13/site-packages/reolink_aio/api.py", line 5943, in send_chunk
response = await self._aiohttp_session.post(url=self._url, json=filtered_body, params=param, allow_redirects=False, timeout=self._timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 529, in _request
raise RuntimeError("Session is closed")
RuntimeError: Session is closed�[0m
�[31m2026-02-22 14:40:03.152 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.7.30 for modules 'Time, DeviceModule' after first update: ('Unable to query the device: 192.168.7.30: Session is closed', RuntimeError('Session is closed'))�[0m
�[31m2026-02-22 14:40:03.152 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.7.30 individually for module query 'get_device_time' after first update: ('Unable to query the device: 192.168.7.30: Session is closed', RuntimeError('Session is closed'))�[0m
�[31m2026-02-22 14:40:03.152 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.7.30 individually for module query 'get_device_info' after first update: ('Unable to query the device: 192.168.7.30: Session is closed', RuntimeError('Session is closed'))�[0m
�[31m2026-02-22 14:40:03.152 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.7.30 individually for module query 'get_device_usage' after first update: ('Unable to query the device: 192.168.7.30: Session is closed', RuntimeError('Session is closed'))�[0m
�[31m2026-02-22 14:40:03.152 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.7.30 data: Unable to communicate with the device update: get_device_info not found in {'get_device_time': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_info': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_usage': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>} for device 192.168.7.30�[0m
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
Beta Was this translation helpful? Give feedback.
All reactions