Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graph missing #146

Open
deltaford opened this issue Feb 16, 2015 · 21 comments
Open

Graph missing #146

deltaford opened this issue Feb 16, 2015 · 21 comments

Comments

@deltaford
Copy link

No graph after upgrade from 0.1.10 to 0.1.12. Tried both mmol/l & mg/dl setting.

@rnpenguin
Copy link
Contributor

what android OS are you running and what phone?

@deltaford
Copy link
Author

We are using Android 4.4.4 (Cyanogenmod) on Moto G (G1 LTE) with Swedish locale.

@francescaneri
Copy link

We are using sansung nexus (Android 4.4.4 - Cyanogenmod) on Moto G (G1 LTE) with H3G ITA.

@trhodeos
Copy link
Contributor

Can you guys take a screenshot and post it here?

On Tue, Feb 17, 2015 at 11:01 PM, Matteo Neri [email protected]
wrote:

We are using sansung nexus (Android 4.4.4 - Cyanogenmod) on Moto G (G1
LTE) with H3G ITA.


Reply to this email directly or view it on GitHub
#146 (comment)
.

@francescaneri
Copy link

screenshot_2015-02-18-17-15-43

@trhodeos
Copy link
Contributor

Thanks! I'll check this out later tonight.

On Wed, Feb 18, 2015 at 8:23 AM, Matteo Neri [email protected]
wrote:

[image: screenshot_2015-02-18-17-15-43]
https://cloud.githubusercontent.com/assets/9915825/6251158/a067b012-b792-11e4-8556-e4f5bc8e09e7.png


Reply to this email directly or view it on GitHub
#146 (comment)
.

@deltaford
Copy link
Author

I'm seeing the exact same thing on my phone.

@scottleibrand
Copy link
Member

This might be a timezone issue. I see what looks like one data point 4h
offset. Check that your Dexcom and Android phone both have the same time
and timezone.
On Wed, Feb 18, 2015 at 9:03 AM deltaford [email protected] wrote:

I'm seeing the exact same thing on my phone.


Reply to this email directly or view it on GitHub
#146 (comment)
.

@scottleibrand
Copy link
Member

Well, Dexcom doesn't have a timezone per se, just a display time that needs
to match the uploader's.
On Wed, Feb 18, 2015 at 9:23 AM Scott Leibrand [email protected]
wrote:

This might be a timezone issue. I see what looks like one data point 4h
offset. Check that your Dexcom and Android phone both have the same time
and timezone.
On Wed, Feb 18, 2015 at 9:03 AM deltaford [email protected]
wrote:

I'm seeing the exact same thing on my phone.


Reply to this email directly or view it on GitHub
#146 (comment)
.

@francescaneri
Copy link

controlled : are ok

@deltaford
Copy link
Author

Dont know if it could be related but I had a similar issue (missing graph) with Chrome Uploader (nightscout/chrome-uploader#16). That issue was related to (swedish) locale on the Dex.

"The dates from mongolab were coming across with a format of mm/dd/YYYY hh:mm:ss aa, BUT aa was 'fm' or 'em' instead of 'am'/'pm' and that was making it lose its mind.

My minute of googling didn't reveal what country uses those markers. Could you share?

In any case, I changed the date parsing code to try to handle it and got a graph after one last reset/download cycle."

@francescaneri
Copy link

@francescaneri
Copy link

scruple changed the format of 12/24 hours both your device and on dex but nothing has changed

@oschumac
Copy link

oschumac commented Mar 5, 2015

Hi i hust have double checked on this also.
ON my phone Samsung galaxy express Android 4.1.2 and Samsung tab3 8 Android 4.4.2 .
Germay locale on both devices.
NightScout 0.1.12 no graph.
After installing 0.1.10 the graph is back again.

CU Oliver

@francescaneri
Copy link

screenshot

I think the problem depends on what time of the European servers . It could at least be. Matteo

@francescaneri
Copy link

@trhodeos

var coll = db.collection('test');
var datetime = new Date();
console.log(datetime);
coll.insert({ "t": "foo", "d": datetime}, function(err, result){
if(err) throw err;
coll.findOne({ "t" : "foo" }, function(err, doc) {
console.log(doc.d);
});
});

try checking. thank

@trhodeos
Copy link
Contributor

What am I checking here?

On Tue, Mar 10, 2015 at 4:08 PM, Matteo Neri [email protected]
wrote:

@trhodeos https://github.com/trhodeos

var coll = db.collection('test');
var datetime = new Date();
console.log(datetime);
coll.insert({ "t": "foo", "d": datetime}, function(err, result){
if(err) throw err;
coll.findOne({ "t" : "foo" }, function(err, doc) {
console.log(doc.d);
});
});

try checking. thank


Reply to this email directly or view it on GitHub
#146 (comment)
.

@francescaneri
Copy link

@trhodeos ...for the problem of the graph. I asked for assistance in mongolab and a technician told me so I think it is a problem of European servers.
I state that no programmer.

@rnpenguin
Copy link
Contributor

was that point just populated at the time shown from the computer?

@francescaneri
Copy link

@rnpenguin yes. if I move about 1 hour / 2 I see the graph . I did a test by changing the time and putting a + 2GMT already with the time zone of London you see the graph (android uploader)
time that there is exactly the time of mongolab London +.000 when it should be gmt + 1.00.

@alexpop
Copy link

alexpop commented May 25, 2015

I'm on GMT+1 and I saw this issue a few days ago. I must have installed version 0.1.12 or an earlier release.

Then, I uninstalled the app, installed 'Dreamsicle (Release 0.1.13)', put both dexcom and phone on the correct time. Looks good, no more graph gap and 'in the future' label. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants