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

20th
May 2018
Tim Gunn
@Tornado-Tim
May 20 2018 00:16
@hamishsprocket: are you fixed up now?
Travis Cannell
@diabeticpilot
May 20 2018 00:27
hey @ecc1 I have some time now and am at my computer
naboull1
@naboull1
May 20 2018 04:36

doing a fresh install on a sd card and cant install

Collecting funcsigs>=1; python_version < "3.3" (from mock->openaps)
Exception:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 215, in main
status = self.run(options, args)
File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 353, in run
wb.build(autobuilding=True)
File "/usr/lib/python2.7/dist-packages/pip/wheel.py", line 749, in build
self.requirement_set.prepare_files(self.finder)
File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 380, in prepare_files
ignore_dependencies=self.ignore_dependencies))
File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 554, in _prepare_file
require_hashes
File "/usr/lib/python2.7/dist-packages/pip/req/req_install.py", line 278, in populate_link
self.link = finder.find_requirement(self, upgrade)
File "/usr/lib/python2.7/dist-packages/pip/index.py", line 465, in find_requirement
all_candidates = self.find_all_candidates(req.name)
File "/usr/lib/python2.7/dist-packages/pip/index.py", line 423, in find_all_candidates
for page in self._get_pages(url_locations, project_name):
File "/usr/lib/python2.7/dist-packages/pip/index.py", line 568, in _get_pages
page = self._get_page(location)
File "/u

Thomas
@TH2100
May 20 2018 13:05
@cluckj … still up and running.
no errors in loop-log, now 7 commits behind, x12, xdrip
Jon Cluck
@cluckj
May 20 2018 13:05
great :D
Thomas
@TH2100
May 20 2018 13:05
oh yes so :smile:
Jon Cluck
@cluckj
May 20 2018 13:05
@naboull1 did you try running it again?
jdunn42
@jdunn42
May 20 2018 13:22
Anyone know how to change the bt Mac address on the Edison? I restored an image to a different Edison, and they now have the same MAC address.
Jon Cluck
@cluckj
May 20 2018 13:25
@rollerdecom someone else is having trouble with an x12 and I think it might be firmware related. which version is your pump running? (you can scroll all the way down to the bottom on the status menu to see)
naboull1
@naboull1
May 20 2018 13:29

@cluckj yeah i went back logged in as root not pi. im back to the same position on repeat. its not picking up the carelink stick. thats with danas script update

Starting oref0-pump-loop at Sun 20 May 23:14:15 AEST 2018 with 30 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory
ImportError: No module named spi_serial

Radio check failed. ImportError: No module named spi_serial
Listening for 40s silence before mmtuning: ........

Jon Cluck
@cluckj
May 20 2018 13:31
did you use the most recent raspbian image?
naboull1
@naboull1
May 20 2018 13:32
i used 2018-04-18-raspbian-stretch-lite
that is the latest
Jon Cluck
@cluckj
May 20 2018 13:36
did you re-run setup after switching to fix-carelink?
naboull1
@naboull1
May 20 2018 13:36
ill try that now
Jon Cluck
@cluckj
May 20 2018 13:37
:thumbsup:
naboull1
@naboull1
May 20 2018 14:04

i ran setup again using bash ~/myopenaps/oref0-runagain.sh

still radio check is failing not picking up on the carelink usb

is there a code to check if its dectecting usb and if it recognises the carelink usb as a radio stick?
Jon Cluck
@cluckj
May 20 2018 14:07
does the tty port that's in oref0-runagain.sh still exist?
and just to make sure the setup went correctly, do you have radio_type=carelink in your pump.ini?
naboull1
@naboull1
May 20 2018 14:13
in /root/src/oref0/bin/oref0-setup.sh
it has the correct line after the setup
cd $directory || die "Can't cd $directory"
echo "Removing any existing pump device:"
( killall -g openaps; killall -g oref0-pump-loop) 2>/dev/null; openaps device remove pump 2>/dev/null
if [[ -z "$ttyport" ]]; then
    openaps device add pump medtronic $serial || die "Can't add pump"
# add carelink to pump.ini
grep -q radio_type pump.ini || echo "radio_type=carelink" >> pump.ini
    # carelinks can't listen for silence or mmtune, so just do a preflight check instead
i havnt touched anything in oref0-runagain.sh
im opening it now to see whats in it. what should i be looking for exactly?
Jon Cluck
@cluckj
May 20 2018 14:15
you should delete that, it has your api_secret
ah :)
naboull1
@naboull1
May 20 2018 14:15

To run again with these same options, use:

oref0-setup --dir=/root/myopenaps --serial=XXX--cgm=xdrip --ns-host=https://librelink.herokuapp.com --api-secret=XXX --pumpmodel=x12 --max_iob=10 --radio_locale='US' --btmac='XX'
just realised lol
philipgo
@philipgo
May 20 2018 14:15
@jdunn42 I can send you the info in a few hours
naboull1
@naboull1
May 20 2018 14:15
could radio locale=US be a problem?
im in australia
i bought the pump from someone in US and the carelink usb is from australia
i dont know if that is relevant
Jon Cluck
@cluckj
May 20 2018 14:18
you don't have a tty port for your carelink in oref0-runagain.sh
can you run the interactive setup instead of oref0-runagain?
I think australia uses the same frequency as north america
naboull1
@naboull1
May 20 2018 14:19

using this code?

cd && ~/src/oref0/bin/oref0-setup.sh

Jon Cluck
@cluckj
May 20 2018 14:20
yes that's the one :) do you know which tty port your carelink is on?
naboull1
@naboull1
May 20 2018 14:20
first time getting into pumping and pretty fresh on coding part so not sure what you mean of ttyport for carelink
sorry where would i find that

in the below question i left it empty and just pressed enter because its neither

Are you using an Explorer Board? [Y]/n n
Are you using mmeowlink (i.e. with a TI stick)? If not, press enter. If so, paste your full port address: it looks like "/dev/ttySOMETHING" without the quotes.
What is your TTY port?

should i be putting something in for the carelink usb?
when i do that it says after "ok, carelink it is.
Jon Cluck
@cluckj
May 20 2018 14:26
yes, I'm also trying to figure out what it would be :) carelink is from before my time
naboull1
@naboull1
May 20 2018 14:27
ah sorry, appreciate the help :)
Jon Cluck
@cluckj
May 20 2018 14:39
argh, I'm not sure
naboull1
@naboull1
May 20 2018 14:39
all good thanks for your help
Jon Cluck
@cluckj
May 20 2018 14:41
try ls /dev/ttyUSB*
naboull1
@naboull1
May 20 2018 14:42
/dev/ttyUSB.Carelink0 /dev/ttyUSB0
thats the reply
so it sees carelink0
Jon Cluck
@cluckj
May 20 2018 14:43
nice
naboull1
@naboull1
May 20 2018 14:43
i can ruleout hardware issue like cable or the usb its self
must be like a snipet of code somewhere
Jon Cluck
@cluckj
May 20 2018 14:45
the error message you were getting doesn't suggest a hardware issue
naboull1
@naboull1
May 20 2018 14:46
is there any setting on the pump i need to turn on? to activate radio communication
its a 512
Jon Cluck
@cluckj
May 20 2018 14:49
you need "remote" on
naboull1
@naboull1
May 20 2018 14:49
remote options is off
ill try now
please work lol
its got add id delete id and review id
Jon Cluck
@cluckj
May 20 2018 14:51
that error message you got earlier means that openaps is also not set up correctly
naboull1
@naboull1
May 20 2018 14:51
the setup could be wrong?
Jon Cluck
@cluckj
May 20 2018 14:52
can you check if radio_type=carelink is in ~/myopenaps/pump.ini?
naboull1
@naboull1
May 20 2018 14:52
ill check now 1 sec
its not in there
[device "pump"]
serial = XXX
radio_locale = US
Jon Cluck
@cluckj
May 20 2018 14:54
hah! okay put it in at the bottom
naboull1
@naboull1
May 20 2018 14:55
ah finally moving in a direction
ill add it now
in the pump what id do i put in remote on?
Jon Cluck
@cluckj
May 20 2018 14:55
you can put whatever random number you want
naboull1
@naboull1
May 20 2018 14:57
shouldnt it be a number from the carelink usb?
i think that number has to do with the remote controller buton thingy we just want it on to receive and send radio cool cool
is there anything else on the pump that needs to change? or i should check?
Jon Cluck
@cluckj
May 20 2018 14:59
I don't think it needs to be the carelink usb #
yes, it just needs to be on :)
cameronrenwick
@cameronrenwick
May 20 2018 15:02
anyone have a situation where SAGE stops displaying a value? Nothing has changed in my setup etc and I am past 30 days (which isn't typical) but I'm left wondering if there's a range for this setting that I've exceeded thus no longer displaying a value?
naboull1
@naboull1
May 20 2018 15:04

YESSS!!! we are getting somewhere

Starting oref0-pump-loop at Mon 21 May 01:01:06 AEST 2018 with 30 second wait_fo r_silence:
Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed' : No such file or directory
using carelink; not waiting for silence
Preflight (x12 models do not support SMB safety checks, SMB will not be availabl e.) OK. Old pumphistory-24h, waiting for 30 seconds of silence: using carelink; not waiting for silence
Old pumphistory-24h refreshed
Old settings: Pump profile refreshed; Could not parse autotune_data
Settings refreshed; Profile valid. Refreshed

Old settings: Pump profile refreshed; Could not parse autotune_data
Settings refreshed; Profile valid. Refreshed pumphistoryWarning: could not parse monitor/glucose.json
/usr/local/lib/node_modules/oref0/lib/determine-basal/cob.js:8
glucose_data = inputs.glucose_data.map(function prepGlucose (obj) {
^

TypeError: Cannot read property 'map' of undefined
at detectCarbAbsorption (/usr/local/lib/node_modules/oref0/lib/determine-basal/cob.js:8:39)
at recentCarbs (/usr/local/lib/node_modules/oref0/lib/meal/total.js:101:13)
at generate (/usr/local/lib/node_modules/oref0/lib/meal/index.js:20:19)
at Object.<anonymous> (/usr/local/lib/node_modules/oref0/bin/oref0-meal.js:97:23)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:140:18)
and meal.json
Checking pump clock: "2018-05-20T10:30:24+10:00" is within 90s of current time: Mon 21 May 01:04:30 AEST 2018
Pump clock is more than 55s off: attempting to reset it
/usr/local/bin/oref0-set-device-clocks: line 44: ntp-wait: command not found
sudo: /etc/init.d/ntp: command not found
Error: pump clock refresh error / mismatch
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
using carelink; not waiting for silence
using carelink; skipping mmtune

from what i see it can see the carelink usb
and i think it can see the insulin pump
because of the clock
Jon Cluck
@cluckj
May 20 2018 15:08
sweet
apt-get install ntp
naboull1
@naboull1
May 20 2018 15:12
installing that now
naboull1
@naboull1
May 20 2018 15:18
Checking pump clock: "2018-05-20T10:42:18+10:00" is within 90s of current time: Mon 21 May 01:16:24 AEST 2018
Pump clock is more than 55s off: attempting to reset it
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
Restarting ntp (via systemctl): ntp.service.
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
Error: pump clock refresh error / mismatch
that clock is all sorted now i think
thank you for your help @cluckj
Jon Cluck
@cluckj
May 20 2018 15:20
is it looping?
naboull1
@naboull1
May 20 2018 15:21

that last error is

Profile less than 60m old; Profile valid. Refreshed pumphistoryWarning: could not parse monitor/glucose.json
/usr/local/lib/node_modules/oref0/lib/determine-basal/cob.js:8
glucose_data = inputs.glucose_data.map(function prepGlucose (obj) {
^

TypeError: Cannot read property 'map' of undefined
at detectCarbAbsorption (/usr/local/lib/node_modules/oref0/lib/determine-basal/cob.js:8:39)
at recentCarbs (/usr/local/lib/node_modules/oref0/lib/meal/total.js:101:13)
at generate (/usr/local/lib/node_modules/oref0/lib/meal/index.js:20:19)
at Object.<anonymous> (/usr/local/lib/node_modules/oref0/bin/oref0-meal.js:97:23)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:140:18)
and meal.json

Checking pump clock: "2018-05-20T10:44:58+10:00" is within 90s of current time: Mon 21 May 01:19:05 AEST 2018
Pump clock is more than 55s off: attempting to reset it
Waiting for ntpd to synchronize... OK!
Setting pump time to Mon 21 May 01:19:09 AEST 2018
IndexError: bytearray index out of range
Setting CGM time to Mon 21 May 01:19:37 AEST 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
using carelink; not waiting for silence
using carelink; skipping mmtune
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Mon 21 May 01:19:46 AEST 2018
Jon Cluck
@cluckj
May 20 2018 15:24
that should fix itself
if you're using xdrip+, it can't set CGM time
naboull1
@naboull1
May 20 2018 15:33

ill leave it to run for abit. I am getting an error whenever i try to run
cd && ~/src/oref0/bin/oref0-setup.sh

i run through the setup again and at the end the last confirmation i get this error

/root/src/oref0/bin/oref0-setup.sh: line 1125: syntax error: unexpected end of file

Jon Cluck
@cluckj
May 20 2018 15:51
yeah, let it run for a while and see what happens
naboull1
@naboull1
May 20 2018 15:58
thanks again for your help i really appriciate it. ive been stuck on this problem for 2 days
Jon Cluck
@cluckj
May 20 2018 15:59
no problem :)
Dana Lewis
@danamlewis
May 20 2018 17:25
@naboull1 for that last attempt, which branch were you running?
philipgo
@philipgo
May 20 2018 20:44

@jdunn42 This is from my notes how to change the Edison Bluetooth MAC adress:

mount /dev/mmcblk0p5 /factory
nano /factory/bluetooth_address
Change the MAC adress, save and reboot

Hope it works!

N3FM
@N3FM
May 20 2018 21:16

Hi all! Doing my first install of oref0 0.6.1 master . My system: Edison+explorer board, Medtronic 530G/Enlite CGM (at the moment), also running a Minimed Connect (915 MHz) to Medtronic's Carelink site. I do notice that mmtune DID find a frequency to use; but I'm continuously seeing preflight fail. Initial log is more than 60 minutes without success. I'll try to paste a bit of the log:

Starting oref0-pump-loop at Sun May 20 16:50:02 EDT 2018 with 20 second wait_for_silence:
MDT CGM configured; not waiting
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. Retrying preflight
Preflight fail. Couldn't preflight
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.540", 5, -90 waiting for 60 second silence before continuing
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. 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 Sun May 20 16:53:35 EDT 2018
grep: monitor/temp_basal.json: No such file or directory

Starting oref0-pump-loop at Sun May 20 16:54:02 EDT 2018 with 26 second wait_for_silence:
MDT CGM configured; not waiting
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. Retrying preflight
Preflight fail. Couldn't preflight
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.540", 5, -80 waiting for 40 second silence before continuing
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. 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 Sun May 20 16:57:10 EDT 2018
grep: monitor/temp_basal.json: No such file or directory

Starting oref0-pump-loop at Sun May 20 16:58:02 EDT 2018 with 9 second wait_for_silence:
MDT CGM configured; not waiting
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. Retrying preflight
Preflight fail. Couldn't preflight
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.540", 5, -73 waiting for 26 second silence before continuing
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. 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 Sun May 20 17:00:40 EDT 2018
grep: monitor/temp_basal.json: No such file or directory

Starting oref0-pump-loop at Sun May 20 17:01:02 EDT 2018 with 25 second wait_for_silence:
MDT CGM configured; not waiting
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. Retrying preflight
Preflight fail. Couldn't preflight
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.564", 5, -83 waiting for 46 second silence before continuing
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. 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 Sun May 20 17:04:17 EDT 2018
grep: monitor/temp_basal.json: No such file or directory

Starting oref0-pump-loop at Sun May 20 17:05:02 EDT 2018 with 11 second wait_for_silence:
MDT CGM configured; not waiting
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. Retrying preflight
Preflight fail. Couldn't preflight
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.564", 5, -85 waiting for 50 second silence before continuing
Radio ok. Listening: .
Starting oref0-pump-loop at Sun May 20 17:09:02 EDT 2018 with 12 second wait_for_silence:
MDT CGM configured; not waiting
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. Retrying preflight
Preflight fail. Couldn't preflight
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.564", 5, -69 waiting for 18 second silence before continuing
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. 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 Sun May 20 17:11:38 EDT 2018
grep: monitor/temp_basal.json: No such file or directory

Starting oref0-pump-loop at Sun May 20 17:12:02 EDT 2018 with 20 second wait_for_silence:
MDT CGM configured; not waiting
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight fail. Retrying preflight
Preflight fail. Couldn't preflight

.. and on, and on...
Thanks for any suggestions! Bob

James Babcock
@jimrandomh
May 20 2018 21:44
Finally gave myself an A52 error (after months of doing the thing-known-to-cause-A52). Post-reboot, it seems to only be able to get portions of the pump history that don't include the A52 itself--pumphistory gives either 2018/05/20 17:41:57 6b/4b decoding failure or unexpected firmware version "\xff\xff\xff\xff\xff\xff...
(I'm going to revert to manual control until my IOB and COB come down to zero. I don't consider this a dangerous condition because A52 happens only during a user interaction and gives clear enough indication that it requires going manual.)
Eric
@ecc1
May 20 2018 21:48
that pumphistory error looks like another program was using the radio at the same time
James Babcock
@jimrandomh
May 20 2018 21:48
Oh right, I forgot to stop cron
(while running pumphistory manually)
The first error, or the second?
Eric
@ecc1
May 20 2018 21:49
second definitely, first possibly too
Eric
@ecc1
May 20 2018 21:55
The latest release should give a "spidev0.0 device in use" error message instead
James Babcock
@jimrandomh
May 20 2018 21:55
I think the first one is not that. I get pump-history entries if I run pumphistory -n <small-number> but not if I run pumphistory -n <large-number> and the oldest entry I'm able to get looks like right after the A52 reboot
(Specifically, the oldest PumpHistory entry is a NewTime setting the time to 2007-01-01, followed by DailyTotal, DailyTotal523, Rewind, BasalProfileStart, then a bunch of settings-changes as I put things back)
The history that I see in the pump's Bolus History menu goes further back than that, though
Eric
@ecc1
May 20 2018 21:58
You can do "pumphistory -a" to get everything on the pump; the "-n #hours" can get confused by time changes
(it will stop at the first record that's n hours old, which will be the case when there's a default time of 2007 or whatever in the way)
James Babcock
@jimrandomh
May 20 2018 22:00
pumphistory -a gives me a 6b/4b decoding failure
Eric
@ecc1
May 20 2018 22:02
those are (hopefully) transient, due to marginal or interfering radio comms. what does "mdt rssi" say the RSSI is?
James Babcock
@jimrandomh
May 20 2018 22:04
Ok, the 6b/4b is actually not reproducible, retrying a bunch of times I get it sometimes and get history other times
Ok, not a software problem, there's just 900MHz pollution in here. pumphistory -a started working when I decreased the pump-Edison distance from 1m to 3cm.
Thomas
@TH2100
May 20 2018 22:11
@cluckj ... all seems to be solved. But just in case: VER 2.2 1.1 B0 B0
alimhassam
@alimhassam
May 20 2018 22:16
@jimrandomh Re A52 error, you just reminded me. I wanted to experiment on adding a small sleep between the first ESC and the next 3. Completely forgot to do that.
James Babcock
@jimrandomh
May 20 2018 22:18
Right before the A52, the ESCs definitely didn't register. Maybe a corner case when there's RF interference with comms?
Jon Cluck
@cluckj
May 20 2018 22:20
@rollerdecom thanks! trying to track down an issue that might be firmware-related
alimhassam
@alimhassam
May 20 2018 22:20
It seemed to me when the error occurred to me a while back that the ESC didn't get pressed while I was scrolling (had down button pressed but not released)
It did stop the scrolling but didn't move back to the previous menu
That's why I thought the sleep would help
James Babcock
@jimrandomh
May 20 2018 22:23
Hrm, there is still a sync problem here--pump log eventually said "Full history refreshed through 2018-05-20T18:00:56-04:00", but that same log then showed an IOB that was missing my manual bolus
I probably had a scroll button held during the ESC, if my memory of the timing is accurate
alimhassam
@alimhassam
May 20 2018 22:28
was the manual bolus before the A52 error?
James Babcock
@jimrandomh
May 20 2018 22:30
There was a manual bolus first thing post reboot, which wasn't picked up, and another manual bolus ~20mins later, which was
Ohh, I see what happened
I'm currently not in my native time zone. And the time stamp on the bolus that wasn't picked up, is off by the difference between my current and home time zones.
Aaaand there it is, synced successfully, but 3 hours earlier than it should be
alimhassam
@alimhassam
May 20 2018 22:31
ah
James Babcock
@jimrandomh
May 20 2018 22:31
(Post reboot, I set the pump clock in local time, which is PST. Then I manually bolused. Then oref0 talked to the pump and set its clock to my home time zone, which is EST.)
alimhassam
@alimhassam
May 20 2018 22:32
i have something in my private repo which adjust records around clock change which might have helped with this.
James Babcock
@jimrandomh
May 20 2018 22:39
Worth a look. As a hack solution, I'm going to put in a Pushover notification for "clock changed by >5m, check if Nightscout history is accurate"
alimhassam
@alimhassam
May 20 2018 22:58
@jimrandomh completely untested and experimental at this point but here it is. Was planning to work on that in a following version... alimhassam/oref0@d095a59
naboull1
@naboull1
May 20 2018 23:59
@danamlewis . i didnt add a branch because i dont know how to do that in code. so i manually edited the file and added those lines. its looping now i gotta learn and understand what all the options and features are
thank you for setting up that code :)