!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

509 Members
Declarative Home Automation and other Sidequests | https://wiki.nixos.org/wiki/Home_Assistant128 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
22 Nov 2024
@hexa:lossy.network@hexa:lossy.networkhuh, not on the cameras21:32:26
@netpleb:matrix.orgnetpleb
In reply to @hexa:lossy.network
huh, not on the cameras
oh...good catch! hopefull that was my problem!
21:32:50
@hexa:lossy.network@hexa:lossy.networkimage.png
Download image.png
21:33:07
@netpleb:matrix.orgnetpleb
In reply to @hexa:lossy.network
sent an image.

awesome! That fixed it. Thanks so much! As I was iterating on this, I ended adding:

  hardware.graphics = {
    enable = true;
    extraPackages = with pkgs; [ intel-media-driver ];
  };
  environment.sessionVariables = {
    LIBVA_DRIVER_NAME="radeonsi";
  };

but I am not sure if either of those are necessary. I will remove them to see, but I am wondering if a reboot is necessary to make sure?

21:39:18
@hexa:lossy.network@hexa:lossy.networkthat is backwards21:39:32
@hexa:lossy.network@hexa:lossy.networkthe intel-media-driver is for intel gpus21:39:42
@hexa:lossy.network@hexa:lossy.network and environment.sessionVariables overwrites discovery mechanisms systeem-wide 21:40:22
@hexa:lossy.network@hexa:lossy.network
hardware.graphics.enable = true;
services.frigate.vaapiDriver = "radeonsi";
21:40:50
@netpleb:matrix.orgnetpleb
In reply to @hexa:lossy.network
the intel-media-driver is for intel gpus
yeah, I was just trying different things while following that PR and know very little about these drivers. Figured maybe there was some sort of shared/common driver in there. I'll remove those items and reboot if necessary.
21:40:50
@hexa:lossy.network@hexa:lossy.networkthat's all you need21:40:54
@hexa:lossy.network@hexa:lossy.networkgpus are highly proprietary21:41:09
@hexa:lossy.network@hexa:lossy.networkthey don't tend to share anything21:41:15
@netpleb:matrix.orgnetpleb ok, so in the frigate web ui now (just cam1 hooked up) I have a status bar of CPU 6%, AMD GPU 1% but then on the far right it says Cam1 has high detect CPU usage (93%). That does not make sense to me, but maybe it is normal? 21:47:36
@hexa:lossy.network@hexa:lossy.networkn oidea22:28:05
@hexa:lossy.network@hexa:lossy.network * no idea22:28:08
@netpleb:matrix.orgnetpleb
In reply to @hexa:lossy.network
no idea
Ok, no worries. It seems to have resolved after I switched the camera url to /cam/realmonitor?channel=1&subtype=1. I do not know enough about this stuff to know why that helped, but it seems to have. Anyway, thanks for your help! Also, I am only now realizing that you are the same person who created that PR!
23:18:37

Show newer messages


Back to Room ListRoom Version: 6