Alex
Alex
Thanks for the quick Reply! I already removed them and Im still unable to connect, I added screenshots of my configuration. I omnitted the endpoint.   
Im sorry for my French but HOLY SHIT, that was it. Thank you very much was stuck for so Long there!
@binaryPUNCH Glad, it could help you! @thomasnordquist A bit late reply, but we used it to compare the workflow with our new WiFi chip, using mqttexplorer we discovered some errors...
Wow how time flies by, I have to apologies. I wanted to make some documentation, but a lot has happened since back then. So I did not have any time...
Hey, from the first overview it looks correct. Please try: 1) connecting without any topic subscription 2) if 1) successful use one random topic without any $ prefix Personally whenever...
Mhm, I think this might be an AWS Policy issue. Pls check the Policy attached to the Thing X Certificates. Try giving it this one: { "Version": "2012-10-17", "Statement": [...