These are chat archives for nightscout/intend-to-bolus
alias l=tail -F /var/log/openaps/pump-loop.login your .bashrc or .bash_profile or whatever
lto get your logs up. :)
openapsis using the
medtronicvendor for the
pumpdevice, it's set up to use the carelink
ls -la /dev/ttyUSB0show?
lsusbshows the carelink?
killall -g openaps; mm-link diagnoseand it should be able to run
killall -g openapsas well to kill whatever it was running last
ssh email@example.com whatever.
npm run global-install
minutesattribute of the basalprofile always match the
startattribute. I got one profile.run.date.json that contains:
startfield. Shouldn't that be left out of the json files? 2) Why is the field called minutes in the basalProfile and why is it called offset in the isfProfile. In needed this in the Export to Excel python script to distinguish the different behaviour
expandedBasal=expandProfile(basalProfile, 'rate', 'minutes') expandedIsf=expandProfile(isfProfile, 'sensitivity', 'offset')
startmismatch, but haven't really tested it yet
Starting ns-loop at Mon 2 Jan 16:14:02 EST 2017:
Refreshed temptargets and meal-carbs
cgm/ns-glucose.json is empty
@jordan-berger try adding
* * * * * sudo wpa_cli scan
to your cron with 'crontab -e'
see if that helps you at all
oref0-onlinerestarts everything if necessary.
startjson was from just before the @sulkaharo fix, so I think I can confirm that the fix works.
edison: everything should be installed and run as root