Is the Bluecon behaving now?
Kind of. It's a bit like Jemima in that poem - when it's good, it's very, very good, when it's bad, it's horrid!
For example, it was running absolutely fine for four days, then all of a sudden it starts reporting half bg levels, for no apparent reason. Then a day or two later, it's fine again. So, still a work in progress.
I'd got to the stage where I'd figured out libre's quirks sufficiently well to be confident bolusing from it with only a couple of bg tests a day to calibrate (there was actually a couple of days where I didn't test at all - first time in 29 years!), and a lot of that confidence came from over-testing in the first few weeks to figure out what the quirks were.
When I brought blucon into the picture, it was like going back to stage one. I'd have meter saying x, reader saying y and linkblucon saying z! I couldn't be bothered doing another couple of weeks of 15 tests a day to figure out it's quirks too.
At the end of the day, it's been interesting having readings direct to my phone, but bolusing from it, nah, maybe not, or, at least, not at the moment.
Although, then again, after realising the algos are different from the reader, they are noticeably less aggressive than the reader's in predicting hypos - the reader will sometimes tell me I'm at 3.5 and plummeting whereas a bg test will tell me I'm at 4.something and blucon's 5 min readings will be showing a slow and manageable slide down, not a plummet. So, reader jumps the gun a bit. Blucon is quite reassuring in that respect, it's just the occasional suddenly and randomly reporting levels half of what they are that makes me say close but no cigar.
I pay very little attention to decimal points - as long as I'm generally 5, 6 or so, it's all good - but I quite like blucon running to 2 decimal points. Managed to get a screenshot of this wonderfully demonic 666. Damian, Damian, daddy's home...
