Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Communication failure in Omnipod Dash #3375

Open
mordechi-david opened this issue Jul 3, 2024 · 5 comments
Open

Communication failure in Omnipod Dash #3375

mordechi-david opened this issue Jul 3, 2024 · 5 comments

Comments

@mordechi-david
Copy link

All users of the Blackview n6000 device report an error every few hours that AAPS does not find the pod the official bluetooth app crashes until the device crashes and restarts, the only solution I have found so far is to turn off the bluetooth until the AAPS direct protocol finds the pump with bluetooth off and then I Turns it back on so that the Dexcom will continue to work
I looked for logs and I don't have any, I don't know why the device doesn't create logs
I'm on version 3.3.0 dev b but most users are on version 3.2.0.4 and they too have the exact same phenomenon
I will be very, very happy if someone finds a solution because we don't want to change a device, it finds the pod in one second and its battery is very strong
In short, we are very pleased with the device for AAPS
Thank you
I will try to find logs and upload

@Philoul
Copy link
Contributor

Philoul commented Jul 5, 2024

For log files, you can send them by mail from AAPS > Maintenance > Send log file by mail
-> you can send them to you an then copy them here.
You can also see them from computer (smartphone connected by USB)
Go to Android/data/info.nightscout.aaps/... (not sure of exact folder name).

Log files can be hidden from phone on some Android versions.

@gerison77
Copy link

gerison77 commented Jul 6, 2024

Hi, I have 2 N6000 rigs running with dash. Can't confirm the reported behaviour. Just lost one pod instantly after activation. Once I had to restart phone to regain connection but since this was a onetimer I blame the pod, not the rig. Running on 3.2.0.4

@vanelsberg
Copy link
Contributor

Afaik you can not run AAPS and DASH app concurrently (when the DASH app connects to the Pod it is blocking access for AAPS.
Uninstall the DASH app and try again?

@gerison77
Copy link

Ok, what do you mean by official Bluetooth app? There should be just AAPS connecting to the pod.

@mk1950
Copy link

mk1950 commented Jul 9, 2024

Hi, I'm also with N6000 and have a lot of problems,
I have already tried many versions of Rom Stock: v06/v07/v08
All of them sometimes have problems with AAPS.
DEXCOM G6 BYODA WORKS FINE ON THIS DEVICE, ONLY AAPS DOES PROBLEMS.
Sometimes there is an error not having a pump available,
And when this happens, you see for a split second a message on the device: the Bluetooth app has stopped, this message lasts for a very short time and then disappears, as if the Bluetooth crashed for a second.
I can go to sleep at night and then see that for several hours there was no communication with the pod.
Sometimes it can be two days that it works well, and then if I turn off - and restart Bluetooth by mistake, or I turn the device back on, it happens again that there is no communication with the pod.
I got the impression that there was some problem in the way that: AAPS gets along with the bluetooth on this device.
(I apologize if I'm not so clear, English is not my native language)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants