Can you try this again in the latest nightly? March 6th.. let me know if I have resolved it. Thanks

Thank you @jamorham ! Now I figured out - or better to say remembered (silly me) how I can easily test this without the real change of the sensor so I will test it and report here. I will make some test NS sites and fresh xdrip installation on spare phone (parakeet system) and test this and report here

Hi @jamorham , I have just tried with nightly 6th March and it seems that the issue is still not resolved. The behavior that I can see is still the same.

HI! I just want to shed some attention to this old issue. I am still experiencing this issue. With dexcom as well as with libre sensors.

@bordeb Is the problem still there with more recent releases of xDrip and Nightscout?

Closing due to inactivity

This issue is still happening as reported here: #2299 (reply in thread) and here #2358 (reply in thread)

@Navid200 asked me to transfer the information to this thread.

Where there are two space separated URLs specified as the Base URL in xDrip settings;

• glucose values (type sgv) are uploaded to both nightscout instances
• CGM calibration events are uploaded to both nightscout instances
• other treatments and events (for instance I've experienced it with:- carbs, insulin, CGM sensor start/stop) only go to the first URL specified

Swapping around the order that the URLs are listed causes to carbs, insulin etc. to go to which ever nightscout instance islisted first.

My current configuration is two nightscout 14.2.5 instances, xDrip nightly from 2022.10.15 and dexcom g6 being read directly by xDrip with the G5/G6 Transmitter hardware data source and the Native Algorithm enabled.

When starting new dex sensor it seems that, if there is more than one Nightscout sites (REST-API) in the Base URL settings (space delimited), the upload of the "eventType: Sensor Start" works only for the 1st (first) NS site in a row. All other NS sites are missing this data. I tried to confirm this with fresh setup of multiple NS sites and clean install of the xDrip+ app and can confirm this issue. I also tried to reorder the NS sites under Base URL settings and it is always only the first one in a row that receives the while all others are missing the "eventType:" "Sensor Start" data. xDrip + app ver latest stable: 2017-11-13 NS ver latest: 0.10.2-release-20171201

After all i found some relevant logs in nginx

tail -f access.log my-redacted-public-ip - - [11/Apr/2023:22:49:22 +0100] "GET /api/v1/treatments HTTP/2.0" 200 2 "-" "okhttp/3.12.13" my-redacted-public-ip - - [11/Apr/2023:22:49:22 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:49:23 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:49:25 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:49:27 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:49:32 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:49:37 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:49:43 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:49:48 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:49:53 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:49:58 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:03 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:08 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:13 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:18 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:23 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:27 +0100] "POST /api/v1/entries HTTP/2.0" 200 68 "-" "okhttp/3.12.13" my-redacted-public-ip - - [11/Apr/2023:22:50:27 +0100] "POST /api/v1/devicestatus HTTP/2.0" 200 161 "-" "okhttp/3.12.13" my-redacted-public-ip - - [11/Apr/2023:22:50:27 +0100] "GET /api/v1/treatments HTTP/2.0" 200 2 "-" "okhttp/3.12.13" my-redacted-public-ip - - [11/Apr/2023:22:50:28 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:33 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:38 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:43 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0" my-redacted-public-ip - - [11/Apr/2023:22:50:48 +0100] "GET /socket.io/?EIO=3&transport=polling HTTP/2.0" 400 51 "-" "okhttp/4.9.0"

I wanted to fix this. But, it is quite complicated.

Can I ask why anyone would need to upload to more than one site other than for emergency?
Let me explain what I mean by emergency.
Let's say I use Nightscout as a part of a loop. So, it is extremely important for me for it to be up and running with no interruptions.
To address this, I set up xDrip to upload to two sites.
If the main site breaks and the loop warns me, I will right away change the hostname in the loop to that of the emergency site, the second site. Then, my loop will continue to function.
When I get home, I will figure out what happened to my main site and fix it.
After I fix my main site, I will use the existing feature in xDrip to backfill the missing data in my main site and switch loop back to my main Nightscout site.

So, I use the capability of xDrip to upload to two sites the same way I use a spare tire in the trunk of my car. I only use it to address an emergency. But, I never use it under normal circumstances.

If that is why everyone uses multiple sites, then, this should not really be an issue, should it?

Tnx for asking!
One real life example can be: For a child being followed and/or monitored through a NS sites, one might want that e.g. parents have highest info on one NS site, some other family members some other info on other NS site, and maybe some care giver/teacher/etc.. some minimal required information on third NS site.

Tnx for asking! One real life example can be: For a child being followed and/or monitored through a NS sites, one might want that e.g. parents have highest info on one NS site, some other family members some other info on other NS site, and maybe some care giver/teacher/etc.. some minimal required information on third NS site.

How would you accomplish that?
Unless I have misunderstood this issue, the request is to change xDrip so that it would upload treatments to all sites included in the base URL setting separated by spaces. Then, all of your sites will become identical as far as what they contain.
How would you only have minimal information on one site and not the others?

How would you accomplish that? Unless I have misunderstood this issue, the request is to change xDrip so that it would upload treatments to all sites included in the base URL setting separated by spaces. Then, all of your sites will become identical as far as what they contain. How would you only have minimal information on one site and not the others?

For example setting some plugins as enabled/disabled and/or shown/not shown and/or alarms active/disabled dependant on the specific NS site. In addition, from experiance, different High/Low thresholds (e.g. parents wirh little bit narrower targeted frame compared to caregivers, or vice versa) to be on the safe side, more or less conservative approach, etc..

For example setting some plugins as enabled/disabled and/or shown/not shown and/or alarms active/disabled dependant on the specific NS site. In addition, from experiance, different High/Low thresholds (e.g. parents wirh little bit narrower targeted frame compared to caregivers, or vice versa) to be on the safe side, more or less conservative approach, etc..

To sum up, I just want to help, and maybe my examples are not so relevant. Honestly, we are using xdrip and NS successfully for years and both are so high end, beautiful, powerful, usefull... pieces of software that it is almost unbelievable that it is all based on open source and volunteer experts like you and others. So, this is really not a big deal, my personal opinion is that it is fully up to you experts to decide if it is worth time and effort investing. In either way, both software remain undoubtedly excellent!