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

14th
Apr 2019
Scott Leibrand
@scottleibrand
Apr 14 01:32
@cluckj would you be able to give @phinious_arms_twitter directions for testing the openaps/oref0#1241 stuff?
Jon Cluck
@cluckj
Apr 14 01:34
yep
Jon Cluck
@cluckj
Apr 14 01:42

if folks want to test it, do a fresh flash of jubilinux 0.2.0, then change the last few lines of the edison bootstrap to:

[bunch of wifi setup stuff]
sleep 10
echo -ne "\nWifi SSID: "; iwgetid -r
sleep 5
curl https://raw.githubusercontent.com/cluckj/oref0/master/bin/openaps-install.sh > /tmp/openaps-install.sh
)

then once that stuff completes, edit /tmp/openaps-install.sh so that a couple lines at the bottom are pointing to cluckj/oref0 instead of openaps/oref0, like so:

curl -s https://raw.githubusercontent.com/cluckj/oref0/master/bin/openaps-packages.sh | bash -
mkdir -p ~/src; cd ~/src && git clone git://github.com/cluckj/oref0.git || (cd oref0 && git checkout master && git pull)
Jonathan Arms
@phinious_arms_twitter
Apr 14 01:44
Much appreciated Scott & Jon. I'll try this and let you know if I can get it to work.
Jon Cluck
@cluckj
Apr 14 01:44
thanks very much :D
Natalia S.
@Propelld
Apr 14 02:58
I am back :( I try to find answers on my own first I promise! Is there a reason why the Pi sometimes won't follow the "reboot" command?
I've tried every variation I could find
Jon Cluck
@cluckj
Apr 14 02:58
yep, there's a silly bug in pibakery; try reboot -f
Natalia S.
@Propelld
Apr 14 03:00
worked! Should I use this from now on?
Jon Cluck
@cluckj
Apr 14 03:03
yep
Natalia S.
@Propelld
Apr 14 03:04
Thanks! @cluckj Also, my system still won't stay looped for more than 30 mins. It does a successful loop and then stops looping

I am getting this in the log:

Starting oref0-pump-loop at Sat 13 Apr 23:00:14 EDT 2019 with 25 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json
Checking pump clock: "2019-04-13T23:03:59-04:00" is within 90s of current time: Sat 13 Apr 23:04:01 EDT 2019
Error: pumphistory too old
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .

Jon Cluck
@cluckj
Apr 14 03:05
did you switch over to dev?
Natalia S.
@Propelld
Apr 14 03:06
I thought I did
I can try it again
Jon Cluck
@cluckj
Apr 14 03:07
sometimes the pumphistory too old error is caused by there being very old pump history (like if you haven't been looping for a while)
when was the last time the pump looped?
Natalia S.
@Propelld
Apr 14 03:08
Ah. 2130

When I run
cd ~/src/oref0 && git checkout dev && git pull

The log says 'already on dev'

Jon Cluck
@cluckj
Apr 14 03:08
I don't think that's long enough, but set a meaningless temp basal or do a tiny bolus anyway
Natalia S.
@Propelld
Apr 14 03:09
ok!
Natalia S.
@Propelld
Apr 14 03:16
I am just running npm run global-install at the moment
But do you think the old pump history is also the reason I stop looping after every temp basal?
It hasn't made it through more than 1 temp duration...
Jon Cluck
@cluckj
Apr 14 03:21
probably not, it should be setting temp basals frequently enough to avoid that
Natalia S.
@Propelld
Apr 14 03:44

Okay, this is my log after switching to dev and re-doing the global install, as well as giving a small bolus:

Starting oref0-pump-loop at Sat 13 Apr 23:42:04 EDT 2019 with 5 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Ref...

...reshed pumphistory and meal.json
Checking pump clock: "2019-04-13T23:45:16-04:00" is within 90s of current time: Sat 13 Apr 23:45:18 EDT 2019
Error: pumphistory too old
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .
Jon Cluck
@cluckj
Apr 14 03:50
could you run jq .[0] ~/myopenaps/monitor/pumphistory-24h-zoned.json?
Natalia S.
@Propelld
Apr 14 03:54
It says no such file or directory
Jon Cluck
@cluckj
Apr 14 03:58
hm, that's no good
are you logged in as root?
Natalia S.
@Propelld
Apr 14 04:02
I t
Yes
juddwakefield
@juddwakefield
Apr 14 08:04
Hi All... Fairly new and have a ton of items I'd like to sell. Can anyone point me in the right direction as to where I can post the items? All Medtronic. 2 pumps and 60 days worth of reservoirs and sets.
Why not
@Whynot2018_gitlab
Apr 14 11:17
Hi, I have a question. If you accidentally drop your Medtronic pump to the floor, does it shuts down by itself? Last time I had to take the battery out and wait a bit and put it back then it started to work again. Is this normal or something wrong?
jvemme
@jvemme
Apr 14 12:01

@jvemme you will need to use at least the dev branch for the rfm69, or my updated-setup branch ( https://github.com/cluckj/oref0/tree/updated-setup )

@cluckj Im gonna try your updated-setup cause dev wasnt working for me

jvemme
@jvemme
Apr 14 12:10
@cluckj Do I need to follow the steps in the official guides like
$ rm -rf ~/go/src/github.com/ecc1 $ go get -u -v -tags "rfm69 walrus" github.com/ecc1/medtronic/... $ cp -pruv $HOME/go/bin/* /usr/local/bin/ $ mv /usr/local/bin/mmtune /usr/local/bin/Go-mmtune
Jon Cluck
@cluckj
Apr 14 12:39
no, it'll do all that stuff automatically for you
Jon Cluck
@cluckj
Apr 14 13:06
there's a setup option decision tree that should let you pick the exact hardware setup you have, and it will download/build the software you need for it
jvemme
@jvemme
Apr 14 13:08
@cluckj I guess I just to run it like this then sudo bash curl -s https://raw.githubusercontent.com/cluckj/oref0/updated-setup/bin/openaps-install.sh > /tmp/openaps-install.sh && bash /tmp/openaps-install.sh
Ran into a few issues, seems it wont overwrite the old installation, and Iv lost my adaptor card for the SD card. Is there another way of doing a clean installation?
Jon Cluck
@cluckj
Apr 14 13:10
cd ~/src && rm -rf oref0 && git clone https://github.com/cluckj/oref0 && cd oref0 && git checkout updated-setup && git pull && npm run global-install
Natalia S.
@Propelld
Apr 14 14:21
@cluckj Hi Jon, thanks again for your help last night. I had to call it quits at midnight 😩 so we were discussing why my rig does not stay consistently connected?
jvemme
@jvemme
Apr 14 14:22

@cluckj Nice install, but its still not working i got this errors
ImportError: No module named mraa

Radio check failed. ImportError: No module named mraa
2019-04-14 16:19:41,702 ERROR port is not set in pump.ini. Please set port to your serial device, e.g. /dev/mmeowlink`
Where it gets the mraa from i dont know. I chose the RFM69HCW radio during setup

Natalia S.
@Propelld
Apr 14 14:22
In a normal log, am I supposed to see 'enact/smb-suggested.json:' with every log?
Right now I only sometimes see the suggestions (when I'm looping) but then I'll get 'Error: pumphistory too old
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning'
jvemme
@jvemme
Apr 14 14:29
@cluckj I tried the manual mmtune using this cd ~/myopenaps && sudo service cron stop && killall -g openaps ; killall -g oref0-pump-loop; OREF0_DEBUG=1 oref0-mmtune && sudo service cron start
But there it states that is using port /dev/spidev0.1 and last time i had tuning working it was on /dev/spidev0.0
Where to go from here?
Jon Cluck
@cluckj
Apr 14 14:29
I'll be back at my pc in a few hours for more advanced troubleshooting 🙃
jvemme
@jvemme
Apr 14 14:30
Just glad you are helping at all :-) Thanks a lot m8
Jon Cluck
@cluckj
Apr 14 14:33
it looks like despite having done a dev-based install, your rig is running an old (master) oref0-pump-loop. could be an npm link or install bug
@Propelld yeah, you should see that stuff for every loop
jvemme
@jvemme
Apr 14 14:39
@cluckj I can see Id better learn this, only used to .net programming
Natalia S.
@Propelld
Apr 14 14:45
@cluckj thanks :) I can come back to this when you return!
Scott Leibrand
@scottleibrand
Apr 14 15:12
@juddwakefield we had to institute a policy against for-sale posts in the openaps-dev google group. Have you tried joining the Looped group on Facebook and checking out their posting rules?
Jon Cluck
@cluckj
Apr 14 15:41
@jvemme try cd ~/src/oref0 && npm install && sudo npm install -g && sudo npm link && sudo npm link oref0
@Propelld check your hardware: is the antenna connected securely to your rig, is the pump battery low, is "remote option" turned on in your pump?
Natalia S.
@Propelld
Apr 14 16:48
@cluckj the battery was always full, now it's at 3/4 bars. I thought remote was on, but I made sure it was on and added an ID of 00000 to be sure. The antenna is on. It got a little bent because of the case it was in.
Jon Cluck
@cluckj
Apr 14 16:51
3/4 bars could be too low depending on the battery type, is it an alkaline or lithium battery?
Natalia S.
@Propelld
Apr 14 17:39
It's alkaline. So basically everything looks as it should? I was looking at the troubleshooting page on https://openaps.readthedocs.io/en/latest/docs/Troubleshooting/Pump-rig-communications-troubleshooting.html#how-can-you-see-the-results-of-your-pump-tuning and when I run 'grep mmtune /var/log/openaps/pump-loop.log' I don't see the pump loop logs like it says I would. Instead I get 'Binary file /var/log/openaps/pump-loop.log matches'
Does that mean anything?
Eric
@ecc1
Apr 14 17:56
@Propelld you can run "grep -a mmtune ..." (grep mistakenly thinks the log file is binary, -a makes it print the lines anyway). If it really is binary and you get a screenful of garbage, something else is wrong
Bernhard Klein
@Volberger
Apr 14 17:56
Hi, I got the following message and I do not know what to do. What will happen if I do not do anything, after all, the loop is gooing well. Message: You are currently running a development branch of oref0. Such branches change frequently.
Please read the latest PR notes and update with the latest commits to dev before reporting any issues.
Completed oref0-pump-loop at Sun 14 Apr 19:52:03 CEST 2019
"HAT Display Updated"
Jon Cluck
@cluckj
Apr 14 18:04
@Volberger you don't need to do anything if everything is working :)
jvemme
@jvemme
Apr 14 18:13
@cluckj Im giving it a try now.
jvemme
@jvemme
Apr 14 18:57

@cluckj Sorry to bother you again, but its still not working.
ImportError: No module named mraa

Radio check failed. ImportError: No module named mraa
2019-04-14 20:57:12,720 ERROR port is not set in pump.ini. Please set port to your serial device, e.g. /dev/mmeowlink

@cluckj I deleted the old folders before i began this time, so nothing should have been kept from the old installation.
Jon Cluck
@cluckj
Apr 14 19:14
the folders in ~/src aren't the problem, it looks like the global links (stuff in /usr/local/bin or /usr/sbin) have master stuff in them
jvemme
@jvemme
Apr 14 19:16
I can see a lot of files in /usr/local/bin including something thats surely is openaps files. And most of them are dated 2 days ago. Can I clean those folders? Maybe delete folders?
Jon Cluck
@cluckj
Apr 14 19:28
it's better to have them installed properly, give me a bit to figure out what is going on...
jvemme
@jvemme
Apr 14 19:28
:-) thx
will the output from putty help you?
Jon Cluck
@cluckj
Apr 14 19:30
nah
what's the output of npm --version?
jvemme
@jvemme
Apr 14 19:33
6.9.0
Natalia S.
@Propelld
Apr 14 19:33
@ecc1 Hi Eric, thank you for that. I want to make sure I have the spacing right because I keep getting an error.
@ecc1 disregard above. I realized it was giving me a correct output
Binary file /var/log/openaps/pump-loop.log matches
Is this what you meant? @cluckj so I ordered some lithium batteries. Other than that everything looks like it should? I guess if I still have connectivity issues I can come back here.
Jon Cluck
@cluckj
Apr 14 19:36
@jvemme now which oref0-pump-loop?
jvemme
@jvemme
Apr 14 19:37
/usr/local/bin/oref0-pump-loop
Jon Cluck
@cluckj
Apr 14 19:38
ls -la /usr/local/bin/oref0-pump-loop
jvemme
@jvemme
Apr 14 19:39
lrwxrwxrwx 1 root staff 48 Apr 12 00:31 /usr/local/bin/oref0-pump-loop -> ../lib/node_modules/oref0/bin/oref0-pump-loop.sh
Jon Cluck
@cluckj
Apr 14 19:40
nano /usr/local/lib/node_modules/oref0/bin/oref0-pump-loop.sh
does that file start with:
#!/usr/bin/env bash

source $(dirname $0)/oref0-bash-common-functions.sh || (echo "ERROR: Failed to run oref0-bash-common-functions.sh. Is oref0 correctly installed?"; exit 1)
or something else?
jvemme
@jvemme
Apr 14 19:41

!/bin/bash

OREF0_DEBUG makes this script much more verbose

and allows it to print additional debug information.

OREF0_DEBUG=1 generally means to print everything that usually

goes to stderr. (It will will include stack traces in case

of errors or exceptions in sub commands)

OREF0_DEBUG=2 is for debugging only. It will print all commands

being executed as well as all their output, (use with care as it

might overflow your log files)

The default value is 0. A silent mode could also be implemented, but

it hasn't been done at this point.

Note: for future changes:

- when subcommand outputs are not needed in the main log file:

- redirect the output to either fd >&3 or fd >&4 based on

- when you want the output visible.

OREF0_DEBUG=${OREF0_DEBUG:-0}
if [[ "$OREF0_DEBUG" -ge 1 ]] ; then
exec 3>&1
else
exec 3>/dev/null
fi
if [[ "$OREF0_DEBUG" -ge 2 ]] ; then
exec 4>&1
set -x
else
exec 4>/dev/null
fi
Jon Cluck
@cluckj
Apr 14 19:42
okay that's definitely a master oref0-pump-loop :\
jvemme
@jvemme
Apr 14 19:42
I guess thats something else
hmm
Jon Cluck
@cluckj
Apr 14 19:42
cd ~/src/oref0 and npm install && sudo npm install -g && sudo npm link && sudo npm link oref0
jvemme
@jvemme
Apr 14 19:42
as i mentioned ealier, thats it from when i tried the /dev branch
-bash: cd: too many arguments
Jon Cluck
@cluckj
Apr 14 19:43
those are two separate commands :)
cd ~/src/oref0 && npm install && sudo npm install -g && sudo npm link && sudo npm link oref0
jvemme
@jvemme
Apr 14 19:44
lol... I need to learn this...
fired them as 2 seperate commands...
Jon Cluck
@cluckj
Apr 14 19:44
:thumbsup:
jvemme
@jvemme
Apr 14 19:45
Guess thats gonna be a while again. Really glad your pitching in
Jon Cluck
@cluckj
Apr 14 19:46
when that's done, check what's in oref0-pump-loop.sh again with: nano /usr/local/lib/node_modules/oref0/bin/oref0-pump-loop.sh
jvemme
@jvemme
Apr 14 19:46
and then it should be as you sent before?
Jon Cluck
@cluckj
Apr 14 19:48
I hope so
jvemme
@jvemme
Apr 14 19:48
Ill post as soon as its done
Jon Cluck
@cluckj
Apr 14 19:55
@Propelld I think eric was suggesting grep -a mmtune /var/log/openaps/pump-loop.log
it should output something like this:
mmtune: "916.600", 3, -75 -- "916.650", 3, -76
mmtune: "916.600", 3, -80 -- "916.650", 3, -82
mmtune: "916.600", 3, -79 -- "916.650", 3, -80
mmtune: "916.600", 3, -59 -- "916.650", 3, -61
mmtune: "916.600", 3, -58 -- "916.650", 3, -59
jvemme
@jvemme
Apr 14 19:58
Script is done, still looks the same though...
Jon Cluck
@cluckj
Apr 14 19:59
okay
jvemme
@jvemme
Apr 14 19:59

!/bin/bash

OREF0_DEBUG makes this script much more verbose

and allows it to print additional debug information.

OREF0_DEBUG=1 generally means to print everything that usually

goes to stderr. (It will will include stack traces in case

of errors or exceptions in sub commands)

OREF0_DEBUG=2 is for debugging only. It will print all commands

being executed as well as all their output, (use with care as it

might overflow your log files)

The default value is 0. A silent mode could also be implemented, but

it hasn't been done at this point.

Note: for future changes:

- when subcommand outputs are not needed in the main log file:

- redirect the output to either fd >&3 or fd >&4 based on

- when you want the output visible.

OREF0_DEBUG=${OREF0_DEBUG:-0}
if [[ "$OREF0_DEBUG" -ge 1 ]] ; then
exec 3>&1
else
exec 3>/dev/null
fi
if [[ "$OREF0_DEBUG" -ge 2 ]] ; then
exec 4>&1
set -x
else
exec 4>/dev/null
fi

main pump-loop

main() {
check_duty_cycle
prep
if ! overtemp; then
echo && echo "Starting oref0-pump-loop at $(date) with $upto30s second wait_for_silence:"

do i need to reboot first?
Jon Cluck
@cluckj
Apr 14 20:00
nope, we get to try a bunch of different combinations of npm commands to see which one will fix it
jvemme
@jvemme
Apr 14 20:00
Yey ;-)
Jon Cluck
@cluckj
Apr 14 20:01
first one is cd ~/src/oref0 && sudo npm install
(then check the contents of oref0-pump-loop.sh)
jvemme
@jvemme
Apr 14 20:01
(Will do)
Natalia S.
@Propelld
Apr 14 20:02
@cluckj I'm getting
mmtune: "916.540", 5, -41 No wait required.
mmtune: "916.540", 5, -41 No wait required.
mmtune: "916.564", 5, -43 No wait required.
mmtune: "916.516", 5, -37 No wait required.
mmtune:
mmtune: "916.516", 5, -67 waiting for 14 second silence before continuing
mmtune: "916.540", 5, -70 waiting for 20 second silence before continuing
mmtune: "916.636", 0, -99 waiting for 78 second silence before continuing
mmtune: "916.636", 0, -99 waiting for 78 second silence before continuing
mmtune: "916.636", 0, -99 waiting for 78 second silence before continuing
mmtune: "916.564", 5, -49 No wait required.
mmtune: "916.636", 0, -99 waiting for 78 second silence before continuing
mmtune: "916.516", 5, -57 No wait required.
Is that good? I am tryi
I am trying to understand what a 'good' log should look like
Jon Cluck
@cluckj
Apr 14 20:03
@ecc1 the number between the freq and dbi is number of retries?
jvemme
@jvemme
Apr 14 20:05
Still the same...
Jon Cluck
@cluckj
Apr 14 20:06
now try sudo npm install -g (you should still be in ~/src/oref0)
jvemme
@jvemme
Apr 14 20:07
I am, and i will
Jon Cluck
@cluckj
Apr 14 20:10
@Propelld those look okay, it does seem like your pump has trouble communicating with your rig though
Dana Lewis
@danamlewis
Apr 14 20:10
@propelld yup - 99 is no comms and the lower the number the better
jvemme
@jvemme
Apr 14 20:13
Still the same...
Jon Cluck
@cluckj
Apr 14 20:13
@Propelld how's the antenna bent? like..is the wire crimped?
okay, try sudo npm link now
if that doesn't work, do npm link (no sudo)
jvemme
@jvemme
Apr 14 20:15
Ok.
jvemme
@jvemme
Apr 14 20:22
Done both, and still the same.
Eric
@ecc1
Apr 14 20:25
@cluckj Yes, middle number is # responses, but that looks like the Python mmtune to me. The Go version defaults to 3 samples, not 5, and returns JSON output (or a cheesy graph on the terminal with the "-g" flag)
Jon Cluck
@cluckj
Apr 14 20:29
@jvemme :| okay, wiping that directory out is sounding better and better: cd /usr/local/lib/node_modules, then rm -rf oref0
then cd ~/src/oref0 && git pull && npm run global-install
jvemme
@jvemme
Apr 14 20:31
Ok its running. Sometimes we need to burn bridges... lol.
Jon Cluck
@cluckj
Apr 14 20:33
I have a bad feeling that npm's link behavior has changed between versions
Natalia S.
@Propelld
Apr 14 20:33
@cluckj not crimped, just like a little wave. However I was still getting bad logs with a straight wire. The HAT is firmly screwed in. Don't know if there's a way to post an image here.
jvemme
@jvemme
Apr 14 20:34
:) Still hoping this well work
Natalia S.
@Propelld
Apr 14 20:37
@cluckj I noticed the trend that I seem to get better loops at night while I'm asleep. Not perfect but more frequently than during the day. @jvemme sorry I keep butting in! 😩
Jon Cluck
@cluckj
Apr 14 20:40
@ecc1 ah, @Propelld was running master for a while before switching
jvemme
@jvemme
Apr 14 20:44
@Propelld I'm just happy someone can help :)
@cluckj Install is done, now nano /usr/local/lib/node_modules/oref0/bin/oref0-pump-loop.sh is empty...
Jon Cluck
@cluckj
Apr 14 20:44
@Propelld maybe it's time to reflash the SD card and install right to dev?
jvemme
@jvemme
Apr 14 20:47
@cluckj Oh i see the folder has changed now which oref0-pump-loop outputs /usr/bin/oref0-pump-loopnow
Jon Cluck
@cluckj
Apr 14 20:47
&$^%# npm
jvemme
@jvemme
Apr 14 20:47
and where do i put that... :-)
Jon Cluck
@cluckj
Apr 14 20:48
track down where that's linked to (do ls -la /usr/bin/oref0-pump-loop)
jvemme
@jvemme
Apr 14 20:49
lrwxrwxrwx 1 root root 48 Apr 14 22:38 /usr/bin/oref0-pump-loop -> ../lib/node_modules/oref0/bin/oref0-pump-loop.sh
Jon Cluck
@cluckj
Apr 14 20:49
nano /usr/lib/node_modules/oref0/bin/oref0-pump-loop.sh
jvemme
@jvemme
Apr 14 20:50

`!/usr/bin/env bash

source $(dirname $0)/oref0-bash-common-functions.sh || (echo "ERROR: Failed to run oref0-bash-common-functions.sh. Is oref0 correctly installed?"; exit 1)`

Jon Cluck
@cluckj
Apr 14 20:50
sweet
jvemme
@jvemme
Apr 14 20:50
Looks a lot like what you asked for before
What should i do now
Jon Cluck
@cluckj
Apr 14 20:51
did you do anything to turn your loop off, like stop cron?
jvemme
@jvemme
Apr 14 20:51
Nope...
Jon Cluck
@cluckj
Apr 14 20:51
okay
check your pump-loop log (l) and see if it's looping
jvemme
@jvemme
Apr 14 20:52
something is happening
Listening for 2s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun 14 Apr 22:51:46 CEST 2019
Retry 2 of refresh_pumphistory_and_meal
Full history refresh failed.
Couldn't invoke_pumphistory_etc - continuing
Listening for 18s: .
Jon Cluck
@cluckj
Apr 14 20:53
when was the last time the pump looped, if at all?
jvemme
@jvemme
Apr 14 20:53
What am i looking for?
Jon Cluck
@cluckj
Apr 14 20:54
have you ever looped with the pump?
its treatment history might be empty
jvemme
@jvemme
Apr 14 20:55
No because I never got past the communication issues with the radio
Jon Cluck
@cluckj
Apr 14 20:55
ah :) set a temp basal or do a tiny bolus
something small, that won't hurt you
jvemme
@jvemme
Apr 14 20:55
on the pump?
Jon Cluck
@cluckj
Apr 14 20:55
yep
jvemme
@jvemme
Apr 14 20:56

{"status":"normal","bolusing":true,"suspended":false}
Retry 1 of refresh_pumphistory_and_meal

{"status":"normal","bolusing":true,"suspended":false}
Listening for 2s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun 14 Apr 22:55:55 CEST 2019
Retry 2 of refresh_pumphistory_and_meal

{"status":"normal","bolusing":true,"suspended":false}
Listening for 30s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun 14 Apr 22:56:26 CEST 2019
Retry 3 of refresh_pumphistory_and_meal

{"status":"normal","bolusing":true,"suspended":false}
Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 9 s silence before mmtuning
"HAT Display Updated"
Listening for 9s: .

Jon Cluck
@cluckj
Apr 14 20:56
awesome :)
jvemme
@jvemme
Apr 14 20:57
So thats while bolus is running
So i take it its working now?
Jon Cluck
@cluckj
Apr 14 20:57
yeah, it'll mmtune then hopefully do some stuff on the next run-through of the loop
it knows you're bolusing, so yeah :D
jvemme
@jvemme
Apr 14 20:58
Nice, im so grateful for your help.
Jon Cluck
@cluckj
Apr 14 20:58
glad it's starting to work now :)
Eric
@ecc1
Apr 14 20:59
looks like npm was being asked to do a global install with a "prefix" config of "/usr", so it was mucking with /usr/bin and /usr/lib (not sure where that's set, I thought it's supposed to be /usr/local, but maybe it got changed somehow?)
Jon Cluck
@cluckj
Apr 14 20:59
yep ^
jvemme
@jvemme
Apr 14 20:59
Properly not my last question, but thanks for now, and Im looking forward to see this in action.
Natalia S.
@Propelld
Apr 14 21:00
@cluckj okay, so reflash the card and follow the steps in the docs again? Anything in particular I should pay attention to/change?
Eric
@ecc1
Apr 14 21:02
https://docs.npmjs.com/files/npmrc.html <-- wow, what an assortment of foot-guns
@ecc1 :sob:
tzachi-dar
@tzachi-dar
Apr 14 21:03
Installing a new rpii rig now. what is the pi recommended version? I see there there is a pi release from a few days ago: Release date:2019-04-08 Does anyone know if it should work? Is it the recommended version?
Jon Cluck
@cluckj
Apr 14 21:03
as diabetics we already have enough freaking foot issues....
@tzachi-dar it should work
I updated my rig to that, but haven't done a flash with it yet
tzachi-dar
@tzachi-dar
Apr 14 21:05
OK, will try it soon...
jvemme
@jvemme
Apr 14 21:14
@cluckj Hate to bother you again so soon, but Is this something thats not working, or am I missing something?
Preflight OK. Profile less than 60m old; Profile valid. Full history refresh failed.
Couldn't invoke_pumphistory_etc - continuing
Retry 1 of refresh_pumphistory_and_meal
Full history refresh failed.
Couldn't invoke_pumphistory_etc - continuing
Listening for 6s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun 14 Apr 23:12:49 CEST 2019
Retry 2 of refresh_pumphistory_and_meal
Full history refresh failed.
Jon Cluck
@cluckj
Apr 14 21:15
is there anything in ~/myopenaps/monitor/pumphistory-24h-zoned.json
?
jvemme
@jvemme
Apr 14 21:16
no such file...
Jon Cluck
@cluckj
Apr 14 21:16
did you do a bolus & a temp basal, or just a bolus?
jvemme
@jvemme
Apr 14 21:17
I did both, the temp is still active
Jon Cluck
@cluckj
Apr 14 21:20
okay, you might have to give it a while (20-30 minutes) before it starts looping
jvemme
@jvemme
Apr 14 21:23
oh ok, i kinda read that a while back on another page... Now its running i cant wait...
another thing, the "buildin" webpage will that be updating then as well? I have seen my glucose values from Nightscout earlier in the process... but its all either 0.0 values or NaN
jvemme
@jvemme
Apr 14 22:24
@cluckj Still not completing loop. temp_basel.json is missing as well. Now i have completed a bolus and a temp basel been 30 mins since i completed temp and over a hour since my bolus. Any idear
Jon Cluck
@cluckj
Apr 14 22:35
okay, we can run a loop in debug mode to see what's going on: systemctl stop cron and wait a few minutes for the loop to finish, then cd ~/myopenaps/ && OREF0_DEBUG=1 oref0-pump-loop
jvemme
@jvemme
Apr 14 22:36
Ok, starting now
Jon Cluck
@cluckj
Apr 14 22:36
if you don't want to wait, you can kill the PIDs for the loop
jvemme
@jvemme
Apr 14 22:40
i waited till now:)
and its running in debug
Should i post output?

root@Kazoaaps:~# cd ~/myopenaps/ && OREF0_DEBUG=1 oref0-pump-loop

Starting oref0-pump-loop at Mon Apr 15 00:40:31 CEST 2019 with 5 second wait_for_silence:
grep: enact/smb-suggested.json: No such file or directory
grep: enact/smb-suggested.json: No such file or directory
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 5s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon Apr 15 00:40:37 CEST 2019
Preflight 2019/04/15 00:40:37 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:37 setting frequency to 868.400
2019/04/15 00:40:38 waking pump
2019/04/15 00:40:48 model 754 pump
2019/04/15 00:40:48 disconnecting RFM69HCW radio on /dev/spidev0.0
OK. Profile less than 60m old; "mmol/L"
"grams"
"mmol/L"
"00:00:00"
20
Profile valid. 2019/04/15 00:40:49 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:49 setting frequency to 868.400
2019/04/15 00:40:49 model 754 pump
2019/04/15 00:40:49 disconnecting RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:49 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:49 setting frequency to 868.400
2019/04/15 00:40:49 model 754 pump
2019/04/15 00:40:49 disconnecting RFM69HCW radio on /dev/spidev0.0
jq: error: Could not open file monitor/pumphistory-24h-zoned.json: No such file or directory
Quering pump for history since:
rm: cannot remove 'monitor/pumphistory-24h-zoned.json': No such file or directory
Full history refreshjq: Could not open openaps.jq: No such file or directory
2019/04/15 00:40:50 retrieving pump history since 2019-04-13 21:40:50
2019/04/15 00:40:50 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:50 setting frequency to 868.400
2019/04/15 00:40:50 model command required 1 retry
2019/04/15 00:40:50 model 754 pump
2019/04/15 00:40:53 stopping pump history scan at 2019-04-13 21:28:38
failed.
Couldn't invoke_pumphistory_etc - continuing
Retry 1 of refresh_pumphistory_and_meal
2019/04/15 00:40:53 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:53 setting frequency to 868.400
2019/04/15 00:40:53 model 754 pump
2019/04/15 00:40:53 disconnecting RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:53 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:53 setting frequency to 868.400
2019/04/15 00:40:54 model 754 pump
2019/04/15 00:40:54 disconnecting RFM69HCW radio on /dev/spidev0.0
jq: error: Could not open file monitor/pumphistory-24h-zoned.json: No such file or directory
Quering pump for history since:
rm: cannot remove 'monitor/pumphistory-24h-zoned.json': No such file or directory
Full history refreshjq: Could not open openaps.jq: No such file or directory
2019/04/15 00:40:54 retrieving pump history since 2019-04-13 21:40:54
2019/04/15 00:40:54 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:54 setting frequency to 868.400
2019/04/15 00:40:54 model 754 pump
2019/04/15 00:40:57 stopping pump history scan at 2019-04-13 21:28:38
failed.
Couldn't invoke_pumphistory_etc - continuing
Listening for 2s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon Apr 15 00:40:59 CEST 2019
Retry 2 of refresh_pumphistory_and_meal
2019/04/15 00:40:59 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:59 setting frequency to 868.400
2019/04/15 00:40:59 model 754 pump
2019/04/15 00:40:59 disconnecting RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:59 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:40:59 setting frequency to 868.400
2019/04/15 00:40:59 model 754 pump
2019/04/15 00:41:00 disconnecting RFM69HCW radio on /dev/spidev0.0
jq: error: Could not open file monitor/pumphistory-24h-zoned.json: No such file or directory
Quering pump for history since:
rm: cannot remove 'monitor/pumphistory-24h-zoned.json': No such file or directory
Full history refreshjq: Could not open openaps.jq: No such file or directory
2019/04/15 00:41:00 retrieving pump history since 2019-04-13 21:41:00
2019/04/15 00:41:00 connected to RFM69HCW radio on /dev/spidev0.0

2019/04/15 00:41:00 setting frequency to 868.400
2019/04/15 00:41:00 model 754 pump
2019/04/15 00:41:02 stopping pump history scan at 2019-04-13 21:28:38
failed.
Couldn't invoke_pumphistory_etc - continuing
Listening for 5s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon Apr 15 00:41:08 CEST 2019
Retry 3 of refresh_pumphistory_and_meal
2019/04/15 00:41:08 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:41:08 setting frequency to 868.400
2019/04/15 00:41:08 model 754 pump
2019/04/15 00:41:08 disconnecting RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:41:08 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:41:08 setting frequency to 868.400
2019/04/15 00:41:08 model 754 pump
2019/04/15 00:41:09 disconnecting RFM69HCW radio on /dev/spidev0.0
jq: error: Could not open file monitor/pumphistory-24h-zoned.json: No such file or directory
Quering pump for history since:
rm: cannot remove 'monitor/pumphistory-24h-zoned.json': No such file or directory
Full history refreshjq: Could not open openaps.jq: No such file or directory
2019/04/15 00:41:09 retrieving pump history since 2019-04-13 21:41:09
2019/04/15 00:41:09 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:41:09 setting frequency to 868.400
2019/04/15 00:41:09 model 754 pump
2019/04/15 00:41:11 stopping pump history scan at 2019-04-13 21:28:38
failed.
Couldn't invoke_pumphistory_etc - continuing
Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 37 s silence before mmtuning
"HAT Display Updated"
Listening for 37s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon Apr 15 00:41:49 CEST 2019
Listening for 37 s silence before mmtuning: Listening for 37s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon Apr 15 00:42:26 CEST 2019
mmtune: 2019/04/15 00:42:26 connected to RFM69HCW radio on /dev/spidev0.0
2019/04/15 00:42:26 setting frequency to 868.400
2019/04/15 00:42:28 waking pump
2019/04/15 00:42:38 frequency set to 868.150
2019/04/15 00:42:40 frequency set to 868.200
2019/04/15 00:42:41 frequency set to 868.250
2019/04/15 00:42:43 frequency set to 868.300
2019/04/15 00:42:43 model 754 pump
2019/04/15 00:42:43 frequency set to 868.350
2019/04/15 00:42:44 frequency set to 868.400
2019/04/15 00:42:44 frequency set to 868.450
2019/04/15 00:42:44 frequency set to 868.500
2019/04/15 00:42:45 frequency set to 868.550
2019/04/15 00:42:46 frequency set to 868.600
2019/04/15 00:42:48 frequency set to 868.650
2019/04/15 00:42:50 frequency set to 868.700
2019/04/15 00:42:51 frequency set to 868.750
{
"scanDetails": [
[
"868.150",
0,
-128
],
[
"868.200",
0,
-128
],
[
"868.250",
0,
-128
],
[
"868.300",
3,
-52
],
[
"868.350",
3,
-41
],
[
"868.400",
3,
-36
],
[
"868.450",
3,
-39
],
[
"868.500",
3,
-49
],
[
"868.550",
0,
-128
],
[
"868.600",
0,
-128
],
[
"868.650",
0,
-128
],
[
"868.700",
0,
-128
],
[
"868.750",
0,
-128
]
],
"setFreq": 868.4,
"usedDefault": false
}
2019/04/15 00:42:53 disconnecting RFM69HCW radio on /dev/spidev0.0
"868.400", 3, -36 -- "868.450", 3, -39
No wait required.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Mon Apr 15 00:43:01 CEST 2019
grep: monitor/temp_basal.json: No such file or directory
"HAT Display Updated"
jvemme
@jvemme
Apr 14 22:46
I found this line Full history refreshjq: Could not open openaps.jq: No such file or directory
Jon Cluck
@cluckj
Apr 14 22:47
yep :)
jvemme
@jvemme
Apr 14 22:49
I guess that file is something that should be somewhere?
Jon Cluck
@cluckj
Apr 14 22:49
ln -sf /root/go/src/github.com/ecc1/medtronic/cmd/pumphistory/openaps.jq ~/myopenaps/openaps.jq
jvemme
@jvemme
Apr 14 22:49
and that only toke a blink of an eye
reboot?
or do a debug run?
Jon Cluck
@cluckj
Apr 14 22:50
make sure it actually worked, cd ~/myopenaps && ls openaps*
should include openaps.jq
jvemme
@jvemme
Apr 14 22:51
That and openaps.ini
Jon Cluck
@cluckj
Apr 14 22:51
cool
yes now run the debug loop again
jvemme
@jvemme
Apr 14 22:51
:-)
same error line just came again
i just tried from WinSCP there i can see the file but when i try to copy it i get this error aswell Received error message from remote side: 'scp: /root/myopenaps/openaps.jq: No such file or directory'
how can that be...
Jon Cluck
@cluckj
Apr 14 22:54
it's a symlink
jvemme
@jvemme
Apr 14 22:55
oh
so link is bad
Jon Cluck
@cluckj
Apr 14 22:55
try to open it with nano
jvemme
@jvemme
Apr 14 22:56
empty...
Jon Cluck
@cluckj
Apr 14 22:56
if it's working, it should say #This is a jq filter...etc, blah blah
ah
try to open /root/go/src/github.com/ecc1/medtronic/cmd/pumphistory/openaps.jq
jvemme
@jvemme
Apr 14 22:57
with nano?
empty...
Jon Cluck
@cluckj
Apr 14 22:58
oh, you used binaries?
jvemme
@jvemme
Apr 14 22:58
[ Directory '/root/go/src/github.com/ecc1/medtronic/cmd/pumphistory' does not exist ]
Jon Cluck
@cluckj
Apr 14 22:58
ln -sf /root/go/bin/openaps.jq ~/myopenaps/openaps.jq
try that one
jvemme
@jvemme
Apr 14 22:58
Used binaries? you mean download manually?
Jon Cluck
@cluckj
Apr 14 22:59
yeah, during the setup when it asked if you wanted to download or build from source?
jvemme
@jvemme
Apr 14 23:00
Im pretty sure i went with source there. Wasnt i supposed to?
Jon Cluck
@cluckj
Apr 14 23:00
yeah...if you're using the walrus pinout you have to build from source :laughing:
jvemme
@jvemme
Apr 14 23:01
Thats why i did what i cant remember doing..
no luck yet
Jon Cluck
@cluckj
Apr 14 23:01
does /root/go/bin/openaps.jq contain anything, and did the link work that time?
jvemme
@jvemme
Apr 14 23:02
nope /root/go/bin/openaps.jq is empty
Cant see file from WinSCP either
Jon Cluck
@cluckj
Apr 14 23:04
:/ wat
okay look in ~/go/ -- what's in there?
jvemme
@jvemme
Apr 14 23:05
21 files
writehistory
txtest
ts
sniff
setbasels
rssi
regenerate
readhistory
readcgm
pumphistory
printrecord
mmtune
mdt
listen
historypage
fakemeter
cgmupdate
cgmts
Jon Cluck
@cluckj
Apr 14 23:07
but no openaps.jq? :laughing:
jvemme
@jvemme
Apr 14 23:07
cgmpage
thats right
Jon Cluck
@cluckj
Apr 14 23:08
:shrug: cd ~/myopenaps && wget https://raw.githubusercontent.com/ecc1/medtronic/master/cmd/pumphistory/openaps.jq
(that may not overwrite the symlink)
jvemme
@jvemme
Apr 14 23:09
and now its there
so should i test debug again?
Jon Cluck
@cluckj
Apr 14 23:09
if it has stuff in it, run the debug loop
yep
jvemme
@jvemme
Apr 14 23:11
now it cant connect to my radio
Preflight 2019/04/15 01:11:26 cannot connect to RFM69HCW radio on /dev/spidev0.0
Jon Cluck
@cluckj
Apr 14 23:12
:\ run it again? maybe reboot
jvemme
@jvemme
Apr 14 23:12
Always fun eh?
tried it a few times, reboot pending...
Jon Cluck
@cluckj
Apr 14 23:13
after reboot, you'll have to stop cron again
jvemme
@jvemme
Apr 14 23:14
much better now at least radio is connected
Now its only failing on autosens.json i can see it found my temp basel
so is autosens being added automaticly
Jon Cluck
@cluckj
Apr 14 23:18
failing or warning? can you paste some of the log around that?
jvemme
@jvemme
Apr 14 23:19
Optional feature Auto Sensitivity enabled. Could not find specified auto-sens: settings/autosens.json
{ Error: ENOENT: no such file or directory, open 'settings/autosens.json'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.readFileSync (fs.js:551:33)
at Object.<anonymous> (/root/src/oref0/bin/oref0-determine-basal.js:148:43)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:188:16)
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: 'settings/autosens.json' }
{"iob":0.412,"activity":0.0103,"basaliob":-0.184,"bolusiob":0.596,"netbasalinsulin":-0.4,"bolusinsulin":4.3,"time":"2019-04-14T23:14:38.000Z","iobWithZeroTemp":{"iob":0.412,"activity":0.0103,"basaliob":-0.184,"bolusiob":0.596,"netbasalinsulin":-0.4,"bolusinsulin":4.3,"time":"2019-04-14T23:14:38.000Z"},"lastBolusTime":1555272637000,"lastTemp":{"rate":0.5,"timestamp":"2019-04-14T23:44:59+02:00","started_at":"2019-04-14T21:44:59.000Z","date":1555278299000,"duration":30}}
{"delta":-2,"glucose":289,"noise":1,"short_avgdelta":-1.75,"long_avgdelta":0.1,"date":1555281323340,"last_cal":0}
null
No deliverAt found.
{"reason":"If current system time Mon Apr 15 2019 01:15:17 GMT+0200 (CEST) is correct, then BG data is too old. The last BG data was read 39.9m ago at Mon Apr 15 2019 00:35:23 GMT+0200 (CEST). Temp 0.5 <= current basal 1U/hr; doing nothing. "}
Couldn't smb_verify_suggested
Jon Cluck
@cluckj
Apr 14 23:19
okay, start up cron and watch your pump-loop log
jvemme
@jvemme
Apr 14 23:20
ok, will do.
Jon Cluck
@cluckj
Apr 14 23:20
it needs some BG readings to continue (which haven't been downloaded since we stopped cron earlier)
jvemme
@jvemme
Apr 14 23:21
ok, its running again now. btw will if it loses power, or reboot does it take 20-30 mins again before its running again?
Jon Cluck
@cluckj
Apr 14 23:22
nope, the delay is because on the first loop the rig has to pull a bunch of brand-new data
jvemme
@jvemme
Apr 14 23:22
oh ok.
Jon Cluck
@cluckj
Apr 14 23:23
it should start looping again pretty quickly after a power loss or reboot
jvemme
@jvemme
Apr 14 23:24
cool, man there is a lot of work gone into this. Have you been attach since the start?
Jon Cluck
@cluckj
Apr 14 23:25
nah, just the last year and a half?
jvemme
@jvemme
Apr 14 23:26
Man this is fantastic, I just got put on a temp basel for the next ½ hour. I am really hoping this can help me clean up my treatment
Jon Cluck
@cluckj
Apr 14 23:27
:D awesome!!! :clap: glad it's working!
jvemme
@jvemme
Apr 14 23:27
Seems to be running flawless right now. Thank you so much, you are a champ :)
Jon Cluck
@cluckj
Apr 14 23:28
do you have a ~/src/openaps-menu directory?
jvemme
@jvemme
Apr 14 23:28
yup
Jon Cluck
@cluckj
Apr 14 23:29
delete it: rm -rf ~/src/openaps-menu
Dana Lewis
@danamlewis
Apr 14 23:29
Yay @jvemme!
jvemme
@jvemme
Apr 14 23:29
oh that was the one we should delete during setup
Dana Lewis
@danamlewis
Apr 14 23:29
And also delete Edison battery too
Jon Cluck
@cluckj
Apr 14 23:29
updated-setup doesn't install it, but you had a dev install at some point
yes
Dana Lewis
@danamlewis
Apr 14 23:30
@cluckj can’t tell but did you find the source of that error through all that (most excellent) troubleshooting?
jvemme
@jvemme
Apr 14 23:30
thats true.
Jon Cluck
@cluckj
Apr 14 23:30
rm ~/myopenaps/monitor/edison-battery.json
@danamlewis maybe? I think there were a couple issues :laughing:
jvemme
@jvemme
Apr 14 23:31
Was I one of the issues?
Jon Cluck
@cluckj
Apr 14 23:31
nope
Dana Lewis
@danamlewis
Apr 14 23:33
@cluckj 😂
Jon Cluck
@cluckj
Apr 14 23:33
I think the npm thing was npm
jvemme
@jvemme
Apr 14 23:33
Well I hope I can learn a bit more of this Linux things, I work with .net and windows applications normally so maybe its not that far of a strech. would like to pitch in at some point
Dana Lewis
@danamlewis
Apr 14 23:33
@jvemme no and thanks for helping go step by step, which helps us debug and find the errors
Jon Cluck
@cluckj
Apr 14 23:33
:thumbsup:
yep thanks a lot for that :)
Dana Lewis
@danamlewis
Apr 14 23:34
@jvemme if you’re game to stick around we could use more help whack a mole-i g this dev branch to get it released soon-ish!
(Not right this minute I mean, but the next few weeks in general)
jvemme
@jvemme
Apr 14 23:34
I kinda know the pain of debugging and impatiant users...
Jon Cluck
@cluckj
Apr 14 23:35
ya I really want to get updated-setup into dev :grimacing:
Dana Lewis
@danamlewis
Apr 14 23:36
:+1:
jvemme
@jvemme
Apr 14 23:36
I'll be around, I know of a few more T1D that might need a setup like this and they diffently are gonna need guidence
Well its way past my bed time, so once again, thanks for all your help. See you
Jon Cluck
@cluckj
Apr 14 23:37
enjoy the closed-loop sleep!
jvemme
@jvemme
Apr 14 23:37
I will :-)
Jon Cluck
@cluckj
Apr 14 23:38
you might want to do a reflash and reinstall in the future, you're set up with a couple weird hacks right now :laughing:
jvemme
@jvemme
Apr 14 23:38
True, but im gonna have this running for a while now. Maybe get another SD card for testing
Dana Lewis
@danamlewis
Apr 14 23:39
:+1:
Enjoy and happy sleeping!
Jon Cluck
@cluckj
Apr 14 23:39
yep
jvemme
@jvemme
Apr 14 23:39
Same 2 you