UIFlow 1.7.3

[Peter]

@felmue
Please include the use of the PaHUB in the next release of the M5Stick C/plus and ATOM.
Peter

[Arno]

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


[felmue]

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)

[felmue]

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

[Arno]

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

[felmue]

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

[sparkgene]

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

Is there a way to see the device log?

[IAMLIUBO]

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.

[ajb2k3]

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

Is there a way to see the device log?

Have you made sure AWS is set up properly?

[Thrasher]

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

[IAMLIUBO]

Hi @sparkgene ,
Just missed AWS Start block.

[IAMLIUBO]

Hi @thrasher ,
Maybe one day we will open source. :)

[ajb2k3]

@iamliubo

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

[sparkgene]

@ajb2k3 Yes. I can publish and subscribe with same setting when I use AWS IoT SDK.

[sparkgene]

@iamliubo I didn't recognize that. Thanks. It's working now on 1.7.3.1

[Dario]

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

[ajb2k3]

@sparkgene @IAMLIUBO Why is the AWS blocks greenyblue in those pictures but yellow on my screen?

[sparkgene]

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

[ajb2k3]

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

[ajb2k3]

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.