Xdrip: Nightscout treatments are not downloaded

[malloy139]

Treatments entered in XDrip are shown on the master and in the Webinterface, but not on the Noghtscout Follower. "Download Treatments" is turned on.
But when a treatment is entered in the Webinterface is shows up on the follower, as can be seen in the attached image.

[GPLExpert]

Same for me here

Treatments entered in XDrip are shown on the master and in the Webinterface, but not on the Noghtscout Follower

[malloy139]

It is still not working. Is this a xdrip issue or a nightscout issue?
This seems to be the only way (if it would work) to distribute treatments for people with phones that have no play services installed and can't use the sync featue.

[GPLExpert]

Hello,
Yes if someone can help debugging ?
I can give all informations if needed
Thanks

[rocketman10404]

Having the same issue on several phones running XDrip

Edit: Interesting note. When looking at the treatment history/database in Nightscout, I see that all the treatments entered from the xdrip app have "xdrip" in the "Entered By" field. In Nightscout, I can manually edit the treatment data, so I tried changing "xdrip" to something else, and afterwards, my XDrip app downloaded that specific treatment.

So, it seems like the issue here is the "Entered By" field used to upload the treatment data. If all phones' XDrip apps are using "xdrip", perhaps they're intentionally ignoring those treatment records, with each app assuming it was the uploader?

Is there anyway to customize or configure XDrip as far the treatment's "Entered By" record?

[rocketman10404]

From my brief and uneducated quick scan of Treatments.java, it does indeed appear as though the "Entered By" record is taken from a hard-coded constant (XDRIP_TAG) that currently cannot be changed in the app.

Also, looking at NightscoutTreatments.java (and this is my best interpretation as a hobbyist's first look) - at line 133, it looks like a check on new treatments to only process non-existing (i.e. new) treatments not coming from xdrip (i.e. "Entered By" is not "xdrip"). There's a else condition block to catch changes for pre-existing treatments whether or not they come from xdrip, but there does NOT look to be any code to process new treatments that come from xdrip. Seems to me like this is the root cause of the issue we're describing.

I'd suggest possibly adding a configurable setting to allow user control over the XDRIP_TAG contents, but have no idea what other negative effects this may have elsewhere. It may be easier to avoid downloading/uploading duplicates if all XDrip users syncing to a Nightscout instance could have treatments uniquely identified via the XDRIP_TAG.

Alternatively, perhaps non-existing treatments could be process whether or not they came from xdrip?

Lastly - this may be a duplicate of #1196. Possibly related to #735, but maybe not.

[tolot27]

This is a duplicate of #1196. The problem reported with #735 is that treatments entered by followers are not uploaded to nightscout.

@jamorham Please can you close this issue?