M5Stack Atom Lite fails after restarting

[gritty light]

A while ago I got a notification in Home Assistant to update my Bluetooth Proxy to the newest version, which was a big mistake because after I did, everything broke. I have reinstalled the bluetooth proxy build on the M5Stack Atom Lite about 10 times now via the web builder, both on the internet and via the addon in Home Assistant. The only way it works is if I install it via the web builder using the generic ESP32 template, and then after the window pops up to connect it to my WiFi. If I then unplug the M5Stack and plug it into a different power outlet or any other USB, it just stays offline. I don't even know if the device is powered on or if it just doesn't connect to my WiFi network. I don't know what to do anymore, can anyone help me with this?

[dire iron]

do you have a hidden ssid?

[gritty light]

Yes I do, but it always worked with a hidden SSID

Do I have to unhide it now due to the new update?

[dire iron]

for esphome to connect to connect to hidden ssid networks you need to enable "fast_connect" in the wifi component.
I cant speak for what the ready made BT proxy firmware used to be but it currently does not include this
so you are probably best of building the firmware with the builder tool with your network info and fast connect set.

Documentation HERE
relevant section :

fast_connect (Optional, boolean): If enabled, directly connects to WiFi network without doing a full scan first. This is required for hidden networks and can significantly improve connection times (thus reducing power consumption). Defaults to off. The downside is that this option connects to the first network the ESP sees, even if that network is very far away and better ones are available. If multiple networks are configured, the last successfully connected one is tested first. In case it fails, all networks are then tested one after the other in their declared order, starting with the first one in the list.

[gritty light]

I'll give that a try, thank you

[late marlin]

I just had the same thing happen to me after I updated

[gritty light]

The fast_connect option seemed to fix my issue @late marlin

Thanks again @dire iron

[dire iron]

awesome, glad to hear it. good luck with your setup 🙂

[dire iron]

@gritty light @late marlin
update on this situation if you care for more information:
was an issue HERE and a PR HERE looks like a change was indeed made and it has been fixed in ESPHome 2025.8.2
this means that the recent Bluetooth proxy ready made project update (firmware2025.8.1) which is based on ESPHome 2025.8.0 will have suffered from the issue. whilst the fix has been deployed into mainline esphome the premade firmwares have not yet been updated. however due to this issue i suspect they will be recompiled and updated at some point soon

[gritty light]

I see, thanks for the info. Good to know it was a known issue and not something random I messed up 👍