@garetis The Pi0 does not have the processing power to work with the HAT reliably. It tends to have issues with timeouts.
I had one working well enough with a plain radio board ('Slice of Radio' device), but trying to make it work with the hat resulted in something rather unstable...
IMHO the best Pi for a rig - if we had a radio/LCD-board designed for it - would be the CM4 or CM3
@Foxy7 you could manually download your files from Ns command line and then upload to OH, but that’s a bit of work if you’ve not done it before. There’s a NS repo for the code behind the uploader tool if you want to check it out.
Can you file an issue in that repo and I can get someone to help take a look? Might be the heroku side of it (which I can’t remember if I have access to but won’t be able to check until I’m back on decent Wi-Fi mid week)
/tmp $ git clone https://github.com/ecc1/medtronic
Cloning into 'medtronic'...
remote: Enumerating objects: 3007, done.
...
/tmp $ cd medtronic/cmd/cgmupdate/
/tmp/medtronic/cmd/cgmupdate $ go build -v
go: downloading github.com/ecc1/nightscout v0.0.0-20181103224750-3f979d458431
github.com/ecc1/medtronic/packet
github.com/ecc1/gpio
github.com/ecc1/nightscout
github.com/ecc1/spi
github.com/ecc1/cc111x
github.com/ecc1/radio
github.com/ecc1/medtronic
github.com/ecc1/medtronic/cmd/cgmupdate
/tmp/medtronic/cmd/cgmupdate $ go version
go version go1.15.9 linux/amd64
golangversion=1.12.5
if go version | grep go${golangversion}.; then
echo Go already installed
else
echo "Removing possible old go install..."
rm -rf /usr/local/go/*
echo "Installing Golang..."
if uname -m | grep armv; then
cd /tmp && wget -c https://storage.googleapis.com/golang/go${golangversion}.linux-armv6l.tar.gz && tar -C /usr/local -xzvf /tmp/go${golangversion}.linux-armv6l.tar.gz
elif uname -m | grep i686; then
cd /tmp && wget -c https://dl.google.com/go/go${golangversion}.linux-386.tar.gz && tar -C /usr/local -xzvf /tmp/go${golangversion}.linux-386.tar.gz
fi
fi
Jul 21 07:00:07 ********* heroku/router at=info method=GET path="/api/v1/entries/sgv.json?count=288" host=*********.herokuapp.com request_id=a57e9b7b-cd93-4c10-8903-f73eb9f70d52 fwd="*********" dyno=web.1 connect=0ms service=5ms status=401 bytes=560 protocol=https
Jul 21 07:00:07 ********* app/web.1 Resolving secret/token to permissions failed
Jul 21 07:00:12 ********* heroku/router at=info method=GET path="/api/v1/entries/sgv.json?count=12" host=*********.herokuapp.com request_id=ee5eef71-627b-4f36-81fd-2eefeb116d9b fwd="*********" dyno=web.1 connect=0ms service=473ms status=401 bytes=560 protocol=https
Jul 21 07:00:12 ********* app/web.1 Resolving secret/token to permissions failed
dev
does not have this problem, and I finally found this commit which seems to describe the issue perfectly openaps/oref0@89a90b8 . Can anyone else confirm whether they are seeing this issue?
I am not sure if that’s the only thing broken in master but you’re not the only one who needed to switch to dev recently and found it resolved the/an issue.
If we can get some volunteers to test some fresh installs and report back (here or in the open PR of dev to master), we could do a release (dev to master) and get master back to a working state.
"enable": " autotune ",
to "enable": "",
?