I have accomplished nothing today I *needed* to do, BUT:

1. I figured out why my #ubuntu server went wonky last night w/ ssh & several #docker containers inaccessible on the LAN. Turns out you shouldn't set ports & then network_mode to auto. Oh & I had configured UFW w/o making a rule to leave those ports open. Ha.

2. I GOT #NIGHTSCOUT TO PULL #DEXCOMSHARE DATA! Now all my #insulin, BGs, carbs, everything is in ONE place! OMFG I am so excited.

#T1D #Type1Diabetes #Diabetes #DiabeticProblems

#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.

https://github.com/chrcraven/Dexcom2NightscoutSync

#T1D #Type1Diabetes #Diabetes #DiabeticProblems

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 🤷‍♂️

#T1D #Type1Diabetes #Diabetes #DiabeticProblems

Just spent like an hour trying to set up #Tandem & #Dexcom —> #Nightscout.

Tandem’s API locked me out for who knows how long because #docker hammered it every time it crashed/restarted during setup 🙄

Dexcom apparently doesn’t port to Nightscout anymore?

NIGHTSCOUT PEEPS: What do I need to do to get this running???

#T1D #Type1Diabetes #Diabetes #DiabeticProblems