shutdown
command both work. Also make sure everything in your preferences is the way you want if you aren't seeing the temps you expect.
ls
to show what's in your directory, or look to the left of the prompt to know where you are
AttributeError: 'NoneType' object has no attribute ‘iter_records’
is exactly what you'd expect, and isn't a problem: it will still loop off of BG from NS, so that part is unrelated to the pill problem
network={
key_mgmt=NONE
priority=-999
}
oref0-setup
is well designed for that :wink:
cat
or head
commands :wink:
@all - sorry for offtopic here in terms of xdrip+ :smile:
here the URL for nightly versions
https://github.com/NightscoutFoundation/xDrip/releases
openaps use pump mmtune
I think, or openaps report invoke /path/to/mmtune.json
FYI. I figured out why I had to reinstall oref0 once a week ago. Turns out that 10v charger works for awhile and then towards end of charge cycle it must cause a battery temp error that reboot won't solve (at least I saw a battery temp error roll by pretty fast during the reboot shutdown). Reboot didn't fix it. Reran script (thanks @danamlewis for that little new line) and problem gone.
I've only accidentally plugged it into that larger charger twice. Both times same results. Now to move them somewhere else so I don't do it on accident a third time.
root@openaps1:~/myopenaps# bt-pan client ac:37:43:89:ea:0f
Traceback (most recent call last):
File "/usr/local/bin/bt-pan", line 228, in <module>
if __name__ == '__main__': sys.exit(main())
File "/usr/local/bin/bt-pan", line 188, in main
dev_remote = find_device(opts.remote_addr, devs.values()[0])
File "/usr/local/bin/bt-pan", line 53, in find_device
return find_device_in_objects(get_manager().GetManagedObjects(), device_address, adapter_pattern)
File "/usr/local/bin/bt-pan", line 68, in find_device_in_objects
raise BTError('Bluetooth device not found')
__main__.BTError: Bluetooth device not found
--btpan=
parameter get recorded into oref0-runagain.sh?
btmac
. It shows up correctly in the cron entry.
gather
alias got a weird angled " mark instead of a normal one somehow.
apt-get install lm-sensors
and then sensors
halt
? I've seen mine do that once or twice, and so far a halt
will fix it when a reboot won't.
sensors
when you start charging, and see if it gets hotter on that higher-wattage charger
openaps alias show gather
output here as text so I can copy and paste it to find where it came from?
”
(curly quotes) character at the end anywhere in the oref0 code base
history | grep "openaps alias add"
output might be interesting
history | grep "/dev/null”"
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"'
openaps alias show gather
again?
openaps alias show gather
that it changed
killall -g openaps; openaps gather
now
openaps alias show gather
show the curly quotes again?
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"'
history | grep oref0-setup
should find the last run, so you can copy and paste and add the new one
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.