Problem after upgrading 3.6.0

ChirpStack Application Server
1

Hi!

moved category

Yesterday i upgraded chirpstack 3.6.0 (cant find versions for the different parts other then network server) and now i have som problems…

Data from sensors are coming in but the integration to influx i partly broken. If i subscribe to mqtt i se all values coming in but for some strange reason not all values from the same sensor gets to the influxdb.

For example,

application/3/device/a81758fffe0461cc/rx {“applicationID”:“3”,“applicationName”:“Nossebro_Energi”,“deviceName”:“co2skola”,“devEUI”:“a81758fffe0461cc”,“rxInfo”:[{“gatewayID”:“fcc23dfffe0ab353”,“uplinkID”:“00000000-0000-0000-0000-000000000000”,“name”:“iotgateway”,“rssi”:-91,“loRaSNR”:10.2,“location”:{“latitude”:58.18887507673164,“longitude”:12.72371292114258,“altitude”:20}}],“txInfo”:{“frequency”:867700000,“dr”:5},“adr”:true,“fCnt”:13871,“fPort”:5,“data”:“AQC/AiIEAAEFBAYBkwcOSA==”,“object”:{“co2”:403,“humidity”:34,“light”:1,“motion”:4,“temperature”:19.1,“vdd”:3656}}

The temperature seems to be the only value inserted into influx…

On a other sensor temperature and airpreassure is inserted into database but distance and humidity is not inserted…

Not really sure where to begin looking for the problem and all input is appreciated.

2

After reviewing logs i found this line that started appearing after the upgrade wich would explain the missing data in influxdb

Jan 30 09:02:49 lorawan chirpstack-application-server[1151]: time=“2020-01-30T09:02:49+01:00” level=error msg=“integration/multi: integration error” ctx_id=8b09fea7-5ff1-44b6-9244-ce16170c22be error=“sending measurements error: expected 2xx response, got: 400 ({“error”:“partial write: field type conflict: input field \“value\” on measurement \“device_frmpayload_data_co2\” is type float, already exists as type integer dropped=5”}\n)” integration="*influxdb.Integration"

Now comes the interresting question… what has changed in chirpstack since everything worked flawlessly prior to update…?

3

The “issue” with InfluxDB is that it uses the first received value to determine the data type. When the first value “looks” like an integer, then all following measurements must be of type integer. This is probably causing your issue, not the update.

4

Okey, so chirpstack is sending values in the same format but its not what influx is expecting… is there a easy way to change this?

5

Please see this issue: https://github.com/brocaar/chirpstack-application-server/issues/411.

1 Like
6

This is a bitt wierd but by some freakish way it all seem to have begun to work again after 5 days of not working…