| 5 Oct 2024 |
 CRTified | Is it possible that mode: storage causes them to get ignored? | 20:43:21 |
 @hexa:lossy.network | yep | 23:55:38 |
| @hexa:lossy.network | No support for declarative Lovelace modules in that case | 23:56:03 |
| 6 Oct 2024 |
|  daniel36191 joined the room. | 01:27:02 |
| CRTified | In reply to @hexa:lossy.network
No support for declarative Lovelace modules in that case Do you know what this actually controls? I can only guess that switching to yaml requires re-creating all dashboards, but the documentation is pretty sparse on this | 10:11:39 |
| @hexa:lossy.network | resources need to be defined in the Lovelace.yaml | 10:15:13 |
| @hexa:lossy.network | If that does not exist, then you need to set that up in the dashboard settings in the frontend | 10:15:38 |
| @hexa:lossy.network | And you can export generated dashboards back to yaml | 10:16:10 |
| CRTified | Ah, I asked imprecisely. Do you know what switching mode: storage to mode: yaml implies? That's what I have a hard time with finding documentation | 10:29:08 |
| @hexa:lossy.network | that will reset dashboards | 10:30:34 |
| @hexa:lossy.network | since one uses the managed .storage subdir to store the dashboards | 10:30:49 |
| @hexa:lossy.network | while the other uses the lovelace.yaml in /var/lib/hass | 10:31:06 |
| @hexa:lossy.network | I suspect the schema is mostly the same though | 10:31:19 |
| CRTified | Thank you :) I'll give it a shot when I have a bit of spare time | 11:33:03 |
|  DerivationDingus changed their display name from bytebandit to DerivationDingus. | 19:43:23 |
|  symphorien joined the room. | 20:09:54 |
| 7 Oct 2024 |
|  @memegames99:matrix.org removed their profile picture. | 00:05:42 |
| @memegames99:matrix.org removed their display name memegames99. | 00:05:52 |
| @memegames99:matrix.org left the room. | 00:06:11 |
|  Sam Lehman changed their profile picture. | 14:24:47 |
| 11 Oct 2024 |
|  Emilia joined the room. | 17:54:33 |
| 12 Oct 2024 |
|  @rcouto:matrix.org joined the room. | 19:17:03 |
|  johnhamelink joined the room. | 20:46:54 |
| johnhamelink | Hi there, I'm trying to install a home-assistant lovelace module (home-assistant-custom-lovelace-modules.valetudo-map-card), and while it seems to install OK, I don't see the card in lovelace when creating a new entity. When using HACS, I'd have to add a "resource" url in order to complete the installation. Is that also necessary in this case, and if so, how would I find the correct URL to use for the resource | 20:48:59 |
 K900 | No, it's not necessary | 20:50:51 |
| K900 | But you may need to force refresh the page | 20:50:56 |
| johnhamelink | Hmm, a force-refresh hasn't helped. When I manually add the yaml block from the valetudo map card docs, lovelace gives an error saying "custom element doesn't exist". | 20:52:53 |
| johnhamelink | Here's the config I've written for context: https://git.sr.ht/~johnhamelink/nix/tree/master/item/os/hosts/sun/services/home-assistant.nix#L73 | 20:53:40 |
| K900 | 
Download image.png | 20:54:01 |
| K900 | It works fine for me | 20:54:03 |
