Tracker One - Battery not always included in webhook

Firmware
1

I have three Particle Tracker Ones. They are all running the default v11 firmware.

One sends battery value in the webhook - like this:

{
"cmd":"loc"
"time":1616001912
"loc":{
"lck":1
"time":1616001913
"lat":35.90859222
"lon":-78.80267334
"alt":88.317
"hd":249.19
"h_acc":3.4
"v_acc":5.7
"cell":43.3
"batt":78.2
"temp":28.1
}
"trig":[
0:
"lock"
]
"req_id":74
}

The other two do not:

{
"cmd":"loc"
"time":1616001990
"loc":{
"lck":1
"time":1616001990
"lat":35.90860367
"lon":-78.80270386
"alt":97.517
"hd":226.1
"h_acc":1.2
"v_acc":2.3
"cell":43.3
"temp":23.2
}
"trig":[
0:
"radius"
]
"req_id":51
}

Any advice on how to correct this?

Thanks,

Chip

2

Hi Chip, could you request a vitals message from all devices and post those results back here?

3

Sure, here is one - Tracker-Dev2

{
  "device": {
    "network": {
      "cellular": {
        "radio_access_technology": "LTE",
        "operator": "AT&T Wireless Inc.",
        "cell_global_identity": {
          "mobile_country_code": 310,
          "mobile_network_code": "410",
          "location_area_code": 9999,
          "cell_id": 196763153
        }
      },
      "signal": {
        "at": "LTE Cat-M1",
        "strength": 45.36,
        "strength_units": "%",
        "strengthv": -97,
        "strengthv_units": "dBm",
        "strengthv_type": "RSRP",
        "quality": 35.29,
        "quality_units": "%",
        "qualityv": -14,
        "qualityv_units": "dB",
        "qualityv_type": "RSRQ"
      },
      "connection": {
        "status": "connected",
        "error": 0,
        "disconnects": 0,
        "attempts": 1,
        "disconnect_reason": "unknown"
      }
    },
    "cloud": {
      "connection": {
        "status": "connected",
        "error": 0,
        "attempts": 1,
        "disconnects": 0,
        "disconnect_reason": "none"
      },
      "coap": {
        "transmit": 12,
        "retransmit": 0,
        "unack": 0,
        "round_trip": 103
      },
      "publish": {
        "rate_limited": 0
      }
    },
    "power": {
      "battery": {
        "charge": {
          "err": -210
        },
        "state": "unknown"
      },
      "source": "unknown"
    },
    "system": {
      "uptime": 25,
      "memory": {
        "used": 92260,
        "total": 165852
      }
    }
  },
  "service": {
    "device": {
      "status": "ok"
    },
    "cloud": {
      "uptime": 7,
      "publish": {
        "sent": 3
      }
    },
    "coap": {
      "round_trip": 946
    }
  }
}

The err -210 might be a clue. The devices does seem to charge and can run on battery however.

Chip

4

Yes, I think that is the key. Have you been able to charge the batteries up to this point?

5

Yes, I am able to charge the batteries and the devices do seem to function on battery power for a significant period of time.

6

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.