Closed rICTx-T1D closed 2 years ago
can report same issue on 3.1.02 (dev) but not doing anything special, using all the time same pump driver.
can report the very same behaviour on 3.1.0.2 (fullrelease). i just press "dismiss" and the app works properly (Accu Check Combo, Decom G6
Additional I will report, that when error message is shown, the insulin injection was not save in database or nightscout. After switching pump driver to an other and back, all working fine with saving the data.
Every restart of AAPS 3.1.0.2 reports the same error. Changing to virtual pump & then physical combo pump fixes till next restart. Not sure if it is impacting any other functionality. But error msg fills the screen and so graph1 on home screen is truncated on s9 plus mobile which has bigger screen compared to even more smaller mobile.
Not sure if you are referring to the full release but we have similar issues with NSClient v 3.1.0.3. we are two parents following our sons master through NSClient. We have dana-I pump. Both NSClient instances get this error. Switching to virtual pump and back (on master) does not resolve the issue. Switching to different pump/MDI and back on NSClient does not resolve it either.
@Pallesauka @muthijammy and others, switching back and fort between pumps will do nothing, this is an issue in the Java Code, it is a bug. @MilosKozak any info on this issue/bug?
For everyone interested, I found following workaround suggested in fb works for me as well when error msg popsup:
choose a virtual pump, subtype is AAPS generic Snooze popup error msg Kill AAPS Reopen AAPS. No error msg Switch to needed pump. Error msg no longer popsup after restart of AAPS or mobile
For everyone interested, I found following workaround suggested in fb works for me as well when error msg popsup:
choose a virtual pump, subtype is AAPS generic Snooze popup error msg Kill AAPS Reopen AAPS. No error msg Switch to needed pump. Error msg no longer popsup after restart of AAPS or mobile
its not about suppressing the error message, but about the error itself. Your solution doesn't work, it's not a permanent solution, the error comes on the AAPS screen and comes from AAPS