sudo killall bluetoothd
Completed pump-loop at Wed Mar 22 21:19:16 EDT 2017
^C
root@purplebird:~# sudo killall bluetoothd
root@purplebird:~# sudo killall bluetoothd
root@purplebird:~# sudo killall bluetoothd
root@purplebird:~# sudo killall bluetoothd
root@purplebird:~# sudo killall bluetoothd
root@purplebird:~# sudo killall bluetoothd
bluetoothd: no process found
root@purplebird:~#
root@purplebird:~# sudo killall bluetoothd
bluetoothd: no process found
root@purplebird:~# sudo /usr/local/bin/bluetoothd --experimental &
[1] 30470
root@purplebird:~# sudo hciconfig hci0 name $HOSTNAME
Can't change local name on hci0: Network is down (100)
and wait longer between steps.
root@purplebird:~# bluetoothd --version
5.37
root@purplebird:~# sudo killall bluetoothd
[1]+ Done sudo /usr/local/bin/bluetoothd --experimental
root@purplebird:~# sudo /usr/local/bin/bluetoothd --experimental &
[1] 6200
root@purplebird:~# sudo hciconfig hci0 name $HOSTNAME
Can't change local name on hci0: Network is down (100)
root@purplebird:~#
hciconfig hci0 reset
and then go through all of it again
`hciconfig hci0 reset
doesnt work thanks
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Mar 22 21:18:47 2017 from imac
root@purplebird:~# sudo killall bluetoothd
bluetoothd: no process found
root@purplebird:~# sudo /usr/local/bin/bluetoothd --experimental &
[1] 4808
root@purplebird:~# sudo hciconfig hci0 name $HOSTNAME
root@purplebird:~# bluetoothctl
[NEW] Controller 98:4F:EE:04:55:44 purplebird [default]
[bluetooth]# power off
Changing power off succeeded
[CHG] Controller 98:4F:EE:04:55:44 Powered: no
[CHG] Controller 98:4F:EE:04:55:44 Discovering: no
[CHG] Controller 98:4F:EE:04:55:44 Class: 0x000000
[bluetooth]# power on
[CHG] Controller 98:4F:EE:04:55:44 Class: 0x400110
Changing power on succeeded
[CHG] Controller 98:4F:EE:04:55:44 Powered: yes
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller 98:4F:EE:04:55:44 Discoverable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller 98:4F:EE:04:55:44 Discovering: yes
[NEW] Device 40:7A:6E:CC:1B:D0 40-7A-6E-CC-1B-D0
[NEW] Device 80:00:0B:2D:E6:81 NYNYCXXU435B8X2
[bluetooth]# default-agent
No agent is registered
[NEW] Device 94:E9:6A:AC:75:3E GKPHONE
[CHG] Device 94:E9:6A:AC:75:3E RSSI: -72
[CHG] Device 80:00:0B:2D:E6:81 RSSI: -87
[CHG] Device 94:E9:6A:AC:75:3E RSSI: -53
[CHG] Device 94:E9:6A:AC:75:3E RSSI: -84
[CHG] Device 80:00:0B:2D:E6:81 RSSI: -79
[CHG] Device 94:E9:6A:AC:75:3E RSSI: -62
[CHG] Device 94:E9:6A:AC:75:3E RSSI: -51
[CHG] Device 9
:65,"temp":"absolute","snoozeBG":59,"recieved":true,"predBGs":{"COB":[65,63,61,60,59,58,58,58,58,59,60,62,63,65,68,71,74,78,82,86,89,93,97,100,104,107,110,113,116,119,122,124,127,129,131,134,136,138,140,142,143,145,147,148,149,151,152,153,154,155,156,156,157,158],"aCOB":[65,67,70,72,75,78,81,84,87,90,93,97,100,104,108,112,117,121,126,130,134,138,141,144,147,149,151,153,154,155,156,157],"IOB":[65,63,60,58,55,53,50,48,45,43,40,39,39]},"rate":0,"reason":"COB: 28, Dev: 33, BGI: -7.38, ISF: 43, Target: 96; BG 65<72","COB":28,"eventualBG":158,"timestamp":"2017-03-22T21:18:38.402191","duration":30,"tick":"+0","IOB":1.299}
Settings less than 10m old
Pumphistory-24 less than 20m old
Completed pump-loop at Wed Mar 22 21:21:52 EDT 2017
Starting pump-loop at Wed Mar 22 22:42:05 EDT 2017:
curl -s https://raw.githubusercontent.com/openaps/docs/master/scripts/quick-packages.sh | bash -
ping google.com
)
So this has nothing to do with OpenAPS, but I don't really know any other diabetics to consult. I got a dexcom a few days ago... and I thought I was pretty in control of my blood sugar... but im all over the place. I ate around 10:30 ~ roughly 70g of carbs. I used my bolus wizard like I always do... and my blood sugar just kept climbing. Just now I bolus'd a bunch more insulin (sugary stuff on stand by just incase) because im at 360mg/dl.
Is it normal for it to spike and then eventually come back down? That was an hour and a half ago and im starting to get concerned. I've been having issues like this since I started the Dexcom, but I had also started a new infusion set that same day and thought maybe the site I was infusing at was just not great... but I changed it this morning and i'm still having the issue.
My issues isn't so much a "spike" that comes back down to normal as much as it feels like its a spike that goes up and then levels off. Like the insulin is keeping me from going into the 400+ range but not much more.
I will indeed start trying the pre-bolus tho and see if I can get that to work.
Thank you guys.
NIGHTSCOUT_HOST=https://XXXXXXXXXX.herokuapp.com
API_SECRET=########################################
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
* * * * * ps aux | grep -v grep | grep -q "oref0-online XX;XX;XX;XX;XX;XX" || oref0-online XX;XX;XX;XX;XX;XX >> /var/log/openaps/network.log
* * * * * sudo wpa_cli scan
* * * * * ( killall -g --older-than 15m openaps; killall -g --older-than 15m oref0-pump-loop; killall -g --older-than 15m openaps-report )
* * * * * cd /root/GREENAPS && oref0-reset-git
* * * * * cd /root/GREENAPS && ps aux | grep -v grep | grep -q oref0-truncate-git-history || oref0-truncate-git-history
* * * * * cd /root/GREENAPS && ps aux | grep -v grep | grep -q 'openaps get-bg' || ( date; openaps get-bg ; cat cgm/glucose.json | json -a sgv dateString | head -1 ) | tee -a /var/log/openaps/cgm-loop.log
* * * * * cd /root/GREENAPS && ps aux | grep -v grep | grep -q 'openaps ns-loop' || openaps ns-loop | tee -a /var/log/openaps/ns-loop.log
* * * * * cd /root/GREENAPS && ps aux | grep -v grep | grep -q 'openaps autosens' || openaps autosens 2>&1 | tee -a /var/log/openaps/autosens-loop.log
5 0 * * * ( oref0-autotune -d=/root/GREENAPS -n=https://###############.herokuapp.com && cat /root/GREENAPS/autotune/profile.json | json | grep -q start && cp /root/GREENAPS/autotune/profile.json /root/GREENAPS/settings/autotune.json) 2>&1 | tee -a /var/log/openaps/autotune.log
@reboot reset_spi_serial.py
* * * * * oref0-radio-reboot
* * * * * cd /root/GREENAPS && ( ps aux | grep -v grep | grep -q 'openaps pump-loop' || openaps pump-loop ) 2>&1 | tee -a /var/log/openaps/pump-loop.log
* * * * * ps aux | grep -v grep | grep -q "oref0-bluetoothup" || oref0-bluetoothup >> /var/log/openaps/network.log
*/15 * * * * cd /root/GREENAPS && openaps battery-status; cat /root/GREENAPS/monitor/edison-battery.json | json batteryVoltage | awk '{if ($1<=3050)system("sudo shutdown -h now")}'
@reboot cd /root/GREENAPS && oref0-delete-future-entries
* * * * * cd /root/GREENAPS && ( ps aux | grep -v grep | grep -q 'openaps pump-loop' || openaps pump-loop ) 2>&1 | tee -a /var/log/openaps/pump-loop.log
curl -s https://raw.githubusercontent.com/openaps/docs/master/scripts/quick-packages.sh | bash -
on a new board is returning openaps 0.1.5. what am I missing?
curl -s https://raw.githubusercontent.com/openaps/docs/master/scripts/quick-packages.sh | bash -
is pulling a 0.1.5 version
Mar 22 21:56:29 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3379, "battery":10}
Mar 22 21:57:30 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3360, "battery":9}
Mar 22 21:58:30 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3346, "battery":9}
Mar 22 21:59:29 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3339, "battery":9}
Mar 22 22:00:29 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3323, "battery":8}
Mar 22 22:01:31 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3297, "battery":8}
Mar 22 22:02:30 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3296, "battery":8}
Mar 22 22:03:33 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3250, "battery":7}
Mar 22 22:04:47 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3226, "battery":6}
Mar 22 22:06:37 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3165, "battery":5}
Mar 22 22:07:47 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3099, "battery":3}
Mar 22 22:09:29 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":3027, "battery":2}
Mar 22 22:10:33 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":2891, "battery":-1}
Mar 22 22:11:29 SarahOpenAPS1 ns-loop.log: {"batteryVoltage":2710, "battery":-5}
pip
is a python package manager. What matters is what version of openaps is in the pip repository
df -h
Completed pump-loop at Thu Mar 23 14:16:56 EDT 2017
? and it's 15:16 EDT now, right?
root@ubitwo:~/myopenaps# cat nightscout/uploaded-entries.json
{
"status": 500,
"message": "Mongo Error",
"description": {
"index": 0,
"code": 11000,
"name": "MongoError",
"driver": true,
"message": "E11000 duplicate key error index: jmcrawford_t1d.entries.$_id_ dup key: { : \"58d2fd1c60d609d61c9345ec\" }",
"errmsg": "E11000 duplicate key error index: jmcrawford_t1d.entries.$_id_ dup key: { : \"58d2fd1c60d609d61c9345ec\" }"
}
Filesystem Size Used Avail Use% Mounted on
/dev/root 1.4G 706M 610M 54% /
devtmpfs 482M 0 482M 0% /dev
tmpfs 482M 0 482M 0% /dev/shm
tmpfs 482M 49M 434M 11% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 482M 0 482M 0% /sys/fs/cgroup
tmpfs 482M 20K 482M 1% /tmp
/dev/mmcblk0p10 1.3G 806M 485M 63% /home
/dev/mmcblk0p7 32M 3.8M 29M 12% /boot
tmpfs 97M 0 97M 0% /run/user/0
cron -l
shows
edison
and do crontab -r
to delete that one, and then log back in and make sure the root one is correct (re-run oref0-setup if needed)
Traceback (most recent call last):
File "/usr/local/bin/openaps-use", line 63, in <module>
app( )
File "/usr/local/lib/python2.7/dist-packages/openaps/cli/__init__.py", line 51, in __call__
self.run(self.args)
File "/usr/local/bin/openaps-use", line 57, in run
output = app(args, self)
File "/usr/local/lib/python2.7/dist-packages/openaps/uses/__init__.py", line 92, in __call__
return self.method.selected(args)(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/uses/__init__.py", line 31, in __call__
return self.method(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/uses/use.py", line 44, in __call__
self.before_main(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 64, in before_main
self.check_session(app)
File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 141, in check_session
self.session = self.get_session_info( ) File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 104, in get_session_info
fields = self.create_session( )
File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 129, in create_session
self.pump.power_control(minutes=minutes)
File "/usr/local/lib/python2.7/dist-packages/mmeowlink/handlers/stick.py", line 222, in power_control
raise CommsException("No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?")
mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
openaps mmtune
?
openaps mmtune
in case the TI Stick is being stubborn.... Thank you, Scott! It seems to be working now!
npm list -g oref0
then I see 0.4.2 for oref0 which corresponds to looking in github at the package.json and files that list oref0 version 0.4.2. BUT, the openaps version 0.1.5
that comes up at the end of the dependencies installation I’m thinking is actually just a tragic coincidence to the fact that the oref0 release also happens to have been 0.2.0 [but subsequent updates (via “tags”) moved oref0 to 0.4.2. which I had not noticed at first]. So is it fair to say that the line that comes up at the end of dependencies install (openaps 0.1.5
) is actually just installing an old version of something (fill in the word because I never got familiar with the manual setup process yet) that subsequently it all gets updated by the next lines anyways? I apologize for the hard time typing this all out…just trying to sort myself through the confusion so that I can understand better. It’s feeling like I don’t quite understand exactly how openaps fits into the scheme which i suspect is from not knowing the manual process so well.
openaps
(python toolkit installed via pip) with oref0
(JavaScript installed via npm)
Pumphistory-24 less than 20m old
Completed pump-loop at Thu Mar 23 18:37:59 EDT 2017
Starting pump-loop at Thu Mar 23 18:52:09 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
ps aux | grep -v grep | grep 'openaps pump-loop'
to see what is still running after it says Completed pump-loop
in the log
crontab -r
?