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

    UI Flow2 UTC time issue

    UiFlow 2.0
    2
    4
    22
    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.
    • C
      csierra67
      last edited by

      I am using a Core S3 with UI Flow2 and having trouble with the RTC functions

      m5_time_example.jpg

      While the year month and day information of the tuple are correct, the hour and minute are not
      Hour is displayed as 0 instead of 17 and minutes are 17 instead of 31.
      Seconds are correct.
      I get the same results with a Core 2 under UI Flow2
      Reverting to UI Flow 1 and Core 2, The information is correct.

      As I examine the python code generated by the blocs, they appear correct to me.
      Thanks a lot for your suggestions

      G 1 Reply Last reply Reply Quote 0
      • G
        gektron @csierra67
        last edited by

        @csierra67 I reported this just a few days ago and the bug has been passed on the the team. See my post here https://community.m5stack.com/topic/7744/rtc-serious-bug-easy-fix-for-development-team

        The block is calling rtc.init(...), it should be calling rtc.datetime(...)

        C 1 Reply Last reply Reply Quote 0
        • C
          csierra67 @gektron
          last edited by

          @gektron thanks for the clarification, I am hoping M5 will fix it. It seems it has been there for a while. I burned my devices with an older version of UI flow2 and the bug is already existing

          C 1 Reply Last reply Reply Quote 0
          • C
            csierra67 @csierra67
            last edited by

            @csierra67 Further to this suggestion, I tried the mpy route but got an error, type mismatch and the device frozen during upload needed to be burned again to recover control
            Finally I tried to not set the time and work with the Time section rather than the RTC section with the assumption that the device being connected to Internet anyway, it would get the correct time by itself.
            The following example works flawlessly and closes my issue as a reference for fuuture developperssolution.jpg

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