AndroidAPS
AndroidAPS copied to clipboard
nightscout
Communication failure in Omnipod Dash
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
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.
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
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?
Ok, what do you mean by official Bluetooth app? There should be just AAPS connecting to the pod.
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)
off the bluetooth until the AAPS direct protocol finds the pump with bluetooth off
If I understand your sentence right, AAPS can connect to Dash without bluetooth on?
The issue mentioned actually happend right now on a N6000. It reconnected, when I shut down the Diakemapp, but deaktivated bluetooth as well. Can there be a conncetion?
Ok, what do you mean by official Bluetooth app?
Actually, I meant the official DASH PDM (which is an app running on an Android PDM device): You cannot have both AAPS and the DASH PDM connected on the same DASH pod
AAPS can connect to Dash without bluetooth on?
Nope. What I think writer meant (or is seeing) that turning BT off and then on again solves his problem.
Blackview n6000
We have seen some phone brands or models having BT connection instability problems or even unable to find the DASH Pod at all. As more users are reporting problems for the N6000, most likely it not compatible with DASH.
N6000, most likely it not compatible with DASH.
I wouldn't say that at this point. I have two N6000 rigs running and they are working. Since I restarted the diakem G7 app, the issue is gone.
I meant as @gerison77 wrote that when I turn off the bluetooth it communicates in AAPS internal protocol and then it works fine Usually it also works with Bluetooth turned on, but sometimes problems suddenly start and it causes the Google Play Service application to crash, then the solution is to turn off Bluetooth
https://github.com/user-attachments/assets/c62e2dc1-aa27-4dbb-a247-d4d21bad9084
It doesn't help me, even if I turn off bluetooth for two hours it doesn't work.
I meant as @gerison77 wrote that when I turn off the bluetooth it communicates in AAPS internal protocol and then it works fine Usually it also works with Bluetooth turned on, but sometimes problems suddenly start and it causes the Google Play Service application to crash, then the solution is to turn off Bluetooth screen-20240804-112103.mp4
Hello! I as it was stated above, there is no internal protocol. There is only a Bluetooth connection. Without Bluetooth enabled, connection can't be established to POD.
It doesn't help me, even if I turn off bluetooth for two hours it doesn't work.
Can you please state if you are using G7.
It doesn't help me, even if I turn off bluetooth for two hours it doesn't work.
Can you please state if you are using G7.
Dexcom g6 + Omnipod Dash
It's a fact that when I turn off the bluetooth I manage to connect to the pod, I can upload more screen videos Another fact is that the pod does not appear in the list of Bluetooth devices, which means that the pod certainly connects via Bluetooth and requires Bluetooth authorization, but not through the built-in Bluetooth application in Android but directly from the loop, so even when Bluetooth is turned off it works Unlike Dexcom, as soon as I turn off the Bluetooth, it stops working
Having checked now this issue with two N6000 over the last two weeks. I can't confirm, that AAPS is able to establish a connection with bluetooth off. Actualisation just fails.
However, I made the observation, that connection can be re-established after a loss, by shutting down Diakem app.
There might be a conflict.
I believe there is nothing we can do on AAPS side. Change your phone if the connection is not reliable
