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

[3.3.1.2] Issue with Bluetooth Devices List "TWI Board" #3746

Closed
m4nnihuber opened this issue Jan 15, 2025 · 7 comments
Closed

[3.3.1.2] Issue with Bluetooth Devices List "TWI Board" #3746

m4nnihuber opened this issue Jan 15, 2025 · 7 comments

Comments

@m4nnihuber
Copy link

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?

  • deactivate pod
  • delete TWI Board from Bluetooth Devices
  • start new pod?

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

@vanelsberg
Copy link
Contributor

AAPS will unbind the pod on de-activation.
I suspect the old "TWI Board" is a manually bounded Pod from before upgrading AAPS?
You should be able to remove using unpair/forget device.

@m4nnihuber
Copy link
Author

I never got a promt for connection with "TWI Board" before Update to 3.3.1.2
after update the promt came up and i connected.
Same happened after changing pod.

Since the second pod i also have 2 identically bluetooth devices in the list.
buth both have different bluetooth adresses

@m4nnihuber m4nnihuber closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2025
@m4nnihuber m4nnihuber reopened this Jan 16, 2025
@vanelsberg
Copy link
Contributor

vanelsberg commented Jan 16, 2025

Since the second pod i also have 2 identically bluetooth devices in the list. buth both have different bluetooth adresses

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.

@olorinmaia
Copy link
Contributor

Did you have connection issues with Dash on android 15 before upgrading to 3.3.1.2?

@m4nnihuber
Copy link
Author

Not before aupdate. But now there are serveral Issues
Mostly Notification TBR could not be set or unknown Error 01

@vanelsberg
Copy link
Contributor

@MilosKozak
Copy link
Contributor

8abfbd5

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

4 participants