Hi, Have you considered a normal socket connection, and simply AES encrypting your data during transmission? You should be able to smash a checksum of the encrypted message down to like 4 bytes, and then include a delimiter sequence to snip the checksum off the datagram. You can use SSL to fetch the initial AES key from your backend, and then use that key in the future over normal network sockets. Sure, you might get MITM, but who cares, if the messages are encrypted and checksummed. Can't help with the AWS stuff, we just push messages to our own backend servers directly.

... forgot duplicate CLIENT_ID in config.py... Problem solved!

I have the same problem using this library or simple mqtt in another thread with version (1.18/1.19 Pybytes) rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:1 load:0x3fff8028,len:8 load:0x3fff8030,len:1984 load:0x4009fa00,len:0 load:0x4009fa00,len:19112 entry 0x400a05e4 Initializing filesystem as FatFS! Guru Meditation Error: Core 0 panic'ed (Cache disabled but cached memory region accessed) Core 0 register dump: PC : 0x401f27e8 PS : 0x00060c34 A0 : 0x8005582c A1 : 0x3ffc0970 A2 : 0x00000000 A3 : 0x00000001 A4 : 0x800995d1 A5 : 0x3ffea5f0 A6 : 0x0000b030 A7 : 0x3ffea6a4 A8 : 0x8008cc86 A9 : 0x01000000 A10 : 0x07040000 A11 : 0x00000000 A12 : 0x00000013 A13 : 0x00000000 A14 : 0x3ffae270 A15 : 0x00000000 SAR : 0x0000000e EXCCAUSE: 0x00000007 EXCVADDR: 0x00000000 LBEG : 0x40099276 LEND : 0x40099285 LCOUNT : 0x00000000 Core 0 was running in ISR context: EPC1 : 0x40092e5f EPC2 : 0x00000000 EPC3 : 0x00000000 EPC4 : 0x401f27e8 with the old version (1.17.3.b1 or 1.18.0) the error was different but there was. Connecting to MQTT broker.... 1 2 3 4 ***ERROR*** A stack overflow in task MPThread has been detected. abort() was called at PC 0x4008e66c on core 1 the mqtt library is: https://github.com/yutter/micropython-mqtt Furthermore after updating to the 1.18.0 or 1.19.4.b4 to try to understand if the problem related to the threads and mqtt had been solved I had another problem, I can not load some files ... example of what happens that did not happen before; I added the size of the files in which I have problems Reading file status Failed to read project status, uploading all files Creating dir lib Creating dir www Creating dir www/bootstrap Creating dir www/bootstrap/css Creating dir www/bootstrap/fonts Creating dir www/bootstrap/js Creating dir www/js [1/18] Writing file SI7006A20.py [2/18] Writing file boot.py [3/18] Writing file hal.py [4/18] Writing file lib/mqttserver.pub.pem [5/18] Writing file main.py [6/18] Writing file mqtt.py [7/18] Writing file umqtt.py [8/18] Writing file www/bootstrap/css/bootstrap.min.css "filesize (121.3kb)" Failed to write file, trying again... Failed to write file, trying again... Filecheck failed [9/18] Writing file www/bootstrap/js/bootstrap.min.js "filesize (36.9kb)" Failed to write file, trying again... [10/18] Writing file www/index.html [11/18] Writing file www/js/angular.min.js "filesize (99.0kb)" Failed to write file, trying again... Failed to write file, trying again... Filecheck failed [12/18] Writing file www/js/app.js [13/18] Writing file www/js/jquery-1.11.1.js "filesize (282.8kb)" Failed to write file, trying again... Failed to write file, trying again... Filecheck failed [14/18] Writing file xApp.py Failed to write file, trying again... [15/18] Writing file xConfigureFile.py [16/18] Writing file xHTTPConfigure.py [17/18] Writing file xWebServer.py [18/18] Writing file xWebSocket.py why? waiting for a quick reply best regards Giacomo

Hey @timh , I have mentioned about the sensor, I am going to use for monitoring and I want to use cellular service, as wifi connection is not available here so not sure about which hardware will be better to use and if I try with GPY then need to know the better way to connect the Private network with GPY which help readings of sensor on AWS cloud And I am new comer to this area so please suggest the tools of AWS cloud which I should use to make this monitoring process display on my smart phone.

@inverseeffect Did you ever get any resolution on the keepalive timer? I'm running into the same issue. For now I've switched to simple.py, but I would much rather use the AWS library.

Hello, I bumped on this very same issue when executing the below (partial) code. The socket create error -8576 showed up upon every attempt of executing the loop: while not pycomAwsMQTTClient.connect(): print("Waiting for AWS...") time.sleep(10) print('AWS connection succeeded!') Have found that the problem was on the root CA certificate. Just to recap, AWS "setup.py" file expects to work with three certificates as follows: AWS_ROOT_CA = "/flash/cert/root-CA.crt" AWS_CLIENT_CERT = "/flash/cert/thing.cert.pem" AWS_PRIVATE_KEY = "/flash/cert/thing.private.key" For some reason the root certificate was not created correctly upon instructions from AWS tutorials. To fix that, run the below command line on a Linux Terminal to download it again: curl https://www.amazontrust.com/repository/AmazonRootCA1.pem > root-CA.crt By doing so, my issue was fixed.

Hi Did you find out about this? I where also able to connect and send a message to the AWS IoT platform. Then I got a similer error where it continiously report "Socket receive error: -80", but no "Socket send error [Errno 104] ECONNRESET" message.

@jonnyboy said in SiPy -> AWS Device Example - CA file not found: CA file not found Can you try formatting the file system and re-uploading the files again, you can do this by running the following from the REPL: import os os.mkfs('/flash') It could be the the file system has become corrupt, it might be worth trying to upload the files via USB if at all possible.

@sunrise17 you must modify esp_get_revision - i do not have guide but on the forum you can find such posted by @robert-hh https://forum.pycom.io/post/13828

Hello, i am trying very hard to subscribe to a topic and actually receive something. I am using the integrated client on the AWS side to debug. i am observing that i am successful when it comes to publishing topics. It works well. If i subscribe to a topic i just do not receive anything at all. I have tried with both simple and the guide in the pycom documentation. I suspect at this point a misconfiguration from the side of AWS. I have permission in my policy to subscribe to any resource. Subscription itself works. No messages are ever displayed though. Callback is never called. any help is appreciated!

@matt3526 DID anyone figure this out?