| 22 Nov 2024 |
 @hexa:lossy.network | that is backwards | 21:39:32 |
| @hexa:lossy.network | the intel-media-driver is for intel gpus | 21:39:42 |
| @hexa:lossy.network | and environment.sessionVariables overwrites discovery mechanisms systeem-wide | 21:40:22 |
| @hexa:lossy.network | hardware.graphics.enable = true;
services.frigate.vaapiDriver = "radeonsi";
| 21:40:50 |
 netpleb | 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 | that's all you need | 21:40:54 |
| @hexa:lossy.network | gpus are highly proprietary | 21:41:09 |
| @hexa:lossy.network | they don't tend to share anything | 21:41:15 |
| netpleb | 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 | n oidea | 22:28:05 |
| @hexa:lossy.network | * no idea | 22:28:08 |
| netpleb | 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 | hi | 23:19:15 |
| @hexa:lossy.network | I'm Martin Weinelt | 23:19:19 |
| @hexa:lossy.network | I maintain home-assistant and frigate among other things 🤪 | 23:19:44 |
| 23 Nov 2024 |
| netpleb | 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 | 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 | * 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 |
|  Frédéric Christ joined the room. | 05:34:01 |
| Fré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 |
| Frédéric Christ | Are other OpenHAB users here or is this Home-Assistant only? | 05:40:49 |
| Frédéric Christ | * Are other openHAB users here or is this Home-Assistant only? | 05:40:58 |
| Frédéric Christ | * Are other openHAB users here or is this Home Assistant only? | 05:41:08 |
|  cicucci joined the room. | 06:27:46 |
| @hexa:lossy.network | Plans were made at Nix-Con 2023 to package it up, not sure what happened since | 12:55:36 |
|  victorbjelkholm joined the room. | 15:25:27 |
| victorbjelkholm | thanks a bunch for the newly added coral stuff hexa ! Just started setting up my home automation stuff yesterday, hit some snags and came across your PR :) | 15:26:56 |
| victorbjelkholm | I did come across one weird issue with frigate though, trying to run it as a service. On nixpkgs 24.05 (0.13.x of Frigate I think), everything worked fine but I'm getting "Illegal Instruction" on 24.11 (from the tensorflow python library) where it's using Frigate 0.14.1. I ended up running Frigate in a podman container instead for now | 15:29:05 |
| @hexa:lossy.network | means it wants to execute an unsupported instruction call | 15:37:03 |
| @hexa:lossy.network | what hardware does it run on? | 15:37:08 |
