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

2nd
Feb 2018
garykidd
@garykidd
Feb 02 2018 00:56
Will try to restart dynos @Kdisimone thx
fidoman
@efidoman
Feb 02 2018 02:01
@skubesch - yes, that is the right version. I think that perhaps flask isn't configured in your crontab for some reason. What did the commands @drnoname82 reveal?
garykidd
@garykidd
Feb 02 2018 02:05
why is my NS page asking for API secret when initially loading after re-dploying all dynos......I entered it---know wjhat it is---but says wrong API secret.
garykidd
@garykidd
Feb 02 2018 02:12
I think i had heroku in maintenance mode---but restarted and redeployed and still Unknown in OpenAPS pill...
@Kdisimone what else I can I try?
Ebgineer
@Ebgineer
Feb 02 2018 02:28
@sdneufer The type of battery isn't crucial. It can be a wall power source or a power pack as long as it has a microUSB plug. Docs are here http://openaps.readthedocs.io/en/master/docs/Customize-Iterate/offline-looping-and-monitoring.html?highlight=uart
garykidd
@garykidd
Feb 02 2018 02:44
wondering if NS is more likely to get tripped up if you have a lot of rigs reporting to it...I have 3 right now...works great for long stretches but always seems to fail eventually...like now.
still looping...still shows manual bolueses, etc...just OpenAPS pill remains Unknown
katie disimone
@Kdisimone
Feb 02 2018 02:56
@garykidd check the application logs in heroku and see what error message might be coming up? If you want, you can message me your url and I’ll take a look at the settings (but I don’t expect those to be the issue). I ran three rigs uploading for a long time and didn’t have any problems with it, so that’s not likely issue I would think
Dana Lewis
@danamlewis
Feb 02 2018 03:13
If it was, mine would die all the time and it doesn't
skubesch
@skubesch
Feb 02 2018 03:36
@drnoname82 For the first question, yes, I did cd ~/src/oref0 && git checkout dev && git pull before npm run global-install. Trying crontab -l | grep flask I get as my output '@reboot cd ~/src/oref0/www && export FLASK_APP=app.py && flask run -p 80 --host=0.0.0.0' (I don't know what any of that means)
philipgo
@philipgo
Feb 02 2018 04:08
@skubesch That means that flask will be started after a reboot. If it still does not work when you use your rigs IP address (http://<ipadress>) you can do „pip list | grep Flask“ to check whether it is installed and „pgrep flask -a“ to check whether it is running
skubesch
@skubesch
Feb 02 2018 05:08
@drnoname82 I tried rebooting first incase that was all it needed, but no change yet. It appears that flask is installed (Flask (0.12.2), Flask-RESTful (0.3.6)) but is not running. Is there a command to start/restart this service?
Sacha M
@coolestkidsever
Feb 02 2018 05:53
Hi all, anyone had an issue where rig will connect to phone via Bt, but phone no longer uploads to NS?
garykidd
@garykidd
Feb 02 2018 05:57
yeah, was just a thought @Kdisimone @danamlewis....not sure why NS always dies out for me...I suspect like in past instances I can just delete the entries database but this would almost be more of a nuisance for me...appreciate the help...still stuck though
anything look out of place here...
connect=0ms service=5ms status=200 bytes=1039 protocol=https 
Feb 02 00:58:19 a1control app/web.1: GRANTED:  67.85.9.72 no-token api:treatments:read default 
Feb 02 00:58:39 a1control app/web.1: Fetching Share Data:  minutes 26 maxCount 6 
Feb 02 00:58:39 a1control app/web.1: RUNNING 0 failures 0 
Feb 02 00:58:39 a1control app/web.1: Fetching new token 
Feb 02 00:58:39 a1control app/web.1: RUNNING 0 failures 0 
Feb 02 00:58:39 a1control app/web.1: First run, fetching 6 
Feb 02 00:58:39 a1control app/web.1: Entries [] 
Feb 02 00:59:03 a1control heroku/router: at=info method=GET path="/api/v1/entries/sgv.json?find[date][$gte]=1517547542677&count=1000" host=a1control.herokuapp.com request_id=89fea635-1ac9-403a-834e-ce34db5577f4 fwd="67.85.9.72" dyno=web.1 connect=0ms service=6ms status=200 bytes=589 protocol=https 
Feb 02 00:59:03 a1control app/web.1: GRANTED:  67.85.9.72 no-token api:entries:read default 
Feb 02 00:59:04 a1control heroku/router: at=info method=GET path="/api/v1/entries/sgv.json?find[date][$gte]=1517547542773&count=1000" host=a1control.herokuapp.com request_id=003dc356-2ceb-4fae-b9f2-5e3fcd8760dc fwd="67.85.9.72" dyno=web.1 connect=0ms service=14ms status=200 bytes=589 protocol=https 
Feb 02 00:59:05 a1control app/web.1: GRANTED:  67.85.9.72 no-token api:entries:read default 
Feb 02 00:59:07 a1control heroku/router: at=info method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2018-02-01T05:59+0000&find[eventType]=Temporary+Target" host=a1control.herokuapp.com request_id=6191e72b-e3fc-449f-bd2e-d36f186a0261 fwd="67.85.9.72" dyno=web.1 connect=0ms service=5ms status=200 bytes=1181 protocol=https 
Feb 02 00:59:07 a1control app/web.1: GRANTED:  67.85.9.72 no-token api:treatments:read default 
Feb 02 00:59:07 a1control heroku/router: at=info method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2018-02-01T05:59+0000&find[eventType]=Temporary+Target" host=a1control.herokuapp.com request_id=f7b8c5bd-d54c-4193-b2ae-9e64e4214991 fwd="67.85.9.72" dyno=web.1 connect=1ms service=9ms status=200 bytes=1181 protocol=https 
Feb 02 00:59:07 a1control app/web.1: GRANTED:  67.85.9.72 no-token api:treatments:read default 
Feb 02 00:59:08 a1control heroku/router: at=info method=GET path="/api/v1/entries/sgv.json?find[date][$gte]=1517547542594&count=1000" host=a1control.herokuapp.com request_id=6feac6f1-25ea-41dc-9b88-ca6d6f58ab13 fwd="67.85.9.72" dyno=web.1 connect=0ms service=7ms status=200 bytes=589 protocol=https 
Feb 02 00:59:08 a1control app/web.1: GRANTED:  67.85.9.72 no-token api:entries:read default 
Feb 02 00:59:09 a1control app/web.1: tick 2018-02-02T05:59:08.737Z 
Feb 02 00:59:09 a1control heroku/router: at=info method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2018-02-01T05:59+0000&find[carbs][$exists]=true" host=a1control.herokuapp.com request_id=f13a47c8-cfa6-43c5-8a14-e5bf4db09dc5 fwd="67.85.9.72" dyno=web.1 connect=0ms service=5ms status=200 bytes=1119 protocol=https 
Feb 02 00:59:10 a1control app/web.1: GRANTED:  67.85.9.72 no-token api:treatments:read default 
Feb 02 00:59:10 a1control app/web.1: searching treatments q { find: { created_at: { '$gte': '2018-01-25T05:59:09.740Z' } }, 
Feb 02 00:59:10 a1control app/web.1:   sort: { created_at: 1 } } 
Feb 02 00:59:10 a1control app/web.1: Load Complete: 
Feb 02 00:59:10 a1control app/web.1:      sgvs:459, treatments:637, profiles:1, sitechangeTreatments:2, sensorTreatments:3, tempbasalTreatments:305, tempTargetTreatments:17 
Feb 02 00:59:10 a1control app/web.1: WS: running websocket.update 
Feb 02 00:59:10 a1control app/web.1: delta calculation indicates no new data is present 
Feb 02 00:59:10 a1control app/web.1: GRANTED:  67.85.9.72 no-token api:treatments:read default 
Feb 02 00:59:10 a1control app/web.1: GRANTED:  67.85.9.72 no-token api:treatments:read default 
Feb 02 00:59:10 a1control heroku/router: at=info method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2018-02-01T05:59+0000&find[carbs][$exists]=true" host=a1control.herokuapp.com request_id=63568476-4330-40c4-b18a-40d1d7d90c8b fwd="67.85.9.72" dyno=web.
garykidd
@garykidd
Feb 02 2018 06:04
actually found this recent issue 9repeat).....pump battery is full FYI...could this be causing issue with having OpenAPS pill show Unknown?
Starting oref0-pump-loop at Wed Jan 31 19:04:02 EST 2018 with 17 second wait_for_silence:
Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json
Checking pump clock: "2018-01-31T18:44:07-05:00" is within 90s of current time: Wed Jan 31 19:06:50 EST 2018
Pump clock is more than 55s off: attempting to reset it
Waiting for ntpd to synchronize... OK!
Setting pump time to Wed Jan 31 19:06:50 EST 2018
mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
Setting CGM time to Wed Jan 31 19:07:17 EST 2018
AttributeError: 'NoneType' object has no attribute 'ReadSystemTime'
Error: pump clock refresh error / mismatch
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!)
Listening for 40s silence before mmtuning: ..........................................No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.468", 5, -92 waiting for 64 second silence before continuing
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight 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 Wed Jan 31 19:12:42 EST 2018
garykidd
@garykidd
Feb 02 2018 06:21
Is this common.....
Setting pump time to Fri Feb 2 01:17:24 EST 2018
mmeowlink.exceptions.InvalidPacketReceived
Setting CGM time to Fri Feb 2 01:17:38 EST 2018
AttributeError: 'NoneType' object has no attribut
e 'ReadSystemTime'
Error: pump clock refresh error / mismatch
oref0-pump-loop failed. pump_loop_completed more
than 15m old; waiting for 40s silence before mmtu
ning
phoenixflame611
@phoenixflame611
Feb 02 2018 06:49
has anyone gotten the following error when trying to configure the edison:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
nodejs : Conflicts: nodejs-legacy
E: Unable to correct problems, you have held broken packages.

Scott Leibrand
@scottleibrand
Feb 02 2018 09:49
@phoenixflame611 that error is most common for people starting with something other than a clean freshly flashed rig (that already has nodejs on it). I would re-flash and try again.
sdneufer
@sdneufer
Feb 02 2018 13:37
@Ebgineer thanks. I was plugging it into the wall overnight to test that it was working. Then went to take it out and all my batteries for backup that use a USB to microusb cable were huge batteries (5000-10,000Mhz), so I wondered what others used that was more carry friendly. The
Photo in the doc shows it plugged in. I will search for a smaller of the battery packs I use for all the iPads and smartphones.
Ebgineer
@Ebgineer
Feb 02 2018 13:41
It's always a trade-off of smaller size or longer battery life. I use a big battery too, 22,000 mah.
phoenixflame611
@phoenixflame611
Feb 02 2018 14:25
@scottleibrand thanks! Every time I try and flash though it leaves all my data and settings intact. How do you do a full factory flash? Is it the "reboot ota" command? Using Windows for everything.
garykidd
@garykidd
Feb 02 2018 16:19
@scottleibrand wondering if you have any ideas on the unknown indication in the OpenAPS pill---still cant figure it out. I'm thinking if I delete my history it'll work---that seems to have worked in past situations---but I really like having the data accessible--especially with an upcoming endo appt. Sorry to ask so many questions--not trying to be an annoyance.
phoenixflame611
@phoenixflame611
Feb 02 2018 16:25
@garykidd I followed these steps, still keeps user data and wifi config post "flash".
garykidd
@garykidd
Feb 02 2018 16:27
I think you may be doing something wrong then...I don't believe it should
Are you using a PC
?
phoenixflame611
@phoenixflame611
Feb 02 2018 16:29
Yes I am. Win10 64bit. I could try using a ubuntu boot stick on a laptop I have worst case scenario.
garykidd
@garykidd
Feb 02 2018 16:31
I've been using Mac...honestly this is one of the areas which the documentation for has greatly improved...I sued to have alot of issues but following the instructions verbatim works for me 100% now.
garykidd
@garykidd
Feb 02 2018 16:37
@phoenixflame611 curious how long the flashing process is taking?
or the attempted flashing process anyway...
THink I'm going have to 86 my data...uploading to OpenHumans now...
garykidd
@garykidd
Feb 02 2018 16:44
Can you upload data from Open Humans back to NS after xferring and then deleting from NS?
Eric
@ecc1
Feb 02 2018 16:54
Based on this description https://openaps.readthedocs.io/en/latest/docs/Give%20Back-Pay%20It%20Forward/data-commons-data-donation.html#how-to-upload-your-data-to-the-openaps-data-commons it looks like you can login and download the JSON files you previously uploaded. I don't know of an existing tool to re-upload those entries to NS, but it wouldn't be difficult (basically iterating over each JSON object and POSTing to the relevant NS api endpoint)
Sounds like a good project for someone with programming experience who wants to contribute
garykidd
@garykidd
Feb 02 2018 16:59
Thanks @ecc1. you don't have any idea how to rectify my unknown error on the OpenAPS pill do you?
Eric
@ecc1
Feb 02 2018 17:02
I don't know anything about that. You can retrieve recent devicestatus entries via curl and see if anything is suspicious
alimhassam
@alimhassam
Feb 02 2018 17:22
@garykidd look for errors in your ns-loop logs??
Or anything suspicious there?
garykidd
@garykidd
Feb 02 2018 18:09
hmmm doesnt look like anything is out of whack on ns-loop.log
Starting oref0-ns-loop at Fri Feb 2 13:09:01 EST 
2018:                                            
Found recent valid BG:                           
{"glucose":247,"dateString":"2018-02-02T13:06:52-
05:00"}                                          
Latest NS temptargets: {"target":120,"duration":6
0,"start":"2018-02-02T00:53:57.925Z"}            
Merging local temptargets: Temptargets merged: {"
target":120,"duration":60,"start":"2018-02-02T00:
53:57.925Z"}                                     
Refreshed carbhistory; COB: 0                    
{"batteryVoltage":3851,"battery":67}             
No new treatments to upload                      
Completed oref0-ns-loop at Fri Feb 2 13:09:20 EST
2018
other than my BG skyrocketing...rrrrhhhggg
@ecc1 could you direct me a bit further on the curl devicestatus retrieval?
should there be a suggested.json...and no new treatments to upload?
garykidd
@garykidd
Feb 02 2018 18:16
well deleted all my records...WTF.....
and still nothing is working...great
garykidd
@garykidd
Feb 02 2018 18:28
Well, it took a bit but deleting all records was the only thing that worked...pump and openaps pill updated finally---happy to provide information if someone wants to loook into this...it's happened on multiple occasions--understanding that if I am the only one it's happening for then it's hard to dedicate any time toward it.
thx
alimhassam
@alimhassam
Feb 02 2018 18:39
@garykidd i have a f eeling something is not working with your ns-loop
would be good to try the commands manually.
which cgm option did you use when you did your setup?
alimhassam
@alimhassam
Feb 02 2018 18:59
anyone knows why we still have this # use old ns-loop for now comment for xdrip?
https://github.com/openaps/oref0/blob/master/bin/oref0-setup.sh#L1026-L1028
Scott Leibrand
@scottleibrand
Feb 02 2018 19:29
Because no one did the work to make it work? I don’t recall exactly what was broken though.
alimhassam
@alimhassam
Feb 02 2018 19:59
seems to work....
it was added here: openaps/oref0#752
but oref0-ns-loop.sh seems to work for me on the dev branch, with xdrip
Scott Leibrand
@scottleibrand
Feb 02 2018 20:05
ah, cool. if you are confident no further testing is needed with xdrip, care to PR in a change over to use oref0-ns-loop? I can't test it myself, so it'll be on all y'all xdrip users. :)
Steve Lund
@902Lund
Feb 02 2018 20:53
Hi All. I have 2 issues going on with my setup and am not sure if they are related at all. Hoping for some opinions. The first issue is that my log details look really strange since last night. Below is what I'm seeing. Secondly, I had "unknown" in my openaps pill and my pump pill was blank...this seems to have started around the same time as the first issue. After compacting and cleaning my data, the second issue seems to have resolved. I'm using an Explorer/Edison rig (2 rigs actually) with a Dexcom G5 that uploads to NS via share/follow. Any thoughts? Both rigs are showing a similar log.
  rate: 0.6,
  offset: 0,
  _date: '3490000212' }
No duration found for 0 U/hr basalundefined { programmed: 3,
  _type: 'Bolus',
  _description: 'Bolus 2018-02-01T23:05:17 head[8], body[0] op[0x01]',
  timestamp: '2018-02-01T23:05:17-04:00',
  _body: '',
  _head: '010078007800ac00',
  amount: 3,
  unabsorbed: 4.3,
  duration: 0,
  type: 'normal',
  _date: '1185376112' } { _type: 'TempBasal',
  temp: 'absolute',
  _description: 'TempBasal 2018-02-01T22:58:02 head[2], body[1] op[0x33]',
  timestamp: '2018-02-01T22:58:02-04:00',
  _body: '00',
  _head: '3300',
  rate: 0,
  _date: '02ba160112' } { _type: 'BasalProfileStart',
  _description: 'BasalProfileStart 2018-02-01T22:58:02 head[2], body[3] op[0x7b]                                                                                        ',
  timestamp: '2018-02-01T22:58:02-04:00',
  _body: '202000',
  profile_index: 3,
  _head: '7b03',
  rate: 0.8,
  offset: 57600000,
  _date: '02ba160112' }
No duration found for 0 U/hr basalundefined { _type: 'BGReceived',
  _description: 'BGReceived 2018-02-02T00:22:07 head[2], body[3] op[0x3f]',
  timestamp: '2018-02-02T00:22:07-04:00',
  _body: 'ce5e13',
  _head: '3f29',
  amount: 335,
  link: 'ce5e13',
  _date: '0796e06212' } { _type: 'TempBasal',
  temp: 'absolute',
  _description: 'TempBasal 2018-02-02T00:16:52 head[2], body[1] op[0x33]',
  timestamp: '2018-02-02T00:16:52-04:00',
  _body: '00',
  _head: '3300',
  rate: 0,
  _date: '3490000212' } { _type: 'BasalProfileStart',
  _description: 'BasalProfileStart 2018-02-02T00:16:52 head[2], body[3] op[0x7b]                                                                                        ',
  timestamp: '2018-02-02T00:16:52-04:00',
  _body: '001800',
  profile_index: 0,
  _head: '7b00',
  rate: 0.6,
  offset: 0,
  _date: '3490000212' }
No duration found for 0 U/hr basalundefined { programmed: 3,
  _type: 'Bolus',
  _description: 'Bolus 2018-02-01T23:05:17 head[8], body[0] op[0x01]',
  timestamp: '2018-02-01T23:05:17-04:00',
  _body: '',
  _head: '010078007800ac00',
  amount: 3,
  unabsorbed: 4.3,
  duration: 0,
  type: 'normal',
  _date: '1185376112' } { _type: 'TempBasal',
  temp: 'absolute',
  _description: 'TempBasal 2018-02-01T22:58:02 head[2], body[1] op[0x33]',
  timestamp: '2018-02-01T22:58:02-04:00',
  _body: '00',
  _head: '3300',
  rate: 0,
  _date: '02ba160112' } { _type: 'BasalProfileStart',
  _description: 'BasalProfileStart 2018-02-01T22:58:02 head[2], body[3] op[0x7b]                                                                                        ',
  timestamp: '2018-02-01T22:58:02-04:00',
  _body: '202000',
  profile_index: 3,
  _head: '7b03',
  rate: 0.8,
  offset: 57600000,
  _date: '02ba160112' }
I eventually get the normal log stuff (like the following)...
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":55,"nsCarbs":55,"bwCarbs":0,"mealCOB":0,"currentDeviation":2.72,"maxDeviation":15.29,"minDeviation":2.45,"slopeFromMaxDeviation":-1.491,"slopeFromMinDeviation":0.111,"allDeviations":[3,3,2,3,5,8,11,13,15],"lastCarbTime":1517592803000,"bwFound":false,"reason":"not enough glucose data to calculate carb absorption"}
{"iob":0.994,"activity":0.0173,"basaliob":-0.258,"bolusiob":1.252,"netbasalinsulin":-1.5,"bolusinsulin":8,"time":"2018-02-02T20:49:29.000Z","iobWithZeroTemp":{"iob":0.994,"activity":0.0173,"basaliob":-0.258,"bolusiob":1.252,"netbasalinsulin":-1.5,"bolusinsulin":8,"time":"2018-02-02T20:49:29.000Z"},"lastBolusTime":1517597721000,"lastTemp":{"rate":1.4,"timestamp":"2018-02-02T16:34:44-04:00","started_at":"2018-02-02T20:34:44.000Z","date":1517603684000,"duration":15.79}}
{"delta":-5,"glucose":200,"short_avgdelta":-5,"long_avgdelta":-5.33,"date":1517604419000}
Autosens ratio: 1; Basal unchanged: 0.85; ISF unchanged: 84.4; CR: 11.785
currenttemp: { duration: 16, rate: 1.4, temp: 'absolute' } lastTempAge: 15 m tempModulus: 1 m
SMB disabled (no enableSMB preferences active)
Last carbs 196 minutes ago; remainingCATime: 7.9 hours; 100% carbs absorbed
Carb Impact: 2.3 mg/dL per 5m; CI Duration: 0 hours; remaining CI (~2h peak): 0 mg/dL per 5m
UAM Impact: 2.3 mg/dL per 5m; UAM Duration: 0.2 hours
minPredBG: 146 minIOBPredBG: 125 minZTGuardBG: 146 avgPredBG: 146 COB: 0 / 55
BG projected to remain above 6.1 for 240 minutes
naive_eventualBG: 116 bgUndershoot: -41 zeroTempDuration: 240 zeroTempEffect: 287 carbsReq: -46
Checking deliverAt: 2018-02-02T20:49:34.900Z is within 1m of current time: Fri Feb  2 16:49:34 AST 2018
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","bg":200,"tick":-5,"eventualBG":130,"insulinReq":0.24,"reservoir":"141.5","deliverAt":"2018-02-02T20:49:34.900Z","sensitivityRatio":1,"predBGs":{"IOB":[200,195,190,185,181,176,172,168,165,161,158,154,151,148,146,143,141,139,137,136,134,133,132,131,131,130,129,129,128,127,127,127,126,126,126,126,126,126,126,126,125],"ZT":[200,193,186,180,174,169,164,160,156,153,151,149,148,147,146,147,147]},"COB":0,"IOB":0.994,"reason":"COB: 0, Dev: 0.8, BGI: -0.4, ISF: 4.7, CR: 11.79, Target: 6.1, minPredBG 8.1, minGuardBG 6.9, IOBpredBG 6.9; Eventual BG 7.2 >= 6.1, temp 1.4 >~ req 1.35U/hr. "}
No smb_enact needed. Temp refreshed: monitor/temp_basal.json: {"duration":16,"rate":1.4,"temp":"absolute"}
No bolus needed (yet). Settings less than 15 minutes old. Edison battery at 69% is charged (>= 98%) or likely charging (60-70%). Pumphistory-24 < 15m old
Your instance of oref0 [0.6.0, master] is up-to-date.
Completed oref0-pump-loop at Fri Feb 2 16:49:38 AST 2018
Steve Lund
@902Lund
Feb 02 2018 21:11
Thanks!
alimhassam
@alimhassam
Feb 02 2018 21:38
@scottleibrand i'll raise a pr to move xdrip to oref0-ns-loop. Hopefully i'm not missing anything, wondering why it was reverted in the first place, maybe the battery issue, which was fixed since?
Scott Leibrand
@scottleibrand
Feb 02 2018 21:40

openaps/oref0#752 indicates that "When I removed the edisonbattery import, that broke MDT (and xDrip) CGM users who still need the old openaps ns-loop for now until we update oref0-ns-loop.sh to support them.

This restores edisonbattery upload functionality for MDT, and restores that plus ns-loop functionality for xDrip."

alimhassam
@alimhassam
Feb 02 2018 21:41
what's "ns-loop functionality for xDrip" ?
Scott Leibrand
@scottleibrand
Feb 02 2018 21:41
that just means "I changed back to the old ns-loop to get things working again"
alimhassam
@alimhassam
Feb 02 2018 21:42
ok, well seems to be uploading to NS for me, and i do see edison battery percentage also in ns, not sure what else to test.
alimhassam
@alimhassam
Feb 02 2018 21:49
ah, looking at the code now, i see what's missing
it's the upload of xdripaps entries when offline
will require some code change, i'll wait before raising the pr.
most of the logic seems there, so it sohuldn't be too hard.
skubesch
@skubesch
Feb 02 2018 22:28
Would anybody running the latest dev branch for OpenAPS be able offer a suggestion on how to get flask running (or why mine isn't despite the command for starting on reboot being there?)
Scott Leibrand
@scottleibrand
Feb 02 2018 22:31
what happens when you run the cron line manually?
skubesch
@skubesch
Feb 02 2018 22:33
I think you mean cd ~/src/oref0/www && export FLASK_APP=app.py && flask run -p 80 --host=0.0.0.0? I just did that but ps -ef | grep -v grep | grep flask still shows nothing
Scott Leibrand
@scottleibrand
Feb 02 2018 22:38
you should get:
# cd ~/src/oref0/www && export FLASK_APP=app.py && flask run -p 80 --host=0.0.0.0
 * Serving Flask app "app"
 * Running on http://0.0.0.0:80/ (Press CTRL+C to quit)
(and it shouldn't give you back your prompt until you Press CTRL+C to quit)
skubesch
@skubesch
Feb 02 2018 22:38
Ah okay, I don't get any of those messages, I just see the next line that shows I've moved to the new directory
Scott Leibrand
@scottleibrand
Feb 02 2018 22:39
run the different commands (in between the &&s) one by one
you can also do export FLASK_DEBUG=1 first
skubesch
@skubesch
Feb 02 2018 22:40
I'm still not able to get that prompt you were showing. I'm seeing this:
root@jubilinux:~# export FLASK_DEBUG=1
root@jubilinux:~# cd ~/src/oref0/www
root@jubilinux:~/src/oref0/www# export FLASK_APP=app.py
root@jubilinux:~/src/oref0/www# flask run -p 80 --host=0.0.0.0
root@jubilinux:~/src/oref0/www#
Tim Street
@tim2000s
Feb 02 2018 22:41
Are you sure your git is set to dev and not master?
Scott Leibrand
@scottleibrand
Feb 02 2018 22:42
ls -la app.py
git branch
skubesch
@skubesch
Feb 02 2018 22:43
root@jubilinux:~# npm list -g oref0 
/usr/local/lib
└── oref0@0.6.1-dev  -> /root/src/oref0

root@jubilinux:~# cd ~/src/oref0 
root@jubilinux:~/src/oref0# git branch
* dev
  master
Does that look right?
Scott Leibrand
@scottleibrand
Feb 02 2018 22:43
ls -la app.py
skubesch
@skubesch
Feb 02 2018 22:44
ls: cannot access app.py: No such file or directory
Okay, once I switch directories: -rw-r--r-- 1 root root 2592 Jan 26 00:34 app.py
Scott Leibrand
@scottleibrand
Feb 02 2018 22:44
heh yeah k
which flask && ls -la $(which flask)
skubesch
@skubesch
Feb 02 2018 22:45
/usr/local/bin/flask
-rwxr-xr-x 1 root root 0 Jan 26 01:00 /usr/local/bin/flask
Scott Leibrand
@scottleibrand
Feb 02 2018 22:45
there's your problem. your flask binary is zero bytes
you can try running the flask install again manually: sudo pip install flask
skubesch
@skubesch
Feb 02 2018 22:47
Thank you, very much