| 4 Oct 2024 |
 @hexa:lossy.network | and when listing them it also calls them | 09:33:59 |
| @hexa:lossy.network | ouch | 09:34:05 |
|  rendakuenthusiast⚡️ left the room. | 09:51:23 |
| 5 Oct 2024 |
|  ˈt͡sɛːzaɐ̯ joined the room. | 04:12:26 |
 CRTified | Short sanity check. I'm running a config with lovelaceConfig = null;. Can I still use customLovelaceModules in a sane way (i.e., without manually configuring every resource) | 17:16:27 |
| CRTified | * I'm running a config with lovelaceConfig = null;. Can I still use customLovelaceModules in a sane way (i.e., without manually configuring every resource) | 17:16:35 |
 Sandro 🐧 | you should | 17:47:37 |
| Sandro 🐧 | if things don't load properly, things are not packaged correctly | 17:47:44 |
| CRTified | In reply to @sandro:supersandro.de
if things don't load properly, things are not packaged correctly Mhhh, I'm not aware of anything special that I have done. I can access the resources under the expected URL, but can't use any special card without loading it as a resource | 20:08:41 |
| Sandro 🐧 | Try clearing the cache? | 20:10:03 |
| Sandro 🐧 | I have two custom cards which show up when clicking Add Card | 20:10:13 |
| Sandro 🐧 | I had such a problem before and the root cause was that the URLs where not correct but that fix was merged months ago | 20:10:31 |
| CRTified | In reply to @sandro:supersandro.de
Try clearing the cache? Nope, doesn't help 😕 | 20:20:41 |
| CRTified | I can also see the values in the configuration.yaml
# yq --yaml-output ".lovelace" configuration.yaml
mode: storage
resources:
- type: module
url: /local/nixos-lovelace-modules/apexcharts-card.js?2.1.2
- type: module
url: /local/nixos-lovelace-modules/decluttering-card.js?1.0.0
- type: module
url: /local/nixos-lovelace-modules/mini-graph-card-bundle.js?0.12.1
- type: module
url: /local/nixos-lovelace-modules/mini-media-player-bundle.js?1.16.9
- type: module
url: /local/nixos-lovelace-modules/mushroom.js?4.0.7
- type: module
url: /local/nixos-lovelace-modules/valetudo-map-card.js?2023.04.0
- type: module
url: /local/nixos-lovelace-modules/zigbee2mqtt-networkmap.js?0.9.0
| 20:36:31 |
| 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 |
