Notehub Geolocation Data Error for Notecarrier AF

Good morning,

Last night, I set up my Notecarrier AF to do asset tracking, by following along with this tutorial: Asset Tracking - Blues Wireless Developers

I saw events showing up in Notehub afterwards, so I left it plugged in to my computer overnight sitting on my desk (not moving anywhere). This morning, when I checked Notehub to see if a heartbeat event had registered, I noticed this error message that happened last night.

I searched the forums and the general internets without much success as to the nature of this error, so can anyone tell me what this means?

By the way, I can still see location data from the _track.qo events when I drill down to their raw JSON.

Thanks,
Paige

Hi @paigen11,

Do you recall ever calling the card.triangulation API?

https://dev.blues.io/notecard/notecard-walkthrough/time-and-location-requests/#using-cell-tower-and-wi-fi-triangulation

Hi @RobLauer ,

I don’t believe I ever included that command when configuring my Notecarrier, no. I followed the asset tracking instructions for periodic location tracking to a T, and there was no mention there of card.triangulation.

This documentation gives me a much better idea of what’s happening, though. As it recommends, I think I’ll allow for triangulation only when the Notecarrier is plugged into a USB power source.

Thanks for the help!

Has the Notecard config changed since the time that you saw the _geolocate.qo event? I would love to know if card.triangulate was set, since there “should” be no other way for Session.ScanResults to get passed back to the Notehub where it will then try to do a triangulation lookup. If you have not changed anything since, can you take a look at what card.triangulate is set to? Although looking at the docs, I can’t tell how we would know if card.triangulate has been set by using any req calls. I see how to set it, but not how to check what it has been set to

The config has not changed since I saw that event.

The Notecarrier has just continued to sit on my desk, plugged into the computer. I looked at the docs also, and I’m not sure how to tell what its current setting is.

I just ran {"req":"card.triangulate"} from the Notecard CLI, and got back the following JSON {"motion":1626290735} though.

I have a factory reset card and {"req":"card.triangulate"} gets me {}. So it must be set to something on your card! We’ll figure out how to read back the config shortly im sure

Ok! I did a {"req":"card.restore","delete":true} on my card before I started enabling the GPS tracking, but maybe it was a glitch.

Thanks for looking into it.

Out of curiosity, what version is the Notecard firmware?

Can you paste the results of {"req":"card.version"}?
https://dev.blues.io/reference/notecard-api/card-requests/#card-version

It looks like the latest firmware:

      "version":"notecard-1.5.5",

Here’s the whole body for reference:

{
   "body":{
      "org":"Blues Wireless",
      "product":"Notecard",
      "version":"notecard-1.5.5",
      "ver_major":1,
      "ver_minor":5,
      "ver_patch":5,
      "ver_build":13080,
      "built":"May 28 2021 17:11:58"
   },
   "version":"notecard-1.5.5.13080",
   "device":"dev:864xxxxxxxxxxx",
   "name":"Blues Wireless Notecard",
   "sku":"NOTE-NBGL-500",
   "board":"1.11",
   "api":1
}

{“req”:“card.triangulate”} will return a motion: field regardless of the setting (or not) of card.triangulate. All that is needed is for the accelerometer to be active and to have sensed movement at some time since the boot.

@paigen11 can u invite me to your project? I want to look at the session data

Triangulation can also be enabled with the environment variable _tri - you could check if it’s set with
{“req”:“env.get”,“name”:"_tri"}
{“text”:“wifi,cell”}

Will return {} if it is not set.

An environment variable set on Notehub would not be cleared by a {“req”:“card.restore”,“delete”:true}

1 Like

Certainly - I’ve invited you to the project now. Let me know if you can see the data that you need.

Looking at the data, the session that tripped the _geolocate.qo note.add event does have scan data attached to it
https://notehub.io/project/app:41f3e95a-3b47-4fb1-8f8d-3625e0f9c17c/devices/dev:864475044279957/sessions/1ab86720-8075-44e8-a16b-3174332d8afd

    "session": "1ab86720-8075-44e8-a16b-3174332d8afd",
    "device": "dev:864475044279957",
    "product": "product:com.blues.paige:pn_gps_project",
    "fleet": "fleet:6bc805eb-e2a8-46d9-87d4-1e0384bd4290",
    "addr": "tcps:26016:10.68.83.83",
    "cell": "310,410,11298,187681040",
    "scan": "UEAA6tQzEH2RFn2AeR6b2koYABUBNBYAKgAAANEf7mABACpFFRcQAAAA0E8BBjYBABwEAAAAAAAAAA==",
    "triangulate": {},
...
}

Which is crazy! You do not have card.triangulate set so data is leaking into that slot somehow. I talked with Ray last night and there is one theory i will apply and deploy. will let you know when it hits production.

1 Like

I deployed a patch that might resolve the issue. Please let me know if a _geolocate note.add event pops up in this project again

1 Like