| 13 Feb 2025 |
@hexa:lossy.network | sigh | 20:21:36 |
@hexa:lossy.network | https://github.com/evcc-io/evcc/releases/tag/0.200.0 | 20:21:42 |
@hexa:lossy.network | this release is full of surprises at the 1 minute mark alread | 20:22:12 |
@hexa:lossy.network | * this release is full of surprises at the 1 minute mark already | 20:22:13 |
motiejus | I can't get the detect process to read from go2rtc, always weirdly get the same ffmpeg error Error opening input files: Invalid data found when processing input when the detect role comes not directly from camera, but from go2rtc (record is fine).
I will put this on hold for some time (a few days?). I disabled detect process, will be recording only for now (no cpu use).
| 20:37:02 |
@hexa:lossy.network | ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
ERROR : [AVHWFramesContext @ 0x7fd4c0078880] Failed to sync surface 0x9: 1 (operation failed).
ERROR : [hwdownload @ 0x7fd4cc0025c0] Failed to download frame: -5.
ERROR : [vf#1:0 @ 0x1b6ef480] Error while filtering: Input/output error
ERROR : [vf#1:0 @ 0x1b6ef480] Task finished with error code: -5 (Input/output error)
ERROR : [vf#1:0 @ 0x1b6ef480] Terminating thread with return code -5 (Input/output error)
| 20:37:59 |
@hexa:lossy.network | this is what I'm seeing every few minutes | 20:38:03 |
motiejus | also, I can't understand the relationship of go2rtc config in frigate, and its own. I guess I shouldn't use go2rtc top-level in frigate config, and just use the rtsp endpoints. But then the docs don't help understand this too:
After adding this to the config, restart Frigate and try to watch the live stream for a single camera by clicking on it from the dashboard. It should look much clearer and more fluent than the original jsmpeg stream.
| 20:39:05 |
@hexa:lossy.network | frigate can run its own go2rtc process and configure it | 20:39:46 |
motiejus | if I run ffmpeg command myself, I logs lots of lost packets (the router behind the camera is under stress). I think it makes sense to restart in higher-bandwidth situation | 20:39:53 |
@hexa:lossy.network | in nixos I just configure go2rtc myself | 20:39:54 |
motiejus | ok, so that's what its for. Ditto, I just did it myself. | 20:40:05 |
motiejus | tailscale0:
TX packets:316154987 errors:0 dropped:51176 overruns:0 carrier:0
that's not too bad.
| 20:42:16 |
| 14 Feb 2025 |
| rane [they/them] joined the room. | 11:29:35 |
tcas | Is there a way to set a user in home assistant from NixOS config? I've got home assistant core running on NixOS and don't want to go through the onboarding procedure manually. | 12:14:23 |
| 15 Feb 2025 |
| JManch joined the room. | 01:41:40 |
| sorin joined the room. | 02:34:18 |
| ThatOneLutenist joined the room. | 06:41:05 |
| BenjB83 joined the room. | 10:14:40 |
| BenjB83 changed their display name from Benjamín Buske to BenjB83. | 10:43:08 |
| 16 Feb 2025 |
motiejus | configured go2rtc. What is the resolution you are feeding to the detect stream? | 19:52:43 |
motiejus | * configured go2rtc, same high cpu usage. What is the resolution you are feeding to the detect stream? | 19:53:43 |
@hexa:lossy.network | api:
listen: :1984
ffmpeg:
bin: /nix/store/a4ha6dhk6xlrkpybnh5d8dnqq6c9mlph-ffmpeg-headless-7.1-bin/bin/ffmpeg
rtsp:
listen: :8554
streams:
g3:
- rtsp://192.168.110.231:554/s0
g3-flex:
- rtsp://192.168.110.230:554/s0
webrtc:
listen: :8555
| 20:35:47 |
@hexa:lossy.network | I would think the native resolution? 😄 | 20:35:54 |
@hexa:lossy.network | neither frigate nor go2rtc has any resolution configured | 20:36:14 |
motiejus |  Download image.png | 20:39:07 |
motiejus | no matter what I try :D | 20:39:11 |
motiejus | it's transcoding h.265 -> h.264 (to conserve bandwidth) using 7-8% of core per stream, and "detecting" with a full core + coral. :) | 20:40:08 |
@hexa:lossy.network | pretty sure my cameras are send h.264 | 20:47:20 |
motiejus | yeah, I was testing this with h.264 all the time, just turned on h.265 for unrelated reasons (it's transcoded to h.264 at the front door) | 20:54:23 |