10514 questions

12522 answers


22051 members

0 votes
125 views 1 comments

When I connect the mqtt publisher to aws iot core, I always get a subscribe failure on router/get. I am on the latest firmware. Interestingly I can get the bridge to subscribe to iot core successfully but that isn't what I want. Cloudwatch logs show this failure:

{ "timestamp": "2022-02-25 17:04:18.296", "logLevel": "ERROR", "accountId": "866312087341", "status": "Failure", "eventType": "Subscribe", "protocol": "MQTT", "topicName": "router/get", "sourcePort": 58253 }

Any help would be much appreciated.

2 Answers

0 votes
I can confirm that AWS doesn't support QOS of 2 which is what the publisher uses
Best answer
0 votes

Regarding this issue of yours may I know what type of authentication are you using? Username password or something else.

You can refer to this document file for reference regarding MQTT Publisher : https://mega.nz/file/KnBU1BjL#jESBf_BUDbuSFUMfXP2DyoT-ZUkgJC0d2v615wZqbDc

I hope this helps

Thanks for the reply Jerome. I'm just using TLS with the CA, private key and certificate files generated by AWS. I have talked with AWS and they think the subscribe failure is because the RUT955 is trying to use QOS 2 which is not compatible. I can get the bridge to connect successfully with a QOS of 1 or 2 which would make sense.

Is it possible to connect the publisher to the local Broker and then use the bridge to forward the events to AWS?