<![CDATA[Bug AtomS3 with UIFlow2 on library time]]>on Alpha 9, the software Time library still return false values:

"get UTC time" return a tuple where:

  • Year is with difference of +30 to reality
  • Day is with difference of -1 to reality

"get system uptime in seconds" is definitely false with a very high value

it come probably from a confusion between unix time year 1970 and unix time year 2000

thanks

]]>https://community.m5stack.com/topic/5222/bug-atoms3-with-uiflow2-on-library-timeRSS for NodeWed, 29 Apr 2026 10:04:00 GMTSat, 15 Apr 2023 12:51:09 GMT60<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Fri, 30 Jun 2023 15:16:39 GMT]]>@iamliubo said in Bug AtomS3 with UIFlow2 on library time:

@ajb2k3 can you show me the code?

We solved it over Twitter

]]>https://community.m5stack.com/post/21418https://community.m5stack.com/post/21418Fri, 30 Jun 2023 15:16:39 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Fri, 30 Jun 2023 10:06:42 GMT]]>@flex said in Bug AtomS3 with UIFlow2 on library time:

@iamliubo
Hi
System uptime in seconds should return 0 when the system (m5stack ….S3) starts, nobostand epoch 1970 or 2000…

When boot up, if device connect to wifi will auto sync the time from ntp server, and time.time() this function will overwritten by new time.

]]>https://community.m5stack.com/post/21410https://community.m5stack.com/post/21410Fri, 30 Jun 2023 10:06:42 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Fri, 30 Jun 2023 10:03:59 GMT]]>@ajb2k3 can you show me the code?

]]>https://community.m5stack.com/post/21409https://community.m5stack.com/post/21409Fri, 30 Jun 2023 10:03:59 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Fri, 30 Jun 2023 10:03:35 GMT]]>@flex yes, we change to 1970

]]>https://community.m5stack.com/post/21408https://community.m5stack.com/post/21408Fri, 30 Jun 2023 10:03:35 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Thu, 22 Jun 2023 09:34:49 GMT]]>@iamliubo
Hi
System uptime in seconds should return 0 when the system (m5stack ….S3) starts, nobostand epoch 1970 or 2000…

]]>https://community.m5stack.com/post/21269https://community.m5stack.com/post/21269Thu, 22 Jun 2023 09:34:49 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Tue, 20 Jun 2023 04:35:37 GMT]]>@IAMLIUBO I'm getting an issue with time with 1.11.9 both the core and core 2 are showing an error with time "Module Time has no attribute"

]]>https://community.m5stack.com/post/21239https://community.m5stack.com/post/21239Tue, 20 Jun 2023 04:35:37 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Mon, 19 Jun 2023 21:22:07 GMT]]>I think that Micropython use epoch 2000 by default

]]>https://community.m5stack.com/post/21238https://community.m5stack.com/post/21238Mon, 19 Jun 2023 21:22:07 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Mon, 19 Jun 2023 03:41:49 GMT]]>@flex

Sorry, last update(aplha-17) we change the epoch time from "2000-01-01" ot "1970-01-01".So "get system uptime in seconds" block return is tiem stamp from 1970-01-01. And use "1970-01-01" as epoch is more compatible.

]]>https://community.m5stack.com/post/21230https://community.m5stack.com/post/21230Mon, 19 Jun 2023 03:41:49 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Mon, 19 Jun 2023 03:08:39 GMT]]>@flex

There is problem when using "Set timezone GMTx":
using "Set timezone GMT+2" and then "get local time", it should
return UTC+2/GMT+2 but it return UTC-2/GMT-2

honestly, I was confused at first, but i saw this link, it explain why the time zone is reversed:https://stackoverflow.com/questions/53076575/time-zones-etc-gmt-why-it-is-other-way-round

There is still problem with "get system uptime in seconds" which is not adjusted to epoch 2000 and returns a very big value

ok, thanks for report, will check this and fix.

]]>https://community.m5stack.com/post/21229https://community.m5stack.com/post/21229Mon, 19 Jun 2023 03:08:39 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Sat, 17 Jun 2023 17:09:50 GMT]]>Hi dev Team,

I made small test on Alpha17:

  • now "get UTC time" works correctly :)

  • There is problem when using "Set timezone GMTx":
    using "Set timezone GMT+2" and then "get local time", it should return UTC+2/GMT+2 but it return UTC-2/GMT-2

  • There is still problem with "get system uptime in seconds" which is not adjusted to epoch 2000 and returns a very big value

Thanks

]]>https://community.m5stack.com/post/21222https://community.m5stack.com/post/21222Sat, 17 Jun 2023 17:09:50 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Mon, 12 Jun 2023 08:07:05 GMT]]>@imaliubo

yes I tried,

it seems that UIFlow (based on 1.19.1) doesn't take epoch into account, which is year 2000 in MP 1.19.1 or 1.20.

Apart that there is confusion created on gmtime() and localtime() in UIFlow apis.

Also to mention that in MP 1.20, the returned values from gmtime() and localtime() are not all time reliable (sometimes the ntpserver requested in MP localtime() return what in fact is gmtime()...)

]]>https://community.m5stack.com/post/21171https://community.m5stack.com/post/21171Mon, 12 Jun 2023 08:07:05 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Mon, 12 Jun 2023 03:55:08 GMT]]>@flex

Hi, did you check this time docs of micropython port?

0_1686542095863_1cceab94-6e76-4b26-8dd3-5423f8a76b5f-image.png

0_1686542112272_c742a3f5-e76c-46bb-8f83-82baab888585-image.png

]]>https://community.m5stack.com/post/21167https://community.m5stack.com/post/21167Mon, 12 Jun 2023 03:55:08 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Wed, 26 Apr 2023 21:23:32 GMT]]>@flex said in Bug AtomS3 with UIFlow2 on library time:

on Alpha 10 the problem remains

on Alpha 11 the problem remains

]]>https://community.m5stack.com/post/20685https://community.m5stack.com/post/20685Wed, 26 Apr 2023 21:23:32 GMT<![CDATA[Reply to Bug AtomS3 with UIFlow2 on library time on Sun, 16 Apr 2023 11:50:51 GMT]]>@flex on Alpha 10 the problem remains

]]>https://community.m5stack.com/post/20617https://community.m5stack.com/post/20617Sun, 16 Apr 2023 11:50:51 GMT