These are chat archives for nightscout/beta

12th
Nov 2014
Greg Waehner
@gregwaehner
Nov 12 2014 03:45
Hey Kevin ... just got home and connected 0.1.10 android-uploader to my test receiver Adult Dex w/505 to website running 0.5.1 via REST API. (gcwtest.azurewebsites.net). I'll let it run overnight. If there's anything specific you want me to try, let me know. Upgraded over 0.1.9 no problem and maintained the configuration. Connect to dex fine. All green status lights. Graph in android-uploader working.
Kevin Lee
@ktind
Nov 12 2014 03:46
awesome. make sure to select "calibrations" and "sensor" data to upload
Greg Waehner
@gregwaehner
Nov 12 2014 03:46
Did that before. Thanks. Already did a calibration. Received the alert on my Pebble via Pushover.
and i see it on the cgm-remote-monitor browser gui
Kevin Lee
@ktind
Nov 12 2014 03:47
Great =)
Patrick Drews
@pgdrews
Nov 12 2014 03:47
I had no issues doing the APK update as well to 1.10
Kevin Lee
@ktind
Nov 12 2014 03:47
FYI - I'm suggesting that we use signed APKs from this point on
only a few members of the team have the key to sign the APK
Patrick Drews
@pgdrews
Nov 12 2014 03:48
Worked with a newly updated Dex with in the first reading or two after 2 hr startup. Nice!
Kevin Lee
@ktind
Nov 12 2014 03:48
0.1.9 fixed that =)
Patrick Drews
@pgdrews
Nov 12 2014 03:49
I noticed that when you disconnect from Dex the uploader still shows green Battery and time icon. If close app and reopen it resets completely.
Very minor in my mind.
Kevin Lee
@ktind
Nov 12 2014 03:50
yeah - I debated that when I added the code for it
for some reason I thought leaving the battery in its last state was good
same for time sync indicator
Greg Waehner
@gregwaehner
Nov 12 2014 03:51
Kevin - unrelated to this 1.10... wanted to run an idea by you re: next uploader.... with the planned demise of "mongodb" upload, and introduce of mqtt and baseline of REST API... a couple of thoughts... and I can put them as github feedback if you want.
  1. We will need to migrate the masses off of mongodb upload before any release b/c their websites won't be setup for REST api
  2. I don't know how mqtt works n detail, but many people use mongodb and rest via primary and dr sites. Would like to ensure there is a "multi destination" upload either via "mqtt + rest" or "rest + rest" or "mqtt + mqtt"... and each primary vs. DR site would need fully separate port/url/credential, etc.
Patrick Drews
@pgdrews
Nov 12 2014 03:51
I'm more concerned in indicators hooking up. Care less about when disconnect.
Kevin Lee
@ktind
Nov 12 2014 03:53
@gregwaehner I started a thread in the core group regarding #2. I'm sure some wifi hotspots (like schools) might block mqtt as it isn't as common as HTTP
Patrick Drews
@pgdrews
Nov 12 2014 03:53
I went back to Ped receiver for the night. Will reconnect new 505 in the early morning when heading back to work. Excited to see any better accuracy, but don't want to mess with possible off values for the first night after update.
Kevin Lee
@ktind
Nov 12 2014 03:53
a deprecation of mongo would be a little more gradual - like we'd give them a warning in the next release - IMO
I can fix that @pgdrews
Greg Waehner
@gregwaehner
Nov 12 2014 03:54
@ktind Yes. I saw the thread. So for example, if REST API, then would like to ensure 2 "REST API" configurations... one for primary and one for backup.
Kevin Lee
@ktind
Nov 12 2014 03:54
I'll add an issue
oh
@gregwaehner I see. The uploader code hasn't been refactored yet. If I recall correctly, it MIGHT be able to handle multiple end points now - I think a space is the delimiter
Greg Waehner
@gregwaehner
Nov 12 2014 03:55
b/c I know I do, and I think Patrick does too... on my primary uploader I send to school with daughter... it uploads via mongo to "site 1" and rest to "site 2" which are in different regions, hosting, etc. in case of network outage, coast outage, etc.
Kevin Lee
@ktind
Nov 12 2014 03:56
@pgdrews that would just be silently added to either the next hotfix or major release. it wouldn't be something that is pushed out alone
Greg Waehner
@gregwaehner
Nov 12 2014 03:56
@ktind interesting. I'll give that a try. I wasn't even thinking about a delimiter in one configuration element. But I like that... will try it out tomorrow after I get you solid data run overnight with 0.1.10
Kevin Lee
@ktind
Nov 12 2014 03:57
the REST api is kinda convoluted with the multiple version support
I think it is referred to as legacy and /v1?
Greg Waehner
@gregwaehner
Nov 12 2014 03:57
yes... I honestly never used legacy
Kevin Lee
@ktind
Nov 12 2014 03:58
heh, someone out there does - we have it reported to google analytics =)
we wanted to strip it out but didn't know how many people it would impact
Patrick Drews
@pgdrews
Nov 12 2014 03:59
Yep. I have my sites split for DR purposes. My main prod site is on Rackspace for Mongo and my DR is on AWS for mongo with REST API uploading.
I haven't tested it, but in theory you should be able to add multiple rest endpoints
Greg Waehner
@gregwaehner
Nov 12 2014 04:00
interesting re: "legacy" b/c cgm-remote-monitor 0.5.1 only has "app.use('/api/v1', api);".. no other "api" url mapping that I can see.
Kevin Lee
@ktind
Nov 12 2014 04:01
oh, heh
maybe there is a bug in our reporting
Greg Waehner
@gregwaehner
Nov 12 2014 04:01
or a defect in my reading the code :-)
Kevin Lee
@ktind
Nov 12 2014 04:02
well
actually, I'm leaning to a bug in our code
I'm not seeing anything OTHER than legacy being used lol
Greg Waehner
@gregwaehner
Nov 12 2014 04:02
in either case, sounds like the REST API already handles my thought, so like normal, you're ahead of me.
@ktind ok. I'm checking out. if you need anything, you have my email (greg.waehner@gmail.com), I'll check here, and FB (gregwaehner). Thanks Kevin.
Kevin Lee
@ktind
Nov 12 2014 04:04
Thank you for testing!
Greg Waehner
@gregwaehner
Nov 12 2014 04:05
and the test site is https://gcwtest.azurewebsites.net
Kevin Lee
@ktind
Nov 12 2014 04:09
I'm checking out as well - my day starts early tomorrow and I get to deal with SAP design discussions all day tomorrow...
my email is klee24@gmail.com
Greg Waehner
@gregwaehner
Nov 12 2014 12:57
@ktind Beta Uploader 0.1.10 ran fine overnight. Just disconnect @ 7:55am ET. Data usage -- 13.44 MB. (and I did not see any other "app update" notifications.
Ross Naylor
@rnpenguin
Nov 12 2014 19:29
huhuhuhu 13.44???
Jason Calabrese
@jasoncalabrese
Nov 12 2014 19:30
maybe updating some apps while on wifi?
Ben West
@bewest
Nov 12 2014 19:32
@gregwaehner are you saying nightscout used > 10MB data in less than a day? we definitely don't expect that... we spent like 2 weeks on similar issue...
Greg Waehner
@gregwaehner
Nov 12 2014 23:53
Hey guys - back from work. that was the MB # the phone gave me this morning from Data Usage. I was on wi-fi yes. I just scrolled the data usage to get something close to the #. (Data Usage doesn't give me hour by hour slide bar). But the nightscout usage was only 0.90 MB... so that was my mistake early in the AM before full cup of coffee. Sorry about that.
Pebble was 4.63MB
FB 1.78MB
Messenger 1.03MB
then Nightscout @ 0.90MB
Ben West
@bewest
Nov 12 2014 23:54
ah, cool
phew
Greg Waehner
@gregwaehner
Nov 12 2014 23:54
then Android OS @ 673KB.. and etc.
so if roughly 12 hours.... that would be 0.075 MB per hr... rough math
Ben West
@bewest
Nov 12 2014 23:56
yeah, that's roughly what we expect
or in line with what we expect and have been seeing
for now