@chr1g1 said in Atom Matrix with FW 1.13.1 not connecting to AWS:
added it as directed above. Still weird behaviour of the Atom Matrix on FW 1.13.2.
Here is the log:
I print out "submitted to aws" after the publish block in the loop.
APIKEY: xxx
submitted to aws
[17797] MQTTException -> 128
reconnect start ...
reconnect finish ...
submitted to aws
submitted to aws
submitted to aws
submitted to aws
submitted to aws
Well there is an improvement as you are no longer getting the [24577] MQTTException -> [Errno 9] EBADF
Which means the Atom is now working
Error 128 means that it tried to subscribe to the AWS topic before the connection was made.
If you make a subscribe and a call, according to your log it should be present.
add a 5 second delay after the AWS start.