🤖Have you ever tried Chat.M5Stack.com before asking??😎
    M5Stack Community
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Core2 cannot be burned as Public and is not active in UI2Flow

    UiFlow 2.0
    4
    5
    49
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      PavelResi
      last edited by

      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

      1 Reply Last reply Reply Quote 0
      • Y
        yuyun2000
        last edited by

        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/

        ajb2k3A 1 Reply Last reply Reply Quote 0
        • ajb2k3A
          ajb2k3 @yuyun2000
          last edited by

          @yuyun2000 Did you Erase existing firmware first?

          UIFlow, so easy an adult can learn it!
          If I don't know it, be patient!
          I've ether not learned it or am too drunk to remember it!
          Author of the WIP UIFlow Handbook!
          M5Black, Go, Stick, Core2, and so much more it cant be fit in here!

          S 1 Reply Last reply Reply Quote 0
          • S
            Slarck @ajb2k3
            last edited by

            @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?

            ajb2k3A 1 Reply Last reply Reply Quote 0
            • ajb2k3A
              ajb2k3 @Slarck
              last edited by

              @Slarck You should always Erase first because of this. never just burn only.
              Thats the reason for the big red erase button being there!

              UIFlow, so easy an adult can learn it!
              If I don't know it, be patient!
              I've ether not learned it or am too drunk to remember it!
              Author of the WIP UIFlow Handbook!
              M5Black, Go, Stick, Core2, and so much more it cant be fit in here!

              1 Reply Last reply Reply Quote 0
              • First post
                Last post