| 18 Feb 2025 |
 @hexa:lossy.network | e.g. ether host <mac> | 15:43:15 |
| @hexa:lossy.network | * ether host <mac> | 15:43:20 |
| @hexa:lossy.network | https://github.com/home-assistant/frontend/tree/dev/src/dialogs/voice-assistant-setup this is the frontend for the voice-assistant setup | 15:43:43 |
 oddlama | I can try, do you want to see packets from the backend or from the device (would have to capture on different hosts)? | 15:44:10 |
| @hexa:lossy.network | the component seems to be assist_satellite | 15:44:22 |
| oddlama | I traced it to this line https://github.com/home-assistant/core/blob/efd7ddeb89f643241ffe78680bfb00b063de4667/homeassistant/components/assist_satellite/websocket_api.py#L201 | 15:44:31 |
| @hexa:lossy.network | ideally somewhere between your firewall and the voice pe | 15:44:51 |
| oddlama | Only some ARP packets and occasional traffic between hass and esphome port (6053) on the PE device | 15:51:25 |
| oddlama | I | 15:52:04 |
| oddlama | * I'll resetup and see if there's moere | 15:52:11 |
| oddlama | * I'll resetup and see if there's more | 15:52:13 |
| oddlama | Okay it doesn't do a lot:
- DNS request for firmware.esphome.io
- Short request to firmware.esphome.io (I presume a version check which returns up to date)
- DNS query for home.my.domain
- Requests the flac file, nginx says:
{"time": 1739893923.762,"remote_addr":"192.168.20.58","status":200,"method":"GET","host":"home.my.domain","uri":"/api/esphome/ffmpeg_proxy/6b5d67d3a0931ee401f33c2fe15fb882/CyvOpsLqds3mqSpuWDUmZQ.flac","request_size":180,"response_size":5,"response_time":2.508,"referrer":"","user_agent":"ESP32 HTTP Client/1.0"}
- Nothing more.
| 15:57:02 |
| @hexa:lossy.network |
192.168.120.202 - - [18/Feb/2025:15:58:54 +0000] "GET /api/esphome/ffmpeg_proxy/39010bc74f2902a85ba88defd1d580fa/Tn6bN89MU6I2ue8h47PgmA.flac HTTP/1.1" 200 112971 "-" "ESP32 HTTP Client/1.0"
| 15:59:04 |
| @hexa:lossy.network | that is the intial request for a "WOOOOOSH" sound | 15:59:11 |
| @hexa:lossy.network | when starting the wizard | 15:59:15 |
| @hexa:lossy.network | do you hear that? | 15:59:16 |
| oddlama | nope | 15:59:21 |
| oddlama | it never plays a sound except when I reset the device, but that file is probably saved locally | 15:59:37 |
| @hexa:lossy.network | yup | 15:59:47 |
| oddlama | I even have two PE devices with the same issue, so I can probably rule out hardware issues | 16:00:19 |
| @hexa:lossy.network | so next step would be connecting to the console of the voice pe | 16:00:22 |
| oddlama | Did that in the web console when updating the firmware | 16:00:37 |
| oddlama | but there are no debug logs at all | 16:00:42 |
| oddlama | just some wifi connection stuff and generic things | 16:00:53 |
| oddlama | Maybe I can recompile the firmware with some added debug prints | 16:01:31 |
| oddlama | But I'm not sure how it is supposed to be compiled | 16:01:50 |
| @hexa:lossy.network | isn't it just an esphome build? | 16:02:15 |
| @hexa:lossy.network | check their CI | 16:02:24 |
| oddlama | A good call | 16:02:40 |
| oddlama | * Ah good call | 16:02:43 |
