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

18th
May 2018
Jon Cluck
@cluckj
May 18 2018 00:14 UTC
@rollerdecom ping
Jon Cluck
@cluckj
May 18 2018 00:24 UTC
hah, you beat me to it scott
I did test 0.7.0-dev on an x12, but not with a WW x12 :)
and I think I tested it on the 722-WW while I still had it?
Thomas
@TH2100
May 18 2018 14:53 UTC
@cluckj I would be happy to help finding out about 0.7.0-dev connectivity with my 512-WW. Only limitation is my one and only rig so far. I don't know about relevance for the whole community, though. I'll also switch pumps in 2 months. Frankly, the only unusual I found was in loop.log. After flashing and switching from master
Jon Cluck
@cluckj
May 18 2018 14:55 UTC
do you still have the logs?
if not, no worries :)
Thomas
@TH2100
May 18 2018 14:57 UTC
Switched to master before sleeping... oops. Frankly, the only unusual I found was in loop.log. After flashing and switching from master to 0.7.0-dev with go src it showed 9XX frequency checks, after another reboot it showed 8XX again.
Anything else was just fine... also new pump battery...
If you want me walk through the logs... I could with now to dev... need just a couple of minutes...
Jon Cluck
@cluckj
May 18 2018 15:00 UTC
hmm, did you do a fresh install of 0.7.0-dev or an in-place upgrade?
Thomas
@TH2100
May 18 2018 15:02 UTC
first an upgrade from 061 by switching branch and new install with precompiled go. Then a linux flash with standard install, which resulted also in 061-master an then a branch switch.
reason: insufficient space for src go after the first upgrade
Jon Cluck
@cluckj
May 18 2018 15:04 UTC
yeah the Go toolchain is GIGANTIC
problematically so on the edison+explorer!
Thomas
@TH2100
May 18 2018 15:06 UTC
when trying to make space by cleaning up .... I made it just too clean... :-))
Jon Cluck
@cluckj
May 18 2018 15:06 UTC
:laughing:
Thomas
@TH2100
May 18 2018 15:06 UTC
flashing's always helping :sparkles:
Jon Cluck
@cluckj
May 18 2018 15:08 UTC
yeah, fresh installs being better is why the upgrade stuff hasn't been extensively tested :)
but that's what I would try if your treatment isn't going to be messed up with some testing/experimenting
like ctrl+c between the bootstrap script and oref0-setup.sh, switch to 0.7.0-dev and continue with oref0-setup.sh
Thomas
@TH2100
May 18 2018 15:14 UTC
Fresh install means also starting with flash, right?
Jon Cluck
@cluckj
May 18 2018 15:18 UTC
Yeah
Thomas
@TH2100
May 18 2018 15:19 UTC
I'm on it...
Jon Cluck
@cluckj
May 18 2018 15:19 UTC
thanks! :)
I'm thinking about what could cause that 9xx frequency thing. Did you stop cron before upgrading from 0.6.1 to 0.7.0-dev?
Thomas
@TH2100
May 18 2018 15:29 UTC
... :worried: guess not
Status: flashing runs
Jon Cluck
@cluckj
May 18 2018 15:32 UTC
haha, I don't mean that it was something you did wrong
Thomas
@TH2100
May 18 2018 15:34 UTC
I think so... but I also remember reading about it being better to do so...
About the bootstrap script later... I will have to stop the script in the middle?
at least I remember it to just run through the master install. But I might be wrong. Then it's all fine :-)
naboull1
@naboull1
May 18 2018 16:01 UTC
hey guys is carelink usb not longer supported? i just finished setting up loop install and stuck with this error message: Radio check failed. ImportError: No module named spi_serial
Dana Lewis
@danamlewis
May 18 2018 16:02 UTC
Screen Shot 2018-05-18 at 9.01.59 AM.png
Jon Cluck
@cluckj
May 18 2018 16:08 UTC
@rollerdecom yes, you want to stop the script when it prompts you
Thomas
@TH2100
May 18 2018 16:16 UTC
some secs and the script should be there. So, I'll change the branch and start oref0-install. Can I set precompiled go or would it even matter?
Thomas
@TH2100
May 18 2018 16:25 UTC
I'm just downloading the precompiled ones
Dana Lewis
@danamlewis
May 18 2018 16:48 UTC
@naboull1 I also just coded up an automatic fix for that - if you want to check out the fix-carelink branch & test that?
and if not, if someone else (@miloskozak or others using carelink right now) could test and comment on this PR openaps/oref0#1011, we can add that to dev and do a patch release 0.6.2 before we head down the Go route with 0.7.0
Thomas
@TH2100
May 18 2018 16:49 UTC
@cluckj oref0-setup (070) stopped with
importing xdrip-cgm file. Not an openaps environment, run: openaps init. Could not import xdrip-cgm.json
Should I just make it run again?
Thomas
@TH2100
May 18 2018 17:13 UTC
@cluckj now it's all up and running. Waiting for some connect with the pump.
Jon Cluck
@cluckj
May 18 2018 17:39 UTC
:thumbsup:
@rollerdecom how's it looking?
Thomas
@TH2100
May 18 2018 17:42 UTC
unfortunately, the same as yesterday...
Unsuccessful oref0-pump-loop at Fri May 18 19:38:23 CEST 2018
would you want to check other logs than loop.log?
Jon Cluck
@cluckj
May 18 2018 17:43 UTC
no, paste the pump-loop.log please :)
Thomas
@TH2100
May 18 2018 17:45 UTC
... please just tell me, if it's too much. I'll edit and delete some text then... :smile:
Starting oref0-pump-loop at Fri May 18 19:39:03 CEST 2018 with 24 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 19:39:29 CEST 2018
Preflight (x12 models do not support SMB safety checks, SMB will not be available.) OK. Profile less than 60m old; Profile valid. Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 44 s silence before mmtuning
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 19:40:31 CEST 2018
Listening for 44 s silence before mmtuning: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 19:41:16 CEST 2018
mmtune: "868.450", 3, -75 waiting for 30 second silence before continuing
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 19:42:18 CEST 2018
Preflight (x12 models do not support SMB safety checks, SMB will not be available.) OK. Done waiting for rigs with better signal.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Fri May 18 19:42:20 CEST 2018
grep: monitor/temp_basal.json: No such file or directory
Jon Cluck
@cluckj
May 18 2018 17:46 UTC
has it been doing that for a while?
Thomas
@TH2100
May 18 2018 17:46 UTC
repeatingly for maybe 40 minutes now
Jon Cluck
@cluckj
May 18 2018 17:52 UTC
can you do a cat monitor/status.json from your myopenaps directory?
Thomas
@TH2100
May 18 2018 17:57 UTC
the file is empty
Jon Cluck
@cluckj
May 18 2018 17:58 UTC
yay (but also not)
Thomas
@TH2100
May 18 2018 17:58 UTC
ok.. :-)
actually nothing happens with cat....
so i nanoed in /monitor
Jon Cluck
@cluckj
May 18 2018 17:59 UTC
:thumbsup:
yay because I know where it's broken, and not yay because it's broken :)
Thomas
@TH2100
May 18 2018 18:01 UTC
you know, where it's broken? Yay!
:-)
Can we do something about it or is it sth for later?
Jon Cluck
@cluckj
May 18 2018 18:03 UTC
if you have time to fool around with it now, I do too
Thomas
@TH2100
May 18 2018 18:03 UTC
up to 2 hours, I can...
Jon Cluck
@cluckj
May 18 2018 18:04 UTC
export MEDTRONIC_PUMP_ID=`grep serial pump.ini | tr -cd 0-9`
export MEDTRONIC_FREQUENCY=`cat monitor/medtronic_frequency.ini`
run those commands in your myopenaps directory, then do mdt status
(it might crash into your loop that's running)
Thomas
@TH2100
May 18 2018 18:06 UTC
wow...
2018/05/18 20:06:21 unexpected firmware version "\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xf..."
Jon Cluck
@cluckj
May 18 2018 18:07 UTC
yeah that's it crashing into the loop, can you turn off your loop with systemctl stop cron?
then killall oref0-pump-loop
Thomas
@TH2100
May 18 2018 18:09 UTC
much better:
2018/05/18 20:09:10 connected to CC111x radio on /dev/spidev5.1
2018/05/18 20:09:10 setting frequency to 868.400
2018/05/18 20:09:11 model 512 pump
2018/05/18 20:09:11 status error: CommandRefused
Jon Cluck
@cluckj
May 18 2018 18:10 UTC
:) excellent
are you comfortable with editing oref0-pump-loop.sh to replace a line?
Thomas
@TH2100
May 18 2018 18:16 UTC
let's just try it. If the loop won't work, I'll just switch to master this night...
Jon Cluck
@cluckj
May 18 2018 18:16 UTC
okay
so nano ~/src/oref0/bin/oref0-pump-loop.sh
Thomas
@TH2100
May 18 2018 18:17 UTC
that really was comfortable! Thanks :)
Jon Cluck
@cluckj
May 18 2018 18:18 UTC
press ctrl+w and search for function refresh_pumphistory_and_meal
lol
Thomas
@TH2100
May 18 2018 18:18 UTC
what should I check or change
Jon Cluck
@cluckj
May 18 2018 18:18 UTC
there's a line below there that looks like ( grep -q "model.*12" monitor/status.json || \
Dave Acklam
@dcacklam
May 18 2018 18:18 UTC
@naboull1
Jon Cluck
@cluckj
May 18 2018 18:19 UTC
change it to ( grep -q "12" settings/model.json || \
Dave Acklam
@dcacklam
May 18 2018 18:20 UTC
@naboull1 Carelink support isn't maintained anymore - hasn't been for a while. It can be made to work if you go through the code and edit everything to use/check the appropriate serial port and so on...
Thomas
@TH2100
May 18 2018 18:21 UTC
done and double checked
Dave Acklam
@dcacklam
May 18 2018 18:21 UTC
I had a carelink based loop working back in January. When I finally figured out how to do SRF based looping, I stopped using the carelink.
Jon Cluck
@cluckj
May 18 2018 18:21 UTC
:thumbsup:
okay, start cron back up and keep an eye on your loop log
Thomas
@TH2100
May 18 2018 18:22 UTC
for the effects... saving... right?
Jon Cluck
@cluckj
May 18 2018 18:22 UTC
:laughing:
Thomas
@TH2100
May 18 2018 18:23 UTC
sorry, want to make the magic really work! :-)
Jon Cluck
@cluckj
May 18 2018 18:23 UTC
yes please save it!!
Dave Acklam
@dcacklam
May 18 2018 18:25 UTC
@scottleibrand
Jon Cluck
@cluckj
May 18 2018 18:27 UTC
you should be able to see it working pretty quickly
Scott Leibrand
@scottleibrand
May 18 2018 18:27 UTC
@dcacklam ?
Thomas
@TH2100
May 18 2018 18:31 UTC
couldn't see an effect. Just rebooted. If you have the time, I'd check our last change to be sure.
Dave Acklam
@dcacklam
May 18 2018 18:31 UTC
What is the logic behind the carb impact limit (that reduces carb impact to a calculated value)? In an earlier iteration of my loop I had disabled it as part of mods to make the loop more responsive for purely unannounced-meal operation (logic: by having UAM Carb Impact (which isn't effected by this limit ) and regular' carb impact (which generally would be the same as UAM impact but-for the limit reducing the value) be the same, the loop would be more biased toward the UAM calculations). No ill effects were seen, but I am looking for some more info on what that value does, and any concerns with adding an option to not have a limit.
Jon Cluck
@cluckj
May 18 2018 18:32 UTC
yeah, I'm putting my 512 rig back together too
Dave Acklam
@dcacklam
May 18 2018 18:33 UTC
@scottleibrand mobile glitch. Gitter app sent a blank message, what I intended to say is below Thomas's post
Scott Leibrand
@scottleibrand
May 18 2018 18:34 UTC
@dcacklam we saw some cases where oref0 would dose too aggressively for rapidly rising BG (from fast carbs, etc.) and end up dosing too much insulin, causing a low later. so we set the carb impact limit to be "what we could reasonably expect to be sustained for more than 30m or so".
Dave Acklam
@dcacklam
May 18 2018 18:35 UTC
Got it...
Scott Leibrand
@scottleibrand
May 18 2018 18:36 UTC
we've found that the limit doesn't prevent it from dosing a proper amount of insulin, as it just slows down the predicted absorption to be over for example 3 hours instead of 1, but either way the eventual impact is the same
Dave Acklam
@dcacklam
May 18 2018 18:37 UTC
My experience operating 'blind' has always been too slow a reaction (similar to the basalminutes situation).... So what I was doing was trying to get it to feed me more insulin, faster.
Scott Leibrand
@scottleibrand
May 18 2018 18:38 UTC
in our experience, that's best done by avoiding the "chase the BGs" situation, and instead give it some sort of eating-soon or meal announcement to get it started earlier
Dave Acklam
@dcacklam
May 18 2018 18:47 UTC
The tuning I did was based on using oref0 to 'pretend I don't have diabetes' for the past 4 months... Seeing as how it's an immediate medical discharge if they ever find out, they don't really have nutrition info for the awful cafeteria food that I've had to live on, and such.... Good news is it more or less worked - and that the less-bad the food was, the better it worked)... Flip side is that I am not exactly a good experimental sample...
Thomas
@TH2100
May 18 2018 18:49 UTC
@cluckj , all change is as intended. I'll just let it run for a while.
Dana Lewis
@danamlewis
May 18 2018 18:52 UTC
@dcacklam your comment about carelink is outdated FYI. Carelink support was re-added to 0.6.1, although will likely be frozen in time with 0.6.2 as we switch over to Go radio code in 0.7.0. @naboull1 see my earlier comment about either adding carelink to pump.ini or using the branch I just created to test an automated fix.
Dave Acklam
@dcacklam
May 18 2018 18:54 UTC
So while I'll actually be able to enter data for most meals now that I'm going off active status again (I know how much carbs are in the stuff I eat on the civilian side)... I still tend to look at things from a 'retain the ability to go pure UAM' perspective... Because I will need it the next time I'm activated....
Jon Cluck
@cluckj
May 18 2018 18:55 UTC
@rollerdecom working on a fix locally, I'll let you know when it works
Thomas
@TH2100
May 18 2018 18:56 UTC
That's very cool! Thank you.
Scott Leibrand
@scottleibrand
May 18 2018 18:58 UTC
@dcacklam glad to see it works pretty well for that kind of use case. I know you can actually get better results, even without nutrition info, if you are willing to do a really rough carb guesstimate. Even if you're off by a factor of 2, the rough guesstimate is enough to get some insulin started, and then it fine-tunes from there.
Thomas
@TH2100
May 18 2018 18:58 UTC
If it doesn't work that quickly, I 'll go back to master for the night. When you found a solution I'm always ready for testing. :smile:
Would that be ok for you?
Jon Cluck
@cluckj
May 18 2018 18:59 UTC
@rollerdecom sure!
okay, go back into oref0-pump-loop.sh and search for function check_status
Dave Acklam
@dcacklam
May 18 2018 19:02 UTC
FWIW, the hardest time for accuracy is when there is a major change in health or diet. Autitune/autosens are really good at dialing in the right adjustments if I stick to a similar routine....
Jon Cluck
@cluckj
May 18 2018 19:03 UTC
change the whole thing to this (copy/paste is best)
function check_status() {
  set -o pipefail
  if ( grep 12 settings/model.json ); then
    touch monitor/status.json
  else
    mdt status 2>&3 | tee monitor/status.json 2>&3 >&4 && cat monitor/status.json | jq -c -C .status
  fi
}
Thomas
@TH2100
May 18 2018 19:04 UTC
done.
Jon Cluck
@cluckj
May 18 2018 19:05 UTC
thanks
Thomas
@TH2100
May 18 2018 19:06 UTC
saved and watching loop-log for changes
Jon Cluck
@cluckj
May 18 2018 19:06 UTC
you're going to get a new error message :laughing:
Couldn't smb_enact_temp
you should switch back to master, I'll fool with this and get it working
it's not the WW pump though! :)
Thomas
@TH2100
May 18 2018 19:08 UTC
was impatient and rebooted :worried: again :)
not the WW-pump? but it worked with yours?
Jon Cluck
@cluckj
May 18 2018 19:09 UTC
no, it's broken on mine (NA model) too
Thomas
@TH2100
May 18 2018 19:09 UTC
:worried:
It's LOOPING !!!
Jon Cluck
@cluckj
May 18 2018 19:10 UTC
lolsob
awesome!
Thomas
@TH2100
May 18 2018 19:10 UTC
ompleted oref0-pump-loop at Fri May 18 2...
Unbelievable!
Good work, man !!!
Jon Cluck
@cluckj
May 18 2018 19:11 UTC
some code I wrote to make the x12 work got deleted between when I wrote it and now :)
woo
mine being broken is probably something else
Thomas
@TH2100
May 18 2018 19:14 UTC
... It's just wonderful and also I'm glad you have one topic off the list
Jon Cluck
@cluckj
May 18 2018 19:14 UTC
me too, thanks for your help!
keep an eye on the logs, though. you're one of the first (if not THE first) to be running that code in-vivo!
Thomas
@TH2100
May 18 2018 19:16 UTC
I'm happy to be helpful and thank you for your patients. I'll just let it run now. If you need some logs or else, please let me know.
Jon Cluck
@cluckj
May 18 2018 19:17 UTC
only if it breaks or is doing weird things to your blood sugar
Thomas
@TH2100
May 18 2018 19:18 UTC
okay, that I will do... my blood sugar is more a mystical creature... so it would be about crashes :-)
Jon Cluck
@cluckj
May 18 2018 19:18 UTC
:thumbsup:
Tim Gunn
@Tornado-Tim
May 18 2018 21:24 UTC
Quick question it seems my CR is far too low because autotune I deleted the autotume run files let it run again it still comes back with incorrect CR, if I keep it this way I am having hypos because of SMB, how can I fix the cob to a set amount so it will prevent from overdosing after I eat. (SMB enabled)
Dana Lewis
@danamlewis
May 18 2018 21:25 UTC
"incorrect carb ratio" - did you check your pump to see if there are multiple schedules you're using by accident?
is it not pulling the correct carb ratio from your pump, or ?
Tim Gunn
@Tornado-Tim
May 18 2018 21:27 UTC
No it's not it's much lower than the pump.... No multpile schedules in pump either....
I thought it would be fixed after deleting autotune but autosens for some reason is still using the bad CR....
Dana Lewis
@danamlewis
May 18 2018 21:28 UTC
so to state the obvious: you may want to turn off SMB while you sort this out
and/or set a higher target, etc.
what autotune files are you deleting? settings, or just the log files?
Tim Gunn
@Tornado-Tim
May 18 2018 21:29 UTC
Everything bar profile.json which I hope didn't have old cr (didn't check)
Just wondering if there is a file I could edit to fix it back up again....
Will disable autotune too in Cron....
Scott Leibrand
@scottleibrand
May 18 2018 21:33 UTC
did you delete anything in ~/myopenaps/settings ?
Tim Gunn
@Tornado-Tim
May 18 2018 21:34 UTC
Nope
Scott Leibrand
@scottleibrand
May 18 2018 21:35 UTC
there's a copy of the autotune settings there
Tim Gunn
@Tornado-Tim
May 18 2018 21:35 UTC
Does openaps run off that file?
Scott Leibrand
@scottleibrand
May 18 2018 21:35 UTC
yes
Tim Gunn
@Tornado-Tim
May 18 2018 21:35 UTC
Ahhhhh
Scott Leibrand
@scottleibrand
May 18 2018 21:36 UTC
I'd be interested in seeing why autotune is getting a stronger CR than you like. you can manually calculate your CR from NS reports: that might be a good next step after you stabilize things
that calculation relies on your basals being well-tuned: does autotune agree with you on those?
Tim Gunn
@Tornado-Tim
May 18 2018 21:39 UTC
Yes but after deletion there was more variance ( but not significant)
Parameter      | Pump     | Autotune
-------------------------------------
ISF [mg/dL/U]  | 39.000   | 26.872
Carb Ratio[g/U]| 9.000    | 6.375
Basals [U/hr]  | -        |
  00:00        | 0.950    | 0.817
  00:30        |          |
  01:00        |          | 1.013
  01:30        |          |
  02:00        | 1.000    | 1.048
  02:30        |          |
  03:00        | 1.000    | 1.108
  03:30        |          |
  04:00        | 1.000    | 0.997
  04:30        |          |
  05:00        | 1.000    | 0.948
  05:30        |          |
  06:00        | 1.000    | 0.871
  06:30        |          |
  07:00        | 1.000    | 0.814
  07:30        |          |
  08:00        |          | 0.794
  08:30        |          |
  09:00        | 1.000    | 0.760
  09:30        |          |
  10:00        |          | 0.894
  10:30        | 1        |
  11:00        | 1.000    | 0.940
  11:30        |          |
  12:00        |          | 0.937
  12:30        |          |
  13:00        |          | 0.944
  13:30        |          |
  14:00        |          | 0.954
  14:30        |          |
  15:00        |          | 0.982
  15:30        | 0.95     |
  16:00        |          | 0.870
  16:30        |          |
  17:00        |          | 0.855
  17:30        |          |
  18:00        | 1.000    | 0.852
  18:30        |          |
  19:00        | 1.000    | 0.942
  19:30        |          |
  20:00        | 1.000    | 0.949
  20:30        |          |
  21:00        | 1.000    | 1.035
  21:30        |          |
  22:00        | 1.000    | 0.892
  22:30        |          |
  23:00        |          | 0.913
  23:30        |          |
statuur
@statuur
May 18 2018 21:46 UTC
@danamlewis fixing the typo in the flowchart, is it 554 or 554 / 754?
Dana Lewis
@danamlewis
May 18 2018 21:47 UTC
554/754. Thanks!
garykidd
@garykidd
May 18 2018 21:47 UTC
it'd be sweet if you could manually run a script that would set the suggested Autotune basal rates as the active pump rates. sounds like a decent amount of work though...ideas easy...implementation not so easy.
Scott Leibrand
@scottleibrand
May 18 2018 21:47 UTC
@Tornado-Tim that is a reasonably sized difference
total daily basal 23.8 from the pump, vs 22.13 from autotune
so 8% different
Tim Gunn
@Tornado-Tim
May 18 2018 21:49 UTC
yea dont get exactly why autotune went borky.... is it recommended to romove those file fairly frequently to stop the same from happening again?
Scott Leibrand
@scottleibrand
May 18 2018 21:49 UTC
I'd like to look at the data to see if autotune went borky or not
it looks like it's trying to get you to give less insulin via basal, and more more meals via stronger CR
Tim Gunn
@Tornado-Tim
May 18 2018 21:50 UTC
do you have my NS url?
Scott Leibrand
@scottleibrand
May 18 2018 21:51 UTC
I don't think so
statuur
@statuur
May 18 2018 21:51 UTC
I made a proof of concept for the replacement of pushover with local notifications today. Should i talk to John Costik about this to implement this in the wip/azurepush branch?
Scott Leibrand
@scottleibrand
May 18 2018 21:51 UTC
you want that public?
fancy rainbow
garykidd
@garykidd
May 18 2018 21:53 UTC
how does one change the color of the various oref prediction lines..that is cool.
Tim Gunn
@Tornado-Tim
May 18 2018 21:54 UTC
yea thats fine I dont mind :)
Would have PM'd you otherwise....
garykidd
@garykidd
May 18 2018 21:55 UTC
i like it, tim
Tim Gunn
@Tornado-Tim
May 18 2018 21:55 UTC
you can run off it if you wish, I forked the NS repo....
Scott Leibrand
@scottleibrand
May 18 2018 21:56 UTC
looks like the NS Day to day report's Insulin distribution is broken and always reporting zero Total basal insulin
same on our NS
Oh a bug in Dev is it?
Scott Leibrand
@scottleibrand
May 18 2018 21:58 UTC
not sure, this is the first I've noticed it
Dana Lewis
@danamlewis
May 18 2018 21:58 UTC
statuur
@statuur
May 18 2018 21:58 UTC
:smile:
Tim Gunn
@Tornado-Tim
May 18 2018 22:00 UTC
Yea I figured it would be a good idea to identify the forecast lines by color rather than having to resort to looking a hover over point to find what forecast was what :smile:
statuur
@statuur
May 18 2018 22:01 UTC
@danamlewis a while a we talked about the possibility to replace pushover notifications with local notifications trough a websocket. You mentioned the wip/azurepush branch. Who can get me get started with the server side on that end?
Tim Gunn
@Tornado-Tim
May 18 2018 22:03 UTC
just replacing my cannula and insulin now, will be back in 5
Scott Leibrand
@scottleibrand
May 18 2018 22:11 UTC
@Tornado-Tim I would make sure that your autosens_max is fairly tight (looks like you raised autosens_max from the default of 1.2 to be able to get ISF and CR 1.41 and 1.45 times higher than your pump).
Tim Gunn
@Tornado-Tim
May 18 2018 22:17 UTC
yup that sounds about right, OK
Tim Gunn
@Tornado-Tim
May 18 2018 22:39 UTC
OK deleted the autotune.json in settings, what do you recommend I do for autosens_max because I find that it needs be a bit more aggressive? knock it back to to 1.2 for now?
Tim Gunn
@Tornado-Tim
May 18 2018 22:47 UTC
disabled autotune scheduling for the meantime as well
Tim Gunn
@Tornado-Tim
May 18 2018 22:59 UTC
CR has fixed itself to the pump settings now, thanks Scott for that info re autotune settings file.....
Scott Leibrand
@scottleibrand
May 18 2018 23:43 UTC
yeah, I'd stick with 1.2 unless/until you have a need for it to be higher