Posts made by ciconde

After doing Erase and flashing UIFlow1, no mater how many times I regenerate the API KEY I always get an error saying that the device has been bound.

I don't know how to unbound in order to use the device again.

Any suggestion?

Slider unit missing

Device manager - apps - ability to open app in editor needed.

I tend to store there the apps, so I'd like to load them from device same as in UiFlow1

Core2 firmware - start screen doesn't refresh User account until navigated out and back in

RGB software element is not working - color can't be changed

EzData2 Debugger wanted

It would be great to have an EzData2 HMI such as we had in EzData1 "debugger".

Thanks for such a great job!

Several screen pages desired.

Suggest to have several pages with different elements on them (like the scenes in Scratch) so it's easy to create a multi page application.

Then an UI instruction for switchToPage(n) would disable and hide all elements but the ones pertaining to that page, potentially applying also separate background color.

I have a Servo2 with Core2 but I don't see it in "Modules".
Can you please add it so we can use it?

My fault, sorry, I explained unproperly.

How do we send information from our code to the console, i.e. to print debug messages?

Sorry if it's a very noob question but I haven't figured the block to use.

UIFlow 1 devices formerly had a way to add them to my user.
Not only they show in my Device Manager, they also refuse to be downloaded anonymously, which is great.

I don't find how to do it anymore.

Please mind all this issue is around binding a device to an user, not how to bind them to the programming tool, which is OK with API KEY.

No, being regular M5stack Core2 and regular Atom Lite they are not S3 and therefore I can't burn UIFlow2. Am I wrong?

I can't recall the manual binding method for UIFlow, would you be so kind of clarifying this?
Long time ago, when I burnt my old devices the burner would ask me if I wanted to bind.
This is the only procedure I know.

@ajb2k3 Just did exactly that: first erase, then burned the firmware.

M5Burner was logged in, but no dialog to bind the device:

Why there's no option nor dialog to bind? I'm using M5Burner latest version, just downloaded it...

I'd like to suggest a bind button on the UI to bind a successfully connected device, so this process would be even better.

Thanks!

@ajb2k3 How do we send to that "web console". I can se the console in Chrome, but can't figure how to send data to it.

@ajb2k3 Register process is done with M5 Burner, isn't it?

Also just happened with Atom Lite, also V1.12.2

Core2 V1.12.2

@m5stack Happening again (similar) in 1.12.2

In this case the only log message is:

>>> reconnect start ...

Device looks hanged at thar moment, not executing and not responsive.

Hello,

I have one new device and after upgrading firmware I don't see any option to register it to my account.

I am successfully logged to both M5Burner and UI Flow web and I can connect to the device and download it, but I see no means of registering it to my device manager.

Tried regenerating API Key, no luck with new one but still able to connect and download.

Thanks!

@m5stack Can you please help here?
I've flashed 1.9.4-en and 1.9.5-en versions without luck...

It's only happening if I "run" the program. In both versions if I do the "download" then screen just go blank.