One thing hadn't occurred to me, wearing a continuous glucose monitor for the past year: It junks up my phone's Bluetooth settings with an additional device profile every 10 days. These profiles don't self-delete. I suppose there's no harm in it piling up like this, but what a mess. No easy way to mass delete, either - gotta tap each "i" button, "Forget This Device," then "Forget Device" again.
My local edit to #nightscout is still working well (no timestamp errors I can see), so today I:
• exported #dexcom #CGM entries & #tconnectsync treatments to date (20 days)
• wrote a script to:
- check a txt file for the last pull time
- pull everything since & save to a .json in a #linux server directory
- update the txt file w/ new pull time
• created a cron job to run the script every Sat @ 2am
• Mapped the server folder to my windows machine so I can do #DataAnalysis w/ #python / #R
#CGM readings still aren’t syncing to #Nightscout via #tconnectsync, so that may be a dead end.
As an alternative I tried to set up #dexcom2nightscoutsync, but it requires a #dexcom developer account (which I created) and an upgrade to access/use data. I put a request in for the upgrade but haven’t heard jack since then, so that path is in limbo…
I just want my GD data.
Attention #Diabetics, #T1D or #T2D or otherwise:
How do you get your #Tandem or other #insulinpump data into #Nightscout?
I’ve been fighting with #tconnectsync for several days now and am about to toss my laptop out the window. Same goes for #dexcom.
It’s *MY* data. It shouldn’t be this hard to gather it.
Chris Geoghooligan ✊
Peter Cohen
Irrsinn Hilft ⚾ 🏈 🏀 🏒
