Nightscout does not show a Trend arrow

[Flori3000]

Subject of the issue
Nightscout does not show a trend arrow anymore.

Your environment
Nightscout version 14.2.4
Source for BG values: Dexcom Share (EU)

Expected behavior
Show trend arrows

Steps to reproduce the behavior:
Set up Dexcom Share as source for BG values.

Info:
Found this here.
"It looks like Dexcom changed the BG arrow trend indicator value (slope) from a number to a string."

[herzogmedia]

does you Dexcom App still work as expected? I've got the same behaviour but for me the Dexcom App now thinks my smart device was not compatible

[Flori3000]

Dexcom App on iOS and Dexcom Follow on an Android device are working as expexted.

[eggepegge]

I've got the same behaviour. Nightscout 14.0.6, getting values from Dexcom Share (EU). The interesting thing is that in my dexcom Follow app (I'm only a follower) I get the trend arrow, and even more interesting, in xDrip having my nightscout as source, I also get the trend arrow. But in the Nightscout web gui it looks like in the screendump above, and via the API I get direction NONE. Ah, and there "trend" explain why I get the arrow in xDrip....

$ curl -q https://xxx.herokuapp.com/api/v1/entries/current.json |json_pp 
[
   {
      "sysTime" : "2021-12-01T11:36:56.000Z",
      "_id" : "xxx",
      "device" : "share2",
      "trend" : "DoubleUp",
      "date" : 1638358616000,
      "type" : "sgv",
      "dateString" : "2021-12-01T11:36:56.000Z",
      "direction" : "NONE",
      "sgv" : 280,
      "utcOffset" : 0
   }
]

[Flori3000]

@eggepegge same behaviour for me.

[sulkaharo]

How are you inserting data into Nightscout? The trend arrow uses the "direction" field value and if your data source is inserting NONE as the value for this field, no arrow will be shown.

[Flori3000]

Seems to be related to this issue

[eggepegge]

How are you inserting data into Nightscout? The trend arrow uses the "direction" field value and if your data source is inserting NONE as the value for this field, no arrow will be shown.

I'm populating nightscout from Dexcom Share (EU). As Flori3000 mentioned, seem to be related to this.

[charlotte130210]

I´ve got the same problem with the trend arrow as shown above.

Nightscout version 14.2.4
Source for BG values: Dexcom Share (EU)

The missing trend arrow appears without the stop being changed.

Is it required in the Heroku Config Vars to use a certain parameter for DIRECTION?

[tuim]

Thanks for your work on this. When should we expect to see the fix on master?

[bewest]

We've asked for help testing the changes in #7146. Once testers for Medtronic Careportal and Dexcom Share can help us achieve high confidence that the changes work as intended, we will issue a new release.

https://www.facebook.com/groups/cgminthecloud/posts/4630775833710303/?comment_id=4636379419816611

Thanks to early feedback, we have continued to make changes to Nightscout's cloud-to-cloud synchronization capabilities.
For Dexcom Share folks we need the following circumstances tested:

• old-style usernames
• email-based usernames
• EU or OUS testers
• US testers

For Medtronic Carelink folks, we need the following scenarios tested:

• Carepartner account
• Patient account
• outside United States
• inside United States

[tuim]

on it. Thank you!

[pdaddyo]

I'm trying to test this fix (in EU) via the official latest_dev docker image (built 2 days ago) but I'm getting Error: Cannot find module jsdom during startup (just after connecting to mongo). Switching back to latest image works fine except for the broken trend arrow, which by the way we suspect is also the culprit crashing my wife's garmin watchface for last day or so! Thanks everyone for your help on this.

[pdaddyo]

Latest dev build is working with arrows restored (we're on EU bridge), thanks all.

[JasmineT1D]

I'm in the US and the arrows are still showing <=>. Is there a fix for US users yet?

[Domfunkle]

The issue was with the nightscout/share2nightscout-bridge node module. The module was updated, but you need to update your package.json file to use the latest version 0.2.8 and then redeploy: "share2nightscout-bridge": "^0.2.8"

[JasmineT1D]

Thanks Domfunkle. I'm a total novice user though and have only done master version updates. Do you know when this fix will be available to update via the master update or is there any chance you can post instructions on how to update the module you noted?

[cpitchford]

I have deployed the dev branch locally and I'm running without problem.

• I am using the share2nightscout-bridge 0.2.8
• I am a EU/UK User with non-email style Dexcom username
• I am running on Ubuntu 18.04/Nodejs 12(nodesource package)

[JasmineT1D]

Thank you for the additional info cpitchford! I just deployed on the Dev branch and the arrow is indeed back! For anyone interested here is a link with detailed instructions on how to deploy the dev branch.

https://nightscout.github.io/update/dev_branch/?fbclid=IwAR2hKwg_2anGOzzQp4SBTrTn9l60IfHInUcLwIDtlRd9qMNU5cWVoLWVMQA

[herzogmedia]

The current master release 14.2.5 should fix it now. Thanks @bewest

[bewest]

Closing for now. The trend arrows should be restored. In addition, there should be less lag fetching new glucose readings from Dexcom. https://github.com/nightscout/cgm-remote-monitor/releases/tag/14.2.5