Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Recommended Posts

Posted

Hi there,

 

I need to connect to AWS MQTT server with tls 1.2 and need to put 3 certificate files, but MQTT always return error code "1".

Here is my code:

 

Please login or register to see this code.

 

My questions are:

  1. AWS wants me to use 3 keys to connect MQTT, basically I should use contents of AmazonRootCA1.pem, private.pem.key and certificate.pem.crt key files, but in tls.options I can see only clientCertificate and certificateAuthority, that made me confused.
  2. When I connect to MQTT with mqtts, I got only error code "1". If code 1 meads " incorrect protocol version", what is the version  of TLS version in QuickAPP Lua?

 

Is any one have same issue?

 

 

 

 

Posted
10 hours ago, xrdandy said:

My questions are:

  1. AWS wants me to use 3 keys to connect MQTT, basically I should use contents of AmazonRootCA1.pem, private.pem.key and certificate.pem.crt key files, but in tls.options I can see only clientCertificate and certificateAuthority, that made me confused.
  2. When I connect to MQTT with mqtts, I got only error code "1". If code 1 meads " incorrect protocol version", what is the version  of TLS version in QuickAPP Lua?

 

afaik tls options does not support keyFile (private.pem.key), so you can't use it like that.

  • Like 1
  • Topic Author
  • Posted
    3 hours ago, tinman said:

     

    afaik tls options does not support keyFile (private.pem.key), so you can't use it like that.

     

    Hi @tinman ,
    Thanks for your reply!!
    If I can't append private key content, how do I connect to AWS MQTT using tls?

     

    Posted
    12 hours ago, xrdandy said:

    If I can't append private key content, how do I connect to AWS MQTT using tls?

     

    sorry can't help you with this, maybe FIBARO @m.roszak has an idea

    • Like 1
    • 2 weeks later...
  • Topic Author
  • Posted
    On 10/6/2022 at 9:57 PM, tinman said:

     

    sorry can't help you with this, maybe FIBARO @m.roszak has an idea

     

    Thank you so much. I'll find out if there is any other way.

    • 2 years later...
    Posted

    In my case, everything works fine, with both a local and remote broker using port 1883. However, when I try to connect to a remote broker with a username and password, using TLS or SSL, port 8883 (no certificate required), I can connect to the broker, but the remote broker disconnects me with "Return Code" 5.
    Have you solved your problem? How did it go?
    I've configured the TLS option as described in this and other posts, but it's still the same. I don't know what I'm doing wrong.
    Some guidance would be appreciated.
    Regards.

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Reply to this topic...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...