-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[3.3.1.2] Issue with Bluetooth Devices List "TWI Board" #3746
Comments
AAPS will unbind the pod on de-activation. |
I never got a promt for connection with "TWI Board" before Update to 3.3.1.2 Since the second pod i also have 2 identically bluetooth devices in the list. |
I think that is because DASH does not present a unique name for the device. That was not needed as it was not designed to be visible in the list of BT devices. When bonding your phone "remembers" the specific DASH device dat was connected. Similar to the Dexcom transmitters after change. Phone will probably cleanup after some time. I'd say you can safely ignore. |
Did you have connection issues with Dash on android 15 before upgrading to 3.3.1.2? |
Not before aupdate. But now there are serveral Issues |
after Updating i did a pod change. now there are 2 "TWI Board" in my Bluetooth device list.
Looks like the Old Pod and The New Pod are listed but Name is identically.
How is the right workflow on a podchange?
otherwise i have a lot of twi Board devices in my list.
Maybe tgqt causew Problems like when having a lot of Dexcom Devices in the List?
Thanks for your Support
The text was updated successfully, but these errors were encountered: