Many years ago, I went a similar route and built a small T1D monitoring stack from scratch for myself. It even pretended to be a Dexcom Follow client so I could get CGM from Dexcom in near real-time. When Dexcom eventually changed their internal APIs and broke my data ingestion, I decided to finally give Nightscout a shot. I've never looked back since.

As I see it, the big advantage of Nightscout is that it is a de facto standard interface, with many integrations already existing. And it's easy to build add-on apps on top of its API. I've built about four myself [0], [1] and there is a big community of users and developers building other things such as [2], [3], [4]...

Even though Nightscout is a little bit messy and requires MongoDB, it's surprisingly easy to self-host. I'm using the stock docker-compose file from the main repo with only minor modifications. I run it on a $6/mo VPS. As an alternative, there are two or three hosted Nightscout services costing little more than that.

I highly recommend you to consider going this "standard" Nightscout route because it can save you work (and worries) in the future, and you get to connect with the community around it. In my experience, going all alone from the start was not worth it.

[0] https://github.com/vitawasalreadytaken/koboscout [1] https://github.com/vitawasalreadytaken/glucoscape [2] https://github.com/kashamalasha/nightscout-widget-electron [3] https://github.com/mlukasek/M5_NightscoutMon [4] https://customtypeone.com/products/sugarpixel

1.	Python package compatibility with free-threading and subinterpreters(parallel.python.tips) 5 points by vita7777777 1 year ago \| 0 comments
2.	The most important Python news in 2023(python.tips) 3 points by vita7777777 2 years ago \| 2 comments

user:	vita7777777
created:	February 12, 2024
karma:	10