!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

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

Load older messages


SenderMessageTime
12 Oct 2024
@hexa:lossy.network@hexa:lossy.networkand not the yaml-based approach21:09:24
@hexa:lossy.network@hexa:lossy.networkhttps://git.sr.ht/~johnhamelink/nix/tree/master/item/os/hosts/sun/services/home-assistant.nix#L6921:10:01
@hexa:lossy.network@hexa:lossy.network
# Automatic loading only works with lovelace in yaml mode.
21:10:05
@hexa:lossy.network@hexa:lossy.networkand21:10:10
@hexa:lossy.network@hexa:lossy.network
    # lovelaceConfig = {
    #   title = "My Awesome Home";
    #   views = [ {
    #     title = "Example";
    #     cards = [ {
    #       type = "markdown";
    #       title = "Lovelace";
    #       content = "Welcome to your **Lovelace UI**.";
    #     } ];
    #   } ];
    # };
21:10:15
@hexa:lossy.network@hexa:lossy.networkmeans your lovelace config is in storage mode21:10:28
@johnhamelink:matrix.orgjohnhamelinkYeah, I just disabled that and hardcoded and waddya know, it shows up now :) I was trying to rapidly design the lovelace config so I could then hardcode it into my repo without having to rebuild with each change. Now I have something to bisect at least :) Thank you!21:12:30
@hexa:lossy.network@hexa:lossy.networkeither way, nixos deploys the lovelace modules and you can reference them21:13:32
@hexa:lossy.network@hexa:lossy.networkimage.png
Download image.png
21:13:44
@johnhamelink:matrix.orgjohnhamelinkThank you both, will get cracking configuring out my config now!21:16:25
13 Oct 2024
@kidsan:matrix.org@kidsan:matrix.org left the room.18:32:22
14 Oct 2024
@sandro:supersandro.deSandro 🐧wow https://github.com/NixOS/nixpkgs/pull/34814909:40:53
@symphorien:xlumurb.eusymphorienoh I had not looked for previous attempts09:42:36
@symphorien:xlumurb.eusymphorienwhat is the limit on hydra ?09:43:46
@sandro:supersandro.deSandro 🐧I don't think they ever made it into any PR because alone fetching the source was to big and after looking at their CI it was kinda given up upon IIRC11:46:13
@sandro:supersandro.deSandro 🐧I think it is just a bit above the ISO size11:46:24
@sandro:supersandro.deSandro 🐧https://github.com/NixOS/infra/blob/01dfaadc10b0a2565c2e8d414f7b059c93e27ce7/build/hydra.nix#L5011:46:42
@sandro:supersandro.deSandro 🐧3.2 GB11:46:46
@mattleon:matrix.orgmattleonThe chip repo doesn't require a full recursive submodule init - if you use the checkout script in the chip repo, it only downloads the required repos and is only a few hundred MB11:49:46
@mattleon:matrix.orgmattleonhttps://matrix.to/#/!QhvgabMQzwEQeWehhZ:lossy.network/$BvRVqF1pRD5U6HZEZuMXCLnIK-n3t0zAUCLGH8omI1A?via=matrix.org&via=nixos.dev&via=tchncs.de12:01:07
15 Oct 2024
@hexa:lossy.network@hexa:lossy.network

@mattleon:matrix.org are you up for reviewing this?

21:04:17
@symphorien:xlumurb.eusymphorienI solved the size issue by removing 3 submodules and compressing the result21:10:36
@symphorien:xlumurb.eusymphorienI really don't want to run the "user friendly" shell scripts, they access the internet as much as they can, and have all sorts of assumptions about the system that break in the sandbox21:11:30
@hexa:lossy.network@hexa:lossy.networkthank you very much for digging so deep into this21:16:37
@hexa:lossy.network@hexa:lossy.networkit it unfortunately one of the most involved builds I've seen in nixpkgs thus far21:16:49
@hexa:lossy.network@hexa:lossy.networksuch a big vendor consortium mess ::/21:16:56
@hexa:lossy.network@hexa:lossy.network * such a big vendor consortium mess 😕21:16:57
@hexa:lossy.network@hexa:lossy.networkI'm slightly afraid of updatinng it21:17:08
@hexa:lossy.network@hexa:lossy.network * I'm slightly afraid of updating it going forward21:17:14
@hexa:lossy.network@hexa:lossy.networkalready moving the src tarball around takes a lot of time21:17:38

Show newer messages


Back to Room ListRoom Version: 6