ns-upload <my NS site> <my API SECRET> devicestatus.json monitor/upload-status.json
upload-status.json
actually lives in upload
. Are you certain your report says that it’s in monitor
?
nightscout autoconfigure-device-crud
?
nightscout autoconfigure-device-crud
it should work..right?
oref0
tools? Do you happen to have a list somewhere of the tools/devices/reports whose functionality is now provided by the oref
tools instead of things like iter_glucose
and the like? I’d like to go through the docs, find the old stuff, and replace it with oref0
.
oref0
received several updates to be easier to use
oref0_glucose
, it's part of the openaps/dexcom vendor
oref0 template
to set up common reports, devices, and even aliases: openaps/docs#132
lsgaps
, select
and friends, openaps/docs#129
ns
device is now like a nightscout swiss army knife
monitor/device-status-for-ns-to-upload.json
, you can do openaps use ns shell upload devicestatus.json monitor/device-status-for-ns-to-upload.json
devicestatus
endpoint
pump
, oref0 template ... | openaps import
creates all the reports with all the zones/units applied
ns-status
prepares the file for devicestatus
ns-status
to create that file
openaps report add monitor/upload-status.json JSON ns-status shell monitor/clock-zoned.json monitor/iob.json enact/suggested.json enact/enacted.json monitor/battery.json monitor/reservoir.json monitor/status.json
invoke monitor/upload-status.json
create the file?
openaps
in front.
openaps report invoke
openaps report invoke monitor/upload-status.json
I still have not gotten the Blood GLucose to Nightscout working, relying on xDrip for this.
If anybody is up for helping me troubleshoot, I would love it
use
as well
@danamlewis @scottleibrand @bewest
Yesterday I got a package. I was very surprised because I didn't know who was sending me a apron.
My germanLOOP friends gave me this wonderful gift as compliment in terms of motivation to improve the A1C.
Our goal is to archive a 5,x A1C (see the „5“ club label on the apron).
Furthermore my loop number is printed on the apron – yeah.
That’s me on this photo.
Hi wonderful people! It’s time for me to ask the obligatory cron question. I can see openaps run in a cron job, but the second that I try to add an alias parameter to the openaps invocation, it says ‘bash: openaps: command not found’. Here’s my crontab:
*/1 * * * * cd ~/clive-openaps-1 && (/usr/local/bin/openaps > hello.log 2>&1)
*/2 * * * * cd ~/clive-openaps-1 && (/usr/local/bin/openaps retry-loop > retry-loop.log 2>&1)
The first line puts what you would expect into hello.log. retry-loop.log ends up containing ‘bash: openaps: command not found’.
Any help is greatly appreciated! Thank you!
echo $PATH
to see your current one
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
*/1 * * * * cd ~/clive-openaps-1 && (openaps > hello.log 2>&1)
*/2 * * * * cd ~/clive-openaps-1 && (openaps retry-loop > retry-loop.log 2>&1)
nightscout
device? And even more improbably, do you recall which field you were saying that it needed to have in it? There were a couple date fields, but from NS apparently wasn’t returning it...
sudo raspi-config
and choose option 3, I think you want to either choose B2 or B4. That way, the pi
user is always logged in.
*/5 * * * * cd ~/clive-openaps-1 && (openaps retry-loop > retry-loop.log 2>&1)
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
openaps report add monitor/clock-zoned.json JSON tz clock monitor/clock.json
should that not create a clock-zoned.json file in monitor
folder ?
clock-zoned.json
is generated by: openaps report add monitor/clock-zoned.json tz clock --timezone "EDT" --adjust "missing" --date "None" --astimezone monitor/clock.json
. I’m a little fuzzy on the tz
device, but yours looks correct as well.
invoke
the newly configured clock-zoned.json report?
rm
, mv
and similar commands in alias
, it's making it hard to debug/understand what's happening
With working rig, using a connected Dexcom G4 - once retry-loop has run, and data uploaded to Nightscout, BGM should go from oref up to Nightscout right?
I am trying to figure why it isn't working still, only solution I have is to get BGM into Nightscout via a xDrip integration
raw
-dir concept without mv
ing the files, or clearing out the monitor
dir prior to running the loop?
oref0 copy-fresher
as a report in a few places as a "null" translation
oref0 template
stuff
git status
is ok. So perfectly safe to run in cron every minute.
oref0-reset-git
running every minute. I should probably prepend that to the loop - every minute is a bit overkill (even if it doesn’t hurt anything). Thoughts?