!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

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

Load older messages

SenderMessageTime
22 Nov 2024
@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
@victorbjelkholm:matrix.orgvictorbjelkholm joined the room.15:25:27
@victorbjelkholm:matrix.orgvictorbjelkholm 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:matrix.orgvictorbjelkholmI 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 now15:29:05
@hexa:lossy.network@hexa:lossy.networkmeans it wants to execute an unsupported instruction call15:37:03
@hexa:lossy.network@hexa:lossy.networkwhat hardware does it run on?15:37:08
@victorbjelkholm:matrix.orgvictorbjelkholm
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@hexa:lossy.networkbingo15:46:42
@hexa:lossy.network@hexa:lossy.networkthat sounds exactly like my hunch15:46:59
@hexa:lossy.network@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:neet.spacezuckerberg joined the room.17:35:19
@netpleb:matrix.orgnetpleb

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:matrix.orgnetpleb *

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:0upti.meK900 pkgs.system 20:56:27

Show newer messages

Back to Room ListRoom Version: 6