Topics created by greenleaf

@greenleaf Images have to be of a very optimised specification to work as the memory of devices is limited.
I haven't replied because I have been so busy with other things.
If I find time today I will have a look at these specifications.

@greenleaf Can you set up some kind or record to show the reading from both over a long time?
I haven't done a long term test so I'm curious.
If you can map the deviation between the two then you should be able to tune the sensor.
Also some thing else to check is if they are reading at the same resolution.

https://uiflow-micropython.readthedocs.io/en/latest/quick-reference/usb-mode.html

For future viewers of this thread, the API key is the same as the MAC address. You can usually find this on your router config where it shows device info. The MAC is also shown in the serial output when you connect a burner device (or FTDI cable as mentioned above.

My problem was the device was stuck and needed reflashing. Once I did that it worked perfectly using the 12-digit MAC as the API key.

You may safely ignore the 8 digit "API Key" that is shown in M5burner or the command line, this was a red herring.

As you can see I'm not doing anything especially exotic or weird here:

0_1660436660810_1d5b4e7a-a8af-4c03-9a12-4820a937aaf3-image.png

I think I probably have a defective unit. I have tried with only a single tab open, latest version of Google Chrome, tried it incognito mode also just to be sure some extension wasn't getting in the way. Despite all efforts it never connects to UIFlow. I know it's on the network because my router is showing it connected and sending/receiving some packets.

I will probably stick with devices that have USB-C on them, this is way too much hassle and I don't want to have to rig up a programmer just to toy around with a prototyping device. Oh well, at least I'm only out $5.

Wow, your balancing star is impressive!

I'm just playing around in UIFlow to see what's possible with this device.

Hello,

It helps to select a different color first. Then you can still make copies. An annoying detour indeed.

In case anyone else has the same issue...the handler works if you hard-code the path to the Wav file

0_1659467223749_c6876809-3335-4966-b617-200384690612-image.png

but cloud path doesn't work with the same trick, it still gives the Data format is not valid error.

@felmue I think I found the issue; my deepsleep() call was inside a loop. Moving it outside the loop sorted it out.

After some more troubleshooting I discovered that a 10ms wait after changing the screen color allows the first few lines to print when working in UIFlow. It appears that 'Set Screen backgroundColor' requires this delay before you can render text with Lcd.print.

This doesn't solve the mystery of the white screen when running in app mode though. Maybe someone else knows what's going on here.

I think I agree with you! I ran out of memory the other day just trying to import a simple Python library...

Did anyone find a place to order the battery for the M5stick CPlus?

Hi @greenleaf ,
Yes, it's Baidu AI cloud service.