<![CDATA[Core2 cannot be burned as Public and is not active in UI2Flow]]>Hi,
I played with a Core2 after long time. I did something wrong. I reprogrammed it. But current result is:
If I burn it, Device is still only "Private" regardless of the programming option (Public/Private).
UI2Flow display device correctly as a Private or Public. But I am not able to activate device. Unregistration in UI2Flow and reburning do not help.
I am able to use UIFlow1 with API Key and connect it by USB in UI2Flow.
How to make it Public and control it online in UI2Flow?
Thanks

]]>https://community.m5stack.com/topic/7635/core2-cannot-be-burned-as-public-and-is-not-active-in-ui2flowRSS for NodeTue, 28 Apr 2026 22:15:28 GMTTue, 24 Jun 2025 12:28:44 GMT60<![CDATA[Reply to Core2 cannot be burned as Public and is not active in UI2Flow on Thu, 03 Jul 2025 19:28:45 GMT]]>@PavelNDC Public (red) means that's it's not connected. normally this is an issue with the M5Stack server.

]]>https://community.m5stack.com/post/29389https://community.m5stack.com/post/29389Thu, 03 Jul 2025 19:28:45 GMT<![CDATA[Reply to Core2 cannot be burned as Public and is not active in UI2Flow on Thu, 03 Jul 2025 11:53:19 GMT]]>Thanks for the reply, but no progress.

My steps are:

Core2 device connected
Core2 device = Private (on display)
logged in to the UI2flow. It shows Core2 as Public, red

  • Core2 unregistered in UI2flow
  • Core2 not visible in UI2flow
  • registered to M5Burner, downloaded last FW 2.3.0-Core2
  • Press Burn, Erase → Erased successfully
  • Press Burn, Start, Baud Rate default (1500000)
  • Checking device...
  • Burn UIFlow2 pop-up window froze
  • Waited 2 min.
  • UI2Flow page refreshed
  • Waited 30 min. → no change
  • Closed Burn pop-up window
  • Reopened Burn pop-up window
  • Press Burn, Erase → Erased successfully
  • Set BaudRate to750000
  • Erased successfully
  • Checking device...
  • Waring: ...bind your account now? → Yes
  • Binding device → keep settings to "Public" → next
  • Binding device successfully
  • Press Erase
  • Erased successfully
  • Brun, Set BaudRate to750000
  • Checking device....
  • Configure, filled Wifi credentials → Next
  • Burning
  • Core2 restarted, Burn successfully
  • I can see on display "Private" again
  • Core2 is visible in UI2Flow as Public, red. (After reloading the page).

Any idea?
Thanks

]]>https://community.m5stack.com/post/29381https://community.m5stack.com/post/29381Thu, 03 Jul 2025 11:53:19 GMT<![CDATA[Reply to Core2 cannot be burned as Public and is not active in UI2Flow on Thu, 26 Jun 2025 04:03:42 GMT]]>@Slarck You should always Erase first because of this. never just burn only.
Thats the reason for the big red erase button being there!

]]>https://community.m5stack.com/post/29336https://community.m5stack.com/post/29336Thu, 26 Jun 2025 04:03:42 GMT<![CDATA[Reply to Core2 cannot be burned as Public and is not active in UI2Flow on Thu, 26 Jun 2025 03:04:16 GMT]]>@ajb2k3 said in Core2 cannot be burned as Public and is not active in UI2Flow:

@yuyun2000 Did you Erase existing firmware first?

Good point, I was also wondering if a full erase before burning might be necessary here. Sometimes leftover configs can cause issues with the device mode not updating properly. Has anyone confirmed if doing a complete erase in M5Burner helped switch the Core2 to Public successfully?

]]>https://community.m5stack.com/post/29335https://community.m5stack.com/post/29335Thu, 26 Jun 2025 03:04:16 GMT<![CDATA[Reply to Core2 cannot be burned as Public and is not active in UI2Flow on Wed, 25 Jun 2025 19:00:35 GMT]]>@yuyun2000 Did you Erase existing firmware first?

]]>https://community.m5stack.com/post/29333https://community.m5stack.com/post/29333Wed, 25 Jun 2025 19:00:35 GMT<![CDATA[Reply to Core2 cannot be burned as Public and is not active in UI2Flow on Wed, 25 Jun 2025 01:11:21 GMT]]>To resolve the issue with your M5Stack Core2 not switching to "Public" mode in UIFlow 2.0, follow these steps:
Steps to Fix:

Reconfigure in M5Burner:

Open M5Burner and ensure you are using the latest firmware for Core2.
Select the correct port and click Configure.
Choose Public mode in the configuration options before burning the firmware.

Check Account Binding:

Ensure the device is bound to the same account used in UIFlow 2.0. Log in to UiFlow2 with the same credentials as M5Burner.
If the device is still "Private," unbind it from your account and rebind it.

Wi-Fi Connection:

Ensure the Core2 is connected to Wi-Fi. A stable connection is required for online control.

Reset and Reburn:

Perform a factory reset on the Core2.
Reburn the firmware, ensuring Public mode is selected.

Verify in UIFlow 2.0:

After reburning, check the device status in UIFlow 2.0 under Select Device. It should now appear as "Public."

Additional Notes:

If the issue persists, contact support@m5stack.com for further assistance.
Ensure no conflicting configurations (e.g., API keys) are interfering with the mode switch.

https://chat.m5stack.com/

]]>https://community.m5stack.com/post/29325https://community.m5stack.com/post/29325Wed, 25 Jun 2025 01:11:21 GMT