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

30th
Apr 2019
Katja Jacob
@straykatz
Apr 30 05:38 UTC
Hello. I just noticed this error: Checking pump status (suspended/bolusing): {"status":"normal","bolusing":false,"suspended":false} Sending ESC ESC, ESC ESC ESC ESC to exit any open menus before SMBing Couldn't mdt -f internal button esc esc - continuing Couldn't smb_bolus Does anyone know what this is about? Pump is not looping. Rebooting the rig got it back to looping (yay!👌). Don't think I have noticed that error before.
Scott Leibrand
@scottleibrand
Apr 30 06:20 UTC
It happens transiently sometimes when pump comms are weak or another rig is transmitting.
It’ll retry on its own: it’s only a concern if the same message repeats dozens of times in a row.
And even then, it’ll try to set a high temp first before trying to bolus if it hasn’t been able to bolus recently.
Katja Jacob
@straykatz
Apr 30 14:40 UTC
Ah, I see. Thank you, Scott.👍
NSewar
@nsewar01
Apr 30 16:01 UTC
pr 30 08:59:54 nsewar02 app/web.1: tick 2019-04-30T15:59:53.886Z
Apr 30 08:59:59 nsewar02 app/web.1: searching treatments q { find: { created_at: { '$gte': '2019-04-22T15:59:58.887Z' } },
Apr 30 08:59:59 nsewar02 app/web.1: sort: { created_at: 1 } }
Apr 30 08:59:59 nsewar02 app/web.1: Load Complete:
Apr 30 08:59:59 nsewar02 app/web.1: sgvs:95, profiles:1, devicestatus:75
Apr 30 08:59:59 nsewar02 app/web.1: reloading sandbox data
Apr 30 08:59:59 nsewar02 app/web.1: OpenAPS hasn't reported a loop yet
Apr 30 08:59:59 nsewar02 app/web.1: WS: running websocket.update
Apr 30 08:59:59 nsewar02 app/web.1: delta calculation indicates no new data is present
Apr 30 09:00:07 nsewar02 app/web.1: GRANTED: 94.8.143.234 no-token api:entries:read default
Apr 30 09:00:08 nsewar02 heroku/router: at=info method=GET path="/api/v1/entries/sgv.json?find[date][$gte]=1556553606534&count=1000" host=nsewar02.herokuapp.com request_id=83833e60-2bde-43f0-95a4-c48d1b51d74d fwd="94.8.143.234" dyno=web.1 connect=0ms service=16ms status=200 bytes=4353 protocol=https
Apr 30 09:00:14 nsewar02 app/web.1: GRANTED: 94.8.143.234 no-token api:treatments:read default
Apr 30 09:00:14 nsewar02 heroku/router: at=info method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2019-04-29T22:00+0000&find[eventType]=Temporary+Target" host=nsewar02.herokuapp.com request_id=a4be004d-cee4-46ed-aec6-58bd04492e98 fwd="94.8.143.234" dyno=web.1 connect=1ms service=4ms status=200 bytes=611 protocol=https
Apr 30 09:00:19 nsewar02 app/web.1: GRANTED: 94.8.143.234 no-token api:treatments:read default
Apr 30 09:00:20 nsewar02 heroku/router: at=info method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2019-04-29T04:00+0000&find[carbs][$exists]=true" host=nsewar02.herokuapp.com request_id=216d1b5c-d4bb-4535-bfae-ea73e37be7bf fwd="94.8.143.234" dyno=web.1 connect=0ms service=4ms status=200 bytes=611 protocol=https
Any advice as to why Nightscout isnt picking up my XDrip info. The above is papertrail log. Thanks
Natalia S.
@Propelld
Apr 30 17:54 UTC
@nsewar01 is your actual Nightscout site working or is it just not passing data to xDrip?
Jason Nerothin
@jasonnerothin
Apr 30 17:57 UTC
I know this is the DEV channel, but this is some nice recognition of the community's efforts: https://www.theatlantic.com/science/archive/2019/04/looping-created-insulin-pump-underground-market/588091/
NSewar
@nsewar01
Apr 30 18:56 UTC
Natalia. I'm getting bs readings in nightscout from dexcom, so it's the comns between the rig and nightscout that are defective.
HuffCam
@HuffCam
Apr 30 21:39 UTC
Hello
This is probably desperately offtopic; is anyone likely to shout at me?
Don't want to be a pain.
Dana Lewis
@danamlewis
Apr 30 21:54 UTC
@HuffCam if it’s super off topic we may suggest another place to post it as well, but it won’t involve shouting.
jonny772
@jonny772
Apr 30 22:11 UTC

Im struggling to get my openAPS loop running (Edison, explorer board). Ive got it running but i think its not receiving data from either the pump (712) or NS. It hasn't pushed any data to NS. Errors below:

Starting oref0-pump-loop at Tue Apr 30 23:06:02 BST 2019 with 21 second wait_for_silence:
MDT CGM configured; not waiting
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight (x12 models do not support SMB safety checks, SMB will not be available.) OK.
Attempting to retrieve MDT CGM data from pump
Unable to get cgm data from pump
Profile less than 60m old; Profile valid. Refgrep: monitor/status.json: No such file or directory
cat: monitor/status.json: No such file or directory
/usr/bin/oref0-pump-loop: line 567: test: ==: unary operator expected
cat: monitor/status.json: No such file or directory
/usr/bin/oref0-pump-loop: line 568: test: ==: unary operator expected

cat: monitor/status.json: No such file or directory
Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)

Jon Cluck
@cluckj
Apr 30 22:14 UTC
what's your cgm source?
jonny772
@jonny772
Apr 30 22:15 UTC
Spike app recording into NS from a Miao
Jon Cluck
@cluckj
Apr 30 22:16 UTC
can you re-run setup with a different CGM choice, like G5 (even though you're not using it)?
jonny772
@jonny772
Apr 30 22:17 UTC
i have tried both a blank CGM source setup and a MDT. I can give it a go with G5 as well
Jon Cluck
@cluckj
Apr 30 22:17 UTC
the MDT cgm choice has some special code in it
jonny772
@jonny772
Apr 30 22:17 UTC
ah
Jon Cluck
@cluckj
Apr 30 22:17 UTC
I recommend the dev branch for the x12 model pump too if you're not already using it
jonny772
@jonny772
Apr 30 22:23 UTC
and i dont think i'm running the dev branch
it was installed using the bootstrap script
Jon Cluck
@cluckj
Apr 30 22:28 UTC
that's okay, it's worth seeing if it works with master
you should delete that message, it contains a lot of personal info
jonny772
@jonny772
Apr 30 22:29 UTC
ive scrambled the keys a little
actually i missed one. shoot
jonny772
@jonny772
Apr 30 23:10 UTC
Brilliant! changing to G5 didnt fix it but moving to the dev branch did. Logs clearly showing pump coms now.
Thank you