It feels random because of .. first try line 162, second try line 198, third try line 67 and finally it´s working without an issue .. and I don´t change anything in the meantime.
@mchott the line error doesn’t always report the correct line unless you know how to read it. I recently found a syntax error due to quote mark formatting
In case someone else runs across this. I had a very similar issue with the Atom S3 Lite not working with the PWM Kit. There is a voltage select 0ohm resister link for the PWM driver. It's labeled 5v and 3v3 just above header pin 21. As shipped the 3v3 is bridged to the center pin. This powers the PWM driver chip off the 3.3v pin of the atomS3. This causes lockups and very intermittent wifi. I removed the resister and bridged 5v to the center pin. All issues went away and everything works normally.
Surprise ... in the old UI flow 1 it is exactly as I had hoped. You add the unit and can then build something directly with it. This shows that some new components are better supported in the old UI flow than in the new UI flow 2.
It's okay for me and my current requirements, but it doesn't give me a good feeling. Which platform should I rely on now if everything is poorly documented and randomly supported?
Yes this works .. its in the tab "Privacy and Security" and there I had to switch from "Appstore and verified developer" to "Appstore" and then open the M5Burner again and confirm "Still open". Now it works on every start.
@mchott Speaking personally, I would have the Master also arbitrate the Slaves by polling them one at a time. Yes, they can all talk at once but it's messy. I have a Master talking to two Slaves ESP-NOW peer to peer with small size of data and no urgency in the process. I may send a simple boolean flag to one to turn on a heater, next sending a int value to the other to set a servo position. (this one also returns a float with the Vent Temp.
I don't think the PbHUB will work ... The PbHUB can only handle analog and digital signals (no clocks !). Reading values from the HX711 weight sensor needs a clock and a data line provided by the ESP32 GPIO Ports ... The UIFlow HX711 library only supports Port B.
If you want to use several weight sensors on the M5Stack you will have to hook them up to different ports and do the programming either in Python or Arduino using the Expansion Port Module getting the additonal Ports C D and E.
P.S: If you want to hook up multiple Weight Sensors to a M5Stack using port A you have to use HX711 devices which can be hooked up to the I2C bus. M5Stack has no such modules nor units, but you will find one made from DFRobot (https://wiki.dfrobot.com/HX711_Weight_Sensor_Kit_SKU_KIT0176). This sensor also has a grove I2C port and by modifying the I2C addresses you can hook up to 4 Weigh sensors to Port A. Using the PaHub I2C-extender you can even hook up 6 to 24 Weigh sensors ......