<![CDATA[UIFlow 1.7.3]]>Ver 1.7.3 time : 2021.03.12

v1.7.3

new features

* IoT Cloud support:
  * AWS
  * Azure
  * Tencent

* ATOM Base support:
  * ATOMIC GPS
  * ATOMIC Stepmotor
  * ATOMIC QR Code Reader

* M5Paper:
  * Internal SHT30 support.

Bug fix:

* ATOM MOTION get speed bug fix.
* M5Paper PORTC pin error bug fix.
* LoRaWAN P2P bug fix.
* Other bug fix.
]]>https://community.m5stack.com/topic/3072/uiflow-1-7-3RSS for NodeThu, 12 Mar 2026 01:01:03 GMTFri, 12 Mar 2021 11:02:05 GMT60<![CDATA[Reply to UIFlow 1.7.3 on Fri, 09 Apr 2021 08:50:31 GMT]]>@iamliubo May I ask you if you are part of M5Stack staff?
Not to bother you, just to understand the M5 ecosystem ;)

]]>https://community.m5stack.com/post/13438https://community.m5stack.com/post/13438Fri, 09 Apr 2021 08:50:31 GMT<![CDATA[Reply to UIFlow 1.7.3 on Mon, 29 Mar 2021 03:51:45 GMT]]>@titimoby
This is not something I can decide, but we will wait until that day :) (Maybe soon

]]>https://community.m5stack.com/post/13302https://community.m5stack.com/post/13302Mon, 29 Mar 2021 03:51:45 GMT<![CDATA[Reply to UIFlow 1.7.3 on Sun, 28 Mar 2021 21:27:39 GMT]]>@iamliubo how can we help to see M5stack go OpenSource?
The devices are great, but software will be boosted in a large way.

]]>https://community.m5stack.com/post/13296https://community.m5stack.com/post/13296Sun, 28 Mar 2021 21:27:39 GMT<![CDATA[Reply to UIFlow 1.7.3 on Tue, 23 Mar 2021 18:25:26 GMT]]>Hello,
I have same issue with MQTT using Core and Stick in UIFlow 1.7.3. In Core, I downgraded firmware to V1.4.5 and work, but i cant do same configuration with Stick.

]]>https://community.m5stack.com/post/13212https://community.m5stack.com/post/13212Tue, 23 Mar 2021 18:25:26 GMT<![CDATA[Reply to UIFlow 1.7.3 on Sat, 20 Mar 2021 22:00:02 GMT]]>@fonix232 said in UIFlow 1.7.3:

A kinda related, but strange question - could you please release the source code for the drivers of the various bits of hardware found in the UIFlow firmware? UIFlow is built upon MicroPython, and I would personally prefer to run a clean MicroPython build on a few devices of mine, however the lack of drivers makes it a bit harder than expected. I'm not interested in the UIFlow-related parts, just the low level Core/Unit/Module support drivers (e.g. for M5Paper, a driver for IT8951, a driver for the PMIC, SHT30, GT911). It would allow the community to build MicroPython images without proprietary code, and possibly result in faster updates as well. Plus, you could merge back community fixes into the official UIFlow firmware easily.

Hello,
Same thing for me.
But I like uiFlow tool to test the code.
For example, Update the UIFlow-code project on git with core2 libs would be cool
Best reguards

]]>https://community.m5stack.com/post/13164https://community.m5stack.com/post/13164Sat, 20 Mar 2021 22:00:02 GMT<![CDATA[Reply to UIFlow 1.7.3 on Sat, 20 Mar 2021 14:45:02 GMT]]>So Now it works ( Had a permission issue on AWS) however I have an issue with the AWS blocks.
@IAMLIUBO return topic doesn't return the topic and there is no return topic payload block.

]]>https://community.m5stack.com/post/13160https://community.m5stack.com/post/13160Sat, 20 Mar 2021 14:45:02 GMT<![CDATA[Reply to UIFlow 1.7.3 on Sat, 20 Mar 2021 06:38:04 GMT]]>@sparkgene I solved the AWS not defined issue as it was due to incorrect placement of the Start block.

I'm just back to the "Cannot create thread" error and completely lost.

]]>https://community.m5stack.com/post/13156https://community.m5stack.com/post/13156Sat, 20 Mar 2021 06:38:04 GMT<![CDATA[Reply to UIFlow 1.7.3 on Sat, 20 Mar 2021 01:11:32 GMT]]>@ajb2k3 I'm not sure, but first it was blue. The latest is yellow(orange?) on my screen too. BTW Try to use the latest uiflow image v1.7.3.1. The error "aws isn't defined" will be fixed.

]]>https://community.m5stack.com/post/13153https://community.m5stack.com/post/13153Sat, 20 Mar 2021 01:11:32 GMT<![CDATA[Reply to UIFlow 1.7.3 on Fri, 19 Mar 2021 16:56:39 GMT]]>@sparkgene @IAMLIUBO Why is the AWS blocks greenyblue in those pictures but yellow on my screen?

]]>https://community.m5stack.com/post/13138https://community.m5stack.com/post/13138Fri, 19 Mar 2021 16:56:39 GMT<![CDATA[Reply to UIFlow 1.7.3 on Fri, 19 Mar 2021 11:38:39 GMT]]>@iamliubo I'm glad to here that you're going to work on the PaHub problem. I think that is important for the user community to know that there is someone looking at issues and working for fix them. It may takes time to fix an issue but if I know that someone in M5Stack is working on it I'm happy and I can wait.

]]>https://community.m5stack.com/post/13132https://community.m5stack.com/post/13132Fri, 19 Mar 2021 11:38:39 GMT<![CDATA[Reply to UIFlow 1.7.3 on Fri, 19 Mar 2021 09:05:36 GMT]]>@iamliubo I didn't recognize that. Thanks. It's working now on 1.7.3.1

]]>https://community.m5stack.com/post/13129https://community.m5stack.com/post/13129Fri, 19 Mar 2021 09:05:36 GMT<![CDATA[Reply to UIFlow 1.7.3 on Fri, 19 Mar 2021 08:51:50 GMT]]>@ajb2k3 Yes. I can publish and subscribe with same setting when I use AWS IoT SDK.

]]>https://community.m5stack.com/post/13127https://community.m5stack.com/post/13127Fri, 19 Mar 2021 08:51:50 GMT<![CDATA[Reply to UIFlow 1.7.3 on Fri, 19 Mar 2021 06:30:48 GMT]]>@iamliubo

I'm getting the error "aws isn't defined"

]]>https://community.m5stack.com/post/13126https://community.m5stack.com/post/13126Fri, 19 Mar 2021 06:30:48 GMT<![CDATA[Reply to UIFlow 1.7.3 on Fri, 19 Mar 2021 03:18:41 GMT]]>Hi @thrasher ,
Maybe one day we will open source. :)

]]>https://community.m5stack.com/post/13119https://community.m5stack.com/post/13119Fri, 19 Mar 2021 03:18:41 GMT<![CDATA[Reply to UIFlow 1.7.3 on Fri, 19 Mar 2021 03:16:05 GMT]]>Hi @sparkgene ,
Just missed AWS Start block.

]]>https://community.m5stack.com/post/13118https://community.m5stack.com/post/13118Fri, 19 Mar 2021 03:16:05 GMT<![CDATA[Reply to UIFlow 1.7.3 on Thu, 18 Mar 2021 18:44:36 GMT]]>@iamliubo M5Stack isn't open source and never will be. They will never disclose their micropy libraries (well, not even documentation).
All questions here about it are taboo and will be left unreplyed. Best solution is to use UIFlow blocks if u want to prototype something. Otherwise its better to switch to another hardware. However, I love build quality and designs.

]]>https://community.m5stack.com/post/13106https://community.m5stack.com/post/13106Thu, 18 Mar 2021 18:44:36 GMT<![CDATA[Reply to UIFlow 1.7.3 on Thu, 18 Mar 2021 17:17:14 GMT]]>@sparkgene said in UIFlow 1.7.3:

@m5stack Great Update!

I try AWS blocks on 1.7.3. In this version subscription don't work(MQTT connect and publish is fine)

Then I try 1.7.3.1. This version don't connect to AWS IoT Core.

0_1616029894713_m5stack-uiflow-error.png

Is there a way to see the device log?

Have you made sure AWS is set up properly?

]]>https://community.m5stack.com/post/13104https://community.m5stack.com/post/13104Thu, 18 Mar 2021 17:17:14 GMT<![CDATA[Reply to UIFlow 1.7.3 on Thu, 18 Mar 2021 02:51:37 GMT]]>Hi @fonix232 @ajb2k3 @robalstona @Arno @felmue @weezer @Thrasher @Peter ,
Sorry to everyone, today I will deal with the PAHUB problem, please forgive me for not solving it for a long time.
Regarding the open source requirements you mentioned, I can't make a decision at present, please understand.

]]>https://community.m5stack.com/post/13085https://community.m5stack.com/post/13085Thu, 18 Mar 2021 02:51:37 GMT<![CDATA[Reply to UIFlow 1.7.3 on Thu, 18 Mar 2021 01:13:15 GMT]]>@m5stack Great Update!

I try AWS blocks on 1.7.3. In this version subscription don't work(MQTT connect and publish is fine)

Then I try 1.7.3.1. This version don't connect to AWS IoT Core.

0_1616029894713_m5stack-uiflow-error.png

Is there a way to see the device log?

]]>https://community.m5stack.com/post/13100https://community.m5stack.com/post/13100Thu, 18 Mar 2021 01:13:15 GMT<![CDATA[Reply to UIFlow 1.7.3 on Wed, 17 Mar 2021 21:12:37 GMT]]>Hello @Arno

I only have an ENV and Ameter unit and I can use them together just fine with the Pa.HUB and M5Core2.

  • Do the units work ok, when used w/o Pa.HUB?
  • Does a single unit work on all ports of the Pa.HUB?
  • Are you sure you have your units connected to the correct ports?
  • Did you try to reset M5Core2 in case some previous code is running?

If it's only some units that fail I am afraid I cannot help as I don't have any other units to test with. Sorry.

Thanks
Felix

]]>https://community.m5stack.com/post/13080https://community.m5stack.com/post/13080Wed, 17 Mar 2021 21:12:37 GMT<![CDATA[Reply to UIFlow 1.7.3 on Wed, 17 Mar 2021 18:33:48 GMT]]>Just by adding the PaHUB + ultrasound + Joystick units without any line of code, I have an Ultrasonic unit maybe not connect error.
It's the same with other I2C units

0_1616005925603_6d24ce61-d397-43a3-9088-7b79d33ed7f6-image.png

0_1616005750021_4f18a371-0bcc-4361-9482-122db643e218-image.png
0_1616005954120_625ba321-1ef8-4b93-b823-a592b90a3e18-image.png
0_1616005975205_fb7d8ae1-0a5c-4c33-9357-e543dbe08f0a-image.png
0_1616006010848_39b058a7-478e-4c57-89b5-b4c99780f945-image.png

]]>https://community.m5stack.com/post/13079https://community.m5stack.com/post/13079Wed, 17 Mar 2021 18:33:48 GMT<![CDATA[Reply to UIFlow 1.7.3 on Wed, 17 Mar 2021 17:40:26 GMT]]>Hello @Arno

I think set pos X open is the wrong command. According to the help text it only opens one position and closes all others. Try set pos X state open instead.

Thanks
Felix

]]>https://community.m5stack.com/post/13076https://community.m5stack.com/post/13076Wed, 17 Mar 2021 17:40:26 GMT<![CDATA[Reply to UIFlow 1.7.3 on Wed, 17 Mar 2021 17:35:25 GMT]]>Hello @Peter

I'd love to. Unfortunately I am just a user like you w/o access to UIFlow source code.

Hopefully M5Stack engineers will look into that soon.

Thanks
Felix

P.S. As a work-a-round in the Python tab you can modify the line for the unit connected to Pa.HUB manually. Not ideal but this works for me.
E.g. from

AMeter0 = unit.get(unit.AMETER, unit.PORTA)

to

AMeter0 = unit.get(unit.AMETER, unit.PAHUB0)
]]>https://community.m5stack.com/post/13075https://community.m5stack.com/post/13075Wed, 17 Mar 2021 17:35:25 GMT<![CDATA[Reply to UIFlow 1.7.3 on Wed, 17 Mar 2021 17:29:26 GMT]]>@felmue False joy ! the PaHUB is now recognized by CORE2 with 1.7.3.1.
But only the first connected I2C module works, if you connect another I2C module it is in error. Tests carried out with Ultrasound, TOH amp, Joystick modules ... whatever I2C module you connect to in PAHUB0 is working, all the other ports are in error with message: Joystick unit maybe not connect or Ultrasound nit maybe not connect.

![0_1616000524477_P1110077.JPG](Uploading 100%)

0_1616000567828_2014d066-d5fe-4d48-a0e9-7356aff93071-image.png

]]>https://community.m5stack.com/post/13074https://community.m5stack.com/post/13074Wed, 17 Mar 2021 17:29:26 GMT