| 22 Nov 2024 |
@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 |
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 |