!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

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

Load older messages


SenderMessageTime
22 Nov 2024
@netpleb:matrix.orgnetpleb
In reply to @hexa:lossy.network
ffmpeg.hwaccel_args
right, so I tried adding cameras.cam1.ffmpeg.imputs.hwaccel_args = ["preset-vaapi"]; (it's an AMD gpu I think, but it's just a gmktec minipc)
21:31:59
@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
@hexa:lossy.network@hexa:lossy.networkhi23:19:15
@hexa:lossy.network@hexa:lossy.networkI'm Martin Weinelt23:19:19
@hexa:lossy.network@hexa:lossy.networkI maintain home-assistant and frigate among other things 🤪23:19:44
23 Nov 2024
@netpleb:matrix.orgnetpleb
In reply to @hexa:lossy.network
I maintain home-assistant and frigate among other things 🤪

I have a zooz S2 Z-wave pluss (ZST10) 908.42 MHz usb stick that I'd like to get working with my nixos home-assistant. If you have any hints, that would be greatly appreciated. So far setting up services.zwave.js = { enable = true; ... } has not seemed to get it working:

Nov 22 16:56:13 aleph0 zwave-server[49798]: Unable to start driver ZWaveError: Failed to open the serial port: Error: No such file or directory, cannot open /dev/ttyACM1 (ZW0100)
Nov 22 16:56:13 aleph0 zwave-server[49798]:     at Driver.openSerialport (/nix/store/bmi1js89yimai7bvqp2dnnmahixb1943-zwave-js-server-1.38.0/lib/node_modules/@zwave-js/server/node_modules/zwave-js/src/lib/driver/Driver.ts:1331:9)

For the serial port, I have services.zwave-js.serialPort = "/dev/ttyACM1"; which is what the output of dmesg | grep tty showed.

01:04:31
@netpleb:matrix.orgnetpleb
In reply to @hexa:lossy.network
I maintain home-assistant and frigate among other things 🤪
*

I have a zooz S2 Z-wave pluss (ZST10) 908.42 MHz usb stick that I'd like to get working with my nixos home-assistant. If you have any hints, that would be greatly appreciated. So far setting up services.zwave.js = { enable = true; ... } has not seemed to get it working:

Nov 22 16:56:13 aleph0 zwave-server[49798]: Unable to start driver ZWaveError: Failed to open the serial port: Error: No such file or directory, cannot open /dev/ttyACM1 (ZW0100)
Nov 22 16:56:13 aleph0 zwave-server[49798]:     at Driver.openSerialport (/nix/store/bmi1js89yimai7bvqp2dnnmahixb1943-zwave-js-server-1.38.0/lib/node_modules/@zwave-js/server/node_modules/zwave-js/src/lib/driver/Driver.ts:1331:9)

For the serial port, I have services.zwave-js.serialPort = "/dev/ttyACM1"; which is what the output of dmesg | grep tty showed. When switching to /dev/ttyACM0 I got a little further, but it kept causing the zwave-js service to restart, claiming:

Nov 22 16:54:37 aleph0 zwave-server[47388]: Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: The Serial API did not respond after soft-reset (ZW0100)

and then I gave up (for now).

01:06:08
@netpleb:matrix.orgnetpleb *

I have a zooz S2 Z-wave pluss (ZST10) 908.42 MHz usb stick that I'd like to get working with my nixos home-assistant. If you have any hints, that would be greatly appreciated. So far setting up services.zwave.js = { enable = true; ... } has not seemed to get it working.

For the serial port, I have services.zwave-js.serialPort = "/dev/ttyACM0"; which is what the output of dmesg | grep tty showed when I plugged the stick in, but got:

Nov 22 16:54:37 aleph0 zwave-server[47388]: Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: The Serial API did not respond after soft-reset (ZW0100)

and then I gave up (for now).

01:30:20
@ftchrist:matrix.orgFrédéric Christ joined the room.05:34:01
@ftchrist:matrix.orgFrédéric Christ
In reply to @hexa:lossy.network
I'm Martin Weinelt
Ah that Martin Weinelt. Hi, I followed your invitation in this frigate PR ;D
05:39:53
@ftchrist:matrix.orgFrédéric ChristAre other OpenHAB users here or is this Home-Assistant only?05:40:49
@ftchrist:matrix.orgFrédéric Christ * Are other openHAB users here or is this Home-Assistant only?05:40:58
@ftchrist:matrix.orgFrédéric Christ * Are other openHAB users here or is this Home Assistant only?05:41:08
@cicucci:matrix.orgcicucci joined the room.06:27:46
@hexa:lossy.network@hexa:lossy.networkPlans were made at Nix-Con 2023 to package it up, not sure what happened since12:55:36

Show newer messages


Back to Room ListRoom Version: 6