nightscout/intend-to-bolus

Discussions around DIY closed looping with #OpenAPS

Sgoldberg89

@Sgoldberg89

the servers being down has been helpful in that I will know when it's working again! I'm not seeing any BG data getting pulled into the rig as I watch the tail

Dana Lewis

@danamlewis

Try it and see? Depends on which version you’re running. If not, upgrade to 0.7.0 and pick xdrip-js during oref0-setup for default offline looping

Do you have the secondary power source plugged in? And which version are you running?

KS615

@KS615

@danamlewis I'm back trying to update my Pi/HAT and receive the following message (Dana, this is Kris Schmitz from Facebook earlier).

error: Your local changes to the following files would be overwritten by merge:
        bin/oref0-mraa-install.sh
Please commit your changes or stash them before you merge.
Aborting
Couldn't pull latest oref0
root@pi1:~# git stash
fatal: Not a git

fatal: Not a git repository (or any of the parent directories): .git

Sgoldberg89

@Sgoldberg89

ok - i'll do that. Yes to the 2nd power source. Not sure what version I have but it's been a while so I will just give it a quick update. If it doesn't work I'm in the same spot I

I'd otherwise be

KS615

@KS615

And that's a different error than I received earlier

KS615

@KS615

ok, answering my own question, when you get the error, "tell us who you are" use the following commands,

git config --global user.name "abc"
     git config --global user.email "abc@example.com"

Sgoldberg89

@Sgoldberg89

E: Version '8.*' for 'nodejs' was not found
Couldn't install nodejs

is that an issue?

Scott Leibrand

@scottleibrand

yes

@KS615 not sure if this is still relevant, but to do git stash you have to be in the repo dir, so cd ~/src/oref0 first

KS615

@KS615

@scottleibrand yes, thank you! i figured that out, but it looks like my follow up message saying that may not have gone through. I'm in the process of re-running the script

will see if it works

KS615

@KS615

@scottleibrand it looks like everything went through now, how long do you think it will take to see a completed loop now that I just enabled xdrip-js? its still giving the notice that BG is too old and nightscout hasn't updated

KS615

@KS615

still not getting updated BGs-do I need to disable to my g6 app on the phone for xdrip-js to work? maybe that's the problem

Martin Haeberli

@mhaeberli

@KS615 in theory, no. But I don’t have enough practical experience to know.

KS615

@KS615

@mhaeberli ok, thanks, I'll give it more time

Dana Lewis

@danamlewis

4 rigs for sale on Fbk if anyone is looking for Edison-Explorer rigs. $250 for 4, which is a super great price.

Scott Leibrand

@scottleibrand

@KS615 did you configure the rig for alternate bluetooth channel to emulate a receiver?

KS615

@KS615

@scottleibrand I'm not sure how to do that-I updated Oref0 and added xdrip-js as my cgm, but didn't do anything else

How do I do that configuration?

@danamlewis thank you for the heads up-I'm sending him a PM

KS615

@KS615

I'm going to be heading to bed soon, but will check this in the AM before my flight, thanks!

Scott Leibrand

@scottleibrand

check the Logger documentation for details, but the tl;dr is vi ~/myopenaps/xdripjs.json

josevicns

@josevicns

recientemente he cambiado en mi Pi, el HAT por un módulo RFM69HCW; no soy capaz de hacerlo funcionar ya que cuando utilizo el script de configuración no se como poner que tendo RFM69HCW. el script que utilizo es....

sudo bash
curl -s https://raw.githubusercontent.com/openaps/oref0/master/bin/openaps-install.sh > /tmp/openaps-install.sh && bash /tmp/openaps-install.sh

Jordy Ruiz

@Dune-jr

@danamlewis ~~Fbk? What does that stand for?~~ I'm silly, that's facebook

Whoops, just realized I PR'd my own repo. Thanks for fixing the issues anyway :)

rafaelruizena

@rafaelruizena

@danamlewis yes, I tested 0.7.0 openaps and new nightscout versión (0.12.5), but also with an old nightscout versión(0.10.2), i have the same issue, no trend arrows on my nightscout web. I have a not updated rig (0.6.3 openaps with oref0), it works finely and my nightscout shows trend arrows next to number.

Dana Lewis

@danamlewis

@rafaelruizena k. Thx for the detail. Have you tried with 0.7.0 and a dev NS?

rafaelruizena

@rafaelruizena

@danamlewis Yes, both of them, and the trend arrows didn't show up, and it's strange because in the version 0.6.3, trend arrows work perfectly.

Dana Lewis

@danamlewis

May be a go-related thing with Medtronic cgm that’s missing. @ecc1 might be better to help troubleshoot?

Eric

@ecc1

@rafaelruizena can you send me a couple of examples of the sgv entries in Nightscout that have the correct trend info? I have code to compute a "direction" field for MDT cgm, but it is likely still buggy

rafaelruizena

@rafaelruizena

@ecc1 {
"_id": {
"$oid": "5de679bc72ad8c3f4a5cc54d"
},
"type": "sgv",
"date": 1575385380000,
"dateString": "2019-12-03T15:03:00.000Z",
"device": "openaps://CHAKIRIG",
"sgv": 90,
"direction": "FortyFiveDown",
"utcOffset": 60,
"sysTime": "2019-12-03T15:03:00.000Z"
}

Eric

@ecc1

@rafaelruizena thanks. can you also post some sgv entries from 0.7 corresponding to where you're not seeing trend arrows?

rafaelruizena

@rafaelruizena

@ecc1 I don`t have any entries from 0.7 with trend arrows

Eric

@ecc1

right, but I'd like to see some sgv entries for readings that are missing the arrows, so I can tell what's wrong with them (is it just a missing "direction" field, or something else?)

rafaelruizena

@rafaelruizena

@ecc1 {
"_id": {
"$oid": "5de679bc72ad8c3f4a5cc550"
},
"type": "sgv",
"date": 1575385080000,
"dateString": "2019-12-03T14:58:00.000Z",
"device": "openaps://CHAKIRIG",
"sgv": 98,
"utcOffset": 60,
"sysTime": "2019-12-03T14:58:00.000Z"
}

@ecc1 {
"_id": {
"$oid": "5de67b6872ad8c3f4a5ccc7d"
},
"type": "sgv",
"date": 1575385680000,
"dateString": "2019-12-03T15:08:00.000Z",
"device": "openaps://CHAKIRIG",
"sgv": 88,
"utcOffset": 60,
"sysTime": "2019-12-03T15:08:00.000Z"

Eric

@ecc1

if you still have a 0.7 rig, can you log into it and try the "cgmhistory" command?

@rafaelruizena gitter isn't working for me very well on my desktop -- if you see this, can we move to the slack channel?

rafaelruizena

@rafaelruizena

@ecc1 sorry but I don't know what is slack channel

Eric

@ecc1

seems to have recovered a bit, so we can keep trying here. anyway, I need to see some CGM entries pulled from your pump via the cgmhistory tool

rafaelruizena

@rafaelruizena

@ecc1 ok, I'm grateful for your help, but my son is not at home now, he comes back in one hour, then i'll send you the logs of cgmhistory.

rafaelruizena

@rafaelruizena

@ecc1 n as: root
root@192.168.1.196's password:
Linux CHAKIRIG 3.10.98-jubilinux-edison #3 SMP PREEMPT Sun Aug 13 04:22:45 EDT 2 017 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Dec 3 18:36:16 2019 from 192.168.1.164
root@CHAKIRIG:~# cgmhistory
2019/12/03 20:01:37 retrieving CGM history since 2019-12-03 14:01:37
2019/12/03 20:01:37 cannot connect to CC111x radio on /dev/spidev5.1
null
2019/12/03 20:01:37 /dev/spidev5.1: device is in use
root@CHAKIRIG:~#

Scott Leibrand

@scottleibrand

killall-g pumpwill stop the pump-loop that's using the radio

Eric

@ecc1

@rafaelruizena and once it does connect it will complain unless you have the MEDTRONIC_PUMP_ID environment variable set to your pump's 6-digit serial number, and optionally MEDTRONIC_FREQUENCY set to the preferred pump frequency in MHz

hson73

@hson73

elodaille01

Where communities thrive

People

Repo info

Activity