I have the exact problem: Chrome 107.0.5304.110 on Fedora 35. All buttons in the UI (label, button, line, etc) are nonfunctional as well as the "load", "save" etc buttons. UIFlow is completely unusable with Chrome. I can reproduce this in Konqueror also.

The buttons seem to work in Firefox though.

Hello @slow-moose

which UIFlow firmware version is running on your M5Core2?

I can use ESPNow blocks from the UIFlow online version 1.10.8 just fine on my M5Core2 running UIFlow firmware 1.10.8.

You can use M5Burner from here to update the UIFlow firmware on your M5Core2.

Thanks
Felix

This looks like a running issues with google chrome as its happening (or not happening as is the case) with other sites that download files.

I have same problem , after some time EspNow recieve callback block returns duplicate message.
Uiflow 1.10.7 , firmware m5 tough 1.10.6

Hello @mchott

in my experience a data SIM (for smartphones, LTE routers, etc.) is not good enough for NB-IoT. You will need a SIM card specifically for NB-IoT plus the NB-IoT service needs to be offered by the provider in your region.

Thanks
Felix

Hello @teiafra

thank you for letting me know. I am glad you found a workable solution.

Thanks
Felix

Hello
I've opened TCP 1883 and my device successfully connected.
Regards

@teastain I try to be helpful!

I managed to solve this issue with this custom block

@isamalatby Do you have a new device or second hand device?

@ajb2k3
I learned that the browser does connect to the Core2 by WiFi and the IDE connects using USB.

Thanks

@german-figueroa2000 What you did was to run the code on the core2 in test mode. You need to download the code to the core 2 from which it will be run on boot.

There are some differences between running in test mode and running in app mode and the biggest is that in app mode you may need to add blocks to initialise wifi communications where as in test mode, the wifi is auto magically run for us.

Thanks Teastain
I have the expansion module for CORE 2
I am looking for advice on the mode of communication to use to transfer from CORE2 to the ATOM Display, and how to transmit around 20 digital variables?

I agree quite frustrating, when you follow the sample and get no results.

Any pointers in the right direction would be fantastic.