| 23 Nov 2024 |
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 |
victorbjelkholm | In reply to @hexa:lossy.network what hardware does it run on? I can dig up some deeper details in a bit if it's useful, it's a N4505 CPU on my NAS where I'm trying to get everything running. My hunch is that tensorflow was compiled with AVX support which the CPU doesn't support, but I was also not defining any detectors so was thinking tensorflow shouldn't even be included in the first place. | 15:46:25 |
@hexa:lossy.network | bingo | 15:46:42 |
@hexa:lossy.network | that sounds exactly like my hunch | 15:46:59 |
@hexa:lossy.network | guess you need to ask in #cuda:nixos.org, but we're a bit understaffed on tensorflow maintenance, so we're consuming the binary wheels iirc | 15:47:30 |
| zuckerberg joined the room. | 17:35:19 |
netpleb | say I add an additional nixpkgs input to my flake input.nixpkgs-custom.url = "github:..."; and then I use it to pin a package way down inside a module, something like:
# inside my zwave.nix module file
{config, lib, pkgs, inputs, ...}: {
services.zwave-js = let
system = "x86_64-linux";
zwave-js-pkg = inputs.nixpkgs-custom.legacyPackages.${system}.zwave-js-server;
in {
enable = true;
package = zwave-js-pkg;
# ...
};
is there a way to access the appropriate value for system without hardcoding it there?
| 20:53:38 |
netpleb | * say I add an additional nixpkgs input to my flake input.nixpkgs-custom.url = "github:..."; (and have specialArgs.inputs = inputs), and then I use it to pin a package inside a module, something like:
# inside my zwave.nix module file
{config, lib, pkgs, inputs, ...}: {
services.zwave-js = let
system = "x86_64-linux";
zwave-js-pkg = inputs.nixpkgs-custom.legacyPackages.${system}.zwave-js-server;
in {
enable = true;
package = zwave-js-pkg;
# ...
};
is there a way to access the appropriate value for system without hardcoding it there?
| 20:55:03 |
K900 | pkgs.system | 20:56:27 |
netpleb | In reply to @k900:0upti.me
pkgs.system ah!!! thank you! I was looking for it in config and could not find it anywhere. | 20:57:09 |
netpleb | In reply to @netpleb:matrix.org
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).
circling back on this for anyone who comes along later. The trick to get this working, at least for my system/device, was to add services.zwave-js.settings.features.softReset = false; | 21:48:59 |
netpleb | In reply to @netpleb:matrix.org
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).
* circling back on this for anyone who comes along later. The trick to get this working, at least for my system/device, was to add services.zwave-js.settings.features.softReset = false; as well as to use services.zwave-js.serialPort = /dev/serial/by-id/usb-... | 21:50:37 |
netpleb | * circling back on this for anyone who comes along later. The trick to get this working, at least for my system/device, was to add services.zwave-js.settings.features.softReset = false; as well as to use services.zwave-js.serialPort = "/dev/serial/by-id/usb-..." | 21:50:52 |
| @nullcube:matrix.org joined the room. | 21:50:59 |
| 24 Nov 2024 |
Frédéric Christ | Is someone using frigate with authentik and would be willing to share his setup?
| 09:23:51 |
K900 | You can probably run it behind oauth2-proxy | 09:24:34 |
K900 | If there's no builtin support | 09:24:46 |
| danjujan joined the room. | 10:33:01 |
@qbit:tapenet.org | _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ???
E pydantic.errors.ConfigError: field "trigger" not yet prepared so type is still a ForwardRef, you might need to call Trigger.update_forward_refs().
pydantic/fields.py:857: ConfigError
=========================== short test summary info ============================
building '/nix/store/raw94y6if2c1fib4lgn08yi97ys0vzh9-crontabs.drv'...
building '/nix/store/9zndksjabfypl9nm3vylrx6s99yx1dsk-unit-dbus.service.drv'...
building '/nix/store/wxv73yh73qcrnrh3fcnrazmwqlhiwmi4-unit-dbus.service.drv'...
FAILED tests/test_scenes.py::test_dict_to_scene - pydantic.errors.ConfigError: field "trigger" not yet prepared so type is st...
========================= 1 failed, 38 passed in 2.36s =========================
error: builder for '/nix/store/hly2k14g727k887miq0xlwz1n40pwzxc-python3.12-dirigera-1.2.1.drv' failed with exit code 1
| 22:23:58 |
@qbit:tapenet.org | sethe dirigera stuff broken for anyone else? | 22:24:19 |
@qbit:tapenet.org | on beta | 22:24:26 |
@hexa:lossy.network | cached on x86_64-linux for me | 22:34:35 |
@hexa:lossy.network | on nixos-24.11-small | 22:34:44 |
@hexa:lossy.network | ok, so you did not give enough context | 22:35:29 |
@hexa:lossy.network | this is about the dirigera in the home-assistant python package set | 22:35:40 |
@hexa:lossy.network | home-assistant-custom-components.dirigera_platform | 22:38:31 |
@hexa:lossy.network | * and in fact about home-assistant-custom-components.dirigera\_platform | 22:38:38 |
@hexa:lossy.network | * and in fact about home-assistant-custom-components.dirigera_platform | 22:38:40 |