The quality of the hardware is really good, it reminds me the Adafruit dynamics.
Open source core tools will be such a good idea to let us, as a community, help and improve all M5Stack software.

Anyone from M5Stack has an opinion on this?

@iamliubo how can we help to see M5stack go OpenSource?
The devices are great, but software will be boosted in a large way.

I made some progress on the control side.
I have a testing android app that communicate with the atom fly through Bluetooth.
It's basic and only to test, now I need some true PID on the motors before writing a fly control app
All code is available as usual : https://gitlab.com/TitiMoby/atomflychallenge

https://youtu.be/_Wg2lruzzcw

And a clear documentation on MicroPython API as all I can guess is from Loboris repository who kindly provide a true MicroPython distribution but without what you can read in UIFlow python screen.

Each company is free to decide whether to open their software or not, but I think that M5Stack will gain so much love and help if they decided to open UIFlow, give a way to contribute to documentation...

Is it possible to have a statement on this from M5Stack or do we continue to ask it without answers as it is for months now?

@iamliubo May I ask you if you are part of M5Stack staff?
Not to bother you, just to understand the M5 ecosystem ;)

@iamliubo how can we help to see M5stack go OpenSource?
The devices are great, but software will be boosted in a large way.

The quality of the hardware is really good, it reminds me the Adafruit dynamics.
Open source core tools will be such a good idea to let us, as a community, help and improve all M5Stack software.

Anyone from M5Stack has an opinion on this?

I’m sorry to post once more, but there sa something I did not get.
In fact, my mistake was to use th Demo button in UIFlow.
There is only a demo for Env v1 and this is what I modified.
The link in the documentation was for a proper ENV v2 UIFlow program but as I never used m5f and there was no prior information in the documentation, I thought it was the same as the Demo in UIFlow.

I know I must pay more attention, but if a beginner comes to the documentation, I think there must be a link to usage of m5f files before.

That’s it, sorry for the noise 🤷‍♂️😇

And the answer was to learn how to handle Hat with UIFlow 🤣
If someone tries to use ENV 2 demo, beware that it references the ENV hat version one.
You need to remove it, add the ENV 2 hat, the replace with the new module functions the different calls.

If someone knows how to do it, I can report the documentation error.

I just spotted your topic and I'm wondering how you solved the issue.
I'm running the current 1.7.2 UIFlow and firmware but when opening ENV II demo from the documentation page it does not recognize the ENV II Hat and error message appear about not connected hat.

As I also use micropython, I inspected modules and saw that there was a hat.ENV2.
So I just had to modify one line of code.

But I did not figure out how to do it from UIFLow blocks.
What is the solution?

On my core gray, I have a specific code to write my config file myself.
That way, I always know how to read it back.
My experiments are available on Github and I used it in several of my videos, for exemple this one on writing and reading this config file.

It’s in french, but I think the code is simple enough.
If it’s not the case, I can answer questions.

As this is not my first M5 board, I think I was in App mode. But as the main source of errors is often between the chair and the keyboard, I'll focus my attention on this point 😉