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

16th
Jan 2019
jgslade
@jgslade
Jan 16 00:15
Glad you got it all connected
straykatz
@straykatz
Jan 16 07:29
I asked this before but I have more specifications now... when I start airpods on my iphone playing anything and I'm at home on wifi. Then leave to walk somewhere, a few minutes the airpods stop playing sound but the phone thinks its still working and podcasts for example keep playing but not producing any audio in the airpods. I'm 99% sure this is due to the edison BT tethering kicking on now that the wifi is no longer reachable. I have a bug in with Apple as I think this is the fault of the BT software stack on the phone/airpods as I have had this problem with both an Iphone 7 and a Xs (which was setup as new) @tomasboudr I just got AirPods and I have observed many disconnects as I am walking in and out of the house (=in and out of WIFI range) to work in the garden. This does not happen away from the house. Same thing you are describing - with the phone acting as if the pods are still playing.
dansuk
@dansuk
Jan 16 13:13
Has anyone got notifications working through Nightscout/IFTTT when a temp basal change is enacted? I get SMB notifications as Correction Bolus but nothing for temp basal changes. I tried ns-info and ns-info-treatmentnotify but don't receive anything.
Tom Boudreau
@tomasboudr
Jan 16 15:15
@straykatz glad to know I'm not the only one. Thanks for confirming.
@kirkbysound I do the same. Notepadd++ txt file with all my commands.
Dana Lewis
@danamlewis
Jan 16 15:24
@dansuk not sure anyone has tried to do that due to the volume of temp basals being set. Most people instead use the “not looping for X minutes” pushover if the rig stops looping
Dustin
@dheald88
Jan 16 15:36
image.png
Trying to close the loop but keep getting the following error. Using a PiZero w/ PiHat. 522 pump.
Not sure exactly what those errors mean.
Dustin
@dheald88
Jan 16 16:05
Nevermind! re-ran the script and errors did not pop up this time!
Dana Lewis
@danamlewis
Jan 16 16:06
:+1:
JohnDoeAkira
@JohnDoeAkira
Jan 16 17:22
Hi, I get a strange behavior of my sensors in my rig (enlite, 722, explorer rig). The expire after 2 or 3 days. I can restart them but they never last the expected 5 or 6 days. Any idea ?
Dana Lewis
@danamlewis
Jan 16 17:30
Aren’t the older enlites only designed to work for 3 days? I think only the newer ones for 6series pumps last the longer time frame
JohnDoeAkira
@JohnDoeAkira
Jan 16 17:56
I am using new sensors but with an old minilink transmitter and a 722. I guess that could well be the answer !! Thank you Dana.
JohnDoeAkira
@JohnDoeAkira
Jan 16 18:21
I had a look at the minilink manual and the sensors expired after 3 days. You were right.
Dana Lewis
@danamlewis
Jan 16 20:38
:+1:
Tom Boudreau
@tomasboudr
Jan 16 20:56
@JohnDoeAkira The Medtronic sensors do only work for 3 days, but you can restart them and get another 3.
I did this with my 722 prior to moving to Dexcom
the Medtronic sensor (including the both the accuracy issues, and the all the calibration processes: ie. fact that it only uses one fingerstick to start with, and stops giving you readings if it wants a cal and you can't do it right then and there) are just not very good. I highly recommend getting a Dexcom
That said, use it on your arms, WAY more accurate than if you use the advised stomach location. This applies to all CGMs (this is for me, and although many agree with this, YMMV)
viq
@viq
Jan 16 22:05
openaps/oref0#1184 - another step on my quest to having autotune run automatically while using AndroidAPS ;)