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

3rd
Sep 2017
peterfulvi
@peterfulvi
Sep 03 2017 00:49
I have a question?
Sorry
Is there a way to sync
peterfulvi
@peterfulvi
Sep 03 2017 00:55
Is there a way to sync the ntp. My problem is I just got a new transmitter from dexcom and tried to get my other rig fired up again which originally was loopinig offline with xdrip .So I have everything setup but it won't sync with the current time. I tried connecting to the Internet which works but soon as I connect it to my phone (which I
Which is my Hotspot I goes back to Jan 2 2000. Is there a manual way to sync it. I had this problem before and it will iron out but it's been 2 dalso
Martin Haeberli
@mhaeberli
Sep 03 2017 01:01

@kcrcgm - I haven’t coded the .sh commands for you, but if you get an http-refresh header into the start of your file, it will auto-refresh at some frequency, specified in seconds. For example, see

<meta http-equiv="refresh" content="5" />
17:58<br>
COB: 0, Dev: 23, BGI: -2.91, ISF: 29, Target: 82, minPredBG 208, IOBpredBG 208; Eventual BG 212 >= 94, adj. req. rate: 10.9 to maxSafeBasal: 5.76, no temp, setting 5.75U/hr.<br>
TBR: 5.75<br>
IOB: 1.287<br>

so this will refresh every 5 seconds. so if you can get your index.html to look like this, by changing http.sh, then it will auto-refresh

Scott Leibrand
@scottleibrand
Sep 03 2017 01:30
@peterfulvi oref0-set-system-clock sets the rig time to match the pump time.
peterfulvi
@peterfulvi
Sep 03 2017 01:38
@scottleibrand can i run that manually somehow?
Scott Leibrand
@scottleibrand
Sep 03 2017 01:44
Yeah, just type it.
It needs a current clock.json.
peterfulvi
@peterfulvi
Sep 03 2017 02:07
@scottleibrand thanks
peterfulvi
@peterfulvi
Sep 03 2017 02:43
@scottleibrand this is my output when i run it
Starting pump-loop at Sun Jan 2 20:52:02 EST 2000:
Waiting up to 4 minutes for new BG: ...^C
root@petersrig2:~# oref0-set-system-clock
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
Restarting ntp (via systemctl): ntp.service.
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
cat: monitor/clock-zoned.json: No such file or directory
Setting system time to later of Sun Jan 2 20:54:00 EST 2000 or :
cat: monitor/clock-zoned.json: No such file or directory
(date +%s; date -d  +%s) | sort -g | tail -1 | while read line; do sudo date -s @$line; done;
cat: monitor/clock-zoned.json: No such file or directory
date: invalid date β€˜+%s’
Sun Jan  2 20:54:00 EST 2000
Scott Leibrand
@scottleibrand
Sep 03 2017 02:44
Looks like that rig hasn't talked to the pump lately: no clock-zoned.json
peterfulvi
@peterfulvi
Sep 03 2017 02:46
i ran cat clock.json and got the right date and time "2017-09-02T14:17:54"
The rigs IP adress shows up on my phone(hotspot) im able to tunnel into it, but the disconnect seems to be with the and the pump @scottleibrand
Tis is what my loop is doing
Starting pump-loop at Sun Jan 2 20:52:02 EST 2000:
Waiting up to 4 minutes for new BG: ...
Starting pump-loop at Sun Jan 2 20:54:02 EST 2000:
Waiting up to 4 minutes for new BG: ........................Radio ok. Listening: .No pump comms detected from other rigs
Profile less than 60m old. temp_basal.json less than 5m old. Pumphistory less than 5m old
Settings less than 10m old
Edison on battery: 27%. Pumphistory-24 < 90m old
Scott Leibrand
@scottleibrand
Sep 03 2017 02:50
It's actually clock-zoned.json it needs, not just clock.json.
peterfulvi
@peterfulvi
Sep 03 2017 02:52
Ok i ran that and got this output "2017-09-02T14:17:54-04:00". How do i make the connection? @scottleibrand
both of them are in my openaps directory
myopenaps/monitor directory
Scott Leibrand
@scottleibrand
Sep 03 2017 02:56
Try running it from ~/myopenaps/
peterfulvi
@peterfulvi
Sep 03 2017 02:57
ok
@scottleibrand Here is the output
root@petersrig2:~/myopenaps#  oref0-set-system-clock
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
sudo: unable to resolve host petersrig2
Restarting ntp (via systemctl): ntp.service.
Waiting for ntpd to synchronize... Unexpected first line <Name or service not known>
Setting system time to later of Sat Sep 2 14:18:35 EDT 2017 or "2017-09-02T14:17:54-04:00":
(date +%s; date -d 2017-09-02T14:17:54-04:00 +%s) | sort -g | tail -1 | while read line; do sudo date -s @$line; done;
sudo: unable to resolve host petersrig2
Sat Sep  2 14:18:35 EDT 2017
Scott Leibrand
@scottleibrand
Sep 03 2017 03:00
:+1:
peterfulvi
@peterfulvi
Sep 03 2017 03:02
@scottleibrand Now my loop should fall in sync with the current time? That was goo to learn how to do that
Scott Leibrand
@scottleibrand
Sep 03 2017 03:02
It's supposed to do that automatically. Would be good to figure out why it didn't.
peterfulvi
@peterfulvi
Sep 03 2017 03:03
ok. Thanks
@scottleibrand The new loop date is current but its at 14:23 EDT
peterfulvi
@peterfulvi
Sep 03 2017 03:12
Ok! @scottleibrand I think its ironing out. It started the loop with the current time
Starting pump-loop at Sat Sep 2 23:08:30 EDT 2017:
Thanks
Giuseppe
@giupo
Sep 03 2017 06:43
Talking about clock.json, how do I setup my rig to use clock-zoned.json instead? I keep getting that warning and I wish I could get rid of it
Scott Leibrand
@scottleibrand
Sep 03 2017 06:44
You'll need to figure out what is broken about the MDT setup and fix it.
Giuseppe
@giupo
Sep 03 2017 06:47
So I have to check the pump?
Scott Leibrand
@scottleibrand
Sep 03 2017 06:48
No, this is a problem with the oref0-setup for MDT CGM
I use Dexcom, so I can't really debug it.
Giuseppe
@giupo
Sep 03 2017 06:50
That's a good way to spend my subday πŸ˜†
sunday
Maybe I should run this https://openaps.readthedocs.io/en/2017-05-21/reference/openaps/openaps-report-monitor-clock-zoned.html and redirect the output in monitor/clock-zoned.json
peterfulvi
@peterfulvi
Sep 03 2017 08:42

I worked through the issue with syncing the date and time now this is showing up in the loop

Starting pump-loop at Sun Sep 3 04:25:13 EDT 2017:
Waiting up to 4 minutes for new BG: date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.Radio ok. Listening: .No pump comms detected from other rigs
Profile less than 60m old. date: invalid date β€˜@’
temp_basal.json less than 5m old. date: invalid date β€˜@’
pumphistory more than 5m old. : Refreshed pumphistory    at node.js:906:3
 and meal.json
Could not parse input data:  [SyntaxError: /root/nopenaps/monitor/glucose.json: Unexpected end of input]
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
enact/enacted.json: cat: enact/enacted.json: No such file or directory
Error, retrying

Im wondering if my CGM data is reaching my rig

Tim Street
@tim2000s
Sep 03 2017 11:30
@kcrcgm - are you using SMB?
If you aren't you'll need to pull the data from a different file, which is why it is not updating frequently.
cameronrenwick
@cameronrenwick
Sep 03 2017 12:20
when going thru screening at the airport, as the rig is "just another computer", you put it thru the scanner with other computers/phones correct? What are people doing to turn it off? Unplug the battery?
William Cannady
@Tilade
Sep 03 2017 16:11
image.png
My wife's rig stopped reporting some major data to nightscout a while back. Thought it was an azure problem and switched to Heroku and no help. The basal settings get reported and reflected, but there is no trend line and history graph displayed. thoughts?
Scott Leibrand
@scottleibrand
Sep 03 2017 16:23
@cameronrenwick you don't have to turn off your phone (or rig) to put to through the X-ray.
@Tilade see the docs troubleshooting page.
cameronrenwick
@cameronrenwick
Sep 03 2017 16:34
glad to hear that... just building a new rig that fits on a belt clip containing xdrip/EB/edison etc but didn't plan on putting an on/off switch. Guess I've always just turned stuff off in the past out of habit..
William Cannady
@Tilade
Sep 03 2017 16:47
image.png
Thanks @scottleibrand . Looked through the doc and doesn't resolve issue. I did find that all my ns reports are referencing blank json files (temptargets, carbhistory, recent-missing-entires, uploaded-entires). however, the cgm/cgm-glucose.json, cgm/glucose.json, and raw-cgm/raw-entires.json are all showing valid numbers. My mlab acct also shows entries for some data--so my nightscout address/pw are working.
peterfulvi
@peterfulvi
Sep 03 2017 17:13

I worked through the issue with syncing the date and time now this is showing up in the loop

Starting pump-loop at Sun Sep 3 04:25:13 EDT 2017:
Waiting up to 4 minutes for new BG: date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.Radio ok. Listening: .No pump comms detected from other rigs
Profile less than 60m old. date: invalid date β€˜@’
temp_basal.json less than 5m old. date: invalid date β€˜@’
pumphistory more than 5m old. : Refreshed pumphistory    at node.js:906:3
 and meal.json
Could not parse input data:  [SyntaxError: /root/nopenaps/monitor/glucose.json: Unexpected end of input]
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
enact/enacted.json: cat: enact/enacted.json: No such file or directory
Error, retrying

I also reran setup,Im wondering if my CGM data is reaching my rig

Scott Leibrand
@scottleibrand
Sep 03 2017 17:24
@Tilade is your rig looping and setting temps?
@peterfulvi it is not: monitor/glucose.json is empty (or contains an error string rather than glucose data)
Tim Street
@tim2000s
Sep 03 2017 17:48
@cameronrenwick There are a fair few places where you are asked to turn a computer on going through security, so I don't think it's something to worry about!
Diadon81
@Diadon81
Sep 03 2017 17:53
Dear I got an error: Old pumphistory-24h refreshmmeowlink.exceptions.InvalidPacketReceived: Error decoding FourBySix packet
Someone could guide me about the reason?
William Cannady
@Tilade
Sep 03 2017 18:03
Yes, it is looping and pump is getting correct values. It's just the reporting on nightscout that isn't working for some reason.
@Diadon81 I received this error, but it was fixed for me after physically power cycling the rig. I'm using the ExplorerBoard.
PieterGit
@PieterGit
Sep 03 2017 18:15
@Diadon81 : it's a rig-pump communication error. Possible errors: 1) rig not tuned ok, 2) pump battery flat, 3) multiple rigs communicating simultanious. If it's problem 1 then it should disappear after a mmtune run and the next pump run.
Samuchco
@Samuchco
Sep 03 2017 18:21
image.png
here is Sammys Looping with SMB. THere are no words to thank ALL of you for this!!!!!
PieterGit
@PieterGit
Sep 03 2017 18:27
@Samuchco :thumbsup:
Samuchco
@Samuchco
Sep 03 2017 18:30
He is using a 522 from when he was 7 years old. Id like to purchase a 722 or the like. Any suggestions?
PieterGit
@PieterGit
Sep 03 2017 20:26
@scottleibrand how long should carbs be counted as carbs on the 0.6.0-branch. Still 1.5*DIA?
Miiko
@tw_miiko_twitter
Sep 03 2017 20:32
SMB-Troubshooting-Watting-1320Days.png
Miiko
@tw_miiko_twitter
Sep 03 2017 20:45
@scottleibrand APS SMB ran quite a few weeks well, for few days was unfortunately very unstable, loop condition always shows again waiting. Who knows to fix it. Thks!
enact/smb-suggested.json: {"insulinReq":0.07,"bg":146,"reservoir":"111.7","temp" :"absolute","snoozeBG":112,"predBGs":{"UAM":[146,144,141,137,133,129,125,122,118 ,115,113,110,108,107,106,105,104,103,103,102],"IOB":[146,144,141,139,136,133,130 ,127,124,121,119,117,115,113,112,111,110,109,109,109,108]},"minPredBG":105,"IOB" :0.678,"reason":"COB: 0, Dev: 10, BGI: -3.67, ISF: 65, Target: 97, minPredBG 105 , IOBpredBG 108, UAMpredBG 102; Eventual BG 112 >= 97, insulinReq 0.07. Waiting 1901493m to microbolus again. temp 0.95 >~ req 0.9U/hr. ","COB":0,"eventualBG": 112,"tick":-2,"deliverAt":"2017-09-03T20:47:04.044Z"}
@scottleibrand, Hello everyone I use SMB-Advanced feature, today I have so Loop Log Problem: (See above)Waiting time: 1901539 Min? So Long? Is waiting 1320 Days for next SMB? Why?
peterfulvi
@peterfulvi
Sep 03 2017 21:15
@scottleibrand Its confirmed xdrip is not talking to the pump. I checked my glucose.json and it was empty, Here is the outpu in case anyone has suggestions
Starting pump-loop at Sun Sep 3 16:58:34 EDT 2017:
Waiting up to 4 minutes for new BG: date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.Radio ok. Listening: .No pump comms detected from other rigs
Profile less than 60m old. date: invalid date β€˜@’
temp_basal.json more than 5m old.
Temp refreshed
Could not parse input data:  [SyntaxError: /root/myopenaps/monitor/glucose.json:                                                                                                                                                              Unexpected end of input]
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
enact/enacted.json: cat: enact/enacted.json: No such file or directory
Error, retrying

Starting pump-loop at Sun Sep 3 17:03:42 EDT 2017:
Waiting up to 4 minutes for new BG: date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.date: invalid date β€˜@’
.Radio ok. Listening: .No pump comms detected from other rigs
Profile less than 60m old. date: invalid date β€˜@’
temp_basal.json less than 5m old. date: invalid date β€˜@’
pumphistory more than 5m old. : Refreshed pumphistory    at node.js:906:3
 and meal.json
Could not parse input data:  [SyntaxError: /root/myopenaps/monitor/glucose.json:                                                                                                                                                              Unexpected end of input]
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
enact/enacted.json: cat: enact/enacted.json: No such file or directory
Error, retrying
Waiting for 30s silence before mmtuning
Radio ok. Listening: .No pump comms detected from other rigs
Listening for 30s silence before mmtuning: .No pump comms detected from other ri                                                                                                                                                             gs
mmtune: "916.564", 5, -57
Scott Leibrand
@scottleibrand
Sep 03 2017 22:08
Miiko: looks like your rig or pump time is/was wrong.
PopcornPam
@PopcornPam_twitter
Sep 03 2017 22:14
Question: I don't really understand the organization of github. How do you find out about whats happening in dev? All the stuff I see are from over a year ago
Dana Lewis
@danamlewis
Sep 03 2017 22:18
You can do a branch compare to compare branches; or look at the open Pr of dev to master to see what's different.
Ie openaps/oref0#591
Miiko
@tw_miiko_twitter
Sep 03 2017 22:30
Hi Scott, thank you very much. I think so, but how can I fix it?
tekrulik
@tekrulik
Sep 03 2017 22:31
Hi! Anyone know how to troubleshoot/fix the following error: Old pumphistory: RefreshIndexError: bytearray index out of range
Tried re-running setup script, but still getting this error.
If I don't get that error, I get this error: Old pumphistory: RefreshValueError: need more than 0 values to unpack
PopcornPam
@PopcornPam_twitter
Sep 03 2017 23:02
@danamlewis is the more aggressive smb in dev now, or not yet?
Dana Lewis
@danamlewis
Sep 03 2017 23:03
Not yet. Current dev is a release candidate for master, so we are just polishing up any last little bugs or tweaks before shipping that.
PopcornPam
@PopcornPam_twitter
Sep 03 2017 23:03
gotcha
tekrulik
@tekrulik
Sep 03 2017 23:11
@danamlewis - Any ideas what causes Old pumphistory: RefreshIndexError: bytearray index out of range?
Dana Lewis
@danamlewis
Sep 03 2017 23:19
Usually self resolves; if it is not self resolving/successfully pulling history, you can manually drill down and start running things to clear it out
tekrulik
@tekrulik
Sep 03 2017 23:22
@danamlewis - Thanks. Good to know. It hasn't resolved in over an hour. I'll try manually running things.
Scott Leibrand
@scottleibrand
Sep 03 2017 23:46
@tw_miiko_twitter start by checking your current rig and pump time
date shows it on the rig