!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

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

Load older messages


SenderMessageTime
26 Dec 2024
@tommy:datenkollektiv.netTommy changed their display name from Tommy to Tommy (3841).16:07:00
@ftchrist:matrix.orgFrédéric Christ changed their display name from Frédéric Christ to Frédéric Christ (DECT 5915).18:28:48
@lorenzleutgeb:matrix.org@lorenzleutgeb:matrix.org changed their display name from Lorenz Leutgeb to Lorenz Leutgeb (📞6343).19:33:46
@lorenzleutgeb:matrix.org@lorenzleutgeb:matrix.org changed their display name from Lorenz Leutgeb (📞6343) to Lorenz Leutgeb 📞6343.19:37:01
@pierre:eng42.devpierre joined the room.19:49:53
27 Dec 2024
@dimitarnestorov:matrix.orgDimitar set a profile picture.11:41:04
@dimitarnestorov:matrix.orgDimitar changed their display name from dimitarnestorov to Dimitar.11:42:05
@nazarewk:matrix.orgkdn changed their display name from nazarewk to kdn.12:37:25
29 Dec 2024
@elikoga:matrix.orgelikoga changed their display name from elikoga (@38c3 📞488{0,1}) to elikoga (@38c3 📞488{0,1,9}).11:03:23
@marlincr:matrix.orgMarlinc joined the room.17:09:05
@hexa:lossy.network@hexa:lossy.network https://github.com/NixOS/nixpkgs/pull/369203 18:18:48
@uep:matrix.orguepsince it's still alive, presumably the c0 stepping21:51:24
@uep:matrix.orguepunlike mine21:51:30
@hexa:lossy.network@hexa:lossy.networkyou mean because of the clock issue?21:51:43
@uep:matrix.orguepwhatever it was that caused them to all die 21:52:11
@hexa:lossy.network@hexa:lossy.networkyeah, the clock in the cpu died21:52:19
@hexa:lossy.network@hexa:lossy.networkbut if the board supplied its own it would continue working21:52:28
@hexa:lossy.network@hexa:lossy.networkthis one is on a supermicro board, so I hope they did a good design 😄 21:52:50
@uep:matrix.orguepi thought it was more than just clock, something about the usb blowing as weel21:52:50
@hexa:lossy.network@hexa:lossy.networkstepping 8 (per lscpu)21:53:00
@uep:matrix.orguepyep, that's c021:53:12
@uep:matrix.orguepi was just looking at this again recently, because someone nearby was selling an old synology with 12 bays and one of those cpus21:53:55
@uep:matrix.orguepunfortunately, full of disks as well they wanted to charge for, so never mind, but would otherwise have been useful to drop my power draw21:54:55
30 Dec 2024
@hexa:lossy.network@hexa:lossy.networkif after upgrading to nixos-24.11 openvino detection cannot find your gpu14:01:50
@hexa:lossy.network@hexa:lossy.network you might need the intel-compute-runtime-legacy1 package instead of intel-compute-runtime 14:02:19
@hexa:lossy.network@hexa:lossy.networkit supports 8th, 9th and 11th gen GPUs14:02:26
@tommy:datenkollektiv.netTommy changed their display name from Tommy (3841) to Tommy.19:26:02
31 Dec 2024
@laurynasp:matrix.orglaurynasp joined the room.13:33:00
@laurynasp:matrix.orglaurynasp

Hi, I have a question about home-assistant's /var/lib/hass/secrets.yaml file.

I would like to generate using modern secret management style. What tools do ppl use for that?
I am leaning towards using sops-nix. In fact, I found example on Mic92/sops-nix README.md

sops.secrets."home-assistant-secrets.yaml" = { owner = "hass"; path = "/var/lib/hass/secrets.yaml"; };

What should the structure of sops' secrets.yaml file ?

I am struggling to figure out how to include home-assistant-secrets.yaml into main sops' secrets.yaml.
I tried using sops-nix PR (github:Mic92/sops-nix?rev=c6233857ac1f096f139ca335c003efbda6087311 ) that allows multiple defoultSopsFiles, but I keep getting error such as below

/nix/store/sxa9p6k23yydwndlipsrpsa1b4vc50q0-sops-install-secrets-0.0.1/bin/sops-install-secrets: Manifest is not valid: Failed to find valid secret hass-secrets.yaml in [/nix/store/wwl8rw4csyq35886i7l9blaghylg11l0-source/secrets.yaml /nix/store/wwl8rw4csyq35886i7l9blaghylg11l0-source/hass-secrets.yaml]

P.s. This is perhaps more of the sops-nix questions, but I couldn't find a room for it

13:47:03
@laurynasp:matrix.orglaurynasp *

Hi, I have a question about home-assistant's /var/lib/hass/secrets.yaml file.

I would like to generate using modern secret management style. What tools do ppl use for that?
I am leaning towards using sops-nix. In fact, I found example on Mic92/sops-nix README.md

sops.secrets."home-assistant-secrets.yaml" = { owner = "hass"; path = "/var/lib/hass/secrets.yaml"; };

What should the structure of sops' secrets.yaml file ?

I am struggling to figure out how to include home-assistant-secrets.yaml into main sops' secrets.yaml.
I tried using sops-nix PR (github:Mic92/sops-nix?rev=c6233857ac1f096f139ca335c003efbda6087311 ) that allows multiple defoultSopsFiles, but I keep getting error such as below

/nix/store/sxa9p6k23yydwndlipsrpsa1b4vc50q0-sops-install-secrets-0.0.1/bin/sops-install-secrets: Manifest is not valid: Failed to find valid secret hass-secrets.yaml in [/nix/store/wwl8rw4csyq35886i7l9blaghylg11l0-source/secrets.yaml /nix/store/wwl8rw4csyq35886i7l9blaghylg11l0-source/hass-secrets.yaml]

P.s. This is perhaps more of the sops-nix questions, but I couldn't find a room for it

13:47:56

Show newer messages


Back to Room ListRoom Version: 6