| 10 Dec 2024 |
 hexa | * their 3.12 support will run out in 2025.2 | 17:46:30 |
 dotlambda | In reply to @hexa:lossy.network
this will make the 3.13 migration much easier Do you have a list of HA dependencies that currently don't build on 3.13? | 22:21:37 |
| hexa | sorry, I don't remember | 22:46:18 |
| 11 Dec 2024 |
| hexa | https://github.com/NixOS/nixpkgs/pull/364068 😢 | 00:49:34 |
| hexa | this will be a big loss to home-assistant maintenance, since people will keep bumping dependencies and nixpkgs-review will not run the related home-assistant test, thereby quietly breaking component support | 00:50:16 |
| hexa | * this will be a big loss to home-assistant maintenance, since people will keep bumping dependencies and nixpkgs-review will not run the related home-assistant tests, thereby quietly breaking component support | 00:50:40 |
 ethan | Am I reading this right that the only thing that would really fix their issue is merging all the ha tests back into one causing all of them to run on small changes? (Essentially reverting #155060) | 04:35:43 |
|  @dminca:matrix.org left the room. | 14:19:05 |
 Sandro 🐧 | move them to passthrough? | 14:55:13 |
| hexa | of each individual dependency? | 15:02:54 |
| hexa | mind you, they are multiple hundreds | 15:03:06 |
| Sandro 🐧 | hmm, moving them to the passthrough of the home-assistant component would not be enough | 15:37:12 |
|  Skallwar joined the room. | 18:42:39 |
|  Aumetra (they/them) joined the room. | 23:14:53 |
| 12 Dec 2024 |
 spacekitteh | Still working on getting the OpenThread Border Router working properly, it's hell because idk when it works because all of my thread devices to test it with are matter devices, and I can't commission them without a working thread BR, and idk if I have `python-matter-server` configured correctly either, plus to commission them into it with HA, you need to use either the full Play Store HA app, or the iOS app, and I don't have the play store version :× | 04:37:06 |
| spacekitteh | My dotfiles repo, it's not fully working yet tho | 04:37:55 |
| spacekitteh | HA *sometimes* picks it up | 04:38:09 |
| 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 | 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 | anyone see anything similar? | 14:40:46 |
| qbit | changing the address to 127.0.0.1 doesn't resolve it | 14:41:04 |
| qbit | on unstable | 14:44:01 |
| hexa | 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 |
