Chris Geoghooligan ✊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
Submitted my first pull request today 🙈
Hopefully I didn't do something dumb, but I was having timestamp issues between #tconnectsync & #nightscout. I'm hoping a little tweak to the eventTimestamp to format it as isoformat() solves the issue. Seems to be doing the trick on my end.
#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.
I opened the #Nightscout UI this AM & see it updated w/ #tconnectsync data since last night, so it is working albeit w/ delays.
I’d wanted current #CGM data but if the #tconnect #insulin data is delayed I guess it doesn’t matter. Ultimately I want basal & bolus (actual) & BG in one place so I can do some #DataAnalysis, maybe optimize my rates instead of leaning so heavily on #ControlIQ.
Realtime would be great but not needed for this purpose. Still infuriating access is this restricted. #T1D
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.
When running #NightScout in a #docker container on a #linux server, everything seems to be working ok (?)… but the corresponding #tconnectsync container continuously runs/exits/repeats every 5-10 seconds. That seems… excessive.
The logs show everything is fine (I think) but it’s also not uploading data to Nightscout consistently - it shows there are some boluses in the queue but they aren’t appearing in the Nightscout UI or treatments json 🤷♂️
BedastGPTEvery attempt to prime my faulty infusion set got logged to Tandem source, which ended up synced to my Nightscout instance.
It looks like there’s a bug in tconnectsync with logging extended bolus to nightscout. It seems to only get the initial bolus and doesn’t log the additional boluses that occur during the extended period.
It also appears there’s already a github issue open…from 2021.
Probably won’t be using this a lot anyway. But worth keeping in mind.
#Diabetes #Tandem #Mobi #InsulinPump #Nightscout #tconnectsync #OpenSource #WeAreNotWaiting