It appears this bug is fixed, not in the firmware, but in the latest version of UIFlow!

@slavs Hi there, to you and to everyone:

I contacted M5Stack support and have received a reply. This issue is a known firmware bug with the ATOM Lite.

They said:

Hi Alex,
Yes. We confirmed that's a bug. We will fix it in recently version.
Currently now, you can click 'reflash' button before downloading the firmware, which should work.

@wsanders Hi there, I am using the latest firmware with the latest UIFlow

Bump on this one, anyone know what might be going on? Thanks!

@felmue Hi Felix

Unfortunately, I am back,

It appears if I reset or unplug and plug back in (effective reset) the device, the issue comes back.

The device will only work after an erase, burn and connect to UIFlow. Once connected, I can run as much as I like. Any disconnect appears to "kill" the device with the aformentioned python error on the COM Monitor until I do another erase, burn and connect etc,

Thanks,

Alex

@felmue Hi Felix,

A full erase and reburn, with a change of API key, has corrected the problem. Doh! How did I not already try this?!?!

Many thanks,

Alex

I used M5Burner to write UIFlow_Lite v1.9.6 for the ATOM Lite to my device. It has sucessfully connected to my WiFi, and I have provided the API key on UIFlow.

When clicking Run in UIFlow, it connects to the device, and the COM Monitor on the device spits this out:

Traceback (most recent call last):
  File "flow/m5cloud.py", line 105, in _exec_data
  File "<string>", line 8, in <module>
NameError: name '__VERSION__' isn't defined

I have tried different versions of the firmware but they all produce this result. I have only just got my device, so I haven't got UIFlow to work at all yet.