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

24th
Feb 2019
ecc1 @ecc1 thinks of the adrenaline injection scene in Pulp Fiction :-)
tepidjuice
@tepidjuice
Feb 24 00:09
@ecc1 could I not request they send one?
As they must have missed it when dispatching my order/
Eric
@ecc1
Feb 24 00:11
sure, if it was supposed to be included (I haven't dealt with them myself)
Dana Lewis
@danamlewis
Feb 24 00:15
I think it should have been included, yes
Jon Cluck
@cluckj
Feb 24 00:21
check the box? it's really small and mostly transparent
I think mine came in a small bag?
tepidjuice
@tepidjuice
Feb 24 00:24
Got it ages ago and I was pretty thorough checking through the box took out all the bags.
Jon Cluck
@cluckj
Feb 24 00:35
:(
tepidjuice
@tepidjuice
Feb 24 00:38
Never mind sent them an email. Anyone able to suggest a good place to buy one if they don't want to send one out? I'm in aus so postage can be frustratingly expensive.
Jon Cluck
@cluckj
Feb 24 00:45
any 916 Mhz antenna with a u.fl connector on it will work, you can probably source them locally
@LilDucky may have ideas
djnoor
@djnoor
Feb 24 00:49
I just upgraded 2 Edison/Explorer Board rigs to 0.7.0 dev. There are two lights to the right of the UART port. They blink periodically. On one rig they both blink green. On the other, they one blinks red and the other blinks green. The Explorer boards are both v. 1.3. Is this normal? The rigs are both looping fine.
Scott Leibrand
@scottleibrand
Feb 24 00:52
@renegadeandy "days missed" is the number of days for which it interpolated that hour due to missing basal data (due to it all being excluded for meals etc.)
straykatz
@straykatz
Feb 24 02:31
Hi there, quick Edison WIFI antenna question. I have some Edisons that are EDI2.SPOF.AL.MP - aka, they do NOT have the internal WIFI antenna. This matters, as it's not picking up a WIFI signal :-(. Am I correct that I can use any 2.4GHz uFL antenna in this case? such as this one? https://www.adafruit.com/product/2308?gclid=Cj0KCQiA-8PjBRCWARIsADc18TJ8GvwkZPw2NHJBCDqeUY_r0gX5o6ke4lMEUQ_xhHugQxtJq9kleDgaAtPUEALw_wcB
straykatz
@straykatz
Feb 24 03:15
@djnoor Hi, I have older 3 boards of two different versions (1.2 and 1.3) with a variety of LED colors - one all red, one is green and red, and the third one is all green - but sadly broken (I like the all green-colors best).
Jon Cluck
@cluckj
Feb 24 03:24
yeah, if the edison has a u.fl for it (there's one on the explorer board but that's for the 900mhz radio)
straykatz
@straykatz
Feb 24 03:25
yes it does. and no the 915 does not work :) but it fits
thanks
Jon Cluck
@cluckj
Feb 24 03:25
:thumbsup:
were you able to get up and running?
straykatz
@straykatz
Feb 24 03:26
ReFLASH, baby.
Yes. :)
Jon Cluck
@cluckj
Feb 24 03:27
yay
straykatz
@straykatz
Feb 24 03:27
Thank you for your help. In the end, a clean slate was what was needed. I moved slowly from installing Master to Dev, and it's running as if it never had an issue. I used a new download of the Jubilinux image - apparently mine was corrupted.
Aarti Kashyap
@grep-aarkash
Feb 24 03:28
Hey! has anyone used the openaps simple-simulator?
Jon Cluck
@cluckj
Feb 24 03:28
:D
Monali Patel
@mhp118
Feb 24 03:56
Help, please. I'm trying to install OpenAPS on the Pi Hat and have tried installing 10 times with each time getting a different error. I was able to resolve the previous ones however the latest error is one that I cannot figure out. Pasting the error in 2 screen shots. The 2nd screen shot is when the error first appeared.
Jon Cluck
@cluckj
Feb 24 04:09
after you switched to dev, did you run npm run global-install?
Monali Patel
@mhp118
Feb 24 04:10
I have not been able to get back Run openaps-install.sh
*get past Run openaps-install.sh
Jon Cluck
@cluckj
Feb 24 04:19
can you go into ~/src/oref0 and do npm run global-install? it looks like some of the commands that oref0-setup is trying to run aren't linked properly
Monali Patel
@mhp118
Feb 24 04:21
Ok trying now, thank you much for your help!
Dana Lewis
@danamlewis
Feb 24 04:26
@grep-aarkash not anyone other than @scottleibrand & I, as far as I know. It’s a bit dusty.
@straykatz :+1: glad things are better today!
Monali Patel
@mhp118
Feb 24 04:41
@cluckj It was the firewall. I switched to tethering on the phone and it's now running through the rest of the install script except now I'm spinning at npm WARN deprecated node-uuid@1.4.8: Use uuid module instead. I have not moved for the past 5 minutes.
Jon Cluck
@cluckj
Feb 24 04:44
ah okay :)
the warnings are fine, the ERR is probably going to cause a problem later
JustineAnne
@MicheleJustine
Feb 24 05:21

Hi there, I am currently trying to install the dependencies for OpenAPS using the bootstrap script and I run into the following error each time:

Depends: node-sha (>= 2.0.1~) but it is not going to be installed
Depends: node-slide (>= 1.1.6~) but it is not going to be installed
Depends: node-sorted-object (>= 2.0.1~) but it is not going to be installed
Depends: node-from2 but it is not going to be installed
Depends: node-stream-iterate but it is not going to be installed
Depends: node-ssri (>= 5.2.4~) but it is not going to be installed
Depends: node-strip-ansi (>= 4.0~) but it is not going to be installed
Depends: node-tar (>= 4.4~) but it is not going to be installed
Depends: node-text-table (>= 0.2~) but it is not going to be installed
Depends: node-uid-number (>= 0.0.6~) but it is not going to be installed
Depends: node-unique-filename (>= 1.1~) but it is not going to be installed
Depends: node-unpipe (>= 1.0~) but it is not going to be installed
Depends: node-boxen (>= 1.2.1~) but it is not going to be installed
Depends: node-import-lazy but it is not going to be installed
Depends: node-is-npm (>= 1.0~) but it is not going to be installed
Depends: node-latest-version (>= 3.0~) but it is not going to be installed
Depends: node-semver-diff (>= 2.0~) but it is not going to be installed
Depends: node-xdg-basedir (>= 3.0~) but it is not going to be installed
Depends: node-validate-npm-package-name (>= 3.0~) but it is not going to be installed
Depends: node-which (>= 1.3~) but it is not going to be installed
Depends: node-wrappy (>= 1.0.2~) but it is not going to be installed
Depends: node-write-file-atomic (>= 2.3~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

I am unsure of what steps to take to resolve this error. Would anyone be able to provide suggestions?

Zakm0n
@Zakm0n
Feb 24 06:09
So, my smb checks are failing like crazy and I can't see why.
Scott Leibrand
@scottleibrand
Feb 24 06:11
Paste the error?
Zakm0n
@Zakm0n
Feb 24 06:11
Retrying SMB checks
Listening for 10s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun 24 Feb 01:04:43 EST 2019
Checking pump status (suspended/bolusing): {"status":"normal","bolusing":false,"suspended":false}
Pump history updated through 2019-02-24T01:04:02-05:00 with 2 new records; meal.json refreshed: {"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":10.05,"maxDeviation":10.5,"minDeviation":8.92,"slopeFromMaxDeviation":-0.21,"slopeFromMinDeviation":0.273,"allDeviations":[10,10,11,9,9],"lastCarbTime":0,"bwFound":false}
Listening for 10s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun 24 Feb 01:05:47 EST 2019
Checking that pump clock: "2019-02-24T01:05:45-05:00" is within 90s of current time: 2019-02-24T01:05:49-0500
Temp refreshed: monitor/temp_basal.json: {"duration":30,"temp":"absolute","rate":11.6}
{"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":10.05,"maxDeviation":10.5,"minDeviation":8.92,"slopeFromMaxDeviation":-0.21,"slopeFromMinDeviation":0.273,"allDeviations":[10,10,11,9,9],"lastCarbTime":0,"bwFound":false}
Autotune exists! Hoorah! You can use microbolus-related features.
{"iob":12.642,"activity":0.1271,"basaliob":12.353,"bolusiob":0.289,"netbasalinsulin":23.6,"bolusinsulin":2.8,"time":"2019-02-24T06:05:48.000Z","iobWithZeroTemp":{"iob":12.642,"activity":0.1271,"basaliob":12.353,"bolusiob":0.289,"netbasalinsulin":23.6,"bolusinsulin":2.8,"time":"2019-02-24T06:05:48.000Z"},"lastBolusTime":1550979521000,"lastTemp":{"rate":11.6,"timestamp":"2019-02-24T01:04:02-05:00","started_at":"2019-02-24T06:04:02.000Z","date":1550988242000,"duration":2.77}}
{"delta":1,"glucose":306,"noise":1,"short_avgdelta":0.56,"long_avgdelta":0.66,"date":1550988258973,"last_cal":0}
Autosens ratio: 1.2; Adjusting basal from 2.35 to 2.8; ISF from 14.1 to 11.8; CR: 4.139
currenttemp: { duration: 30, temp: 'absolute', rate: 11.6 } lastTempAge: 3 m tempModulus: 3 m
Adjusting targets for high BG: min_bg from 120 to 80; target_bg from 120 to 80; max_bg from 120 to 80
SMB enabled due to enableSMB_always
profile.sens: 14.105 sens: 11.8 CSF: 2.8509301763711044
Limiting carb impact from 8.1 to 7.1 mg/dL/5m ( 30 g/h )
Carb Impact: 7.1 mg/dL per 5m; CI Duration: 0 hours; remaining CI (~2h peak): 0 mg/dL per 5m
UAM Impact: 8.1 mg/dL per 5m; UAM Duration: 3 hours
minPredBG: 243 minIOBPredBG: 191 minZTGuardBG: 198 minUAMPredBG: 294 avgPredBG: 243 COB: 0 / 0
BG projected to remain above 80 for 240 minutes
naive_eventualBG: 157 bgUndershoot: -97 zeroTempDuration: 240 zeroTempEffect: 110 carbsReq: -73
IOB 12.642 > COB 0; mealInsulinReq = 0
profile.maxUAMSMBBasalMinutes: 30 profile.current_basal: 2.329
naive_eventualBG 157, 0m 0U/h temp needed; last bolus 147.9m ago; maxBolus: 1.2
2019-02-24T06:06:32.331Z
Checking deliverAt: 2019-02-24T06:06:32.331Z is within 1m of current time: Sun 24 Feb 01:06:33 EST 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","bg":306,"tick":"+1","eventualBG":294,"insulinReq":5.358,"reservoir":"210.4\n","deliverAt":"2019-02-24T06:06:32.331Z","sensitivityRatio":1.2,"COB":0,"IOB":12.642,"units":1.2}
"COB: 0, Dev: 48, BGI: -7, ISF: 12, CR: 4.14, Target: 80, minPredBG 243, minGuardBG 294, IOBpredBG 192, UAMpredBG 294; Eventual BG 294 >= 80, max_iob 18,  insulinReq 5.358; maxBolus 1.2. Microbolusing 1.2U. adj. req. rate: 13.5 to maxSafeBasal: 11.645000000000001, temp 11.6 >~ req 11.6U/hr. "
UAM: REMOVED TO SAVE CHARS
IOB:
ZT:
No smb_enact needed. Checking pump status (suspended/bolusing): {"status":"normal","bolusing":false,"suspended":false}
Temp refreshed: monitor/temp_basal.json: {"duration":29,"temp":"absolute","rate":11.6}
2019-02-24T06:06:32.331Z
Checking deliverAt: 2019-02-24T06:06:32.331Z is within 1m of current time: Sun 24 Feb 01:06:44 EST 2019
and that smb-suggested.json is less than 1m old
Checking reservoir: reservoir level before: 210.4, suggested: 210.4 and after: 210.2
Listening for 10s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun 24 Feb 01:06:59 EST 2019
Retry 2 of smb_check_everything
Here is my smb suggested:
enact/smb-suggested.json: {"temp":"absolute","bg":316,"tick":"+10","eventualBG":401,"insulinReq":5.236,"reservoir":"209.4\n","deliverAt":"2019-02-24T06:11:57.678Z","sensitivityRatio":1.2,"COB":0,"IOB":12.764,"units":1.2}
"COB: 0, Dev: 83, BGI: -8, ISF: 12, CR: 4.14, Target: 80, minPredBG 302, minGuardBG 322, IOBpredBG 200, UAMpredBG 401; Eventual BG 401 >= 80, max_iob 18,  insulinReq 5.236; maxBolus 1.2. Microbolusing 1.2U. adj. req. rate: 13.3 to maxSafeBasal: 11.645000000000001, temp 11.6 >~ req 11.6U/hr. "
UAM: [316,322,327,333,337,342,346,350,354,358,362,365,369,372,376,379,382,385,388,391,393,396,398,400,401]
IOB: [316,315,313,311,308,305,301,297,293,288,283,277,271,266,261,256,251,247,243,239,235,232,229,226,223,221,219,217,215,213,212,210,209,208,207,206,205,204,203,203,202,202,201,201,201,201,200]
ZT:  [316,308,301,293,286,278,271,265,258,252,247,241,236,232,228,224,221,218,215,213,211,210,209,208,207,207,207,208,208]
No smb_enact needed. Checking pump status (suspended/bolusing): {"status":"normal","bolusing":false,"suspended":false}
Zakm0n
@Zakm0n
Feb 24 06:17
Since i've setup this new pi/hat rig, it seems like it almost never smbs, where my old edison would do it all the time.
Zakm0n
@Zakm0n
Feb 24 06:28
basals are working, just not smb
viq
@viq
Feb 24 10:25
@MicheleJustine what are the lines just above that Depends stuff you pasted? Can you paste output of apt-get update? That's where I would start debugging, seeing as I know debian but aren't too familiar with oaps
amspoke
@amspoke
Feb 24 12:57
Hello, after a small sucessfull afternoon of starting looping, everything stoped working, and i am in a continuous loop since yesterday afternoon, in which always appears the following sequence. Please help:
Feb 24 13:22:05 robertoAPS pump-loop.log: Starting oref0-pump-loop at Sun 24 Feb 13:22:05 CET 2019 with 25 second wait_for_silence: Feb 24 13:22:07 robertoAPS pump-loop.log: Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory Feb 24 13:22:48 robertoAPS pump-loop.log: Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!) Feb 24 13:23:15 robertoAPS pump-loop.log: Preflight fail. Retrying preflight Feb 24 13:28:00 robertoAPS pump-loop.log: Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistory Feb 24 13:28:00 robertoAPS pump-loop.log: Warning: setting mealCOB to 0 because currentDeviation is null/undefined Feb 24 13:28:00 robertoAPS pump-loop.log: and meal.json Feb 24 13:28:43 robertoAPS pump-loop.log: Checking pump clock: "2019-02-24T13:28:40+01:00" is within 90s of current time: Sun 24 Feb 13:28:43 CET 2019 Feb 24 13:28:44 robertoAPS pump-loop.log: Error: pumphistory too old Feb 24 13:28:44 robertoAPS pump-loop.log: oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning Feb 24 13:29:35 robertoAPS pump-loop.log: Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!) Feb 24 13:30:25 robertoAPS pump-loop.log: Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!) Feb 24 13:32:23 robertoAPS pump-loop.log: mmtune: "916.588", 5, -30 No wait required. Feb 24 13:32:23 robertoAPS pump-loop.log: If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop. Feb 24 13:32:23 robertoAPS pump-loop.log: Unsuccessful oref0-pump-loop at Sun 24 Feb 13:32:22 CET 2019
Any help?
Jon Cluck
@cluckj
Feb 24 15:08
are you running the master branch on a pi0?
Monali Patel
@mhp118
Feb 24 15:17
Has anyone been able to successfully "Run openaps-install.sh"on their Pi Hat in the past 2 days? I can't seems to get past the DeprecationWarning? The system just hangs there and does not finish installing the script. I've gotten to this part the previous 4 times and have not been able to get past this point. On a separate note, if I run the master branch install it seems to work fine but not applicable for the Pi Hat.
Jon Cluck
@cluckj
Feb 24 15:28
how long does it hang for? the pi0 is very slow
Monali Patel
@mhp118
Feb 24 15:59
@cluckj left it overnight and it was still there this morning. And the previous 3 times had it hanging for well over 2 hours.
Jon Cluck
@cluckj
Feb 24 16:02
yikes
which version of node and npm are you using? node --version and npm --version
Monali Patel
@mhp118
Feb 24 16:49
@cluckj node v8.11.1 and npm 1.4.21
Zakm0n
@Zakm0n
Feb 24 16:51
So I'm trying to figure out why my smb Checks keep failing. I found where someone posted about running mdt -f internal button esc but when I run it, I'm getting no response. My basals are working and updating, but I'm maybe getting 1% of the smbs I'm used to.
Zakm0n
@Zakm0n
Feb 24 17:02
Another thing I've noticed is smb-suggested is calling for 1.9u bolus, and then the rig is saying smb not needed.
Feb 24 17:12

@renegadeandy "days missed" is the number of days for which it interpolated that hour due to missing basal data (due to it all being excluded for meals etc.)

so is this a 'bad' thing, a 'good' thing or neutral?

amspoke
@amspoke
Feb 24 17:13
Ok, i found my problem, if i get my RPi0 to 700Mhz the scripts are not fast enough to update the info, and the whole loop stops working :-( so i need to go back to the standard ARM Frequency and this drains the battery in 4-6 hours. This is not enough for my son to go to the school with the rig... any help? (I'm using a 3800mah battery!)
Dana Lewis
@danamlewis
Feb 24 17:26
@amspoke worth trying a Pi3?
Scott Leibrand
@scottleibrand
Feb 24 17:27
@Zakm0n reservoir level before: 210.4, suggested: 210.4 and after: 210.2
Are you underclocked? Looks like your max basal is too high and your rig is too slow to get through the refresh checks before the pump gives 0.2U of basal.
If the rig is running at full speed, you could lower your max basal so the reservoir only decreases by 0.1U between checks. Or you could modify the code to relax that safety check from 0.1 to 0.2U.
Zakm0n
@Zakm0n
Feb 24 17:33
I was underclocked for a while, but I just reversed that. How do I modify the code? I am very insulin resistant, so I need the high basals.
Scott Leibrand
@scottleibrand
Feb 24 17:34
If SMB is working you won’t need a very high max basal. Maybe 2x your normal.
I’ve never seen this problem with max basals below 4 U/h
Zakm0n
@Zakm0n
Feb 24 17:35
Well, I guess I'll try that and see what happens.
Scott Leibrand
@scottleibrand
Feb 24 17:35
But see if you still see the issue without underclocking.
Once it gets an SMB or two in and can switch to setting zero temps, it will no longer be an issue for that meal.
Teamhrach
@Teamhrach
Feb 24 17:58
Hi, I'm trying to get my Raspberry Pi up and running without success. It seems to be connecting to my pump and to NS but gives the errors listed below. Has anyone any suggestions as to how I can fix this?
Feb 24 17:55:56 tomaspi cgm-loop.log: full refresh of cgm data
Feb 24 17:55:56 tomaspi cgm-loop.log: rm: cannot remove 'monitor/cgm-mm-glucosedirty.json': No such file or directory
Feb 24 17:55:56 tomaspi cgm-loop.log: rm: cannot remove 'cgm/cgm-glucose.json': No such file or directory
Feb 24 17:55:56 tomaspi cgm-loop.log: rm: cannot remove 'cgm/glucose.json': No such file or directory
Feb 24 17:55:56 tomaspi cgm-loop.log: rm: cannot remove 'monitor/glucose.json': No such file or directory
Dana Lewis
@danamlewis
Feb 24 18:26
@Teamhrach what type of cgm are you using?
And how are you getting bg data to your rig?
Teamhrach
@Teamhrach
Feb 24 18:27
Via the Pi
Feb 24 18:30:32 tomaspi cgm-loop.log: 2019/02/24 18:30:32 read 0 entries from monitor/cgm-mm-glucosedirty.json
Feb 24 18:30:33 tomaspi cgm-loop.log: 2019/02/24 18:30:33 connected to CC111x radio on /dev/spidev0.0
Feb 24 18:30:33 tomaspi cgm-loop.log: 2019/02/24 18:30:33 setting frequency to 868.250
Feb 24 18:30:33 tomaspi cgm-loop.log: 2019/02/24 18:30:33 model 715 pump
Feb 24 18:30:33 tomaspi cgm-loop.log: 2019/02/24 18:30:33 CGM clock difference = 4.584430711s
Feb 24 18:30:33 tomaspi cgm-loop.log: 2019/02/24 18:30:33 retrieving records since 2019-02-23 12:30:29
Feb 24 18:30:34 tomaspi cgm-loop.log: 2019/02/24 18:30:34 6b/4b decoding failure
Feb 24 18:30:34 tomaspi cgm-loop.log: cgm full refresh failed.
Feb 24 18:30:34 tomaspi pump-loop.log: Couldn't mdt_get_bg
Jon Cluck
@cluckj
Feb 24 18:32
it looks like you chose MDT as your CGM type during setup? can you re-run oref0-setup with G5 or xdrip as your cgm type?
Teamhrach
@Teamhrach
Feb 24 18:33
I presume that MDT stands for Medtronic?
Jon Cluck
@cluckj
Feb 24 18:33
yes
Teamhrach
@Teamhrach
Feb 24 18:34
But I use the 640g as a CGM?
It seems counter intuitive to pick a dummy name?
Jon Cluck
@cluckj
Feb 24 18:35
the MDT/medtronic option in openaps setup is only for the enlite sensor attached to the pump you're looping with
Teamhrach
@Teamhrach
Feb 24 18:35
I've tried so many other things without success so I guess that there is no harm in trying this
Oh - that makes sense. I'll give this a try then
I 'll you know how I get on
Jon Cluck
@cluckj
Feb 24 18:37
:thumbsup:
Teamhrach
@Teamhrach
Feb 24 20:19
@cluckj @danamlewis wohoo that worked - the Pi rig is looping now.
Jon Cluck
@cluckj
Feb 24 20:32
:clap: great! :thumbsup:
Teamhrach
@Teamhrach
Feb 24 20:35
@danamlewis I wonder, for others setting up a 640G on the Pi, would it be worth adding in a note in relation to the above? I'd be happy to suggest some text?
I can try this via a PR?
Dana Lewis
@danamlewis
Feb 24 20:42
JustineAnne
@MicheleJustine
Feb 24 21:14

@viq I am unable to view the output above the depends since it goes blank. This is what I am able to see:
Depends: node-has-unicode (>= 2.0.1~) but it is not going to be installed
Depends: node-hosted-git-info (>= 2.6~) but it is not going to be installed
Depends: node-iferr (>= 0.1.5~) but it is not going to be installed
Depends: node-inflight (>= 1.0.6~) but it is not going to be installed
Depends: node-inherits (>= 2.0.3~) but it is not going to be installed
Depends: node-ini (>= 1.3.5~) but it is not going to be installed
Depends: node-npm-package-arg but it is not going to be installed
Depends: node-promzard but it is not going to be installed
Depends: node-jsonstream (>= 1.3.2~) but it is not going to be installed
Depends: node-json-parse-better-errors (>= 1.0.1~) but it is not going to be installed
Depends: node-lazy-property (>= 1.0~) but it is not going to be installed
Depends: node-libnpx (>= 10.0.1~) but it is not going to be installed
Depends: node-lockfile (>= 1.0.3~) but it is not going to be installed
Depends: node-lru-cache (>= 4.1.1~) but it is not going to be installed
Depends: node-mississippi (>= 3.0~) but it is not going to be installed
Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
Depends: node-move-concurrently (>= 1.0.1~) but it is not going to be installed
Depends: node-nopt but it is not going to be installed
Depends: node-normalize-package-data (>= 2.4~) but it is not going to be installed
Depends: node-gyp (>= 3.6.2~) but it is not going to be installed
Depends: node-resolve-from (>= 4.0~) but it is not going to be installed
Depends: node-encoding but it is not going to be installed
Depends: node-errno but it is not going to be installed
Depends: node-npmlog (>= 4.1.2~) but it is not going to be installed
Depends: node-once (>= 1.4~) but it is not going to be installed
Depends: node-opener (>= 1.4.3~) but it is not going to be installed
Depends: node-osenv (>= 0.1.5~) but it is not going to be installed
Depends: node-path-is-inside (>= 1.0.2~) but it is not going to be installed
Depends: node-promise-inflight (>= 1.0.1~) but it is not going to be installed
Depends: node-ansi but it is not going to be installed
Depends: node-qw (>= 1.0.1~) but it is not going to be installed
Depends: node-read (>= 1.0.7~) but it is not going to be installed
Depends: node-read-package-json (>= 2.0.13~) but it is not going to be installed
Depends: node-request (>= 2.83~) but it is not going to be installed
Depends: node-retry (>= 0.10.1~) but it is not going to be installed
Depends: node-rimraf (>= 2.6.2~) but it is not going to be installed
Depends: node-safe-buffer (>= 5.1.1~) but it is not going to be installed
Depends: node-semver (>= 5.5~) but it is not going to be installed
Depends: node-sha (>= 2.0.1~) but it is not going to be installed
Depends: node-slide (>= 1.1.6~) but it is not going to be installed
Depends: node-sorted-object (>= 2.0.1~) but it is not going to be installed
Depends: node-from2 but it is not going to be installed
Depends: node-stream-iterate but it is not going to be installed
Depends: node-ssri (>= 5.2.4~) but it is not going to be installed
Depends: node-strip-ansi (>= 4.0~) but it is not going to be installed
Depends: node-tar (>= 4.4~) but it is not going to be installed
Depends: node-text-table (>= 0.2~) but it is not going to be installed
Depends: node-uid-number (>= 0.0.6~) but it is not going to be installed
Depends: node-unique-filename (>= 1.1~) but it is not going to be installed
Depends: node-unpipe (>= 1.0~) but it is not going to be installed
Depends: node-boxen (>= 1.2.1~) but it is not going to be installed
Depends: node-import-lazy but it is not going to be installed
Depends: node-is-npm (>= 1.0~) but it is not going to be installed
Depends: node-latest-version (>= 3.0~) but it is not going to be installed
Depends: node-semver-diff (>= 2.0~) but it is not going to be installed
Depends: node-xdg-basedir (>= 3.0~) but it is not going to be installed
Depends: node-validate-npm-package-name (>= 3.0~) but it is not going to be installed
Depends: node-which (>= 1.3~) but it is not going to be installed
Depends: node-wrappy (>= 1.0.2~) but it is not going to be installed
Depends: node-write-file-atomic (>= 2.3~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

The output of apt-get update is the following:
Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease
Hit:4 http://cdn-fastly.deb.debian.org/debian stretch-backports InRelease
Hit:5 http://cdn-fastly.deb.debian.org/debian stretch Release
Hit:6 https://deb.nodesource.com/node_6.x stretch InRelease

viq
@viq
Feb 24 21:20
@MicheleJustine you can close a block of text in triple backticks () on each side to make it formatted as code. You probably can also scroll withshift+page up
That backfired :p
is the character for quoting code
shift + page up are the buttons for scrolling
I guess it's trying to install node... What happens if you do apt install node?
LilDucky
@LilDucky
Feb 24 21:43
@tepidjuice send me a PM if I can help out
JustineAnne
@MicheleJustine
Feb 24 21:51

@viq Thank you for your help. Using the page up I am still not able to scroll through the output. This is the output of apt install node:

Reading package lists... Done
Building dependency tree
Package node is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'node' has no installation candidate

viq
@viq
Feb 24 21:52
triple backticks for longer block ;) How about apt-cache showpkg node ?
JustineAnne
@MicheleJustine
Feb 24 21:53

@viq This is the output
Package: node
Versions:

Reverse Depends:
nodejs-legacy,node
Dependencies:
Provides:
Reverse Provides: 

viq
@viq
Feb 24 21:56
Oh, I guess it was apt-cache policy node. And I guess there needs to be a newline between code and backticks. As you can see don't always remember the formatting either ;)
shift + enter for newline without sending
JustineAnne
@MicheleJustine
Feb 24 21:57
@viq thank you. This is the output:
node:
Installed: (none)
Candidate: (none)
Version table:
viq
@viq
Feb 24 21:58
That's much less output than I expected...
JustineAnne
@MicheleJustine
Feb 24 21:59
@viq unfortunately that's the only output given.
viq
@viq
Feb 24 22:00
..oh, I may have an idea
https://deb.nodesource.com/node_6.x stretch InRelease - that's a repo for ancient node, aren't 8 and 10 versions used now?
@MicheleJustine that's a fresh install, or you're trying to upgrade an existing rig?
JustineAnne
@MicheleJustine
Feb 24 22:01
@viq this is a fresh install. I was trying to use the 10x version previously but changed after experiencing the same error.
viq
@viq
Feb 24 22:03
Let me find what the install script tries to do
Which script are you running when this happens?
viq
@viq
Feb 24 22:10
Eric
@ecc1
Feb 24 22:10
The Debian package is nodejs, not node
viq
@viq
Feb 24 22:11
Ah, so it is. So what would be apt-cache showpkg nodejs?
straykatz
@straykatz
Feb 24 22:14
A follow-up on the "plugin the G6 receiver question" - @cluckj
there was one PR that will make it easier for the support to happen that was merged, but the support isn't merged yet
just needs openaps/openaps#139 - I read this to mean - "not yet" globally. but is there a way to make it work for just case for the G6 receiver (without consideration for other receivers that I personally neither have nor need :) )
Thank you!
Jon Cluck
@cluckj
Feb 24 22:15
@straykatz yep, you can add the support for it pretty easily :)
straykatz
@straykatz
Feb 24 22:17
@cluckj That's great :-D
And how :)?
viq
@viq
Feb 24 22:18
@MicheleJustine sorry, I'm going to call it a night, I hope you figure it out. I'd start with nodejs setup, so possibly running ttps://deb.nodesource.com/setup_8.x manually
JustineAnne
@MicheleJustine
Feb 24 22:19

@viq it is the bootstrap script that is for setting up the wifi connection and installing the dependencies. This is the script:

#!/bin/bash
(
dmesg -D
echo Scanning for wifi networks:
ifup wlan0
wpa_cli scan
echo -e "\nStrongest networks found:"
wpa_cli scan_res | sort -grk 3 | head | awk -F '\t' '{print $NF}' | uniq set -e echo -e /"\nWARNING: this script will back up and remove all of your current wifi configs." read -p "Press Ctrl-C to cancel, or press Enter to continue:" -r echo -e "\nNOTE: Spaces in your network name or password are ok. Do not add quotes." read -p "Enter your network name: " -r SSID=$REPLY
PSK=$REPLY cd /etc/network cp interfaces interfaces.$(date +%s).bak
echo -e "auto lo\niface lo inet loopback\n\nauto usb0\niface usb0 inet static\n  address 10.11.12.13\n  netmask 255.255.255.0\n\nauto wlan0\niface wlan0 inet dhcp\n  wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf" > interfaces
echo -e "\n/etc/network/interfaces:\n"
cat interfaces
cd /etc/wpa_supplicant/
cp wpa_supplicant.conf wpa_supplicant.conf.$(date +%s).bak echo -e "ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev\nupdate_config=1\nnetwork={\n ssid=\"$SSID\"\n  psk=\"\$PSK\"\n}" > wpa_supplicant.conf
echo -e "\n/etc/wpa_supplicant/wpa_supplicant.conf:\n"
cat wpa_supplicant.conf
echo -e "\nAttempting to bring up wlan0:\n"
ifdown wlan0; ifup wlan0
sleep 10
echo -ne "\nWifi SSID: "; iwgetid -r
sleep 5
curl https://raw.githubusercontent.com/openaps/oref0/master/bin/openaps-install.sh > /tmp/openaps-install.sh
bash /tmp/openaps-install.sh
)

ok, thank you for all of your help !

Jon Cluck
@cluckj
Feb 24 22:31
@straykatz gimme a bit to get the commands together
Zakm0n
@Zakm0n
Feb 24 22:32
@scottleibrand dropping max basal fixed it. Working great now.
Jon Cluck
@cluckj
Feb 24 22:35
(and I want to make sure it works for me before sending you off on a wild goose chase)
straykatz
@straykatz
Feb 24 23:13
Thankyou Jon.
Jon Cluck
@cluckj
Feb 24 23:48
pip install git+git://github.com/openaps/dexcom_reader.git to get dexcom_reader with the right patches
then for openaps:
cd ~/src/
git clone https://github.com/openaps/openaps
cd openaps
python setup.py install