3 ms·
It seems like you and the GP didn't read even the first 20% of the article. The author shows their CGM in the first 2 page lengths. They mentioned they did all
by muwtyhg 3y ago
It seems like you and the GP didn't read even the first 20% of the article. The author shows their CGM in the first 2 page lengths. They mentioned they did all of this because the official Libre app was constantly losing connection with their CGM. He bought a "hat" device called a "Miao Miao" and then siphoned off the data to his own CGM service that won't cut out if it receives, as the author puts it, "anomalous readings"
It has a side benefit of allowing them to show it on their Apple Watch using Google Calendar only.
- natdempk 3y agoActually I did read the whole thing before posting... There are different CGM models where some require scanning and some report continuously. My reading was that the author's model seemed to only support scanning thus the need for the hat, rather than periodic updates to an app that newer models provide, but it doesn't seem 100% definitive from the article as I don't know if on newer models data export might require scanning? The point of my comment was that rather than all this work, getting a different device could more-or-less enable the desired functionality without so many workarounds and the bulky hat device by eliminating the whole scanning/inconsistency aspect. Though if you want to pull the raw datapoints etc. and export them elsewhere, then there are still more complications. The non-scanning ones might still be a bit unreliable as well, not sure where that aspect is coming from.