I’m now wondering if it might also be an issue with your M5Stack Atom Lite board. Do you have any other ESP32 board handy for testing purposes?
Or can you connect the M5Stack Atom Lite to your computer (which OS) for serial output logging purposes?
Maybe, but before I put the whitelist in devices would appear in HA. Doesn’t mean it isn’t quite right though. I might pick up another ESP32 board and test with that.
I have Windows, but would need to look at what is needed for serial connection as that is something i haven’t looked at yet.
Were they discovered through the MQTT discovery and OpenMQTTGateway, or possibly through some other HA integration? I. e. did they have discovery entries created under the home assistant topic in MQTT Explorer?
I was just wondering if there is stack/memory issue with the M5Stack Atom Lite board during BM2 discovery, which might/should not happen with other ESP32 boards.
That is just a theory of mine though, and without a BM2 here all I can say is that with my other ESP32 boards my other devices are being discovered just fine.
You could connect to the OpenMQTTGateway gateway’s WebUI - Concorde to view the output.
Might need to log in quickly after a restart or roll up once there 
Alternatively, if you installed the binary through the web install page, similarly you could use a web serial monitor to watch the serial output during restart and discovery you went though above. Like
Also you should try to install the same M5Stack Atom Lite binary, but from the development upload page with the latest development branch state of OpenMQTTGateweay, just to see if it makes any difference.
Maybe try this first before monitoring any serial output
1 Like
So glad to see that things are working fine for you now. Sorry about all the hassle, as v1.8.1 should have functioned exactly the same proper way as well
@1technophile - definitely something we’ll need to look into with the current 1.8.1 release.
1 Like
Nothing to say sorry about :). Thanks for putting in the time to help 
1 Like