pachi81
Notification Read Feature Request
Xdrip+ has a companion mode that reads notifications from various sources (Dexcom G6, G7, One+, etc.) and transfers the values to other apps like AAPS. Unfortunately, Xdrip+ doesn't use the arrow values (e.g., ↗️) and creates its own, causing issues in apps like AAPS. I currently use GlucoDataHandler to bypass this, but it requires an internet connection to fetch values from Dexcom Share or Nightscout, which isn't always available.
Would it be possible to integrate a feature into GlucoDataHandler that reads notifications directly, allowing for offline use with my Dexcom and AAPS setup? Since Xdrip+ is open source, perhaps some of their code could be modified to achieve this.
If you're able to implement this feature, I'd be happy to buy you a coffee as a token of my appreciation.
Thank you!
Hi, the feature is still planned and the main part is already implemented. But I have the same problem like xDrip, that I need historical data to calculate the trend. So you will have the same problem, that the trend is calculated. But I can try to parse also the trend arrow. Can you provide a screenshot of the notification?
(The mail was also from you? So I do not reply to the mail, again.)
Regards, Michael
Hi there @pachi81,
Yes the mail was from me!
It's not that Xdrip doesn't calculate the trend arrows, it's that it's WRONG. It's because you cannot change what values it considers for which arrow, for example, if my Dexcom is 5.5↗️ then Xdrip might be 5.5⏫ (Double up arrow). I believe xdrips threshold is lower (say 0.01 per minute instead of 0.1) and it's not changeable. I Believe you can do this :D
To the best or my knowledge, it's because they don't use the same values to calculate what qualifies as an ⬆️ or ⏫ (also ⬇️⏬) I have attached what Dexcom uses to calculate the arrows, at least the extreme ones. You will also want to convert them to Mg/DL but I'm sure you have that already
Attached is the Dexcom notification as requested and the threshold for at least the extreme/rising and falling fast arrows from inside the Dex app
Oh, it is configurable... At the moment, I do not plan to make it configurable. But we are checking, if it is possible to parse the arrow from notification. If it is an unicode string it may be possible. Not for icons...
It's not really configurable as such, those values are what they use for arrows (that you can put into GDH)
The first option is the default, and means you will get an alert when it's a single arrow OR a double arrow, 2nd option will ONLY alert you when it's a double arrow
Since you already have alerts set up and working in GDH that won't be an issue, it's already configurable in GDH!
All you need (I think) are those values to work out the trend arrows yourself on GDH when reading the notification - 0.1-0.2mmol/L or 0.5-1.0mmol every 5 minutes is ⬆️⬇️ and anything above that is ⏫⏬, and guessing the ↗️↘️ something like 0.3-0.4 every 5 mins
Obviously I can't give you values for the other arrows (↗️ etc) but I'm guessing it's somewhere below the single arrow values, keeping in mind that those values are per minute, and it only visually shows a value every 5 minutes (I'm assuming it times that value by 5, e.g 0.2mmol/L per minute would be ⏫ if it was 1.0mmol/L per 5 minutes)
If I have understood all that correctly!
Ah, you mean, for double up and down it should be related to the alert settings!? OK, at the moment, these are fixed values related to rate/scope value provided by Juggluco and xDrip. But these values have not a real unit and even hard to compare. For me it looks a little bit like mmol per minute*10. For my trend calculation I also check the values of the last 25 minutes (at the moment). For rising alert I only check the last delta. But you are right, maybe I have to re-think the rising and falling alert...
Your alerts are fine, I'm just talking about GDH calculating the trend for a local setup since you (I think) can already read the value, but you can't read the arrow since it's not text, not that it's related to the alert settings
I think I was a bit confusing with that's screenshot. That screenshot IS from the alert settings, but it also has values there showing what it uses to make that alert (so what it considers rising fast or falling fast. Aka the arrows ) Your alerts are already great and I don't believe the need changing
0.1-0.2mmol/L or 0.5-1.0mmol every 5 minutes is ⬆️⬇️ and anything above that is ⏫⏬, and guessing the ↗️↘️ something like 0.3-0.4 every 5 mins, but I don't have a value for that directly
I was doing *5 because if it's 0.1mmol/L per minute, *5 would be 5 minutes
I was just giving what I think are the values so you can work out the trend arrow locally :)
Hi, I also re-think and will let the alarms as there are. At the moment, the double arrow will be visible, if the value per minute is 0.3 mmol/l over the last 25 minutes. So I think at the moment the double arrow is not really present, I only got it once at the moment. Not sure, if I have to change this behavior, but a double arrow is a real exception... 0.2 mmol per minute is arrow up/down and 0.1 mmol per minute would cause 45° arrow. Maybe I can change the double up/down to 0.25, but not really sure.
Regards, Michael
Alright, I can't wait to test!
I cant use xdrip but because it works the arrows out differently to Dexcom, it messes up when you have a pump, say I'm 7.5↘️ on Dexcom, xdrip will say I'm 7.5 ⬇️⬇️ so it stops delivering insulin when it shouldn't. I use GDH to bypass this so the arrows are correct, but it's not offline (yet)
Look forward to testing your new release :D
Hi, ready to test 😉 You can install in parallel to GDH for testing. But you have to enable also the Dexcom foreground notification, as the notifications of Dexcom are really strange...
https://drive.google.com/drive/folders/1NIIDsqwnXDdfZjeI9I_-DUQzPacWrSqi
Sorry I missed this. GitHub emails are trashola and never arrived half the time. Testing in progress!
Ok, initial feedback! @pachi81
Seemed to be consistently 5 Minutes behind when I first installed, but then it caught up and was exactly the same tile as Dexcom notification update?- What's going on there?
Works with Dexcom's notification minimised (as I have it, xdrip also won't read the notification without this, see 1st picture)
Trend arrows are SPOT on, so far (They are a little off axis when using 1 min delta (you use more than 5 arrow directions, excluding doubles), thae 1 min delta should be disabled (as in locked out) in both sources and notification reader areas of Dexcom of any type is the selected app (Mainly Dexcom G7 and Dexcom One+) + See 2nd picture, but not an issue so far when configured properly
~~The delta is way off (see 2nd and 3rd pictures). Original GDH is correct, and I watched it update in real time so I know it's definitely wrong - I went from 10.1 to 10.2, so +0.1~~ I had turned off 5 minutes delta and didn't realise that you had 1 minute stats on the home screen now. You have to have 5 minutes delta on in both the sources area, and the notification reader area for this to work properly. If it's on in the notification reader area, and off in sources. It's WAY OFF. So far perfect but further testing required
See 3rd picture for them all matching up, it's satisfying. I'll do further testing in the next few days, and assuming it can push those values to AndroidAPS, we have a winner!
The 15 mins trend value, and the bottom trend value on the app homepage are broken I think, both say 0, but it's development version so expected!
What a f*cking amazing developer you are, where do I buy you a coffee for your hard and amazing work?!
Trend arrows are SPOT on, so far (They are a little off axis when using 1 min delta (you use more than 5 arrow directions, excluding doubles), thae 1 min delta should be disabled (as in locked out) in both sources and notification reader areas of Dexcom of any type is the selected app (Mainly Dexcom G7 and Dexcom One+) + See 2nd picture, but not an issue so far when configured properly
Yes, I use 5° steps instead of 45° steps. I think this makes more sense. Especially if you have a trend of 44° all apps are showing steady trend arrow... I think, that is wrong, so I'm using 5° steps. Also double arrows are possible, but in really corner cases...
You can switch to 5 min delta in settings. As I'm using libre, I prefer 1 min delta. That is the reason, I also show this delta value.
The 5 min interval for notification reader is not related to delta, it is related to reading, as the notifications are updated quite often, so it is hard to detect, which one is a new value or only a notification update. For G7 I also recommend to enable Dexcom foreground notification, as it helps to better detect...
The 15 mins trend value, and the bottom trend value on the app homepage are broken I think, both say 0, but it's development version so expected!
It seems, you understand it wrong, the 15 min delta is the real difference between your last value and the value 15 min ago, so related to your graph, the delta is correct. Only the 1 min delta is calculated, if there is no 1 min interval. The last trend value is the trend arrow rotation in degree. It is more a debug output for me and it my be removed in final release.
What a f*cking amazing developer you are, where do I buy you a coffee for your hard and amazing work?!
Checkout the readme for this app here on GitHub 😉
Thank you for your feedback!
I don't have AndroidAPS installed at the moment due to new phone, the only question I have, is how those arrows will translate to androidaps, at that ONLY supports ⏫⏬⬆️⬇️↗️↘️➡️ and is the whole reason for this update (for me anyway). But I do like that it has more arrows!
Struggling with the delta a little also, Old GDH will tell me +0.2 where New GHD may say +0.02 and I think they should be the same (like old GDH) - may be a bug, or may be just what I'm used to but I'll attach a few pictures anyway - The arrows are also sometimes different (as in completely) which is BAD as AndroidAPS needs accurate arrows. It acts on delivering insulin with these arrows
You can see the differences in those 2 images. And Old GDH is always correct as it's pulling from nightscout. I do believe the arrow direction (even if you keep the 5° ones) needs fixing, e.g when new GDH shows ⬇️ when it's ➡️ as AndroidAPS could kill me with that
Other than that, it's perfect :)
You have to enable 5 minute delta, the only bug is your config 😉 It will translate as normal, 0-40° steady, 45-85° is diagonal up, 90° up...
The old version can only show the arrows, received from source, so not my problem.
I believe I have been using 5 minutes delta already, but the arrows are still not what they should be. If you show me where I enable it I will test but this is what I've been using. The previous screenshots were using the below settings
See the arrows here. the delta is correct this time but the arrows is not. I've been using the above settings since before my initial feedback
Just NOW the below screenshot shows the delta not right again, but this time the arrow is correct
You can not compare with xDrip source, as xDrip has its own calibration algorithm. Just checkout the graph in second
It's not Xdrip, both are GlucoDataHandler. Xdrip is not involved. Original GDH is using Dexcom Share, new GDH is reading Dexcom notification
Please enable Dexcom foreground notification. And please show the app screenshot, I can not say anything without graph.
What do you mean by foreground notification? The one in the screenshot or the foreground channel in 2nd screenshot? It works without the foreground channel as long as the main notification is there (1st screenshot). As you can see the delta should be 0.1 but it's 0.06.
All the foreground channel does is keep showing a notification saying "Dexcom app is running"
Please enable Foreground Channel for Dexcom. And sorry, but I do not really care at the moment 🤣
Not may people do care if I die, don't worry 😂 I have enabled it, I'll keep testing
Enjoy your holiday dude!
The problem with the notification is, that there are multiple notification within 5 minutes, so it is hard to detect, what is a new value, what is only an update of the notification. So the delta may differ, as the wrong notification is detected... With foreground channel notification it os working quite better, as this normally only update for new value, so I'm using this as indicator... but I also have seen irregular updates of this notification. I really have no idea, what dexcom is doing with their notifications. It is really weird. If you really want to have only new values, you need to use either Dexcom Share or BYODA.
I also not sure about the trend calculation, as I do not have any experience with. I think it is working, but in some situations like having steady values and then an increase, like in your one screenshot, the calculated value is too high. Maybe I have to re-think.
Ok, almost final feedback - you will like this :D
I'm awaiting the results for AndroidAPS integration (with the arrows etc), that will take a few days!
The new GDH seems to, more often than not, be MORE accurate than the OLD GDH for the delta, after giving it more time (the +-0.1). The arrows I still believe should have a 45° mode - maybe an option in settings? I like the extra arrow directions but I don't think AndroidAPS does, but I will have final results in a few days. I will post a final feedback in a few days but mostly great so far
There is an issue, with at least the G7 app and new GDH, that if Dexcom pushes a "rising/falling fast" notification, that GDH seems to use that notification and not the persistent notification, so I lose values whilst that notification is there, but it has been stable since turning it off (I use GDH notifications anyway)
The only thing that is sort of missing is some onboarding, or default settings to ensure it's smooth running first off for notification reading. I'll keep you updated when my AndroidAPS results are in
Thanks again!
OK, final feedback @pachi81
Overall, very good. Sometimes the arrow direction is more accurate than Dexcom itself!
I was high there, but dropped because insulin was given. New GDH was more accurate.
There needs to be a way to handle HIGH and LOW values via the notification reading, I believe you already have this mostly implemented, just needs a tweak. It currently shows as a disconnection and shouldn't, the values are literally HIGH and LOW
And finally, there is a timing issue, it's 100% due to because it has to read the notification and there is some latency there, but I wondered if there was a way to smooth out the timing so this doesn't happen, and example of AndroidAPS complaining about it is below
The timing isn't a super deal breaker but it does affect AndroidAPS' operation slightly and it would be nice to see if fixed if possible
Thank you very much for your hard work, I'm happy to see that as an update after this!
If the alarms occur again, please send the logs, but there seems to be ignored, only the error message appear...
Related to the irregular readings, have you checked the graph in GDH? Are there only new values every 5 minutes or are there more? If there are more, please provide logs and app screenshot with graph, but be aware, that the logs only covers 15-20 minutes depends on the phone.
One more thought, you can try to specify the interval in settings - transfer values, so GDH will pnly send new values every 5 minutes, even if there are more. But if the readings from notification comes to late it is much harder. Therefor I need the lofs to analyse! Logs can be saved in Import/Export settings. But not the first entry for settings!
Hi @manor7777 any news on this topic? Can you provide logs and graph screenshots for the problem? Otherwise there is nothing I can do...