Same problem with the CORE2, do you have a solution for this error with M5burner V3 under win10

The update 1.9.7 works well, but impossible to configure the ATOM Display still the error message "Get configurations failed"

impossible to use the ATOM Display without the API Key

@lishengkkk all it takes is a small stroke of the cutter and the track is cut cleanly.
I scraped off the white paint to get to the copper. So if needed a drop of solder and everything works as it did at the start.

@lishengkkk I only use UIFLOW, no need to change the code once the connection is cut

@ajb2k3 J'attends avec impatience la version Française. super boulot, félicitations

With the M5Paper, Uiflow displays Alpha M5Paper and not 1.9.2...

https://www.thingiverse.com/search?q=M5stack&type=things&sort=relevant

Thanks @felmue

The PaHUB solution on internal I2C 21/22 does not seem to be the right solution.
I only have to use two EXTEND I/O with two different addresses, but Uiflow only recognizes address 0x27.
Do you have an example of using EXTEND I/O with the I2C master functions of Uiflow without going through the declaration of an EXTEND I/O unit.
I only need the 8 I / O input and to read their status

an example of use would be very useful

I am limited in number of ports for my project, I have to use I2C with internal ports 21/22.
When I declare in Uiflow a PaHUB alone on 21/22, I don't get an error message. But if I declare in Uiflow a Pahub and an Extend i/o unit on the Pahub, I systematically get an error message on the CORE2 "Pahub unit may be not connected".
If I connect and declare the Pahub whith extend i/o on port A it works.
I need several Extend i/o, I have no other solution than the PaHUB.
I tried to modify the I2C address of an extend i/o (0x25), but Uifow does not recognize it, it looks for it on 0x27 (possible to change that?)
A little help would be appreciated