| 12 Oct 2024 |
 johnhamelink | Ahh, right. And to get the card to show up, did you do anything other than add to customLovelaceModules? | 20:55:45 |
 K900 | No | 20:56:41 |
| johnhamelink | Damn, I wonder where I've gone wrong then :/ | 20:56:58 |
| johnhamelink | Will try manually restarting and see if I can see anything in the logs that might stop it becoming enabled... | 20:57:36 |
| johnhamelink | Ah, so there is a "ModuleNotFoundError: No module named 'xiaomi_gateway'" - I will try and get rid of that now | 20:59:10 |
 @hexa:lossy.network | In reply to @johnhamelink:matrix.org
Damn, I wonder where I've gone wrong then :/ automatic resource configuration only works with declarative lovelace configuration | 21:08:56 |
| @hexa:lossy.network | so my guess is, you use the ui editor in the frontend | 21:09:16 |
| @hexa:lossy.network | and not the yaml-based approach | 21:09:24 |
| @hexa:lossy.network | https://git.sr.ht/~johnhamelink/nix/tree/master/item/os/hosts/sun/services/home-assistant.nix#L69 | 21:10:01 |
| @hexa:lossy.network |
# Automatic loading only works with lovelace in yaml mode.
| 21:10:05 |
| @hexa:lossy.network | and | 21:10:10 |
| @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 | means your lovelace config is in storage mode | 21:10:28 |
| johnhamelink | Yeah, 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 | either way, nixos deploys the lovelace modules and you can reference them | 21:13:32 |
| @hexa:lossy.network | 
Download image.png | 21:13:44 |
| johnhamelink | Thank you both, will get cracking configuring out my config now! | 21:16:25 |
| 13 Oct 2024 |
|  @kidsan:matrix.org left the room. | 18:32:22 |
| 14 Oct 2024 |
 Sandro 🐧 | wow
https://github.com/NixOS/nixpkgs/pull/348149 | 09:40:53 |
 symphorien | oh I had not looked for previous attempts | 09:42:36 |
| symphorien | what is the limit on hydra ? | 09:43:46 |
| Sandro 🐧 | 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 IIRC | 11:46:13 |
| Sandro 🐧 | I think it is just a bit above the ISO size | 11:46:24 |
| Sandro 🐧 | https://github.com/NixOS/infra/blob/01dfaadc10b0a2565c2e8d414f7b059c93e27ce7/build/hydra.nix#L50 | 11:46:42 |
| Sandro 🐧 | 3.2 GB | 11:46:46 |
 mattleon | The 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 MB | 11:49:46 |
| mattleon | https://matrix.to/#/!QhvgabMQzwEQeWehhZ:lossy.network/$BvRVqF1pRD5U6HZEZuMXCLnIK-n3t0zAUCLGH8omI1A?via=matrix.org&via=nixos.dev&via=tchncs.de | 12:01:07 |
| 15 Oct 2024 |
| @hexa:lossy.network | @mattleon:matrix.org are you up for reviewing this?
| 21:04:17 |
| symphorien | I solved the size issue by removing 3 submodules and compressing the result | 21:10:36 |
| symphorien | I 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 sandbox | 21:11:30 |
