TDE
/
tdebluez
3
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
Labels Milestones
New Issue

Devices with same factory name can not be added #24

Closed
opened 11 months ago by deloptes · 1 comments
deloptes commented 11 months ago
Collaborator

Basic information

  • TDE version: 14.1
  • Distribution: Debian Bullseye
  • Hardware: amd64

Description

I bought one device called Palovue Linkflow. It was so good that I bought a second one. When I tried to pair with it, I got an error message from tdebluez, that the name already exists.
This seems to be, because we use the Name and not the Alias, but the factory default is that both are equal. So we have to change the code in such a way, that:

  1. in tdebluez we use the Alias and
  2. if there is already a device with such a name (Alias), it would rename the newly added device to something like #2

Steps to reproduce

  1. have two devices of same brand/model - they should have the same factory default name
  2. pair one of them - device should appear in the list with its default name
  3. pair the second device - this results is an error that device is already in the list

Screenshots

## Basic information - TDE version: 14.1 - Distribution: Debian Bullseye - Hardware: amd64 ## Description I bought one device called Palovue Linkflow. It was so good that I bought a second one. When I tried to pair with it, I got an error message from tdebluez, that the name already exists. This seems to be, because we use the Name and not the Alias, but the factory default is that both are equal. So we have to change the code in such a way, that: 1. in tdebluez we use the Alias and 2. if there is already a device with such a name (Alias), it would rename the newly added device to something like <Alias>#2 ## Steps to reproduce 1. have two devices of same brand/model - they should have the same factory default name 2. pair one of them - device should appear in the list with its default name 3. pair the second device - this results is an error that device is already in the list ## Screenshots <!-- If it seems useful, please provide provide one or more screenshots. -->
MicheleC added this to the R14.1.1 release milestone 11 months ago
MicheleC commented 11 months ago
Owner

Fixed by PR #26 via PR #23

Fixed by PR #26 via PR #23
MicheleC closed this issue 11 months ago
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
r14.1.x
master
Labels
Apply labels
Clear labels
GE/need-info
General - need additional info from contributor PR/keep-branch
Pull request - do not delete branch after merging PR/not-ok
Pull request - need fixing PR/rfc
Pull request - request for comments PR/update-trans
Pull request - update to translation files needed PR/wip
Pull request - work in progress RS/R14.0.x
Related to R14.0.x series RS/R14.1.x
Related to R14.1.x series SL/critical
Severity level - critical SL/major
Severity level - major SL/minor
Severity level - minor SL/normal
Severity level - normal SL/regression
Severity level - regression from previous version SL/trivial
Severity level - trivial SL/wishlist
Severity level - wishlist request ST/duplicate
Status - duplicate of another issue ST/invalid
Status - invalid report ST/notourproblem
Status - not our problem ST/rejected
Status - rejected ST/wontfix
Status - won't fix ST/worksforme
Status - works for me, unable to reproduce
No Label GE/need-info PR/keep-branch PR/not-ok PR/rfc PR/update-trans PR/wip RS/R14.0.x RS/R14.1.x SL/critical SL/major SL/minor SL/normal SL/regression SL/trivial SL/wishlist ST/duplicate ST/invalid ST/notourproblem ST/rejected ST/wontfix ST/worksforme
Milestone
Set milestone
Clear milestone
No items
No Milestone
R14.1.1 release
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: TDE/tdebluez#24
Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(<nil>)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes