AWS IoT Core MQTT Chirpstack V4 integration

1

Hi guys,

I would like to know if the integration with IoT core is possible using V4.

Using V3 I had this configuration on the chirpstack-application-server.toml file

image
image848×154 9.58 KB

I would like to do the same on the V4. Is it possible?

2

Guys I have tried without success.

Here is my log:

chirpstack_1                       | 2023-02-25T19:20:24.471218Z  INFO chirpstack::integration::mqtt: Initializing MQTT integration
chirpstack_1                       | 2023-02-25T19:20:24.474332Z  INFO chirpstack::integration::mqtt: Configuring connection with TLS certificate ca_cert= tls_cert= tls_key=~/chirpstack-docker/configuration/chirpstack/private.pem.key
chirpstack_1                       | 2023-02-25T19:20:24.479393Z  INFO chirpstack::integration::mqtt: Connecting to MQTT broker server_uri=ssl://a170ach1dll0jq-ats.iot.eu-west-2.amazonaws.com:8883 client_id=572da5f962aff5c3 clean_session=false
chirpstack_1                       | Error: Setup MQTT integration
chirpstack_1                       | 
chirpstack_1                       | Caused by:
chirpstack_1                       |     0: Connect to MQTT broker
chirpstack_1                       |     1: [-1] TCP/TLS connect failure

Here is my code:


[integration]
  enabled=["mqtt"]

  [integration.mqtt]
    server= "ssl://[aws-host].amazonaws.com:8883"
    tsl_cert = "~/chirpstack-docker/configuration/chirpstack/certificate.pem.crt"
    tls_key= "~/chirpstack-docker/configuration/chirpstack/private.pem.key"
    ca_cert_= "~/chirpstack-docker/configuration/chirpstack/ca_cert.pem"
    json=true
3

Solved, we need to use the absolute path inside the docker, not the path of the volume.

2 Likes