The integration is great and presents me with data in a graphable way that is better than the Dexcom App.
One great improvement would be to not hide the data forcing the error message caused by the data not being available currently. Being able to graph the existing previous data but show an error at the end of the graph might be better. The error message shows up as non-numeric data. it occurs when the sensor and phone loose touch for a while, 5-10+ minutes.
Just to clarify – are you saying if your BG prior to losing bluetooth connectivity is 100, the graph would continue to show 100 until bluetooth connectivity is reestablished?
It’s getting around the change of data type to the graph card I’m using that causes the graph to become invalid and then show the error message and not the graph. I don’t think showing the 100 in your example is correct (data isn’t real), showing a zero would show something unexpected. The beauty of the graph card is the step by step detail. I can see changes in the rate of change in the steps.
Hope that explains it better.
Not familiar with the graph card that you are using, would you mind sharing it?
I wonder if having some sort of template would be helpful to you in this situation? A template sensor that copies the Dexcom BG value, but is 0 when the BG value is unavailable / null.
Let me know!
Sorry, the standard Gauge Card is what I am using. I’ll look at the template sensor idea.