Closed AISMap closed 2 years ago
I had the same issue several weeks ago with AAPS 3.0-RC and surprisingly with the same (wrong) date. I am not sure was also the timestamp same. This problem has not occurred after that.
This seems to be about the same problem: https://github.com/nightscout/AndroidAPS/issues/1421
Quick question, did you use the action button to let APS know that you changed the Sensor? I had the same problem, when using the action button that date appears in future. But after avoiding the button its working for me because it seems that BYODA notifies APS automatically about sensor change. Maybe this is the trouble maker that APS has 2 dates... but of course maybe I am wrong.
@ideaweb I used xdrip for a while and there I used the action button to reset the time of the sensor. Since a few months I'm back on BYOD app and do not need this anymore because of the automatic notification as you mentioned.
Hi,
No - I haven't done anything manually. AAPS creates the change date automatically after having received the info from BYODA. I am running this setup quite a while and with 2.8.2 there was never an issue.
/Arne
11.03.2022 10:19:21 Tom @.***>:
Quick question, did you use the action button to let APS know that you changed the Sensor? I had the same problem, when using the action button that date appears in future. But after avoiding the button its working for me because it seems that BYODA notifies APS automatically about sensor change. Maybe this is the trouble maker that APS has 2 dates... but of course maybe I am wrong.
— Reply to this email directly, view it on GitHub[https://github.com/nightscout/AndroidAPS/issues/1426#issuecomment-1064923896], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ALXWGBSLPDWNJTSPUIAFUIDU7MFZLANCNFSM5QMDDUSA]. Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. You are receiving this because you authored the thread.[Verfolgungsbild][https://github.com/notifications/beacon/ALXWGBSIPMEQTW5YLTNBMBDU7MFZLA5CNFSM5QMDDUSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH54XF6A.gif]
Hi,
I use BOYDA for managing my Dex G6 sensor and AAPS 3.0.0.1 as receiver. Sensor changes are kept automatically and sent to NightScout.
Since I changed to AAPS 3.0.0.1 the timestamp for sensor change is not correct:
sensor change happened
2022-Mar-10 07:26 CET
- displayed in AAPS as well as sent timestamp to NightScout is2106-02-07T06:28:1500Z
instead.AAPS does not allow to delete this wrong data anymore, it is possible only flagging it as "invalid".
Please get that fixed as it spoils up NightScout data as well as AAPS. Thank you