Did another test today with Master and AMA. I had a cheeseburger and barely a blip. I went up to about 120 something. So then I went to Shake Shack and had a double-frozen custard and an order of Cheese Fries. That comes to 111 grams of carb. I was lowish and didn’t want to bolus the normal amount, so I did a 50% bolus but told it the correct number of carbs. 3-4 hours after eating, I did go up to 164, but it is chipping away at it and coming down. If I did this manually I could easily have reached 300.

@peterfulvi when you get persistent Error, retrying you need to pause the cron and run the commands manually to dig into what's really going on.

also keep in mind that zero temps take up to 2 hours to really kick in, so if there's reason to think your BG will rebound by then, it'll be looking at what you need 2-3 hours from now, not what you wish you could've done differently 2 hours ago.

thx right now just trying to avert immediately pre-bedtime low - our practice had been for comfort level to run a bit higher at night; we probably need to tell the pump new night time target ~125 not 110

I am having trouble using the gitter search (it used to be heaps better!)... I maybe missing the obvious but I am wanting to setup oref1 (SMB) on one of my rigs, but the how to do that is not jumping out at me... where should i look? thanks

Thinking about bolussnooze...if my son starts to run or hard play after a meal i observed how loop starts zero temping immediately when it observes a drop while openaps does it later. If i set bolus snooze to zero will openaps works better with these sudden drops after meal too.

@scottleibrand Thanks, I have placed an order for the explorer board (backordered) and the Edison rig has unfortunately been out of stock since I've been trying to order. Is flashing really that miserable of an experience? I've only been looping one day and the wifi on my RPi has already crashed and I'd like to move forward with another setup sooner than later.

@danamlewis regarding To test SMB, you'll need to run oref0-setup with a "microbolus" enable flag I am on the oref0dev branch and have tried manually entering microbolus as an enable flag as there was no option prompted from the setup script. However I do have all the relevant options in my preference.json file. What have I missed to enable microbolus? thanks

This morning I woke up to “OpenAps last looped six hours ago.” I looked at my rig, and the charging cable had pulled out and it was dead. The good news is last night I had looked at the auto-time logs and programmed my pump with the recommended basals. I woke up at 103. That is awesome. I do have a question though. NS is missing my glucose from about 3am onward. Dexcom had the data. Why is that missing from NS?

@skubesch Flashing is one of the easiest steps in the OpenAPS process, at least on a Mac. It is 15 minutes of work. You just plug it in and copy and paste a few command lines. Just remember to be patient as it looks like it is stuck in a loop and it repeats a reboot 3-4 times, but that is a normal part of the process. The docs even say you will think it is stuck in a loop but it is not.

@rsilvers129 the rig only uploads a bit of cgm data each time, so if the upload fails for a while you'll miss some data. I'm planning on writing a buffered-curl that will upload when the rig is online again

I got a no loop alert. I looked at the log and had a -99 signal. Pump was 2-3 feet from Explorer. I moved the pump to a few inches away, and the loop started working again. I just want to confirm that this is not unusual and that the RF distance is sometimes less than two feet.

@mhaeberli if you find some results on that I would be super keen to see them, my long range rig uses the Ti stick as I just cant get the range with my edison even with making the cut to tune it to 915....

@iainct naively, it would seem to me that the Edison cases I have seen the LithiumIon battery right next to the explorer. So some loose exploration with the battery as far away as possible from the Edison/Explorer MIGHT show larger range...

@rsilvers129 interested in what you find out however my experience is that the edison plugged in downstairs in the kitchen (which is under our master bedroom) was looping when the pi with carelink (extended cable was next to me and right net to my pump). At first I moved the edison down to the basement, then I gave up and plugged it in (to charge the battery overnight) and it is 2 to 3 feet away from the bed. Perhaps it is dependent on which pump you are using also? I am using a 554 (Canadian).

OK, i think i have a big problem. I have autotune turned on, and my rig was running while I was on beta bionics (more for curiosity than anything...) and now autotune says my isf is 85 (i thought it was set at 60) and CSF n/a, and carbs at 16. This probably explains the higher bgs since returning to openaps

I am not sure how to fix this, since the settings in nightscout and my pump are correct. I don't undertand where in edison it is setting these new basals, and how to fix it

@PopcornPam_twitter to start - if you want to, turn autotune off. other options include going in and editing the autotune file back (or deleting the files from when you were off OpenAPS) to something closer to your original ISF and letting it start tuning back from scratch

yes. that’s the short term solution. but I would also consider deleting the data from the days you weren’t actually using OpenAPS, or putting in a revised file from yesterday for it to use that’s closer/is what’s in your pump

I have the URL correct i cannot get it to temp basal.Like i said i was getting an error code evert yime it would refresh old pum history, so i reloaded my pump settings on my actual pump. That seemed to get thiungs moving, now my loo[p is having a hard time getting in sync. NS is reading the loop but not any BG'S

can anybody explain the difference between the UAM, COB, aCOB, IOB prediction lines/array's of BG in determine-basal. Is the UAM one the only prediction that tries to take into account for unabsorbed carbs. If I would want a good prediction to see "hypo expected in X minutes" should I use the UAM one?

found: some link (removed) @danamlewis@scottleibrand : Is aCOB or COB the one that assumes 10 mg/dL/5m)? Is UAM BG forecast always available and the one that is the best of those 4 prediction lines/ forecasts?

@scottleibrand yeah---just happening on one rig---good idea to try swapping edison module or explorer board (same difference I suppose) to other rig... ALso wondering if just re-running script at this point would have any effect on issues...seems to happen when coming/going from BT hotspot to/from home wifi...

the pushover notification do some of the carbsreq notification, but i noticed it doesnot warn in all cases.so i think i'll parse the UAM array (if available) and warn for "hypo of X expected in Y minutes". If there is no UAM, I'll use the COB Bg array. Is that the best way to guestimate future BG values?

That's more complicated than needs to be, I think. Check for some of the TODO's in the code for some places where we've flagged needing to add carbsreq but haven't gotten to it yet - that may get closer to what you're wanting it to do

@Kendra_HS_twitter : if you're sure none other git processes are running ps -ef | grep git you can rm -rf /root/Eviesaps/.git/index.lock. If that doesn't work save the git for future reference and create a new one mv .git ../git-corrupted ; git init

@PieterGit thanks for the response. I haven't dealt with this before, so I'm not totally understanding what you are saying, sorry! I had this before, but just deleted and re-installed everything! Can you help me understand?

SO I ran the first command, and got this response... what does that mean? root 7736 2700 0 18:30 pts/0 00:00:00 grep git

ps -ef | grep git shows all the processes that have git in their names. the only one running is the command trying to find the git processes, so it's safe to remove the lock

if a git process is running, removing the lock is not a good idea

i'll stop for toningt, but if you need more help i'm sure somebody else would be willing to help. good luck getting your rig back online. reinstalling a rig because of a broken git repo is a bit too much (and that's an understatement :smile: )

git stores it's repository information (all the inforamtion about files that are changed) in a directory /root/Eviesaps/.git. That directory / repo can get corrupt (or a git processes did not return the lock when it was ready; e.g. because you ran out of battery or the rig was out of power for some reason)