Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 31 2019 15:51
    xen0n starred openaps/oref0
  • Jan 31 2019 15:12
    cclauss opened #1191
  • Jan 31 2019 15:09
    cclauss edited #1190
  • Jan 31 2019 15:08
    cclauss edited #1189
  • Jan 31 2019 15:07
    cclauss edited #1190
  • Jan 31 2019 15:07
    cclauss opened #1190
  • Jan 31 2019 15:00
    cclauss synchronize #1189
  • Jan 31 2019 14:52
    cclauss opened #1189
  • Jan 31 2019 14:10
  • Jan 31 2019 14:06
    Owaisaaa starred openaps/docs
  • Jan 31 2019 12:20
    cclauss synchronize #22
  • Jan 31 2019 12:16
    cclauss opened #22
  • Jan 31 2019 12:11
    cclauss edited #21
  • Jan 31 2019 12:09
    cclauss opened #21
  • Jan 31 2019 11:31
    tuzoenduro commented #1406
  • Jan 31 2019 11:25
    cclauss opened #140
  • Jan 30 2019 05:53
  • Jan 29 2019 16:03
    tzachi-dar commented #1406
  • Jan 29 2019 14:46
    rostag starred openaps/oref0
  • Jan 27 2019 22:06
    PieterGit synchronize #1176
Scott Leibrand
@scottleibrand
@peterfulvi that looks good now
should be able to run killall -g openaps; openaps gather now
@hilarykoch did you click the ... next to 24HR and enable it there?
Matt Walker
@walker0
@hilarykoch check that the tick box is still ticked
hilarykoch
@hilarykoch
BINGO! Thank YOU!
peterfulvi
@peterfulvi
Hows that
hilarykoch
@hilarykoch
So running successfully for two hours. Woot! The BG range is taken from the pump, right? Unless specified through NS as a temp target? And the ranges set for NS in Heroku don’t affect OpenAPS, right?
peterfulvi
@peterfulvi
image.png
Dana Lewis
@danamlewis
@hilarykoch correct
hilarykoch
@hilarykoch
Great. Thank you!
Dana Lewis
@danamlewis
:+1: :smile:
Scott Leibrand
@scottleibrand
@peterfulvi weird. does another openaps alias show gather show the curly quotes again?
if so, you might need to add the killall to that command too: killall -g openaps; openaps alias add gather '! bash -c "(openaps monitor-pump || openaps monitor-pump) 2>/dev/null >/dev/null && echo refreshed pumphistory || (echo unable to refresh pumphistory; exit 1) 2>/dev/null"'
peterfulvi
@peterfulvi
image.png
Scott Leibrand
@scottleibrand
yep, that looks like the race condition I was talking about. try the killall version
peterfulvi
@peterfulvi
image.png
I ran it this is what it looks like after the kill all
Scott Leibrand
@scottleibrand
ok, I give up on this method. go ahead and re-run oref0-setup.
peterfulvi
@peterfulvi
Ok thanks for your time. Im goin home to my kids now and i,ll have at it tomorrow night on my third shift? I'll keep you posted
Scott Leibrand
@scottleibrand
k
have a good evening
peterfulvi
@peterfulvi
Thanks
dan lightner
@danimaniac
I am currently sourcing my openAPS compatible pump (should be arriving this weekend), Edison, Explorer board, and battery. The production and dev documentation provides instruction for setting up the rig using a Pi, Windows, and Mac. Where would I find setup instructions for using my debian based linux laptop? I like to think I can follow directions pretty well, but...
Scott Leibrand
@scottleibrand
that should be pretty similar to the Pi, but no guarantees: no one has actually tried that yet AFAIK
you might have enough RAM to skip the swap space stuff
hilarykoch
@hilarykoch
I’m trying to setup Bluetooth. Following the directions here. Is the first step this (with the MAC address from my phone)?? cd && ~/src/oref0/bin/oref0-setup.sh --btmac=AA:BB:CC:DD:EE:FF
katie disimone
@Kdisimone
yes, mac address of phone
hilarykoch
@hilarykoch
If so, it looks like it is trying to take me through the interactive setup again...
Scott Leibrand
@scottleibrand
it's best if you add that --btmac=AA:BB:CC:DD:EE:FF to the end of your existing command from the runagain
katie disimone
@Kdisimone
yes but it will ask you an additonal question about the MAC address this time
Scott Leibrand
@scottleibrand
(or from your bash history) to avoid interactive
history | grep oref0-setup should find the last run, so you can copy and paste and add the new one
katie disimone
@Kdisimone
@scottleibrand that reminds me…when i ran that bash runagain script this morning…I dont’ think it included the —btmac part. But when i ran bluetoothcntl, it still listed the iPhone as a paired device. So, just confirming…that rerun script does NOT need the —btmac if it was already run and paired once?
hilarykoch
@hilarykoch
@scottleibrand @Kdisimone Still not getting it. Did you asked, but isn’t that line essentially what I had above? I’m missing something here… If I type it in, it looks like I’m going through the entire setup again, asking for pump SN
katie disimone
@Kdisimone
It should ask an additional question in there about whether you want to pair a device or phone through BLE
and then it will ask you for the MAC address of it
hilarykoch
@hilarykoch
ok. hang on. DO I put ALL of this in one line? or are these two commands? cd && ~/src/oref0/bin/oref0-setup.sh --btmac=AA:BB:CC:DD:EE:FF
katie disimone
@Kdisimone
one line.
hilarykoch
@hilarykoch
ok, so go ahead and answer questions about pump again?
katie disimone
@Kdisimone
replace the AA:bb: stuff with your phone’s BT MAC
Andy Sharrow
@dramageek
@Kdisimone @scottleibrand Yeah, I mentioned that earlier with my other BT problems. Even if you add it in manually to the oref0-runagain, it gets re-written and taken out when the setup completes. It doesn't mention it on the pre-install summary either.
hilarykoch
@hilarykoch
right did that
katie disimone
@Kdisimone
yes...
@dramageek Did you check to see if your pairing still worked though (sorry, i missed your earlier discussions)? I think ours are still working just fine
Andy Sharrow
@dramageek
@hilarykoch If you end up doing this multiple times, you can nano oref0-runagain.sh and add it to the end of the line, quit & save, then just bash oref0-runagain.sh. It won't re-ask you the questions then.
hilarykoch
@hilarykoch
well now it isn’t letting me do anything. “command not found"
Andy Sharrow
@dramageek
@Kdisimone We settled on me re-flashing later tonight. Probably something that got set when I was trying to tether a few weeks back that needs to be cleared out.
PRs welcome if there's a better place for this in the docs