@felmue there is also a king running issue with the ENV III unit
-
RE: [CoreS3] I2C doesn't work...
-
StickC (Not Plus) reports RoverC not connected.
StickC (Not Plus) reports RoverC not connected.
-
RE: UIflow2 ATOMS3 WIFI timeout when ENV3 attached to port A
Look in the Discussion about the ENV III and the Core S3
-
RE: ENV III Causes CoreS3 to restart.
I’ve reported it to M5STACK and they are looking into it
-
Basic guide to using the #M5Stack ENV IV in UIFLow
Basic guide to using the #M5Stack ENV IV in UIFLow
https://youtu.be/f2dxN4hG_rI?si=zcSdBrfsIIX1HZWg -
Basic Guide to to #M5Stack ENV IV with UIFlow 2
Basic Guide to to #M5Stack ENV IV with UIFlow 2
https://youtu.be/xKzHqtA98nc?si=2TDDZprJ_ywdnnSU -
RE: m5tough UIFlow2.0 Alpha 24. mqtt. first-timer needs some guidance
You need two devices, one set as AP and one as STA for it to work.
What error are you getting when set to STA?