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

19th
Mar 2019
Stargazer32584
@Stargazer32584
Mar 19 14:01
Today, i found a ESP32 development board on amazon. With all features we need for a rig. All is on-board. Is it possible to develop the openaps-system on a board like this ? Or does it make no sense ?
Abigail Cember
@acember
Mar 19 14:44
@scottleibrand So, my rig has definitely never been able to get the clock time from my pump. (When I first started looping, it took me a really long time to figure out that this was the problem with offline, actually. ) Every time I power on the rig if it's been turned off, if there's no wifi then I have to do a manual date -s with a keyboard or I will never start looping. (I'll just get the "failed to synchronize" error over and over and over.) If I could get it to get clock time from the pump, that would majorly solve my problem!
Tom Boudreau
@tomasboudr
Mar 19 15:36
image.png
hi friends... attempting an install on pihat and seeing this
Is that "Unable to lock the administration directory" a thing to worry about?
Scott Leibrand
@scottleibrand
Mar 19 16:14
@acember you should be able to always leave the rig powered on, so it never loses time. If you need to do a hard reboot, leaving battery power on and rebooting with the black button will keep the clock running.
do you have logs showing the rig attempting to get pump time and set rig time when it's 1999?
Abigail Cember
@acember
Mar 19 17:20
My battery doesn't work at all, and even if I fixed it I'd really prefer to just be able to plug and unplug the rig if possible without worrying about having to keep the battery charged...
What do you mean about it being 1999?
Scott Leibrand
@scottleibrand
Mar 19 17:23
When the rig loses time, it thinks it's midnight UTC Jan 1, 2000 (which is Dec 31, 1999 local time west of UTC).
The question is whether there's anything useful in pump-loop.log about the rig attempting to set time from the pump in that scenario.
Tom Boudreau
@tomasboudr
Mar 19 17:48
Q for the group... Is the dev install un-borked? (@danamlewis 's term). Running into lots of issues.
Dana Lewis
@danamlewis
Mar 19 17:52
It was unborked, but always possible to bork again. What are you seeing?
Tom Boudreau
@tomasboudr
Mar 19 17:56
errors on npm global-install
and I'm not coounting deprecation warnings
Tom Boudreau
@tomasboudr
Mar 19 18:13
hilariously it worked the third time
so nevermind
Stargazer32584
@Stargazer32584
Mar 19 18:23
@tomasboudr I'am with you. In this moment, i have formatted the card an do all installations again. But the npm errors makes me a little bit disencouraged...
Jon Cluck
@cluckj
Mar 19 18:52
upgrade to node v10?
Abigail Cember
@acember
Mar 19 18:58
@scottleibrand Oh boy, the plot thickens. My rig does not reset all the way to 1999 when it "loses time": it seems to reset to some time that's only a few hours ago. I always assumed without really checking that that was whenever it last had power. Now I'm guessing that what's really happening is not that it's "losing time", but that it's somehow getting a new time from a source that's actually wrong. And this is probably related to those weird problems I was having with NS.
With this new information in hand I need to do some experimenting as soon as I get a chance...
Tom Boudreau
@tomasboudr
Mar 19 19:05
well then during a run of the setup script it fails with npm errors with 'Could not run oref0-get-profile' being the last thing
image.png
Tom Boudreau
@tomasboudr
Mar 19 19:13
@cluckj trying that and updating node now by running "npm install npm@latest -g"
tepidjuice
@tepidjuice
Mar 19 19:51
mmtune: 2019/03/20 06:49:50 cannot connect to CC111x radio on /dev/spidev5.1
2
This radio error started last night when
I was asleep
Jon Cluck
@cluckj
Mar 19 20:20
@tomasboudr that'll just update npm, you'll have to install node v10 manually
Tom Boudreau
@tomasboudr
Mar 19 20:20
@cluckj that helped!
Jon Cluck
@cluckj
Mar 19 20:20
oh, cool
Tom Boudreau
@tomasboudr
Mar 19 20:21
I would have bet $ updating node was included in our setup script and other pre-req updates, but I guess it isn't
Jon Cluck
@cluckj
Mar 19 20:22
it uses the raspbian version, which is v8
there's no v10 for the edison, or nodesource installer for the pi0
it's kind of a crappy situation...
Stargazer32584
@Stargazer32584
Mar 19 20:23
@cluckj me too.... !! Now...i try for me the 'git clone https://github.com/cluckj/oref0/ '. But he stopped with: ' root@APS:~/src# rm -rf oref0/
root@APS:~/src# git clone https://github.com/cluckj/oref0/
Cloning into 'oref0'... '
Jon Cluck
@cluckj
Mar 19 20:25
:) good luck
maybe we can get away with just updating npm to latest.........
Stargazer32584
@Stargazer32584
Mar 19 20:39

So..i have a message:

fatal: unable to access 'https://github.com/cluckj/oref0/': gnutls_handshake() failed: Error in the push function.

tepidjuice
@tepidjuice
Mar 19 20:54
and I get this on my hat rig...
Stargazer32584
@Stargazer32584
Mar 19 21:01
@cluckj The handshake was done. The installation is running with npm. With the npm - update, it works without errors... Thank you...!
Jon Cluck
@cluckj
Mar 19 21:12
great :D
Stargazer32584
@Stargazer32584
Mar 19 21:51

@cluckj The installation is fixed. But now, after the last reboot of the rig, i wrote the following:

pi@APS:~ $ sudo bash
root@APS:/home/pi# l

But nothing happend. The Unicorn is on the display and nothing happend.

Very strange..

Jon Cluck
@cluckj
Mar 19 21:58
it may take a little while for it to get started; can you see if cron is running: systemctl status cron
tepidjuice
@tepidjuice
Mar 19 22:48
Any ideas on why the radio would not be responding? i.e. cc111x: no response