# TrackerD no measurements appear at ttnmapper?

**URL:** <https://www.thethingsnetwork.org/forum/t/trackerd-no-measurements-appear-at-ttnmapper/70435>\
**Category:** Application Development\
**Tags:** ttn-mapper\
**Created:** [January 25, 2025, 12:40pm UTC](https://www.thethingsnetwork.org/forum/t/trackerd-no-measurements-appear-at-ttnmapper/70435 "2025-01-25T12:40:20Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![huegelfunk](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/huegelfunk/32/45876_2.png) [@huegelfunk](https://www.thethingsnetwork.org/forum/u/huegelfunk)\
**Post date:** [January 25, 2025, 12:40pm UTC](https://www.thethingsnetwork.org/forum/t/trackerd-no-measurements-appear-at-ttnmapper/70435/1 "2025-01-25T12:40:21Z")

</div>

Hi, I’m a TTN freshman but managed to get my TrackerD GPS tracker up and pushing messages to TTN. Unfortunatly I don’t seem to push measurements to the ttnmapper, even if I doublechecked my setup twice:

- Device transmits messages and last seen is a current datetime
- Custom decoder added from the dragino [Trackerd repo](https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD). Payload gets decoded as expected in the preview:

```auto
{
  "ALARM_status": "FALSE",
  "BatV": 3.344,
  "Bg": 0,
  "Date": 0,
  "Hum": 59.2,
  "LON": "ON",
  "Latitude": 54.07,
  "Location": "54.07,12.14",
  "Longitud": 12.14,
  "MD": 0,
  "Tem": 1.82,
  "Time": 0,
  "Transport": "STILL",
  "location_tago": {
    "latitude": 54.07,
    "longitude": 12.14
  }
}

```

(location is manually trunced)

- ttnmapper webhook added as the [howto explains](https://docs.ttnmapper.org/integration/tts-integration-v3.html). The URL is correct, ID set, notihing special.

If I wait for transmissions that have valid position, nothing appears if I query the ttncoverage advanced maps for my device ID and daterange. Also tried different ID formating, but no nothing happens ☹

Any tips what might be wrong and preventing me from contributing measurements?

---

<div class="post-metadata">

**Author:** ![WaterschapValleiEnVe](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/w/a8b319/32.png) [@WaterschapValleiEnVe](https://www.thethingsnetwork.org/forum/u/WaterschapValleiEnVe)\
**Post date:** [January 25, 2025, 1:14pm UTC](https://www.thethingsnetwork.org/forum/t/trackerd-no-measurements-appear-at-ttnmapper/70435/2 "2025-01-25T13:14:01Z")

</div>

I had the same issue this morning

---

<div class="post-metadata">

**Author:** ![clv](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/clv/32/46568_2.png) [@clv](https://www.thethingsnetwork.org/forum/u/clv)\
**Post date:** [January 25, 2025, 2:33pm UTC](https://www.thethingsnetwork.org/forum/t/trackerd-no-measurements-appear-at-ttnmapper/70435/3 "2025-01-25T14:33:28Z")

</div>

TTNmapper has some problems. Donations are welcome.  
[https://www.thethingsnetwork.org/forum/t/ttnmapper-integration-down/](https://www.thethingsnetwork.org/forum/t/ttnmapper-integration-down/)

But I think you also need altitude and optional hdop, accuracy or sats.

---

<div class="post-metadata">

**Author:** ![jpmeijers](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jpmeijers/32/48543_2.png) [@jpmeijers](https://www.thethingsnetwork.org/forum/u/jpmeijers)\
**Post date:** [January 26, 2025, 2:43pm UTC](https://www.thethingsnetwork.org/forum/t/trackerd-no-measurements-appear-at-ttnmapper/70435/4 "2025-01-26T14:43:21Z")

</div>

> [@huegelfunk](#):
>
> ```auto
> "Latitude": 54.07,
> "Location": "54.07,12.14",
> "Longitud": 12.14,
> 
> ```

From the docs you link I quote:

> A JSON object containing the keys “latitude”, “longitude”…

You JSON keys are different. Especially there is a missing **e** for longitude. But please also bring it in line to exactly what the mapper’s docs says, so lower case **L**.

---

<div class="post-metadata">

**Author:** ![huegelfunk](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/huegelfunk/32/45876_2.png) [@huegelfunk](https://www.thethingsnetwork.org/forum/u/huegelfunk)\
**Post date:** [February 14, 2025, 12:09pm UTC](https://www.thethingsnetwork.org/forum/t/trackerd-no-measurements-appear-at-ttnmapper/70435/5 "2025-02-14T12:09:57Z")

</div>

Yep, fixing the first letter seems to fix the issue. As the docs mention ‘similar names’, I thought beeing case insensitive is also covered 😉

BTW. I asked the TrackerD manufacturer to add DOP values: [transmit DOP values? · Issue #38 · dragino/TrackerD · GitHub](https://github.com/dragino/TrackerD/issues/38)

---

<div class="post-metadata">

**Author:** ![jpmeijers](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jpmeijers/32/48543_2.png) [@jpmeijers](https://www.thethingsnetwork.org/forum/u/jpmeijers)\
**Post date:** [February 14, 2025, 12:34pm UTC](https://www.thethingsnetwork.org/forum/t/trackerd-no-measurements-appear-at-ttnmapper/70435/6 "2025-02-14T12:34:42Z")

</div>

It must be the missing `e` that prevented it from working. I just had a look and capitalized is supported:

> <https://github.com/ttnmapper/ingress-api/blob/4e93ff62a079679b428bfd3669fc21c8560e3360/utils/payload_fields_parser.go#L75-L75>

and

> <https://github.com/ttnmapper/ingress-api/blob/4e93ff62a079679b428bfd3669fc21c8560e3360/utils/payload_fields_parser.go#L95-L95>

HDOP: not required, but always useful to have. It doesn’t contribute much to the mapper at the moment, just a little bit of filtering of really bad gps values:

> <https://github.com/ttnmapper/ingress-api/blob/4e93ff62a079679b428bfd3669fc21c8560e3360/utils/data_validator.go#L25-L30>

---

<div class="post-metadata">

**Author:** ![system](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/6/2/6250ea44fd2b0d6259489e1a92748df681e1f970.png) [@system](https://www.thethingsnetwork.org/forum/u/system)\
**Post date:** [February 15, 2025, 12:35pm UTC](https://www.thethingsnetwork.org/forum/t/trackerd-no-measurements-appear-at-ttnmapper/70435/7 "2025-02-15T12:35:19Z")

</div>

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