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

May 2018
May 09 2018 03:16

@scottleibrand Excuse me, annoying, but I do not know what else to try to make the cycle work.
I detail some of the controls that I made

  • The time of the boma is good with the CGM, this is what you showed me
    root@myopenaps:~# oref0-set-device-clocks
    Waiting for ntpd to synchronize... OK!
    Setting pump time to Tue May 8 00:34:51 -03 2018
    Setting CGM time to Tue May 8 00:34:52 -03 2018

  • Internet I have because the ping responds to google
    root@myopenaps:~# ping
    PING ( 56(84) bytes of data.
    64 bytes from ( icmp_seq=1 ttl=52 time=183 ms
    64 bytes from ( icmp_seq=2 ttl=52 time=271 ms

  • NS is giving me this message that I do not know if it is correct, but if I consult Ns
    by Mozilla, they are shown the correct glucose values
    The NS is well created because we are using it in another loop perfectly

root@myopenaps:~# tail -F /var/log/openaps/ns-loop.log
Latest NS temptargets: Merging local temptargets: Temptargets merged: Refreshed carbhistory; COB: 0
No recent suggested.json found; last updated May 8 00:27
Couldn't upload latest treatments to NS

Starting oref0-ns-loop at Tue May 8 00:37:02 -03 2018:
No recent valid BG found. Most recent:
Latest NS temptargets: Merging local temptargets: Temptargets merged: Refreshed carbhistory; COB: 0
Couldn't upload devicestatus to NS

  • Attached image of what the loop shows.
    Anything else you can think of to identify the problem?
    A detail, I do not have the cell phone with me and neither the G5, does this affect the configuration
    to give me these problems?

I hope you can help me and apologize for the inconvenience

Scott Leibrand
May 09 2018 04:05
It looks like your Nightscout URL is wrong.
Cas Eliëns
May 09 2018 07:08
I'm gonna try to reproduce the issue where my rig doesn't upload meal bolused correctly to nightscout, and then gather some logs
Paul Andrel
May 09 2018 14:02
Hmm some interesting sessions at IO Today, Particularly, this one Check out [Session] Machine learning and medicine happening at #io18 on May 9
May 09 2018 18:45
Hi, fellow loopy people. I remember that there's a place in the docs with instructions on setting the frequency with which my Edison communicates with my pump, admonishing me not to make it communicate too often lest my pump use excessive numbers of batteries. I've been searching through the docs but I can't seem to find that information any more. Could someone please kindly point me to the page I'm looking for?
I'm going through about one battery every 24-48 hours.
Scott Leibrand
May 09 2018 18:49
unfortunately there's no good way to make a AAA alkaline work much longer than that. we recommend AAA lithiums, which last almost a week
May 09 2018 18:53
@scottleibrand Thanks, Scott. I thought that limiting the frequency of pump communications (downloading pump history?) had a big effect. Not true?
Scott Leibrand
May 09 2018 19:01
if you want to experiment with that, the 0.7.0-dev branch uses an entirely new Go-based pump comms library that is way more efficient on the rig side, but also doesn't have to keep the channel open with the pump as long
you could also change your cron to run less frequently, but I think the benefit of that is marginal
May 09 2018 19:19
@scottleibrand That's good news on the comms library. I'll probably do both. I hadn't realized that lithium AAA batteries had dropped in price so quickly.
May 09 2018 19:33
I'm not sure this is the right place to ask this question. I have gotten 2 e-mails from mlabs saying I have exceeded my limits. I have cleared out the dbs and compacted the db. Do I need to pay for more size or is there something else I need to do? TIA
May 09 2018 22:23
@stavlor any link to that Google io talk you're referring to?