| 14 Jan 2025 |
 Samsonite | live view works fine, but as soon as i change the frigate card to recordings, i just see this: | 03:48:14 |
| Samsonite | 
Download image.png | 03:48:16 |
| Samsonite | and if i go to media -> frigate -> recordings, i get this | 03:48:44 |
| Samsonite | 
Download image.png | 03:48:46 |
| Samsonite | but within frigate itself i can click on camera history and scroll through a timeline just fine | 03:48:58 |
 @hexa:lossy.network | "see logs for details" | 03:48:59 |
| @hexa:lossy.network | also, are you on nixos-24.11 or unstable? | 03:49:16 |
| Samsonite | 24.11 | 03:49:20 |
| Samsonite | i went to haos -> settings -> system -> log and clicked around but don't see anything relevant in there | 03:49:44 |
| Samsonite | within frigate i'm doing journalctl -u frigate -f and i don't see anything coming up as i click around in homeassistant | 03:50:04 |
| @hexa:lossy.network | no logs, no bueno | 03:51:03 |
| Samsonite | and not sure if this is relevant or not, but within the camera entity in haos, in the configuration pod, everything is unchecked. if i check something, it automatically unchecks itself in a second | 03:52:03 |
| Samsonite | 
Download image.png | 03:52:05 |
| Samsonite | haos is weird, there's no journalctl installed, and nothing really in /var/log either | 03:52:35 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/372427#issuecomment-2588884663 | 03:56:23 |
| @hexa:lossy.network | just backported this | 03:56:27 |
| @hexa:lossy.network | maybe related, i don't know | 03:56:40 |
| Samsonite | didn't fix it :/ | 14:17:35 |
| Samsonite | im noticing some other issues as well now that i'm playing with it more. in the web gui, logs never load. settings -> system logs just spins forever. | 14:21:46 |
| Samsonite | journalctl logs says "no such file or directory: '/dev/shm/logs/frigate/current' | 14:22:08 |
| Samsonite | i'm also not able to save any motion masks or anything, error is read only file system. not sure that can ever be fixed based on how nixos does things? | 14:23:08 |
| @hexa:lossy.network | it cannot | 14:24:23 |
| @hexa:lossy.network | for logs … we could maybe patch it to read logs from the journal | 14:24:39 |
| @hexa:lossy.network | can a service read its own journal? | 14:24:50 |
| @hexa:lossy.network | I'm sure as hell not granting it elevated permissions for that | 14:25:03 |
| Samsonite | would there be any hacky way to allow gui config changes to write a different file somewhere that does have write access that only exists for current session, and if you want it permanent then you can just copy the contents into your configuration.nix | 14:26:22 |
| @hexa:lossy.network | it should give you the bounding box in some format | 14:26:38 |
| @hexa:lossy.network | that you can migrate into your configuration | 14:26:44 |
| Samsonite | ohh i see i can copy coordinates to clipboard | 14:27:53 |
| Samsonite | that's cool | 14:27:54 |
