| 18 Feb 2025 |
 @hexa:lossy.network | I don't think so | 15:36:44 |
| @hexa:lossy.network | home-assistant should be the hub for all requests | 15:37:10 |
 oddlama | yeah I'm pretty sure there is no packet going to the device | 15:37:19 |
| @hexa:lossy.network | did the setup wizard work for you? | 15:37:46 |
| oddlama | no, it fails in the last step which is where it calls this internal assist_satellite/test_connection action on the entity | 15:38:23 |
| oddlama | but the device will still be there | 15:38:30 |
| oddlama | this action times out, but I couldn't find the code responsible for that since I'm not sure where this async event is handeled in the backend | 15:39:05 |
| @hexa:lossy.network | the last step was iirc where it tried playing back sound from home-assistannt 😄 | 15:39:17 |
| @hexa:lossy.network | * the last step was iirc where it tried playing back sound from home-assistant 😄 | 15:39:19 |
| @hexa:lossy.network | that's where I was initially stuck as well | 15:39:29 |
| oddlama | That matches my experience exactly | 15:40:44 |
| oddlama | How did you "unstuck" it? | 15:40:54 |
| @hexa:lossy.network | it was the ipv6 issue for me 😄 | 15:41:11 |
| oddlama | rip, my dns only responds with ipv4 | 15:41:44 |
| oddlama | maybe an mdns query returns a v6 | 15:42:05 |
