[Experience + Proposal] Universal local video surveillance in Gladys — go2rtc + Frigate (person/dog/horse detection... without cloud)

[Will_71]

Otherwise, the detection has nothing to do with the TAPO app. Once it’s in place, I think I’ll disable it on the TAPO side and keep only Frigate’s detections. I was like you, I’d heard about it but I’d never taken the time to try Frigate.

[Terdious]

Exactly what I thought ^^ It’s crazy ^^

[Terdious]

For info, updated image, just before your last message. Things should be fixed normally, you can try again, I also restarted Fable on your last message

Also:
@prohand (and @Will_71 if you want to test on a remote machine or next to it on another image), For info, I just deployed a new image docker pull terdious/gladys:Frigate-test-externe for the external Frigate.

Note, not finished yet, but it works ^^

[Will_71]

@Terdious

At @Will_71 if you want to test on a remote machine or next to another image), For information, I just deployed a new image docker pull terdious/gladys:Frigate-test-externe for the external Frigate.

I need to set up a dedicated machine with some storage. Too bad, I still have a mini PC but without a GPU, with very little RAM and a crappy CPU.

[Terdious]

Oh but exactly, in this case, you should be able to test with a low-end PC / RPI! Nothing will run on it, it just retrieves the MQTT messages.
I’m doing the test myself on a RPI (I think it’s a 4^^) with 8GB of RAM.
This is exactly the interest in addition to Prohand’s request.

[Will_71]

I was talking about installing Frigate (externally) and having storage for the recordings.

[Terdious]

Aaaah yes sorry, that’s right.

Well I think I’m going to go for a HA + Gladys + Frigate setup:
https://amzn.eu/d/02nHoFcU

And move the current one to full dev

[Terdious]

@Will_71

@Terdious

Cabane (C610) : the error Failed setup for format vaapi / h264 profile 77 comes from hardware decoding that was using your NVIDIA card instead of the Intel GPU (bi-GPU bug fixed in the image you installed). After the update, these errors should disappear — if you still see them, send us the logs. And since your C610 is on a solar panel: make sure to activate the « always active / continuous monitoring » mode in the Tapo app, it is designed for cameras powered live.

So the setting is on certain models. I don’t have it.
Here are the logs, the errors concern only this camera now. I’m afraid we won’t be able to get the stream.

Fable’s response:

Good news: the GPU decoding errors have disappeared, the update fixed that part. What remains on the C610 is a camera authentication refusal (401 Unauthorized). Two things to try: 1) in the camera’s card in Gladys, set the « Authentication Variant » to SHA256 then save — some recent Tapo battery firmwares no longer accept the cloud password in plain text; 2) if still 401, recheck the TP-Link cloud account password (the one from the Tapo app), and close the Tapo app during the test (simultaneous stream limit). No problem for the missing « always active » mode: the 401 is an authentication refusal, not a sleep mode. For the C500, let us know how it goes now that it’s in the catalog.

=> The new image is built

[Will_71]

For the C610, I already tried, but without success.

For the C500, it worked without and it works with.

I’m currently installing your latest image: what did you modify?

[Will_71]

Something has changed because in Frigate it is now searching, unlike before where I had an error message

but in the logs, the same errors persist

2026-07-14 14:26:23.463820500  16:26:23.463 WRN [rtsp] error="streams: 401 Unauthorized" stream=cabane
2026-07-14 14:26:23.475466636  [2026-07-14 16:26:23] frigate.video                  ERROR   : cabane: Unable to read frames from ffmpeg process.
2026-07-14 14:26:23.483274406  [2026-07-14 16:26:23] frigate.video                  ERROR   : cabane: Unable to read frames from ffmpeg process.
2026-07-14 14:26:23.489258010  [2026-07-14 16:26:23] frigate.video                  ERROR   : cabane: ffmpeg process is not running. exiting capture thread...
2026-07-14 14:26:31.511008839  [2026-07-14 16:26:31] watchdog.cabane                ERROR   : Ffmpeg process crashed unexpectedly for cabane.
2026-07-14 14:26:31.512087672  [2026-07-14 16:26:31] watchdog.cabane                ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2026-07-14 14:26:31.512526498  [2026-07-14 16:26:31] ffmpeg.cabane.detect           ERROR   : [rtsp @ 0x55c08a502440] method DESCRIBE failed: 404 Not Found
2026-07-14 14:26:31.513245505  [2026-07-14 16:26:31] ffmpeg.cabane.detect           ERROR   : [in#0 @ 0x55c08a502100] Error opening input: Server returned 404 Not Found
2026-07-14 14:26:31.514667154  [2026-07-14 16:26:31] ffmpeg.cabane.detect           ERROR   : Error opening input file rtsp://127.0.0.1:8554/cabane.
2026-07-14 14:26:31.515663069  [2026-07-14 16:26:31] ffmpeg.cabane.detect           ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 14:26:31.516321781  [2026-07-14 16:26:31] watchdog.cabane                INFO    : Restarting ffmpeg...

[Terdious]

Sorry for the back and forth!! And a big thank you for your tests.

Can you do a docker exec gladys-frigate curl -s http://127.0.0.1:1984/api/streams | python3 -m json.tool The cabane section will precisely tell what the camera is responding (wrong password, handshake failure…).

EDIT: Be careful, there are passwords in the sections!

[Terdious]

@Will_71

Something has changed because in Frigate it’s now searching, unlike before where I had an error message

The « ça cherche » is actually proof that the update fixed the GPU decoding: before, the pipeline crashed immediately (hence the error message); now it starts correctly and waits for images. As your C610 still refuses authentication (the 401 Unauthorized in the logs), no images arrive — hence the infinite wait. So there’s only one problem left: the cloud password for this camera. Send us the result of docker exec gladys-frigate curl -s http://127.0.0.1:1984/api/streams | python3 -m json.tool (section cabane) so we can see exactly what it responds — and tell us if your Tapo account is a Google/Apple account (in this case you need to create a real TP-Link ID password, that’s what the camera expects).

[Will_71]

@Terdious

Sorry for the back and forth!! And a big thank you for your tests.

No problem, I told you I would do tests so it doesn’t bother me at all.

@Terdious

ocker exec gladys-frigate curl -s http://127.0.0.1:1984/api/streams | python3 -m json.tool

"cabane": {
        "producers": [
            {
                "url": "tapo://password_tpcloud@ip_caméra?channel=0&subtype=1"
            }
        ],
        "consumers": null
    },

I replaced my password and the IP!

@Terdious

If your Tapo account is a Google/Apple account (in this case you need to create a real TP-Link ID password, that’s what the camera expects)

It’s a TP-Link account, I never go through Google/Apple

[Terdious]

@Will_71

"cabane": {
        "producers": [
            {
                "url": "tapo://password_tpcloud@ip_caméra?channel=0&subtype=1"
            }
        ],
        "consumers": null
    },

I replaced my password and the IP!

Well… ok… let’s try again ^^ There’s no information^^

So don’t be offended by the first question, Fable wants to check everything ^^ :

1. Are you the owner of the camera in the Tapo app, or is it shared with you? The local stream only accepts the password of the owner account — a guest/shared family account will give exactly this refusal.
2. To see the exact exchange, enable detailed go2rtc logs from the Frigate UI (no terminal needed): open the Frigate interface → configuration editor (pencil icon) → add under the existing go2rtc: section:

go2rtc:
  log:
    level: debug

→ save/restart, then check the Frigate logs: the tapo lines will tell if it’s a password refusal or a protocol issue (C610 firmware too recent for the go2rtc of Frigate 0.17.2 — in this case we’ll report it upstream and note it in the catalog).

[ProtZ]

Hello,

Great feature idea, I’ll keep a close eye on it.
I already have a separate broker and a Frigate instance with 6 cameras, I’ll be waiting impatiently for the non-Docker version.

[Terdious]

Hi @ProtZ,

Do you mean external? If so, I already have a test image if you want to test

@Terdious

Also:
@prohand (and @Will_71 if you want to test on a remote machine or next to it on another image), For info, I just deployed a new image docker pull terdious/gladys:Frigate-test-externe for the external Frigate.

It will be updated in about 5 minutes available ^^

[Terdious]

It’s starting to become quite nice ^^ (Sorry for showing off in public ^^

If only the desktop view could be wider 5 columns would be perfect!!

[GBoulvin]

Hi! I just ran a test from the image and I have a crazy bug… When I click on the service configuration page, without having added a camera (Edit: even after), on enable I get this in the logs 2026-07-14T22:08:48+0200 <info> setEnabled.js:12 (FrigateManager.setEnabled) Frigate: setting integration enabled = true 2026-07-14T22:08:48+0200 <info> system.isDocker.js:13 (System.isDocker) System.isDocker: This system is running inside Docker. 2026-07-14T22:08:48+0200 <info> detectHardware.js:78 (FrigateManager.detectHardware) Frigate: no compatible render node found, video decoding on CPU 2026-07-14T22:08:48+0200 <info> allocatePorts.js:33 (FrigateManager.allocatePorts) Frigate: allocated port 1885 for MQTT broker 2026-07-14T22:08:48+0200 <info> allocatePorts.js:33 (FrigateManager.allocatePorts) Frigate: allocated port 8971 for Frigate UI 2026-07-14T22:08:48+0200 <info> allocatePorts.js:33 (FrigateManager.allocatePorts) Frigate: allocated port 5000 for Frigate API 2026-07-14T22:08:48+0200 <info> allocatePorts.js:33 (FrigateManager.allocatePorts) Frigate: allocated port 8554 for Frigate RTSP restream 2026-07-14T22:08:48+0200 <info> checkForContainerUpdates.js:14 (FrigateManager.checkForContainerUpdates) Checking for current installed versions and required updates... 2026-07-14T22:08:48+0200 <info> checkForContainerUpdates.js:18 (FrigateManager.checkForContainerUpdates) Frigate MQTT container: update #1 of the container required... 2026-07-14T22:08:48+0200 <info> checkForContainerUpdates.js:32 (FrigateManager.checkForContainerUpdates) Frigate MQTT container: update #1 of the container done 2026-07-14T22:08:48+0200 <info> checkForContainerUpdates.js:37 (FrigateManager.checkForContainerUpdates) Frigate container: update #1 of the container required... pi@gladys:~$ And… The Gladys container self-deletes! Nothing left, Nada! I tried three (four) times thinking I made a mistake… The folder containing the DB is also emptied. I’m on a Beelink S13 with 16GB RAM The command used is: sudo docker run -d --log-driver json-file --log-opt max-size=10m --cgroupns=host --restart=unless-stopped --privileged --network=host --name gladys-frigate -e NODE_ENV=production -e SERVER_PORT=8089 -e TZ=Europe/Paris -e SQLITE_FILE_PATH=/var/lib/gladysassistant-frigate/gladys-production.db -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/gladysassistant-frigate:/var/lib/gladysassistant -v /dev:/dev -v /run/udev:/run/udev:ro terdious/gladys:Frigate-test

[mutmut]

I dug out an old Myfox HD camera from a box and was able to access the RTSP streams (with a bit of tinkering and help from Claude).
I’m currently testing it.

For the first installation of Frigate, I waited, waited, waited without seeing anything except Activating containers and this for almost 5 minutes in my case.
Couldn’t we have a bit more information: Activating machin container Activating bidule container Starting configuration, etc. It helps to keep you waiting.
Besides, not knowing if it was working or not, I had a view of the containers in Portainer so I could see things progressing.

A silly question but is it better to have several MQTT servers?
Doesn’t it take too many resources?

By the way, I think the first one (linked to Gladys) should be called gladys-mqtt.

Will iGPUs be usable?
I have an i7-6700T with an Intel HD Graphics 530, and my configuration is in LXC on Proxmox.

After adding a camera, you have to restart Frigate via the button, it’s very quick to remove but when I check on the Frigate interface, you can see it working for several seconds.
Is it possible to have a message saying that it is restarting and another one saying that Frigate has restarted successfully?I have a weird thing in the frigate logs because no stream received:

2026-07-14 21:42:43.421036237  [2026-07-14 23:42:43] watchdog.myfox                 ERROR   : Ffmpeg process crashed unexpectedly for myfox.
2026-07-14 21:42:43.421510877  [2026-07-14 23:42:43] watchdog.myfox                 ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2026-07-14 21:42:43.421817862  [2026-07-14 23:42:43] ffmpeg.myfox.detect            ERROR   : [rtsp @ 0x5df3e9281080] method DESCRIBE failed: 404 Not Found
2026-07-14 21:42:43.422323531  [2026-07-14 23:42:43] ffmpeg.myfox.detect            ERROR   : [in#0 @ 0x5df3e9280d80] Error opening input: Server returned 404 Not Found
2026-07-14 21:42:43.423726003  [2026-07-14 23:42:43] ffmpeg.myfox.detect            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox_sub.
2026-07-14 21:42:43.423730236  [2026-07-14 23:42:43] ffmpeg.myfox.detect            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:42:43.424062999  [2026-07-14 23:42:43] watchdog.myfox                 INFO    : Restarting ffmpeg...
2026-07-14 21:42:43.427597903  [2026-07-14 23:42:43] ffmpeg.myfox.record            ERROR   : [rtsp @ 0x587306110180] method DESCRIBE failed: 404 Not Found
2026-07-14 21:42:43.429486004  [2026-07-14 23:42:43] ffmpeg.myfox.record            ERROR   : [in#0 @ 0x58730610fe80] Error opening input: Server returned 404 Not Found
2026-07-14 21:42:43.429805258  [2026-07-14 23:42:43] ffmpeg.myfox.record            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox.
2026-07-14 21:42:43.430051951  [2026-07-14 23:42:43] ffmpeg.myfox.record            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:42:43.430383271  [2026-07-14 23:42:43] watchdog.myfox                 INFO    : Terminating the existing ffmpeg process...
2026-07-14 21:42:43.430691065  [2026-07-14 23:42:43] watchdog.myfox                 INFO    : Waiting for ffmpeg to exit gracefully...
2026-07-14 21:42:43.430965571  [2026-07-14 23:42:43] watchdog.myfox                 INFO    : FFmpeg has exited
2026-07-14 21:42:43.437221377  [2026-07-14 23:42:43] frigate.video                  ERROR   : myfox: Unable to read frames from ffmpeg process.
2026-07-14 21:42:43.437797003  [2026-07-14 23:42:43] frigate.video                  ERROR   : myfox: ffmpeg process is not running. exiting capture thread...
2026-07-14 21:42:53.431715655  [2026-07-14 23:42:53] watchdog.myfox                 ERROR   : Ffmpeg process crashed unexpectedly for myfox.
2026-07-14 21:42:53.432368812  [2026-07-14 23:42:53] watchdog.myfox                 ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2026-07-14 21:42:53.432704330  [2026-07-14 23:42:53] ffmpeg.myfox.detect            ERROR   : [rtsp @ 0x564cdad4d080] method DESCRIBE failed: 404 Not Found
2026-07-14 21:42:53.433077687  [2026-07-14 23:42:53] ffmpeg.myfox.detect            ERROR   : [in#0 @ 0x564cdad4cd80] Error opening input: Server returned 404 Not Found
2026-07-14 21:42:53.433374886  [2026-07-14 23:42:53] ffmpeg.myfox.detect            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox_sub.
2026-07-14 21:42:53.433696196  [2026-07-14 23:42:53] ffmpeg.myfox.detect            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:42:53.434000833  [2026-07-14 23:42:53] watchdog.myfox                 INFO    : Restarting ffmpeg...
2026-07-14 21:42:53.439373784  [2026-07-14 23:42:53] ffmpeg.myfox.record            ERROR   : [rtsp @ 0x583f9a60e180] method DESCRIBE failed: 404 Not Found
2026-07-14 21:42:53.440255376  [2026-07-14 23:42:53] ffmpeg.myfox.record            ERROR   : [in#0 @ 0x583f9a60de80] Error opening input: Server returned 404 Not Found
2026-07-14 21:42:53.440965331  [2026-07-14 23:42:53] ffmpeg.myfox.record            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox.
2026-07-14 21:42:53.441911306  [2026-07-14 23:42:53] ffmpeg.myfox.record            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:42:53.442440790  [2026-07-14 23:42:53] watchdog.myfox                 INFO    : Terminating the existing ffmpeg process...
2026-07-14 21:42:53.442986980  [2026-07-14 23:42:53] watchdog.myfox                 INFO    : Waiting for ffmpeg to exit gracefully...
2026-07-14 21:42:53.443247330  [2026-07-14 23:42:53] watchdog.myfox                 INFO    : FFmpeg has exited
2026-07-14 21:42:53.445484742  [2026-07-14 23:42:53] frigate.video                  ERROR   : myfox: Unable to read frames from ffmpeg process.
2026-07-14 21:42:53.445978370  [2026-07-14 23:42:53] frigate.video                  ERROR   : myfox: ffmpeg process is not running. exiting capture thread...
2026-07-14 21:43:03.445628473  [2026-07-14 23:43:03] watchdog.myfox                 ERROR   : Ffmpeg process crashed unexpectedly for myfox.
2026-07-14 21:43:03.446132919  [2026-07-14 23:43:03] watchdog.myfox                 ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2026-07-14 21:43:03.447043962  [2026-07-14 23:43:03] ffmpeg.myfox.detect            ERROR   : [rtsp @ 0x5c740b722080] method DESCRIBE failed: 404 Not Found
2026-07-14 21:43:03.447350613  [2026-07-14 23:43:03] ffmpeg.myfox.detect            ERROR   : [in#0 @ 0x5c740b721d80] Error opening input: Server returned 404 Not Found
2026-07-14 21:43:03.447811850  [2026-07-14 23:43:03] ffmpeg.myfox.detect            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox_sub.
2026-07-14 21:43:03.448273042  [2026-07-14 23:43:03] ffmpeg.myfox.detect            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:43:03.448804734  [2026-07-14 23:43:03] watchdog.myfox                 INFO    : Restarting ffmpeg...
2026-07-14 21:43:03.452103766  [2026-07-14 23:43:03] ffmpeg.myfox.record            ERROR   : [rtsp @ 0x5cc2b3bc3180] method DESCRIBE failed: 404 Not Found
2026-07-14 21:43:03.452565866  [2026-07-14 23:43:03] ffmpeg.myfox.record            ERROR   : [in#0 @ 0x5cc2b3bc2e80] Error opening input: Server returned 404 Not Found
2026-07-14 21:43:03.453068291  [2026-07-14 23:43:03] ffmpeg.myfox.record            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox.
2026-07-14 21:43:03.453483860  [2026-07-14 23:43:03] ffmpeg.myfox.record            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:43:03.454207492  [2026-07-14 23:43:03] watchdog.myfox                 INFO    : Terminating the existing ffmpeg process...
2026-07-14 21:43:03.454906745  [2026-07-14 23:43:03] watchdog.myfox                 INFO    : Waiting for ffmpeg to exit gracefully...
2026-07-14 21:43:03.457581480  [2026-07-14 23:43:03] watchdog.myfox                 INFO    : FFmpeg has exited
2026-07-14 21:43:03.461976405  [2026-07-14 23:43:03] frigate.video                  ERROR   : myfox: Unable to read frames from ffmpeg process.
2026-07-14 21:43:03.462400707  [2026-07-14 23:43:03] frigate.video                  ERROR   : myfox: ffmpeg process is not running. exiting capture thread...
2026-07-14 21:43:08.856999847  [2026-07-14 23:43:08] frigate.comms.dispatcher       INFO    : Turning off recordings for myfox
2026-07-14 21:43:10.709484624  [2026-07-14 23:43:10] frigate.comms.dispatcher       INFO    : Turning on recordings for myfox
2026-07-14 21:43:13.459302772  [2026-07-14 23:43:13] watchdog.myfox                 ERROR   : Ffmpeg process crashed unexpectedly for myfox.
2026-07-14 21:43:13.459729793  [2026-07-14 23:43:13] watchdog.myfox                 ERROR   : The following ffmpeg logs include the last 100 lines prior to exit
```.
2026-07-14 21:43:13.460032195  [2026-07-14 23:43:13] ffmpeg.myfox.detect            ERROR   : [rtsp @ 0x5f0f25870080] method DESCRIBE failed: 404 Not Found
2026-07-14 21:43:13.460358529  [2026-07-14 23:43:13] ffmpeg.myfox.detect            ERROR   : [in#0 @ 0x5f0f2586fd80] Error opening input: Server returned 404 Not Found
2026-07-14 21:43:13.460667518  [2026-07-14 23:43:13] ffmpeg.myfox.detect            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox_sub.
2026-07-14 21:43:13.460929915  [2026-07-14 23:43:13] ffmpeg.myfox.detect            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:43:13.461248905  [2026-07-14 23:43:13] watchdog.myfox                 INFO    : Restarting ffmpeg...
2026-07-14 21:43:13.465161434  [2026-07-14 23:43:13] ffmpeg.myfox.record            ERROR   : [rtsp @ 0x578c4485f180] method DESCRIBE failed: 404 Not Found
2026-07-14 21:43:13.465727570  [2026-07-14 23:43:13] ffmpeg.myfox.record            ERROR   : [in#0 @ 0x578c4485ee80] Error opening input: Server returned 404 Not Found
2026-07-14 21:43:13.466149678  [2026-07-14 23:43:13] ffmpeg.myfox.record            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox.
2026-07-14 21:43:13.466728581  [2026-07-14 23:43:13] ffmpeg.myfox.record            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:43:13.467129440  [2026-07-14 23:43:13] watchdog.myfox                 INFO    : Terminating the existing ffmpeg process...
2026-07-14 21:43:13.467700844  [2026-07-14 23:43:13] watchdog.myfox                 INFO    : Waiting for ffmpeg to exit gracefully...
2026-07-14 21:43:13.468594620  [2026-07-14 23:43:13] watchdog.myfox                 INFO    : FFmpeg has exited
2026-07-14 21:43:13.471832732  [2026-07-14 23:43:13] frigate.video                  ERROR   : myfox: Unable to read frames from ffmpeg process.
2026-07-14 21:43:13.472497646  [2026-07-14 23:43:13] frigate.video                  ERROR   : myfox: ffmpeg process is not running. exiting capture thread...
2026-07-14 21:43:20.189883772  [2026-07-14 23:43:20] frigate.api.camera             ERROR   : Failed to fetch streams from go2rtc
2026-07-14 21:43:23.470405289  [2026-07-14 23:43:23] watchdog.myfox                 ERROR   : Ffmpeg process crashed unexpectedly for myfox.
2026-07-14 21:43:23.470737491  [2026-07-14 23:43:23] watchdog.myfox                 ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2026-07-14 21:43:23.471086462  [2026-07-14 23:43:23] ffmpeg.myfox.detect            ERROR   : [rtsp @ 0x5a230f805080] method DESCRIBE failed: 404 Not Found
2026-07-14 21:43:23.471331927  [2026-07-14 23:43:23] ffmpeg.myfox.detect            ERROR   : [in#0 @ 0x5a230f804d80] Error opening input: Server returned 404 Not Found
2026-07-14 21:43:23.471663693  [2026-07-14 23:43:23] ffmpeg.myfox.detect            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox_sub.
2026-07-14 21:43:23.471940651  [2026-07-14 23:43:23] ffmpeg.myfox.detect            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:43:23.472171553  [2026-07-14 23:43:23] watchdog.myfox                 INFO    : Restarting ffmpeg...
2026-07-14 21:43:23.475971145  [2026-07-14 23:43:23] ffmpeg.myfox.record            ERROR   : [rtsp @ 0x5b50c05db180] method DESCRIBE failed: 404 Not Found
2026-07-14 21:43:23.476509999  [2026-07-14 23:43:23] ffmpeg.myfox.record            ERROR   : [in#0 @ 0x5b50c05dae80] Error opening input: Server returned 404 Not Found
2026-07-14 21:43:23.477018122  [2026-07-14 23:43:23] ffmpeg.myfox.record            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox.
2026-07-14 21:43:23.477468843  [2026-07-14 23:43:23] ffmpeg.myfox.record            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:43:23.477875002  [2026-07-14 23:43:23] watchdog.myfox                 INFO    : Terminating the existing ffmpeg process...
2026-07-14 21:43:23.478301308  [2026-07-14 23:43:23] watchdog.myfox                 INFO    : Waiting for ffmpeg to exit gracefully...
2026-07-14 21:43:23.478838076  [2026-07-14 23:43:23] watchdog.myfox                 INFO    : FFmpeg has exited
2026-07-14 21:43:23.483380449  [2026-07-14 23:43:23] frigate.video                  ERROR   : myfox: Unable to read frames from ffmpeg process.
2026-07-14 21:43:23.483380449  [LOGGING] Last message repeated 2 times
2026-07-14 21:43:23.484659189  [2026-07-14 23:43:23] frigate.video                  ERROR   : myfox: ffmpeg process is not running. exiting capture thread...
2026-07-14 21:43:33.481020152  [2026-07-14 23:43:33] watchdog.myfox                 ERROR   : Ffmpeg process crashed unexpectedly for myfox.
2026-07-14 21:43:33.481387563  [2026-07-14 23:43:33] watchdog.myfox                 ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2026-07-14 21:43:33.481610589  [2026-07-14 23:43:33] ffmpeg.myfox.detect            ERROR   : [rtsp @ 0x5d205eacf080] method DESCRIBE failed: 404 Not Found
2026-07-14 21:43:33.481878236  [2026-07-14 23:43:33] ffmpeg.myfox.detect            ERROR   : [in#0 @ 0x5d205eaced80] Error opening input: Server returned 404 Not Found
2026-07-14 21:43:33.482090185  [2026-07-14 23:43:33] ffmpeg.myfox.detect            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox_sub.
2026-07-14 21:43:33.482419045  [2026-07-14 23:43:33] ffmpeg.myfox.detect            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:43:33.482702233  [2026-07-14 23:43:33] watchdog.myfox                 INFO    : Restarting ffmpeg...
2026-07-14 21:43:33.486926971  [2026-07-14 23:43:33] ffmpeg.myfox.record            ERROR   : [rtsp @ 0x5f6565b85180] method DESCRIBE failed: 404 Not Found
2026-07-14 21:43:33.487488252  [2026-07-14 23:43:33] ffmpeg.myfox.record            ERROR   : [in#0 @ 0x5f6565b84e80] Error opening input: Server returned 404 Not Found
2026-07-14 21:43:33.487980415  [2026-07-14 23:43:33] ffmpeg.myfox.record            ERROR   : Error opening input file rtsp://127.0.0.1:8554/myfox.
2026-07-14 21:43:33.488438135  [2026-07-14 23:43:33] ffmpeg.myfox.record            ERROR   : Error opening input files: Server returned 404 Not Found
2026-07-14 21:43:33.488859639  [2026-07-14 23:43:33] watchdog.myfox                 INFO    : Terminating the existing ffmpeg process...
2026-07-14 21:43:33.489252009  [2026-07-14 23:43:33] watchdog.myfox                 INFO    : Waiting for ffmpeg to exit gracefully...
2026-07-14 21:43:33.489591472  [2026-07-14 23:43:33] watchdog.myfox                 INFO    : FFmpeg has exited
2026-07-14 21:43:33.494613336  [2026-07-14 23:43:33] frigate.video                  ERROR   : myfox: Unable to read frames from ffmpeg process.
2026-07-14 21:43:33.494891970  [2026-07-14 23:43:33] frigate.video                  ERROR   : myfox: ffmpeg process is not running. exiting capture thread...
It's more explicit with go2rtc:

2026-07-14 21:52:49.478393677 [INFO] Preparing new go2rtc config…
2026-07-14 21:52:49.933774211 [INFO] Starting go2rtc…
2026-07-14 21:52:50.382846133 23:52:50.382 INF go2rtc platform=linux/amd64 revision=df95ce3 version=1.9.10
2026-07-14 21:52:50.382943628 23:52:50.382 INF config path=/config/go2rtc_homekit.yml
2026-07-14 21:52:50.383533609 23:52:50.383 INF [rtsp] listen addr=:8554
2026-07-14 21:52:50.383725377 23:52:50.383 INF [api] listen addr=:1984
2026-07-14 21:52:50.384027776 23:52:50.384 INF [webrtc] listen addr=:8555
2026-07-14 21:52:56.715912143 23:52:56.715 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox_sub
2026-07-14 21:52:56.746682658 23:52:56.746 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox_sub
2026-07-14 21:52:58.246229812 23:52:58.244 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox_sub
2026-07-14 21:52:58.252579037 23:52:58.251 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox
2026-07-14 21:52:58.470033836 [INFO] Starting go2rtc healthcheck service…
2026-07-14 21:53:18.244258503 23:53:18.244 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox_sub
2026-07-14 21:53:18.252711056 23:53:18.252 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox
2026-07-14 21:53:28.257319855 23:53:28.257 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox_sub
2026-07-14 21:53:28.264956895 23:53:28.264 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox
2026-07-14 21:53:38.280052154 23:53:38.279 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox_sub
2026-07-14 21:53:38.294744579 23:53:38.294 WRN [rtsp] error=« streams: dial tcp 192.168.1.63:554: connect: connection refused » stream=myfox

I'm going to fiddle with the camera again because the stream doesn't seem to be accessible.

[Terdious]

Hi @GBoulvin !

No worries, your test ultimately came back « normal », but it did reveal a flaw that we can fix — and that’s exactly what these tests are for, so thank you so much!

The explanation: your test container is called gladys-frigate… which was precisely the name that the integration gave to its Frigate container. On first startup, the update routine looked for « its » container by that name, found yours, and replaced it — hence the self-deletion (your logs stop abruptly right after update #1 of the container required...). This is really related to the test setup: in a normal installation, the Gladys container is called gladys, and no one names a manually installed container « gladys-frigate ». But the flaw was real, and it’s fixed in the updated image:

• the integration containers are now called gladys-frigate-server / gladys-frigate-mqtt;
• the name is verified before use (automatic fallback to a suffixed name if it’s already taken), then remembered;
• and most importantly, an existing container is only « recognized » if its image proves it’s ours.

Your Gladys container will therefore never be looked at again, even if it keeps its current name.

If you could try again with the fresh image (your same docker run command works as is), it should work.

Quick question by the way: what was exactly left in /var/lib/gladysassistant-frigate after the incident? A docker rm normally doesn’t empty a mounted folder, so I want to check if it was a side effect of the restarts or a second issue to investigate.

EDIT: And on the other hand, this would reveal an identical bug for the Zigbee2mqtt, Node-red, and Matterbridge containers according to Claude …