| 11 Aug 2024 |
 @hexa:lossy.network | 
Download image.png | 00:05:36 |
| @hexa:lossy.network |
- built-in
- apexcharts
- mini-graph-card
| 00:05:46 |
| @hexa:lossy.network | the custom lovelace modules are both very big and can't be made smaller | 00:05:56 |
| @hexa:lossy.network | hoping for 2024.8.0 | 00:06:08 |
| @hexa:lossy.network | and mini-graph-card only ever shows one value prominenlty | 00:07:09 |
| @hexa:lossy.network | * no pretty graph card for sections layout 🤔 | 00:20:06 |
| 13 Aug 2024 |
 mjm | i got cliraop built with nix. now the coredump has even less info | 03:13:51 |
| mjm | ok got symbols in there, we're getting somewhere | 03:52:43 |
| mjm | i'm starting to get a hunch that this is crashing just because it's picking ports that aren't open on the firewall | 04:14:52 |
| mjm | haha that was it, cliraop opens UDP ports for listening from the local IP port range, and the device you're playing to needs to be able to connect to those. and its error handling for if that doesn't work is just...terrible | 04:46:06 |
| @hexa:lossy.network | cool | 10:38:54 |
 @adam:robins.wtf | can you not configure the ports it uses? | 12:27:39 |
| mjm | It’s hardcoded to open sockets with port 0 so no, not as far as I can tell | 13:41:40 |
| mjm | At least not without patching cliraop somehow | 13:42:18 |
| @hexa:lossy.network | port 0 is random | 14:05:04 |
| @hexa:lossy.network | have fun firewalling that | 14:05:15 |
| @hexa:lossy.network | https://github.com/rhasspy/wyoming/issues/23 debian people at it 😄 | 14:12:23 |
| @hexa:lossy.network | I mean, sure. Run your home assistant voice infrastructure on an IBM mainframe from 20y ago | 14:13:48 |
| @hexa:lossy.network | * I mean, sure. Run your home assistant voice infrastructure on an IBM mainframe from 30y ago | 14:14:47 |
| @hexa:lossy.network | * I mean, sure. Run your home assistant voice infrastructure on an IBM mainframe from >20y ago | 14:15:05 |
| mjm | In reply to @hexa:lossy.network
have fun firewalling that https://git.midna.dev/mjm/nix-config/-/blob/main/services/home-assistant/music-assistant.nix?ref_type=heads#L58-66
😭😭😭
| 14:22:35 |
| @hexa:lossy.network | 👏 | 14:23:05 |
 Sandro 🐧 | Security, what is that?! | 14:31:59 |
| mjm | idk but i don't have it anymore | 14:35:58 |
| @hexa:lossy.network | setting the port would be an improvement 😄 | 14:41:31 |
| @hexa:lossy.network | * bein able to set the port would be an improvement 😄 | 14:45:05 |
| mjm | the library code in it can do that, but main.c doesn't take an argument for it, and music-assistant wouldn't pass it anyway. if i get some time, i might look at patching them to support that | 14:49:57 |
| mjm | new issue: why is like...half of my music library just disabled in music assistant??? it doesn't make it clear why | 16:59:35 |
|  jul1u5 changed their display name from Julius Marozas to jul1u5. | 21:58:51 |
| 14 Aug 2024 |
| mjm | i think i fixed the music being unavailable by deleting the entire library. no idea how it got like that: the subsonic provider never marks anything unavailable | 00:07:26 |
