Alternatives to this

[lRoberth]

So the connection to Alexa drops pretty frequently, making it impossible to launch it to production (as the post says).

Is there an alternative to have Alexa communication with ESP32 with a solid connection? (I do have a server with an API that I can set up, but I need an idea on how to do this).

Probably I'd think about Alexa Skills, but it's something that I find pretty confusing and not enough information on how to make a Smart Home project with Alexa and ESP32 using my own server (I don't want to use Lambda. Don't know if it can be optional tbh)

[BoeckEH]

Are you using WIFiMulti? I have a garage opener via esp32 that loses connection if my Unify starts bouncing. I haven't implemented multi in that esp32 because only learned about it. Cycling power brings it back online, so should work. Lambda is pretty easy, skills are ok, but getting them published is hard to pass all the criteria, imo.

[lRoberth]

Never heard about WiFiMulti, I'm gonna give it a look. And about the skills, prob i'd get rejected, since I only want it to control my AC unit, not planning on giving the tool to other people.

[lRoberth]

Woops. Miss click, haha

[lRoberth]

Oh ok, so it basically adds "wifi mesh" functionality. Sadly there's just one access point available, so prob not an option.
Also, from what I've seen, I think it's not losing connection due to weak WiFi signal, I think it's something with the API. Since Echo Dot will not respond to my commands, saying the device is offline. In the Alexa app, the device shows as "Unresponsive", but if I move the dim slider, it somehow works and updates my device, then goes off again. The turn on/off button doesn't work at all in this state, and tried scheduling setting the slider at certain hour, but it doesn't work either.