InfluxDB integration (v4, protobuf)

Hello,

I have installed ChirpStack v4 with docker and using a gateway with bridge v3, I get messages from end nodes with protobuf formatting through MQTT.

Now, I’m looking to integrate InfluxDB v2.7.0. The device profiles codec return a dummy value for test purposes, I see it on the Events windows and the decoded uplink reaches mosquitto.

The influxDB v2 integration is done in the application with bucket and token configured, the docker bridge IP is used for the API.

Where should I look to understand why the payload is not written on influxDB?

Regards

Best would be to inspect the ChirpStack logs for integration errors in this case.

Thank you for your reply!

I was not running InfluxDB on the same docker’s network… The integration works as expected:)

Do you know if it is possible to modify the field name of a returned value and add a tag (retrieved from the payload parameter)?

Hi @tapitapo
Can you please advise me on this topic.
To avoid compose up making a standalone chirpstack docker network I tried to set network mode:bridge (bridge network where the influx container resides) for each service in the chirpstack.yaml (chirpstackv4, compose ver3) but get yaml config errors.

If you want everything on the same network you do that in the docker-compose.yml.

Here’s an example snippet from mine:

  postgres:
    image: postgres:14-alpine
    restart: unless-stopped
    volumes:
      - ./configuration/postgresql/initdb:/docker-entrypoint-initdb.d
      - postgresqldata:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=root
    networks:
      default:

  redis:
    image: redis:7-alpine
    restart: unless-stopped
    command: redis-server --save 300 1 --save 60 100 --appendonly no
    volumes:
      - redisdata:/data
    networks:
      default:

volumes:
  postgresqldata:
  redisdata:

networks: 
  default:

Thankyou
I ended up defining a network in there and making a .yml file for influx wherein I set to that network and that worked fine.