| 18 Feb 2025 |
 @hexa:lossy.network | * it requires IPv4, if you don't have that | 14:26:02 |
 oddlama | I do have ipv4. It's a bit weird, because the esphome part works fine, and it requests the .flac file from the HA server and gets a 200 response. But the frontend somehow calls assist_satellite/test_connection on the entity which fails with a timeout without logging why that happens. | 14:29:29 |
| oddlama | Initially i found that there was an issue when the internal url is served via https, but that had already been fixed in the version I'm using | 14:30:21 |
| oddlama | and my server responds 200, so that must have worked | 14:30:31 |
| oddlama | * Initially i found that there was an issue when the internal url is served via https, but that had already been fixed in the updated version I'm using now | 14:30:56 |
| @hexa:lossy.network | hm 🤔 | 14:45:30 |
| oddlama | I guess the only thing that's different on my instance is the internal https url :/ | 14:56:52 |
| oddlama | Looks like a bug in the frontend, since there are no packets sent to the device at all in this step | 14:57:36 |
| @hexa:lossy.network | wdym internal https | 14:59:26 |
| @hexa:lossy.network | is it self-signed? | 14:59:31 |
| oddlama | I have a nginx proxy running locally, all certs are letsencrypt | 15:15:37 |
| oddlama | internal dns resolver resolves home.my.domain to the internal HA ip | 15:16:04 |
| oddlama | In the settings I use the same addresso i just the same address for internal_url and external_url | 15:18:09 |
| oddlama | * In the settings I use the same address for internal_url and external_url | 15:18:22 |
| @hexa:lossy.network | I'm using a single address with LE https | 15:18:37 |
| @hexa:lossy.network | but it is purely internal and only available at home or on a VPN | 15:18:55 |
| oddlama | mine is also internal only | 15:19:05 |
| oddlama | sounds like a similar setuo | 15:19:10 |
| oddlama | * sounds like a similar setup | 15:19:12 |
| @hexa:lossy.network | why they internal/external dance? | 15:20:26 |
| @hexa:lossy.network | 
Download image.png | 15:21:05 |
| oddlama | thats exactly what I have | 15:21:21 |
| @hexa:lossy.network | the upper address looks important ::D | 15:21:21 |
| @hexa:lossy.network | * the upper address looks important 😄 | 15:21:23 |
| oddlama | I mean the device also uses the address correctly | 15:21:35 |
| @hexa:lossy.network | when mine didn't work I tcpdumped what it did | 15:21:37 |
| oddlama | Am I maybe missing some component which trips up the backend server? | 15:21:55 |
| @hexa:lossy.network | for me it stopped after a dns lookup, so it was clear, that it didn't like ipv6 only setups 🤡 | 15:22:00 |
| @hexa:lossy.network | filed an issue, no response | 15:22:05 |
| @hexa:lossy.network | you probably have pipelines setup | 15:22:22 |
