I think I do not have any cert problems, see. I found an MQTT provider and they dont require certs. only username and pass are enough https://console.hivemq.cloud/
But even this one doesn’t work, I tried mqtt and TCP, no of them works.
AT+KMQTTCFG=1,1,“xxxxxx.s1.eu.hivemq.cloud”,8883,4,“BX3101”,30,1,1,“home/LWTMessage”,“BX3101offline”,0,1,“username”,“pass”
+KMQTTCNX: 2
+CME ERROR: 907
+KMQTT_IND: 2,0
How did you test with tcp on this server
AT+KTCPCFG=1,0,“broker.hivemq.com”,1883,0,0
here is the public mqtt server, they provide, I tried this command but no chance,
you are using pure TCP client to test this server, right?
What is the result?
What do you mean exactly by “pure TCP client”? can you elaborate on it?
AT+KTCPCFG=1,0,“broker.hivemq.com”,1883,0,0
OK
AT+KTCPCNX=1
+KTCP_IND: 1,1
+KTCP_NOTIF: 1,4
That means not ssl socket
I sorted out the issue :
here is the issue:
it seems None of the default chipper suit config is suitable to get mqtt connection. To have it I needed to set a custom cipher suit with different Authentication. I set the 3 — Mutual authentication and then worked for me.
this is the complete config for me:
AT+KSSLCRYPTO=0,8,1,8192,4,4,3,0
Do you have any comment @jyijyi on this, if not, I am going to close out this issue.
It is good that it works for you.
no, i don’t have further comment