Thingsboard Integration: "error":"json: cannot unmarshal bool into Go value of type uint32","code":3

santobedi · December 16, 2021, 11:13am

We are trying to send a downlink (RPC command from Thingsboard) to a RAK7431 end node. We could do it using the ‘external REST API’ call from the Thingsboard rule chain. However, we get “error”:“json: cannot unmarshal bool into Go value of type uint32”,“code”:3 while trying with integration downlink node in the rule chain. It seems the issue is with the Chirpstack. The downlink msg that we want to send is a Modbus RTU request to a relay, which is connected to the RAK7431 device:

        "deviceQueueItem": 
        {
         "confirmed": true,
        "data": "AgABAAgBBQAB/wDd+g==",
         "devEUI": "ac1f09fff*******",
         "fCnt": 0,
        "FPort": 129,
         "jsonObject": ""
    }

The issue is with downlink only, we are able to receive uplink raw data from the RAK7431 device. How can we solve it?

chopmann · December 16, 2021, 3:39pm

github.com

brocaar/chirpstack-api/blob/master/protobuf/as/external/api/deviceQueue.proto#L48


      
          
          message DeviceQueueItem {
              // Device EUI (HEX encoded).
              string dev_eui = 1 [json_name = "devEUI"];
          
              // Set this to true when an acknowledgement from the device is required.
              // Please note that this must not be used to guarantee a delivery.
              bool confirmed = 2;
          
              // Downlink frame-counter.
              // This will be automatically set on enquue.
              uint32 f_cnt = 6;
          
              // FPort used (must be > 0)
              uint32 f_port = 3;
          
              // Base64 encoded data.
              // Or use the json_object field when an application codec has been configured.
              bytes data = 4;
          
              // JSON object (string).

Have you tried not setting the fCnt?

santobedi · December 17, 2021, 1:23pm

I tried it. The same error persists.

santobedi · January 6, 2022, 11:01am

Upgrading the Thingboard version 3.2.2PE to version 3.3.2PE solved the problem.