AS-ESP32-S3 won't initialize

[scottq]

I just purchased a AS-ESP32-S3 device to act as a voice assistant for my Home Assistant. When I received the unit, something inside it was rattling around loosely - like something had broken inside. Not sure if that's ultimately important or not. 

When I plugged the device into the HA server, all of the lights turned blue and a tone built up in about 3 steps to a steady tone. The tone continued without stopping for as long as I had the device plugged it (up to 15 minutes, when I unplugged it). It doesn't seem to me that it was flashed with any new firmware as described in this YouTube video: https://www.youtube.com/watch?v=g-KsrZjFljY

While the tone was sounding, I did try to configure the device in my home assistant. I selected "Add Device", saw ESPHome and selected it, and was presented with a modal asking for the host ip address, which I provided. I got a "Unable to connect to the ESPHome device. Make sure the device's YAML configuration includes an 'api' section." as shown in the attached screenshot. I have no way to access any YAML that the device might be using since I can't access the device and can't do anything with it in Home Assistant.

What do I do to get this thing working?

Scott

[admin]

https://www.kincony.com/forum/showthread.php?tid=7232

[scottq]

https://www.kincony.com/forum/showthread.php?tid=7232

This does not help. As I noted, the buzzing tone never stops and it seems that the firmware is never flashed. And again - I am not experiencing the problem as is shown in the YouTube video I provided above - in that video it seems that the new firmware is flashed very quickly and without disruption.

Were I to follow your thread, where would I put the YAML file? Directly on the filesystem via the File Editor? If so where do I put it?

[admin]

install esphome on home assistant, then create yaml paste our code.

[scottq]

install esphome on home assistant, then create yaml paste our code.

As shown in my first post, I can't install it b/c whatever YAML it's trying to use doesn't have an `api` section... it's like a race condition.