| 12 Dec 2024 |
 spacekitteh | Plus, it requires Avahi, whereas I have systemd-resolved configured to be my mDNS daemon (which doesn't work properly, it looks like) so I have been testing in a container, which only works with a MACVLAN interface for some reason | 04:39:48 |
| * spacekitteh pulls out her hair | 04:39:56 |
 Skallwar | Hi 👋
I've been running HA from the Nixos module for quite some time now. I wanted to revamp my dashboard with some nice lovelace modules like mushroom. I followed this and came up with this
services.home-assistant = {
enable = true;
customLovelaceModules = with pkgs.home-assistant-custom-lovelace-modules; [
mushroom
];
config = {
# Includes dependencies for a basic setup
# https://www.home-assistant.io/integrations/default_config/
default_config = {};
};
};
Inside the HA ui I try to use custom:mushroom-entity-card but then I get this error Custom element doesn't exist: mushroom-entity-card.
Any idea?
| 09:25:49 |
 CRTified | In reply to @skallwar:matrix.org
Hi 👋
I've been running HA from the Nixos module for quite some time now. I wanted to revamp my dashboard with some nice lovelace modules like mushroom. I followed this and came up with this
services.home-assistant = {
enable = true;
customLovelaceModules = with pkgs.home-assistant-custom-lovelace-modules; [
mushroom
];
config = {
# Includes dependencies for a basic setup
# https://www.home-assistant.io/integrations/default_config/
default_config = {};
};
};
Inside the HA ui I try to use custom:mushroom-entity-card but then I get this error Custom element doesn't exist: mushroom-entity-card.
Any idea?
You probably need to set the Lovelace mode to yaml | 11:01:12 |
| CRTified | I think it was storage-mode? | 11:01:32 |
| CRTified | Still need time to do that step :D | 11:01:46 |
| Skallwar | Interesting. I will have a look at the module source | 13:42:48 |
| Skallwar | I was kind of giving up on yaml config in nixos since everytime I have an HA update I get warnings about stuff not supported anymore in Yaml that need to be done in the UI now | 13:44:01 |
 @qbit:tapenet.org | it seems esphome pukes if you have a wireguard interface:
Dec 12 07:42:40 box esphome[277422]: 2024-12-12 07:42:40,130 INFO Starting dashboard web server on http://0.0.0.0:6053 and configuration dir /var/lib/esphome...
Dec 12 07:42:40 box esphome[277422]: 2024-12-12 07:42:40,195 WARNING Error with socket 11 (('192.168.112.4', 5353))): [Errno 126] Required key not available
Dec 12 07:42:40 box esphome[277422]: Traceback (most recent call last):
Dec 12 07:42:40 box esphome[277422]: File "/nix/store/zv1kaq7f1q20x62kbjv6pfjygw5jmwl6-python3-3.12.7/lib/python3.12/asyncio/selector_events.py", line 1275, in sendto
Dec 12 07:42:40 box esphome[277422]: self._sock.sendto(data, addr)
Dec 12 07:42:40 box esphome[277422]: OSError: [Errno 126] Required key not available
| 14:40:40 |
| @qbit:tapenet.org | anyone see anything similar? | 14:40:46 |
| @qbit:tapenet.org | changing the address to 127.0.0.1 doesn't resolve it | 14:41:04 |
| @qbit:tapenet.org | on unstable | 14:44:01 |
 @hexa:lossy.network | Skallwar: the simple truth is that we can only autoload custom lovelace modules when lovelace is in yaml mode, but even when it is not we still install the modules, but you need to load them manually | 14:52:11 |
| @hexa:lossy.network | 
Download image.png | 14:52:34 |
| @hexa:lossy.network | click the pen top right, from the burger menu choose manage resources | 14:53:12 |
| Skallwar | I borked my ssh connection to my home lab... I will look at that later. Thanks for your input ! | 15:15:07 |
 dotlambda | What do we do about https://github.com/NixOS/nixpkgs/pull/364068 ? | 15:16:52 |
| @hexa:lossy.network | I agree that it is a hack | 15:17:36 |
| @hexa:lossy.network | substract 899 from your rebuild count and you're golden | 15:17:43 |
| @hexa:lossy.network | that'll throw us back years in terms of maintainability | 15:18:04 |
| @hexa:lossy.network | rebuild count and nixpkgs-review look at the same list | 15:18:36 |
| @hexa:lossy.network | so we can't have one without the other | 15:18:40 |
| @hexa:lossy.network | and folding all tests back in will make the core package much more annoying again | 15:19:23 |
| @hexa:lossy.network | not recursing into the attrset also means we don't get hydra results anymore | 15:19:46 |
| dotlambda | We could add a top-level attr tests that is recursed into but subtracted from the rebuild count | 15:20:16 |
| @hexa:lossy.network | to be fair, they are rebuilds, and unpacking the home-assistant source 900 times has a certain cost to it | 15:20:56 |
| @hexa:lossy.network | and creating a precedent for top-level attributes that are free is probably not smart | 15:21:39 |
| dotlambda | In reply to @hexa:lossy.network
to be fair, they are rebuilds, and unpacking the home-assistant source 900 times has a certain cost to it I don't think many people mind the cost the builds incur on Hydra. | 15:22:26 |
| dotlambda | In reply to @hexa:lossy.network
and creating a precedent for top-level attributes that are free is probably not smart Wdym? | 15:22:34 |
| @hexa:lossy.network | emacs people are also saying their package set rebuilds are essentially free 😄 | 15:24:48 |
