| 23 Nov 2024 |
 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 |
| @qbit:tapenet.org | yep | 22:30:53 |
| @hexa:lossy.network | imo this is a pydantic version mismatch | 22:41:34 |
| @hexa:lossy.network | except upstream doesn't pin to a version <2 while home-assistant does | 22:42:01 |
| @hexa:lossy.network | https://github.com/Leggin/dirigera/blob/main/pyproject.toml#L25 | 22:42:01 |
| @qbit:tapenet.org | dang | 22:35:10 |
| @hexa:lossy.network | qbit: https://github.com/NixOS/nixpkgs/pull/350542 | 23:30:48 |
| @hexa:lossy.network | the author claimed it built on x86_64-linux 🙂 | 23:32:15 |
| 25 Nov 2024 |
| @hexa:lossy.network | lol, my home-assistant behaved oddly, so I checked the journal and surely | 01:09:56 |
| @hexa:lossy.network | Nov 25 01:09:29 meduna hass[312719]: Traceback (most recent call last):
Nov 25 01:09:29 meduna hass[312719]: File "/nix/store/901c80rlps5q05bnjk1sj4zaz5k736nc-python3-3.12.7/lib/python3.12/asyncio/selector_events.py", line 178, in _accept_connection
Nov 25 01:09:29 meduna hass[312719]: File "/nix/store/901c80rlps5q05bnjk1sj4zaz5k736nc-python3-3.12.7/lib/python3.12/socket.py", line 295, in accept
Nov 25 01:09:29 meduna hass[312719]: OSError: [Errno 24] Too many open files
Nov 25 01:09:29 meduna hass[312719]: 2024-11-25 01:09:29.847 ERROR (MainThread) [homeassistant] Error doing job: socket.accept() out of system resource (None)
| 01:10:00 |
| @hexa:lossy.network | I ran out of file descriptsors | 01:10:07 |
| @hexa:lossy.network | * I ran out of file descript0ors | 01:10:09 |
