These are chat archives for nightscout/intend-to-bolus

8th
May 2016
Greg Scull
@komby
May 08 2016 00:41
last few times I have taken the Edison rig out for a walk (from the house) it has hung up and refused to update despite connecting to my phone hotspot.
Scott Leibrand
@scottleibrand
May 08 2016 00:43
What does that mean?
Greg Scull
@komby
May 08 2016 00:43
eventually I power cycled it by pulling the battery After pulling the battery it started uploading again
Scott Leibrand
@scottleibrand
May 08 2016 00:43
"hung up and refused to update"?
if you don't have wpa roaming set up properly, it might not switch wifi networks...
Greg Scull
@komby
May 08 2016 00:44
@scottleibrand not sure exactly but the dexdrip was uploading and i know that the edison had a hotspot connection to my iphone
Scott Leibrand
@scottleibrand
May 08 2016 00:45
Could you ssh to it from your phone?
Greg Scull
@komby
May 08 2016 00:45
so the xdrip kept reporting to nightscout but the openaps wouldnt
Scott Leibrand
@scottleibrand
May 08 2016 00:45
(how) do you know it was the Edison connected to the hotspot?
Greg Scull
@komby
May 08 2016 00:45
no i couldnt ssh to it. but I did have two devices connected to my hotspot
Scott Leibrand
@scottleibrand
May 08 2016 00:46
i would check your /etc/network/interfaces and compare to a working rig.
I think the default Edison wpa setup may be wrong for roaming.
Greg Scull
@komby
May 08 2016 00:47
Its a pretty reliable rig
Scott Leibrand
@scottleibrand
May 08 2016 00:47
Also check syslog
Greg Scull
@komby
May 08 2016 00:48
Ill try that next time. I shouldnt have rebooted it and just saved it for checking via the serial console
Scott Leibrand
@scottleibrand
May 08 2016 00:48
You can check logs after the fact.
Should be some good clues in there even after reboot.
Greg Scull
@komby
May 08 2016 00:52
scrolling now
Stephan
@MosiGitHub
May 08 2016 02:43
the loop stopped working after a sensor problem. When I was looking what the reason is, openaps was unable to rezone the pumphistory report (timestamp out of range). Now I used openaps use pump iter_pump_hours 1 and got the following crap. By the way the report is nearly endless and goes back to 21st of april 2016, but especially the beginning is crazy:

[
{
"_type": "PumpSuspend",
"_description": "PumpSuspend 2000-01-07T03:17:38 headangular/angular.io#1192, body[0] op[0x1e]"$
"timestamp": "2000-01-07T03:17:38",
"_body": "",
"appended": [
{

.
.
.
},
{
"_type": "PumpSuspend",
"_description": "PumpSuspend 2081-01-01T03:17:38 headangular/angular.io#1192, body[0] op[0x1e]",
"timestamp": "2081-01-01T03:17:38",
"_body": "",
"_head": "1e0a",
"_date": "2651e32151"
},
{
"_type": "NewTimeSet",
"_description": "NewTimeSet 2000-12-05T05:01:16 headangular/angular.io#1192, body[0] op[0x18]",
"timestamp": "2000-12-05T05:01:16",
"_body": "",
"_head": "1892",
"_date": "d001050500"
},
{
"_type": "ResultDailyTotal",
"appended": [
{
"_body": "",
"_head": "1592",
"_type": "Base",
"_date": "5bcc446715",
"_description": "Base (2021, 7, 7, 4, 12, 27) headangular/angular.io#1192, body[0] op[0x15]"
}
],
"_description": "ResultDailyTotal 2120-08-03T00:00:00 head[5], body[0] op[0x07]",
"timestamp": "2120-08-03T00:00:00",
"_body": "",
"valid_date": "2120-08-02",
"_head": "0710006006",
"_date": "8278"
},
{
"_type": "LowBattery",
"_description": "LowBattery 2064-06-16T07:21:38 headangular/angular.io#1192, body[0] op[0x19]",
"timestamp": "2064-06-16T07:21:38",
"_body": "",
"_head": "1977",
"_date": "66956710c0"
},
.
.
.

Stephan
@MosiGitHub
May 08 2016 03:29
so, finally I have no more ideas what to try next (except changing the pump) - has anybody a clue how to clear the pumphistory of the pump? maybe removing the batterie for an hour or so?
Ben West
@bewest
May 08 2016 03:29
mm-stick diagnose
are you using carelink stick?
Jason Calabrese
@jasoncalabrese
May 08 2016 03:30
I'm guessing the "angular/angular.io" junk is coming from gitter rendering
Ben West
@bewest
May 08 2016 03:30
@MosiGitHub it'd be better to continue collecting enough data to fix the issue
if you're using carelink usb, it'd be good to get the raw data: mm-send-comm.py --serial 123456 --init ReadHistoryData --save --page 0
Andrew Warrington
@andrew-warrington
May 08 2016 04:29
@timomer - 1pm on the 26th, my son and I will be there.
looking forward to it.
ddaniels1
@ddaniels1
May 08 2016 05:12
Got NS uploads working and can see loop now. Don't see temp basals or boluses displayed despite configuring: openaps upload-recent-treatments and uploading. Any idease?
Brian Bonner
@itsn0tm3
May 08 2016 05:14
my only idea could be that the zoned option isn't being done correctly so it's not showing up in the same time range? (just a guess on my part)
(I don't have a clue.. )
ddaniels1
@ddaniels1
May 08 2016 05:16
Possible as I was having time issues earlier, but now pumphistory.json and iob.json reflect the correct date and I do get an IOB accurate on NS so that seems less likely
Brian Bonner
@itsn0tm3
May 08 2016 05:16
oh
do you have pump history zoned?
let me fire up my pi and check out what I have
ddaniels1
@ddaniels1
May 08 2016 05:18
should you be able to see the temp basal and boluses on NS?
Brian Bonner
@itsn0tm3
May 08 2016 05:19
yes
do you have this?
format-latest-nightscout-treatments ! bash -c "nightscout cull-latest-openaps-treatments monitor/pumphistory-zoned.json settings/model.json $(openaps latest-ns-treatment-time) > upload/latest-treatments.json"
it requires pumphistory-zoned
thats why I'm wondering if that is part of your problem
ddaniels1
@ddaniels1
May 08 2016 05:21
yes I have that and have pumphistory-zoned
Brian Bonner
@itsn0tm3
May 08 2016 05:21
my pumphistory looks like:
[
  {
    "_type": "TempBasalDuration",
    "duration (min)": 30,
    "_description": "TempBasalDuration 2016-05-08T01:04:21 head[2], body[0] op[0x16]",
    "timestamp": "2016-05-08T01:04:21",
    "_body": "",
    "_head": "1601",
    "_date": "5544014810"
  },
  {
    "_type": "TempBasal",
    "temp": "absolute",
    "_description": "TempBasal 2016-05-08T01:04:21 head[2], body[1] op[0x33]",
    "timestamp": "2016-05-08T01:04:21",
    "_body": "00",
    "_head": "331b",
    "rate": 0.675,
    "_date": "5544014810"
my zoned looks like
[
  {
    "_type": "TempBasalDuration",
    "_description": "TempBasalDuration 2016-05-08T01:04:21 head[2], body[0] op[0x16]",
    "timestamp": "2016-05-08T01:04:21-04:00",
    "_body": "",
    "_head": "1601",
    "duration (min)": 30,
    "_date": "5544014810"
  },
  {
    "_type": "TempBasal",
    "temp": "absolute",
    "_description": "TempBasal 2016-05-08T01:04:21 head[2], body[1] op[0x33]",
    "timestamp": "2016-05-08T01:04:21-04:00",
    "_body": "00",
    "_head": "331b",
    "rate": 0.675,
    "_date": "5544014810"
  },
does yours match?
(notice the -04:00 part)
Iain
@iainct
May 08 2016 05:23
@ddaniels1 have you enabled it in the NS webpage options?
Brian Bonner
@itsn0tm3
May 08 2016 05:23
or it could be that easy....
:)
Iain
@iainct
May 08 2016 05:23
:-)
a general question, are you guys using heroku or azzure?
Brian Bonner
@itsn0tm3
May 08 2016 05:26
@ddaniels1 I'd go with what @iainct said and check your NS settings, that could just be it
ddaniels1
@ddaniels1
May 08 2016 05:26
Ah, here is my zoned:
"_type": "BasalProfileStart",
"_description": "BasalProfileStart 2016-05-07T21:37:20 head[2], body[3] op[0x7b]",
"timestamp": "2016-05-07T21:37:20+00:00",
"_body": "101400",
"profile_index": 2,
"_head": "7b02",
"rate": 0.5,
"offset": 28800000,
"_date": "5465150710"
},
{
"_type": "TempBasalDuration",
"_description": "TempBasalDuration 2016-05-07T21:37:20 head[2], body[0] op[0x16]",
"timestamp": "2016-05-07T21:37:20+00:00",
"_body": "",
"_head": "1600",
"duration (min)": 0,
"_date": "5465154710"
},
{
"_type": "TempBasal",
"temp": "absolute",
"_description": "TempBasal 2016-05-07T21:37:20 head[2], body[1] op[0x33]",
"timestamp": "2016-05-07T21:37:20+00:00",
"_body": "00",
"_head": "3300",
"rate": 0.0,
"_date": "5465154710"
},
{
"_type": "BasalProfileStart",
"_description": "BasalProfileStart 2016-05-07T21:31:17 head[2], body[3] op[0x7b]",
"timestamp": "2016-05-07T21:31:17+00:00",
"_body": "101400",
"profile_index": 2,
"_head": "7b02",
"rate": 0.5,
"offset": 28800000,
"_date": "515f150710"
},
{
"_type": "TempBasalDuration",
"_description": "TempBasalDuration 2016-05-07T21:01:17 head[2], body[0] op[0x16]",
"timestamp": "2016-05-07T21:01:17+00:00",
Iain
@iainct
May 08 2016 05:26
the '+' doesn't look right...
sorry, are you at GMT?
Brian Bonner
@itsn0tm3
May 08 2016 05:27
00:00? what state do you live in if I can ask?
ddaniels1
@ddaniels1
May 08 2016 05:27
matches the pumphistory.json
I am in California, PDT
Iain
@iainct
May 08 2016 05:28
what time zone is your pi?
ddaniels1
@ddaniels1
May 08 2016 05:28
PDT, I checked that earlier
Actually not PDT, just "Pacific New"
Iain
@iainct
May 08 2016 05:29
are your glucose reports also zoned?
e.g. the same zone?
Brian Bonner
@itsn0tm3
May 08 2016 05:30
california should be -07:00
so the timezone is off
ddaniels1
@ddaniels1
May 08 2016 05:30
Any idea where to fix this problem?
Brian Bonner
@itsn0tm3
May 08 2016 05:30
go into timezone settings and change to USA> Los Angeles
Pacific New for some reason doesn't sound right to me
ddaniels1
@ddaniels1
May 08 2016 05:31
in sudo raspi-config?
Brian Bonner
@itsn0tm3
May 08 2016 05:31
yes
internationlization options
Change timezone
pick America
then Los_Angeles
ddaniels1
@ddaniels1
May 08 2016 05:33
done, gives the same time stamp which is :smile: Current default time zone: 'America/Los_Angeles'
Local time is now: Sat May 7 22:32:47 PDT 2016.
Universal Time is now: Sun May 8 05:32:47 UTC 2016.
let me look at the reports again though
Brian Bonner
@itsn0tm3
May 08 2016 05:33
Ooooh
there's another place I can think of that might be off
lemme find it
not sure if it's still there
but check your openaps.ini
ddaniels1
@ddaniels1
May 08 2016 05:34
I wonder if it is with my tz device
Brian Bonner
@itsn0tm3
May 08 2016 05:34
find the timezone = line
and see what it says?
ddaniels1
@ddaniels1
May 08 2016 05:34
checking

var code = "formatted";

[report "monitor/pumphistory-zoned.json"]
use = rezone
reporter = JSON
astimezone = False
date = timestamp dateString start_at end_at created_at
adjust = missing
input = monitor/pumphistory.json
device = tz
timezone = UTC

Brian Bonner
@itsn0tm3
May 08 2016 05:37
ah there you go
you should fix all of your timezone = lines to say timezone = PDT
do you feel comfortable editing your openaps.ini?
ddaniels1
@ddaniels1
May 08 2016 05:37
What about when daylight savings is over? I thought the point of the TZ device was to adjust
Iain
@iainct
May 08 2016 05:37
@itsn0tm3 do you need to update the tz device when ever you travel to a new time zone..?
ddaniels1
@ddaniels1
May 08 2016 05:38
yes I can edit in nano
Brian Bonner
@itsn0tm3
May 08 2016 05:38
I'm not quite sure actually, Scott and Dana since they travel a lot would be the one to ask
there was some talk about fixing it somehow
Iain
@iainct
May 08 2016 05:38
righto, I will look into that
Brian Bonner
@itsn0tm3
May 08 2016 05:38
I think they just update the clock time via NTP but not sure if they change the TZ option still
I know some just take the clock time off their pump
Iain
@iainct
May 08 2016 05:39
i use the clockset.sh
works great offline
Brian Bonner
@itsn0tm3
May 08 2016 05:39
Scott did mention that the body can only change like 1 hour at a day or whatever, so it made more sense to just leave it or whatevver
I haven't travelled with my pump yet so I'm not sure at all
blah I mean OpenAPS
ddaniels1
@ddaniels1
May 08 2016 05:40
How does OpenAPS work for you? how long have you been using?
Iain
@iainct
May 08 2016 05:40
i'm outa here catch you guys later
Brian Bonner
@itsn0tm3
May 08 2016 05:40
g'day or g'nite!
ddaniels1
@ddaniels1
May 08 2016 05:40
thanks
Brian Bonner
@itsn0tm3
May 08 2016 05:40
@ddaniels1 Works great, my range is improving
I think I closed the loop March 1st or around then
was using the open loop for a while for testing and had to find a pump that was compatible since mine was too new
Scott Leibrand
@scottleibrand
May 08 2016 05:45
Try deleting the timezone from the ini instead of changing it.
Hmm, actually mine do say PDT, but I also have astimezone=False.
Not sure if that will be right for DST, but it hasn't been an issue updating timezone when traveling.
Brian Bonner
@itsn0tm3
May 08 2016 05:47
thats because NS stays in the same timezone right?
Scott Leibrand
@scottleibrand
May 08 2016 05:47
We dpkg-reconfigure tzdata (same as doing it through raspi-config) and then use clockset.sh
NS does everything in absolute times, so it doesn't care as long as things are zoned right.
Brian Bonner
@itsn0tm3
May 08 2016 05:48
hmm ok
Scott Leibrand
@scottleibrand
May 08 2016 05:49
Wonder if y'all have astimezone = True?
ddaniels1
@ddaniels1
May 08 2016 05:49
looking
Scott Leibrand
@scottleibrand
May 08 2016 05:49
Or if there's something else...
Brian Bonner
@itsn0tm3
May 08 2016 05:49
yeah I have it
but mine is set to false
ddaniels1
@ddaniels1
May 08 2016 05:50
[report "monitor/pumphistory-zoned.json"]
use = rezone
reporter = JSON
astimezone = False
date = timestamp dateString start_at end_at created_at
adjust = missing
input = monitor/pumphistory.json
device = tz
timezone = UTC
Scott Leibrand
@scottleibrand
May 08 2016 05:51
[report "monitor/pumphistory-zoned.json"]
use = rezone
reporter = JSON
astimezone = False
date = timestamp dateString start_at end_at created_at
adjust = missing
input = monitor/pumphistory.json
device = tz
timezone = PDT
ddaniels1
@ddaniels1
May 08 2016 05:51
ok, what about the other report with timezone:
[report "monitor/clock-zoned.json"]
use = clock
reporter = JSON
astimezone = False
date = None
adjust = missing
input = monitor/clock.json
device = tz
timezone = UTC
Brian Bonner
@itsn0tm3
May 08 2016 05:52
yea should change all UTC's to PDT
Scott Leibrand
@scottleibrand
May 08 2016 05:53
Other rig that was used last time we traveled:
[report "monitor/pumphistory-zoned.json"]
use = rezone
reporter = JSON
astimezone = False
date = timestamp dateString start_at end_at created_at
adjust = missing
input = monitor/pumphistory.json
device = tz
Notice missing timezone
Brian Bonner
@itsn0tm3
May 08 2016 05:54
interesting
Scott Leibrand
@scottleibrand
May 08 2016 05:54
I think that is what we want to be able to handle DST and tz changes.
Will need to get the tool or docs updated to do that by default.
Brian Bonner
@itsn0tm3
May 08 2016 05:54
that would make sense since it would follow the device tz
Scott Leibrand
@scottleibrand
May 08 2016 05:55
Yeah. Looks like I need to change all my rigs over. Glad we figured that out before our next trip. :-)
Brian Bonner
@itsn0tm3
May 08 2016 05:55
:)
ddaniels1
@ddaniels1
May 08 2016 05:55
running monitor-pump alias now and will look at output
bingo
"_type": "BasalProfileStart",
"_description": "BasalProfileStart 2016-05-07T22:31:44 head[2], body[3] op[0x7b]",
"timestamp": "2016-05-07T22:31:44-07:00",
"_body": "101400",
"profile_index": 2,
"_head": "7b02",
"rate": 0.5,
"offset": 28800000,
"_date": "6c5f160710"
},
{
"_type": "TempBasalDuration",
"_description": "TempBasalDuration 2016-05-07T22:01:44 head[2], body[0] op[0x16]",
"timestamp": "2016-05-07T22:01:44-07:00",
"_body": "",
"_head": "1601",
"duration (min)": 30,
"_date": "6c41164710"
},
{
"_type": "TempBasal",
"temp": "absolute",
"_description": "TempBasal 2016-05-07T22:01:44 head[2], body[1] op[0x33]",
"timestamp": "2016-05-07T22:01:44-07:00",
"_body": "00",
"_head": "330d",
"rate": 0.325,
"_date": "6c41164710"
},
{
"_type": "BasalProfileStart",
"_description": "BasalProfileStart 2016-05-07T21:37:20 head[2], body[3] op[0x7b]",
"timestamp": "2016-05-07T21:37:20-07:00",
"_body": "101400",
"profile_index": 2,
"_head": "7b02",
"rate": 0.5,
"offset": 28800000,
"_date": "5465150710"
},
{
"_type": "TempBasalDuration",
"_description": "TempBasalDuration 2016-05-07T21:37:20 head[2], body[0] op[0x16]",
"timestamp": "2016-05-07T21:37:20-07:00",
pumphistory-zoned.json
Brian Bonner
@itsn0tm3
May 08 2016 05:56
:)
ddaniels1
@ddaniels1
May 08 2016 05:57

related but separate question, in thinking about the order to run the commands I was thinking:

openaps monitor-pump
openaps suggest
openaps enact
openaps status-upload
openaps upload-recent-treatments

Make sense?

Brian Bonner
@itsn0tm3
May 08 2016 05:58
order looks right as long as monitor-pump gets all the things that the rest of it requires
(to me at least)
ddaniels1
@ddaniels1
May 08 2016 06:00
I noticed that the docs could stand with some clarification. For example pumphistory-zoned is required for the upload-recent-treatments but isn't in the docs clearly, figured it out while debugging
Brian Bonner
@itsn0tm3
May 08 2016 06:00
@danamlewis will be really happy if you do a PR to clarify it :)
Scott Leibrand
@scottleibrand
May 08 2016 06:00
Yeah, that is the basic flow. Make sure the monitor alias does a rm on your data files so you can't enact based on old data.
Yes, she will. :-)
(as will I and a few others) :-)
Brian Bonner
@itsn0tm3
May 08 2016 06:01
:)
Scott Leibrand
@scottleibrand
May 08 2016 06:02
There are lots of little things that need clarified, and we need people going through them for the first time to do so. Many of us have seen them too many times and can't see what's missing from a newbie's perspective.
ddaniels1
@ddaniels1
May 08 2016 06:04
I got it, still trying to wrap my head around it all, but I think I am actually starting to get it
I am making my notes and will update the docs once I'm sure it is right
So just repeated upload-recent-treatments and the bolus I gave an hour ago and the temp basal still not showing up. Any other ideas?
Brian Bonner
@itsn0tm3
May 08 2016 06:06
maybe what @iainct said was right, check your NS settings? Go to Settings, then scroll down to "Render Basal"
what do you see there?
(also it doesn't show up right away, takes 1 or 2 more updates to show up sometimes for me)
ddaniels1
@ddaniels1
May 08 2016 06:07
"Default"
Brian Bonner
@itsn0tm3
May 08 2016 06:08
oh hmm
ddaniels1
@ddaniels1
May 08 2016 06:08
I'm sure it is a timezone issue because of this:
blob
Scott Leibrand
@scottleibrand
May 08 2016 06:09
Might need to delete future entries
there's a sub-menu in NS
ddaniels1
@ddaniels1
May 08 2016 06:10
Those were temp basals that I was playing with early this morning and they showed up 7 hours later
Scott Leibrand
@scottleibrand
May 08 2016 06:10
the uploader checks most recent, and you have some from a few hours in the future.
Admin tools, remove future items from mongo
in the NS menu
ddaniels1
@ddaniels1
May 08 2016 06:12
i don't have that menu
NS 0.90 dev
Scott Leibrand
@scottleibrand
May 08 2016 06:13
Reports, profile editor, admin tools. Third one from the top.
If it's missing, you might need to authenticate with your secret
Brian Bonner
@itsn0tm3
May 08 2016 06:14
it should show up, I'm not authenticated and I see it
ddaniels1
@ddaniels1
May 08 2016 06:14
ok got it
Dana Lewis
@danamlewis
May 08 2016 06:16
Hooray for PRs and clarified docs ;) thx @ddaniels1 @itsn0tm3 :)
ddaniels1
@ddaniels1
May 08 2016 06:17
ok, removed. Should I be able to see boluses in NS if I do one now?
or only temp basals?
Dana Lewis
@danamlewis
May 08 2016 06:18
All pump activity should show
Boluses etc will be dots on the CGM line
ddaniels1
@ddaniels1
May 08 2016 06:19
ok and just to clarify, I should just have to do: monitor-pump, then upload-recent-treatments?
Dana Lewis
@danamlewis
May 08 2016 06:19
Same with any care portal entries
ddaniels1
@ddaniels1
May 08 2016 06:19
ok, familiar with care portal entries
Here is my monitor-pump alias:
monitor-pump report invoke monitor/clock.json monitor/pumphistory.json monitor/temp_basal.json monitor/pumphistory-zoned.json monitor/iob.json enact/suggested.json monitor/battery.json monitor/reservoir.json monitor/status.json monitor/clock-zoned.json
Dana Lewis
@danamlewis
May 08 2016 06:22
Yea
ddaniels1
@ddaniels1
May 08 2016 06:23
here is the output:
pi@raspberrypi:~/Documents/try5 $ openaps upload-recent-treatments
[{"bolus":{"programmed":0.2,"_type":"Bolus","_description":"Bolus 2016-05-07T23:21:25 head[8], body[0] op[0x01]","timestamp":"2016-05-07T23:21:25-07:00","_body":"","_head":"0100080008000800","amount":0.2,"unabsorbed":0.2,"duration":0,"type":"normal","_date":"5955576710"},"timestamp":"2016-05-07T23:21:25-07:00","created_at":"2016-05-07T23:21:25-07:00","eventType":"Correction Bolus","insulin":0.2,"notes":"Normal bolus (solo, no bolus wizard).\nProgrammed bolus 0.2\nDelivered bolus 0.2\nPercent delivered: 100%","medtronic":"mm://openaps/mm-format-ns-treatments/Correction Bolus","enteredBy":"openaps://medtronic/523"}]
Dana Lewis
@danamlewis
May 08 2016 06:23
Looks like enact/suggested.json is tucked in there. Shouldn't hurt, but you'll want to make sure it's in your enact alias too
Scott Leibrand
@scottleibrand
May 08 2016 06:24
Also, I don't see anything that deletes old stuff from the monitor directory.
ddaniels1
@ddaniels1
May 08 2016 06:24
how do I do that?
ddaniels1
@ddaniels1
May 08 2016 06:25
should I run that at the beginning of the alias? before the reports are invoked to make sure old data isn't acted on?
Scott Leibrand
@scottleibrand
May 08 2016 06:26
Yes
And you also need to refresh your profile at some point to pick up changes in which of your scheduled basals is active.
ddaniels1
@ddaniels1
May 08 2016 06:27
I was planning on automating gather-profile once an hour in case I change sensitivites, targets ect. Does that sound reasonable?
Scott Leibrand
@scottleibrand
May 08 2016 06:27
Or if you switch patterns or something. I do that at the end of my loop, after enacting.
Main challenge with a separate cron is making sure it doesn't overlap with your main one. Can only do one thing at a time with the stick.
ddaniels1
@ddaniels1
May 08 2016 06:29
got it, run everytime then, makes sense
Scott Leibrand
@scottleibrand
May 08 2016 06:29
And there is no guarantee your hourly refresh would be successful.
but some people do it that way.
ddaniels1
@ddaniels1
May 08 2016 06:29
OK, I see so I can run the gather alias as the first step in the loop? That should do it yes?
My bolus just showed up!!
Scott Leibrand
@scottleibrand
May 08 2016 06:30
Yeah. You can of course define and organize them however you want. Aliases are just convenient ways to group them.
Dana Lewis
@danamlewis
May 08 2016 06:31
:)
ddaniels1
@ddaniels1
May 08 2016 06:31
Ok, since I have the braintrust online I was thinking about an idea. The accuracy of the algorithm to an extent is dependent on the accuracy of the insulin sensitivity which is changing all the time.
What if, we make a report that totals the 24 hour insulin use and then recalculates the estimated insulin sensitivity based on the 1900 rule?
Dana Lewis
@danamlewis
May 08 2016 06:32
A) have you seen auto sensitivity? :)
ddaniels1
@ddaniels1
May 08 2016 06:32
then that is fed back to the bg_sensitivity json
Dana Lewis
@danamlewis
May 08 2016 06:33
Possibly not because it's an advanced feature, but you'll like the idea because it's similar
ddaniels1
@ddaniels1
May 08 2016 06:33
how do I find out about that?
Also, for that matter meal assist?
Dana Lewis
@danamlewis
May 08 2016 06:34
And b) we are talking about improving it further, so as you read into auto sensitivity, you should also look at/add feedback to 99 which is a proposal for further improving it
Scott Leibrand
@scottleibrand
May 08 2016 06:34
That's oref0 issue openaps/oref0#99
Dana Lewis
@danamlewis
May 08 2016 06:34
A lot of these have been logged as "issues" under oref0. On phone so hard to dig, but go to openaps/oref0, look under issues. 99 is open, but look under closed to see some of the ideation around meal assist and advanced meal assist
Scott Leibrand
@scottleibrand
May 08 2016 06:35
Curious about this 1900 rule. How would that work?
ddaniels1
@ddaniels1
May 08 2016 06:35
It's an old school way of estimating your insulin sensitivity. 1900/TDD = sensitivity
Dana Lewis
@danamlewis
May 08 2016 06:36
Most of these are not well documented because they've been in dev, but there's a hint at the end of the setup docs: https://openaps.readthedocs.io/en/latest/docs/walkthrough/phase-6/advanced-features.html
And as we do a new release of oref0 dev coming soon, we'll need to improve the docs to correlate better with what's default in master and what's possible to enable as these advanced features
ddaniels1
@ddaniels1
May 08 2016 06:36
Because the total daily dose (TDD) is constantly changing, so will the sensitivity. Illness being a good example
Dana Lewis
@danamlewis
May 08 2016 06:37
Tdd is also a reflection of various carb intake and activity level, though
(But once we set plumbing up better for auto sensitivity and then improved basal tuning, could easily swap in your own sensitivity algorithm if it works better for you than what we put in)
ddaniels1
@ddaniels1
May 08 2016 06:38
true, certainly not perfect. A method of tracking changes at night in response to temp basal adjustements when there should be no COB is maybe another way
Dana Lewis
@danamlewis
May 08 2016 06:39
Yep look at 99 and all related :)
We have some ideas about how to calculate and exclude carb activity time frames
But also about doing some averages to blend over the gaps so you still get an improved estimate for the time period when carb acidity may take place
Scott Leibrand
@scottleibrand
May 08 2016 06:42
Would be interesting to run some historical reports and compare how autosens and the 1900 rule compare. They might be pretty close, in which case we might want to make the 1900/TDD thing more of a default, with the #99 autosens stuff as an advanced version...
Brian Bonner
@itsn0tm3
May 08 2016 06:55
Good night, and thank you all for still bringing a smile to my face every morning :)
Dana Lewis
@danamlewis
May 08 2016 06:55
:)
ddaniels1
@ddaniels1
May 08 2016 07:03
another nifty thing is a way to see the %deviation of BGs to the CGM. If the BGs that are entered to calibrate are communicated to the share server and available a % deviation could be continuously updated on NS perhaps and used by the algorithm to adjust the target glucose. For example, shoot for higher if the deviation is high to avoid lows
Stephan
@MosiGitHub
May 08 2016 08:00
@bewest Hi Ben, thanks for your advise to collect some data - that helped 👍😀 because it was in the middle of the night (around 5:30 AM local time) I gave up and went to bed. Just tried it again after breakfast and it is working again. It is a RIG with an ERF by the way. Have a nice sunday.
Ben West
@bewest
May 08 2016 08:01
ah, I see :-)
yeah, I'm sorry weird things happen from time to time
if I were smarter, I'd make some kind of post-mortem diagnostic tool
Stephan
@MosiGitHub
May 08 2016 08:08
😀😀😀
@jasoncalabrese you asked who is on DEV yesterday. I just set up a rig with AMA, but then I recognized that there are more changes necessary from MA and auto-sense than I expected. So I will continue to work on it the next days if time permits.
Alex Kuzmanov
@alexkuzmanov
May 08 2016 11:07
@xpucuto Когато стратираме $ ns-upload $NIGHTSCOUT_HOST $API_SECRET devicestatus.json monitor/upload-status.json Като вече имаме дефинирани сайт и парола излиза грешка: Input file entries.json does not exist.
Hristina Dimova
@xpucuto
May 08 2016 11:08
@alexkuzmanov пиши ми на лично съобщение, аз ти писах просто ми отговори.
Matthias
@ceben80
May 08 2016 11:30
@xpucuto .....what :astonished: ..... :smile: :smile: :smile:
Hristina Dimova
@xpucuto
May 08 2016 11:30
sorry it was a mistake
:blush:
they setting up openaps and im trying to help but so far i dont want to spam the chat here , if i can not help we will continue here ;)
Matthias
@ceben80
May 08 2016 11:32
:wink:
Hristina Dimova
@xpucuto
May 08 2016 11:33
@ceben80 can you give a link with the Edison module , i have 3 different ones i n thelocal distributor and im not sure which one is the correct ?
can be german no problem
Matthias
@ceben80
May 08 2016 11:34
just a sec
Hristina Dimova
@xpucuto
May 08 2016 11:34
ok
Hristina Dimova
@xpucuto
May 08 2016 11:36
ok i found it i have the same. Do you know the difference between the internal and external antenna?
Matthias
@ceben80
May 08 2016 11:39
not really must pass this question to @/all regards the antenna....
Hristina Dimova
@xpucuto
May 08 2016 11:40
ok i didnt find info and wa curious about it .
probwaj towa
This message was deleted
sorry again.
Tim Howard
@tghoward
May 08 2016 11:46
@xpucuto , Yes, I think that's the one you want. For comparison, here's the source that a lot of US folks have gone to:
I think they all have the on board antenna -- for some reason they are just saying it in the title? I can't find any that do not.
Hristina Dimova
@xpucuto
May 08 2016 11:48
@tghoward here it is with an external antenna
https://store.comet.bg/CatalogueFarnell/Product/1549888/
Tim Howard
@tghoward
May 08 2016 11:51
Thanks. The spec sheet on that page mostly describes the breakout board, not the Edison. So I'm still not sure what they are describing
Hristina Dimova
@xpucuto
May 08 2016 11:53
aha ok , if everybody is using this one i suppose it ithe right one so i will be ordering it tomorrow so i can get my mobile loop as small as possbile :)
Tim Howard
@tghoward
May 08 2016 11:53
I have a feeling they are selling you a connector, but showing a picture of the edison ...
Tim Howard
@tghoward
May 08 2016 11:56
ah .. ok ... looking
Tim Howard
@tghoward
May 08 2016 12:04
This must be an EU thing? but, what you'll end up needing is the internal wifi and the internal ble antennas. The TI stick (or erf) you will need to add on no matter what. It looks like both have wifi and ble, but to be safe I'd still get the internal antenna version.
The breakout board, which connects to the edison, will be where you connect the TI stick.
Hristina Dimova
@xpucuto
May 08 2016 12:07
thanks for the clarification, this is gettin pricy. But health has no price ;)
Tim Howard
@tghoward
May 08 2016 12:08
Agree! Good luck with the orders.
Hristina Dimova
@xpucuto
May 08 2016 12:08
thank you :)
timomer
@timomer
May 08 2016 12:55
@andrew-warrington @colinlennon great! Will contact you with location soon - im not sure if there is anyone else who would be good to inform, please invite anyone else you talk too
Pete Schwamb
@ps2
May 08 2016 13:06
Wondering if anyone has an extra battery cap for a medtronic pump (maybe from an old broken pump?). Got a pump off craigslist and the seller somehow misplaced the cap. I think the caps are interchangeable amongst various models.
Hristina Dimova
@xpucuto
May 08 2016 13:09
all the caps are the same for the medtronic pumps except 640G, i bought one from the local distributor as my old one was causing problems and pump wasnt working.
if you have a pump under warranty i am sure medtronic will send a new one .
Pete Schwamb
@ps2
May 08 2016 14:39
Thanks, I’ll try that.
Hristina Dimova
@xpucuto
May 08 2016 14:42
:+1:
Sulka Haro
@sulkaharo
May 08 2016 15:25
Bizarre new Edison / Ubilinux issue. The loop started failing all of a sudden, when when trying to log to the Edison, I'm getting "fatal: Access denied for user xxx by PAM account configuration" on the account I've used for the longest time
Sulka Haro
@sulkaharo
May 08 2016 15:41
Right, forced fsck on boot, login now work
Scary
Scott Leibrand
@scottleibrand
May 08 2016 16:18
@xpucuto @alexkuzmanov awesome to see OpenAPS getting enough traction to occasionally see conversations in languages I can't even identify. :-)
Hristina Dimova
@xpucuto
May 08 2016 16:20
A lot of people got inspired from my success so expect many Bulgarians to start asking questions . I will do my best to share my experience but I still need help myself.
Scott Leibrand
@scottleibrand
May 08 2016 16:32
:-D
Scott Leibrand
@scottleibrand
May 08 2016 16:58
@TC2013 rebooting the Edison doesn't get rid of the blinky green charge light for me.
The left power light blinks off once, but the flashing never stops until I unplug the USB power.
Dana Lewis
@danamlewis
May 08 2016 17:56
WSJ article referencing #OpenAPS. (Online now, probably tomorrow’s paper.) TY to everyone who’s contributed to this work & this community :) <3 https://twitter.com/danamlewis/status/729367152046657536
Brian Bonner
@itsn0tm3
May 08 2016 18:21
:+1:
ruud de rooij
@ruuddotorg
May 08 2016 19:09
Just read the article. Awesome to get this exposure in the mainstream media! 🌟
Dana Lewis
@danamlewis
May 08 2016 19:10
:+1: :clap:
Brett
@burgertime14
May 08 2016 19:22
finally have all of the HW, and got a good start, but I am stuck. following the docs and running " openaps vendor add openapscontrib.timezones" getting the error that openapscontrib.timezones does not appear to be an importable python module...any guidance?
Scott Leibrand
@scottleibrand
May 08 2016 19:25
That got asked and answered yesterday. Try searching gitter?
and then we need to fix the package or the docs to avoid tripping up the next person. If you want, you can submit a PR to fix the docs until @bewest gets the package dependencies fixed (if he can)
Dana Lewis
@danamlewis
May 08 2016 19:30
(If you're having trouble searching, the web interface of gitter is a little better for finding previous convos using the search feature)
Brett
@burgertime14
May 08 2016 19:37
If is a known issue, I will work through figuring it out or wait until someone with more knowledge. The conversation about the issue on glitter expects someone with more knowledge on the topic than this n00b
Scott Leibrand
@scottleibrand
May 08 2016 19:40
You just have to install one dependency. You can find that conversation on gitter.im a lot easier than we can on our phones.
Ben West
@bewest
May 08 2016 19:41
that one is just sudo pip install openaps-contrib
Brett
@burgertime14
May 08 2016 19:43
thanks, going to have to work on Python fu, as a CSCI grad from the early 90s it is not my native tongue
although, I had already tried that one to no avail, I am close enough to the beginning to do a make clean and start again, in case i missed something
thanks for the quick responses, looking forward to getting up to speed and hopefully being more help than burden ;)
jaylagorio
@jaylagorio
May 08 2016 19:55
Speaking of hardware, I might finally have a line on a reasonably priced OpenAPS-compatible pump. Am I reading correctly on the Hardware page (http://openaps.readthedocs.io/en/master/docs/walkthrough/phase-0/hardware.html) that any 722 is compatible and I don't need to worry about firmware revision? Have you guys seen cases of 722s that have firmware that's too new?
Dana Lewis
@danamlewis
May 08 2016 19:55
Correct
Any 722 will be fine
Not a guy, though ;)
jaylagorio
@jaylagorio
May 08 2016 19:56
Awesome
I'll take an answer from you regardless!
Dana Lewis
@danamlewis
May 08 2016 19:57
;)
jaylagorio
@jaylagorio
May 08 2016 19:57
"Guys" is my version of "y'all" since I'm not southern
Dana Lewis
@danamlewis
May 08 2016 19:58
It's hard to tell when you're addressing a subgroup though ;)
jaylagorio
@jaylagorio
May 08 2016 19:59
Noted!
Dana Lewis
@danamlewis
May 08 2016 19:59
Thx :)
Did you find the 722 via craiglist or ?
Brett
@burgertime14
May 08 2016 20:01
@danamlewis I was able to get a compatible 723 via reddit /r/diabetes
Dana Lewis
@danamlewis
May 08 2016 20:02
Wow @burgertime14 good to know! We'll probably see a flurry of people so nice to have a new potential avenue for sourcing compatible pumps
If someone else has success there that may be something to mention on hardware page of docs
jaylagorio
@jaylagorio
May 08 2016 20:04
I found one on Medwow
Some of the prices are a little on the outrageous side but I found one in the price area that's comfortable for me
It's a 722 that was manufactured in 2011
Dana Lewis
@danamlewis
May 08 2016 20:05
Oh good glad there are new sellers on there, for a while it seemed like there were no (compatible) pumps up for sale
Brett
@burgertime14
May 08 2016 20:05
@danamlewis I had a couple of others message me that they were looking for one as well, I am afraid that there will be less of them available with UHC forcing medtronic on its policy holders and Medtronic offering the $500 credit for trade-in
jaylagorio
@jaylagorio
May 08 2016 20:06
I don't know if that rings any bells in terms of when Medtronic started locking stuff down. Are they not disabling the remote temp basil feature when those go back to the company?
@burgertime14 That $500 credit is what made me send my old pump in last time around. Had I known about this I never would have done it (I don't even know if it would have been OpenAPSable)
Dana Lewis
@danamlewis
May 08 2016 20:06
@jaylagorio they do. So if someone has a pump, it's one that didn't go back to manufacturer. Not everyone turns them in when their warranty expires
@burgertime14 that shouldn't impact the current number of them out there since the firmware stuff happened several pumps ago .
Ben West
@bewest
May 08 2016 20:07
maybe we should put a standing offer for $600 to make sure there's an incentive not to send it to medtronic
Dana Lewis
@danamlewis
May 08 2016 20:07
The switch happened in the middle of 523s and 530g is the standard prescribed model now
:+1: @bewest
jaylagorio
@jaylagorio
May 08 2016 20:08
Right, I get that. The way the hardware page is worded it looks like they'll referb/disable and resell 723s. But when someone sends a 722 in they don't referb and resell those? What do they do with them?
Dana Lewis
@danamlewis
May 08 2016 20:08
Although I don't know many ppl think to sell as an alternative
Brett
@burgertime14
May 08 2016 20:09
They want to keep them off the market, so people have to go direct
Dana Lewis
@danamlewis
May 08 2016 20:09
@jaylagorio they will resell but they won't be compatible.
jaylagorio
@jaylagorio
May 08 2016 20:10
That makes sense. Does that mean there's a firmware version on the 722 that indicates it won't work for OAPS?
Dana Lewis
@danamlewis
May 08 2016 20:10
@jaylagorio feel free to pr to the hardware page if the language needs clarifying!
No. All 722s are fine. If a 722 goes back to Medtronic it won't come out as a 22.
jaylagorio
@jaylagorio
May 08 2016 20:11
Ah, OK - that was the detail I needed. I didn't realize they would put it back out into the world with a different model number.
Dana Lewis
@danamlewis
May 08 2016 20:11
They'd get a 723 or a 730, either of which would not be compatible with openAPS
jaylagorio
@jaylagorio
May 08 2016 20:11
Thank you!
Dana Lewis
@danamlewis
May 08 2016 20:11
Yup!
Brett
@burgertime14
May 08 2016 20:14
@bewest @scottleibrand @danamlewis -- I cleaned up my install and started over building from source, and the "openapscontrib.timezones doesn't seems to be an importable python module" did not reappear. Assuming that either the src build is ok, or someone committed the fix. Either way, thanks.
Ben West
@bewest
May 08 2016 20:15
@burgertime14 try sudo pip install openaps-contrib first
sounds like you don't have openaps-contrib installed
can verify by trying pydoc openapscontrib which should bring up a page explaining the contents of the code, or an error
Brett
@burgertime14
May 08 2016 20:18
@bewest I was just documenting that taking the build from source path worked and everything is good. I have been able to continue to move forward.
ddaniels1
@ddaniels1
May 08 2016 20:19
I'm having difficulty understanding what "SnoozeBG" refers to, help?
Dana Lewis
@danamlewis
May 08 2016 20:20
@ddaniels1 under bolus snooze in reference design: https://openaps.org/reference-design/
ddaniels1
@ddaniels1
May 08 2016 20:21
I read that but what does the number refer to, is that the projected BG after the snooze period?
Dana Lewis
@danamlewis
May 08 2016 20:23
It's the eventual BG adjusted for snooze bolus iob
(On phone in grocery story, sorry for being cryptic, will circle back later if no one else does)
ddaniels1
@ddaniels1
May 08 2016 20:23
I see, but I did not give a bolus so why is it present? does it take into account the temp basal iob?
Scott Leibrand
@scottleibrand
May 08 2016 20:36
If snoozeBG is different from eventualBG, then there's been a bolus in the last DIA/2 hours.
ddaniels1
@ddaniels1
May 08 2016 20:53
Ok, I did give
Didn't give but somehow different numbers. I'll investigate a bit and then ask again thanks
my mistake, same number, but what does this mean?
{"temp":"absolute","bg":125,"tick":"+4","eventualBG":111,"snoozeBG":111,"reason":"Eventual BG 111>100, temp 0.85 >~ req 0.62U/hr"}
suggested.json (END)
temp 0.85 >~ req 0.62U/hr". IF it is more than required why isn't another lower temp basal suggested?
Brian Bonner
@itsn0tm3
May 08 2016 20:56
because it's close enough
thats what the ~ means
ddaniels1
@ddaniels1
May 08 2016 20:57
got it, just want to understand all the various possible outputs so I trust what is going on. I'm sure it's all right, but only makes sense to be cautious given the implications
Brian Bonner
@itsn0tm3
May 08 2016 20:58
agreed, it's always good to make sure you understand what is happening
Dana Lewis
@danamlewis
May 08 2016 20:58
Snooze = eventual, so no snooze happening. What's the usual basal? That one probably (?) has less than 30 min to run, so better to let it continue than set a lower temp that would have to run longer, especially if it would ultimately do same amount of insulin.
That's the long way of what @itsn0tm3 says ;)
ddaniels1
@ddaniels1
May 08 2016 20:59
I was thinking of inventing some glucose.json outputs to test all the various possibilites and then publishing that for people to really understand.
Brian Bonner
@itsn0tm3
May 08 2016 21:00
That would be cool, it would help people starting out to understand what COULD happen if THAT happened, and so on
Dana Lewis
@danamlewis
May 08 2016 21:00
That would be great to do as unit tests @ddaniels1 :)
ddaniels1
@ddaniels1
May 08 2016 21:04
ok cool, once I get this all wired I am going to write a number of things that may help non programmers. I agree that just handing people an executable script is a bad idea given the implications from our wonderful regulatory agency, but just because someone doesn't use the command line for their livelihood doesn't mean they should be excluded
Brian Bonner
@itsn0tm3
May 08 2016 21:06
That is one of the things that @bewest is working on I think
Dana Lewis
@danamlewis
May 08 2016 21:06
Exactly. And more help making it possible to achieve this vision is definitely needed :)
Brian Bonner
@itsn0tm3
May 08 2016 21:06
he's making templates
Dana Lewis
@danamlewis
May 08 2016 21:06
But even fixing docs as you go would be great, too
While it is fresh and top of mind
Brian Bonner
@itsn0tm3
May 08 2016 21:06
(nods) which reminds me, I probably need to do a few PR's myself ha
Dana Lewis
@danamlewis
May 08 2016 21:07
:D
Waiting with confetti for them ;)
Brian Bonner
@itsn0tm3
May 08 2016 21:07
;)
Ben West
@bewest
May 08 2016 22:12
@itsn0tm3 like this? http://labs.tidepool.io:8083/
regarding regulatory, it's important to note they haven't restricted us in any way. the way they operate is via official correspondence using letters that are permanently archived. the one thing they've asked us to do and we haven't done is send them letters on a fairly regular basis to provide a way to discuss openaps and similar projects. if they don't like what you're doing, they send a letter, generally
Brian Bonner
@itsn0tm3
May 08 2016 22:22
@bewest That was exactly what I was thinking of, I was playing with it earlier today
I don't refer that many people to it though since it's not THAT intuitive to use
ddaniels1
@ddaniels1
May 08 2016 22:24
PS- I am the cardiologist
Thanks to all of you for helping me! you are fantastic!
Dana Lewis
@danamlewis
May 08 2016 22:27
:)
ddaniels1
@ddaniels1
May 08 2016 22:28
my "PS" was in reference to the WSJ article btw
Dana Lewis
@danamlewis
May 08 2016 22:28
Ya
Lori
@LoriLori
May 08 2016 22:31
Andrew Baugh
@baughaw
May 08 2016 22:32
@danamlewis Question: Is there any documentation on tips and tricks for OpenAPS? For example: I know you gave some advice on how to cancel the temp basal when you are showering so that it doesn't count against your IOB calc. I would love any other advice/experience you have that might be useful.
Dana Lewis
@danamlewis
May 08 2016 22:45
Hm. Not written up in one place but if you give me a starter list of tips you'd like (and super bonus points if you email it to me), I'll Pr a page into the docs
Or file it as an issue and tag me, either way
Then others can add to it. Imagining it'll go in phase 6
Dana Lewis
@danamlewis
May 08 2016 22:51
(Gitter is not how things get added to my to-do list so throwing that out as a disclaimer :))
Andrew Baugh
@baughaw
May 08 2016 22:52
sure let me see what I can come up with and I will email it over. Thx :)
Dana Lewis
@danamlewis
May 08 2016 22:54
Perfect thx