Hello @travisstdenis
have you tried to connect to test.mosquitto.org? Does that work or are you getting the same error?
Thanks
Felix
Hello @travisstdenis
have you tried to connect to test.mosquitto.org? Does that work or are you getting the same error?
Thanks
Felix
Hello @YigalB
yes, the I2C address is stored in flash. There is no need to repeat that step (changing I2C address) after every power up. It just needs to be done once.
Alternatively you can use a PaHub like @teastain suggested.
Thanks
Felix
Hello @Coopersmith-24601
glad to hear that the RGB example helped.
The four pogo pins are GND, 5V, SDA and SCL. E.g. power and I2C. See top right corner of schematic - Socket_Power_4P.
Firmware download uses a serial connection and not I2C. In other words the M5GO/FIRE Battery Bottom Charging Base can only be used to charge the battery.
Edit: I just confirmed by opening it: only GND and 5 V are connected at the USB-C port.
How do you know the battery isn't getting charged? Isn't there a red (or green) light?
Thanks
Felix
Hello @Coopersmith-24601
Re charging: the M5GO3 has its own charger IC built-in. A red LED indicates charging and when the battery is full the green LED in M5GO3 lights up. The built-in charger IC cannot be queried by software; is that what you mean by 'data'?
Re RGB: please find an example in the UIFlow2 Project Zone: M5CoreS3_M5G03Bottom_RGB_UIFlow2.1.3
Thanks
Felix
Hello @aitech
have you double-checked that port A actually has power? You'll need a multimeter for that and measure between black (GND) and red (5 V) wires.
Thanks
Felix
Hello @aitech
did you adjust SDA and SCL accordingly? The example is for M5Core which uses different GPIOs on port A (red) than M5CoreS3.
Try changing this line:
Wire.begin(21, 22);
to
Wire.begin(2, 1);
You can also try the I2C scanner (internal and port A) from here.
Thanks
Felix
Hello @IAMLIUBO
thank you for confirming, much appreciated.
In the past I worked on projects which had similar restrictions - for various reasons some parts had to stay close - so I fully understand.
BTW: no need to be sorry. I am very glad most of UIFlow2 firmware is open source, so thank you for that.
Thanks
Felix
Hello @ajb2k3
I doubt it. M5Things has been introduced over a year ago with this commit as far as I can tell.
Also M5Things is available (and used to contact M5Stack backend) when firmware is installed from M5Burner.
BTW: It is also used to display the user avatar etc. on the screen, which I believe you worked on.
Thanks
Felix
Hello @rodrigob
I did some research as well and I cannot find where M5Things is implemented. I also tried released firmware from github - see here - and it also fails to connect via WiFi to the M5Stack backend.
Everywhere M5Things is used it's enclosed by a try / except statement which clearly indicates that it is anticipated that in some cases M5Things might not be available.
Another observation is that this time M5Burner already offered UIFlow firmware v2.1.3 while the github repository still showed v2.1.2 being the latest.
All that makes me wonder about whether firmware for M5Burner is actually being built with additional source files - containing the missing M5Things - but which are hosted somewhere else and are not available to the public.
Thanks
Felix
Hi guys
@ajb2k3 : Groove2Groove 5 V line is not connected between the white and black Groove connector by default as R1 isn't populated (at least not in my unit). See schematic here.
@l-roca : the wiring goes as follows:
ext. 5 V Groove2Groove FAN
5 V (red) ---> 5 V 5 V ---> (red) 5 V
GND (black) ---> GND GND ---> (black) GND
GND 5 V D.IN
(black)(red)(yellow)
^ ^ ^
| | |
| | |
M5Dial (Port B)
You can find the UIFlow2 example in the Project Zone: M5Dial_Grove2Grove_Test_UIFlow2.1.3
Thanks
Felix
Hello @PascalS
at least we know now that the hardware is ok.
Apart from that I am stumped. Sorry.
Thanks
Felix
Hello @PascalS
hmm, that is really strange. Do you have any other hat to try if the hat port works for you in general?
ENV III hat is supported in UIFlow2. Maybe try with UIFlow2? Just to see if it works that way.
Thanks
Felix
Hi guys
KmeterISO unit is available in UIFlow2.1.2. Does it not work? (Note: I don't have that unit so I cannot test.)
If you want to run an I2C scan (internal and on port A) check out my example in the UIFlow2 Project Zone: M5Core2_I2CScan_Intern_PortA_UIFlow2.1.2
Thanks
Felix
Hello @PascalS
hmm, have you tried to power cycle M5StickCPlus2?
Thanks
Felix
P.S. if that doesn't make the HAT show up in the I2C scan or make it work with the original program then I am afraid that yes, there might be a hardware issue.
Hello @cocoa
if you want to use NB-IoT mode I found you'll need to un-comment the define in TinyGsmClientSIM7028.h
line 32 as well.
#define MODE_NB_IOT //Comment this macro definition when using CAT mode
BTW: CAT mode (e.g. not NB-IoT mode) works for me too.
Thanks
Felix
Hello @PascalS
from your first log I think the ENV III Hat was recognized properly else the log would have ended with either of the "Couldn't find ...".
Anyways, please find an I2C scanner for internal, Groove and Hat here.
Thanks
Felix
the only difference between Hat and Unit (apart from the different GPIOs it uses as @ajb2k3 pointed out) is that the Hat is powered by 3.3 V from M5StickCPlus2 whereas the Unit is powerd by 5 V (with an internal DC/DC converter).
I used the M5Unit-ENV library, copied the code you posted and manually wired the Unit to the Hat port. In other word I used exactly the code you posted without any modifications.
Sorry, at this point I have not more ideas as to why it wouldn't work on your side.
Thanks
Felix
Hello @PascalS
hmm, your code works for me.
Note: I don't have an ENV III hat, but I have the ENV III unit which I used to simulate ENV III hat. So it could be something subtle between the two making it work for me.
That said, I suggest you first try with the ENV III example alone and if that still doesn't work try to only init and read either qmp or sht3x and see how that goes.
Thanks
Felix
Hello @frank_b
please find an explanation here. (It's for M5CoreInk, but I think the same thing is happening here.)
Thanks
Felix