@sistar_hh said in Certificate based MQTT (AWS IoT) trouble with changed umqtt:

Hi,
unfortunately the micropython certificate handling for MQTT has been changed last year. good description
Here is the new way to do it:

Create an SSL context context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT) context.verify_mode = ssl.CERT_REQUIRED # Load certificates context.load_verify_locations(cafile='/flash/certificate/ca.der') context.load_cert_chain('/flash/certificate/cert.der', '/flash/certificate/key.der') mqtt = MQTTClient(client_id=client, server=endpoint, port=8883, keepalive=1200, ssl=context) print("Connecting to AWS IoT...") mqtt.connect() print("Done")

While the code and certificates work fine on ESP32-S3 Micropython they result in the following error on uiflow2

Traceback (most recent call last):
File "<stdin>", line 74, in <module>
File "<stdin>", line 52, in mqtt_connect
File "/flash/libs/umqttn/simple.py", line 69, in connect
File "ssl.py", line 1, in wrap_socket
ValueError:
The certificate validity has expired
I triple checked the certificate validity..
Next suspect would be an incorrect system time. Therfore I set the time as follows before attempting to initialize a mqtt connection:

sta_if = network.WLAN(network.STA_IF)
sta_if.active(True)
if sta_if.isconnected():
sta_if.disconnect()
sta_if.connect(wifi_ssid, wifi_password)
while not sta_if.isconnected():
utime.sleep(1)
print("Connecting...")
print("Connected:", sta_if.ifconfig())

print(f"time before NTP settime {time.localtime()}")
ntptime.settime()
print(f"time after NTP settime {time.localtime()}")
import machine
rtc = machine.RTC()

Set manually to a known correct UTC date/time: (year, month, day, weekday, hour, minute, second, microsecond)

rtc.datetime((2025, 3, 14, 1, 14, 0, 0, 0))
print("Manually set time:", machine.RTC().datetime())
Still I get the same error:

Connecting...
Connecting...
Connecting...
Connecting...
Connected: ('192.168.5.0', '255.255.252.0', '192.168.4.1', '192.168.4.1')
time before NTP settime (2025, 3, 14, 12, 8, 44, 5, 72)
time after NTP settime (2025, 3, 14, 12, 8, 45, 5, 72)
Manually set time: (2025, 3, 14, 5, 14, 0, 0, 67)
Connecting to AWS IoT...
MQTT Connection failed:
The certificate validity has expired

Traceback (most recent call last):
File "<stdin>", line 79, in <module>
File "<stdin>", line 57, in mqtt_connect
File "/flash/libs/umqttn/simple.py", line 69, in connect
File "ssl.py", line 1, in wrap_socket
ValueError:
The certificate validity has expired
I used the micropython/umqtt.simple/umqtt/simple.py implementation installed as module umqttn in the /flash/libs folder. It differs from the m5stack implementation (which is currently broken for certificate based MQTT due to the described changes in Micropython).

At this point I wonder why the same code (umqtt.simple, demo-code, exactly the same certificate files) work on an UMFeatherS2 MicroPython v1.24.1 but fail on MicroPython v1.24.0-dirty on 2025-03-06; M5STACK CoreS3 with ESP32S3.

I would happy for any hint on how to solve this.

Aha! When trying the following change:
context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)
context.verify_mode = ssl.CERT_OPTIONAL # Instead of CERT_REQUIRED
I successfully connected!

@DarshanAtwal As long as you know how to program in micropython You can still use programs like Thonny to program directly.

@DarshanAtwal Use the latest version of UIFlow2 is its just a graphical front ent to Micropython.
There is a console mode in UIFlow2 to directly access the Micropython or you can use a program to directly access Micropython.

I can be more specific.

When I "Download" from UI Flow 2 to the device, it works:

Press BtnA to switch on.
Press BtnA to switch off, once my program allows, with custom MPY:

hold_pin = Pin(46, Pin.OUT) hold_pin.value(0)

But a problem is if I LONG press (6 secs) BtnA, the device FULLY resets. It goes to the QR code and device Mac screen. That menu crashes almost immediately, meaning I can't rotate the dial to run my Python script. The only way to get it back working is to redownload from UI Flow 2?

Is there a way to turn off that long-press reset function? Or to stop the QR code menu from crashing, so I can at least run my program?

These details about long press BtnA or the reset button on the back don't seem to be covered by the main reference, https://docs.m5stack.com/en/core/M5Dial

Hi @xPalter
Have you tried XPowersLib? I think you can post an issue to the author to update AXP2102
https://github.com/lewisxhe/XPowersLib

@Russ

I had version 1.14 from you at the time
https://github.com/russhughes/ili9342c_mpy

which worked great for me for years on the M5Stack Core2.
But now there is a new version of Core2 version 1.1

Unfortunately, this version no longer runs with your version 1.14.
Is there a way to make the 1.14 version work with the new firmware 1.1?

The differences between Core2 and Core2 v1.1 are as follows:
1.The power management scheme is iterated from Core2(AXP192) to Core2 v1.1(AXP2101+INA3221). The ID of AXP192 and AXP2101 is different, and the program uses this as a sign to distinguish the versions;
2.The power indicator is changed from green to blue;
3.Add RTC chip power supply battery to ensure accurate timing when power is off.

@mehulge stuck with same issue, did you ever found the fix?

@JDZAWODNIAK not at present as I haven’t had time to work on a project.

@ajb2k3 I can only find this one for M5Stack products:-

https://micropython.org/download/?vendor=M5 Stack

@madsrassmussen Yes, I noticed this odd behavior starting in 2.0.3 and it seems to be a different odd in 2.0.4, but neither work as expected.

When letting the web terminal do the upload, the named file under 'apps' is zero bytes and the file contents end up in 'main.py'

In 2.0.3 I could download main.py to my PC, rename it, and use web terminal file manager to upload it into the apps folder, and all was well.

In 2.0.4 however, it almost seems like the device 'My Apps' menu/list is unaware of this file, even though it is listed. When selected the device runs the .py file listed after the one I selected instead.

I've also had the variable undefined errors but I think that is a different issue. Maybe not?
One example is copy/pasting the mpy code to a windows computer into say notepad.
The device requires unix style line endings, not windows line endings. It also requires no blank lines to exist.
(This is why I would copy the existing 'main.py', as it was already formatted correctly.)

Otherwise, most times the upload just doesn't work at all. I too have not found a pattern or submitted a bug report due to this lack of info. I wasn't even sure it wasn't just me :)
Hopefully someone more knowledgeable can chime in