| 20 Dec 2024 |
|  erahhal joined the room. | 04:53:55 |
 spacekitteh | warnings =
let
sub2_4GHzPhy = lib.trivial.mod (lib.fromHex dataset.channelMask) (lib.fromHex "0x0800") != 0;
in
lib.optional sub2_4GHzPhy
"OpenThread Border Router has been configured with a channel mask which includes a sub-2.4GHz IEEE 802.15.4 channel. While there appears to be support for this in OpenThread, it is not in the Thread standard itself, as of Thread 1.4.";
this should probably be a warning, not an assertion, right?
| 06:05:24 |
|  🐰 xiaoxiangmoe joined the room. | 13:58:35 |
 @qbit:tapenet.org | i see the customLovelaceModules making it into the configuration.. but I can't see them when adding a card | 21:34:13 |
| @qbit:tapenet.org | anyone experience the same? | 21:34:15 |
 @hexa:lossy.network | I don't understand the problem statement tbh | 21:54:09 |
| @hexa:lossy.network | "when adding a card" means you are configuring the dashboard interactively? | 21:54:35 |
| @hexa:lossy.network | we cannot install external resources in that case | 21:55:23 |
| @hexa:lossy.network | because home-assistant manages that config at /var/lib/hass/.storage/lovelace | 21:55:58 |
| @hexa:lossy.network | 
Download image.png | 21:56:18 |
| @hexa:lossy.network | use manage resources here | 21:56:20 |
| @hexa:lossy.network | 
Download image.png | 21:56:34 |
| @hexa:lossy.network | and reference them manually | 21:56:36 |
| 21 Dec 2024 |
 ibizaman | Thanks for the PR to fix Music Assistant. Works like a charm! | 09:03:30 |
|  Dimitar joined the room. | 19:46:31 |
 mjm | yeah, i was able to remove my own patch :) | 21:01:38 |
|  @sleepymonad:matrix.org joined the room. | 21:15:24 |
| @sleepymonad:matrix.org set a profile picture. | 21:56:38 |
| 22 Dec 2024 |
| @hexa:lossy.network | https://developers.home-assistant.io/blog/2024/12/21/moving-to-pydantic-v2 🥳 | 17:23:21 |
| 23 Dec 2024 |
| @qbit:tapenet.org | ah, thanks. I assumed those were being added by the existence of the customLovelaceModules directive | 15:03:40 |
| @hexa:lossy.network | they are, but only when we control the YAML config | 15:04:35 |
| @hexa:lossy.network | if you opt out of that 🤷 | 15:04:43 |
| @hexa:lossy.network | the lovelace config and the resources are in the same file, so we cannot mix and match | 15:05:03 |
| @qbit:tapenet.org | right, but that isn't obvious unless you are in the code on the regular i'd say | 15:05:41 |
| @hexa:lossy.network | hm ok, then our documentation is probably unclear | 15:07:50 |
| @hexa:lossy.network | * hm ok, then our documentation is probably incomplete | 15:09:06 |
| @qbit:tapenet.org | "Automatic loading only works with lovelace in yaml mode." | 15:08:29 |
| @hexa:lossy.network | hm ok | 15:09:31 |
| @hexa:lossy.network | ::: {.note}
Automatic loading only works with lovelace in `yaml` mode.
:::
| 15:09:44 |
| @hexa:lossy.network | I fault s.n.o not rendering admonitions | 15:10:00 |
