-
Notifications
You must be signed in to change notification settings - Fork 20
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
Changing the bluetooth connection section #370
Comments
Sadly, this instability is so severe it's prevented me from using the Bluetooth capabilities for over 6 months. So many thanks @EugeneRymarev Eugene for raising the issue. 🙏 Even with a simple constellation, iPad and iPhone, switching device very rarely succeeds. So in practice I just use the display function rekeying the password into my iOS device. As you can imagine, particularly as many sites hide the password as it's typed in, this is very awkward. Steps to reproduce.
===> Sometimes the BLE does connect with the iPhone, Sometimes the iPhone displays the failed message but then the status does change to connected (timing issue?), but mostly connection simply fails and you have to keep retrying. Often during a connection attempt the sleep message on the BLE displays and you have to move the wheels to keep it awake, which may interfere with the handshaking (guessing here). Initially I tried the workaround of deleting all pairings every time I wanted to reconnect with a different device but this is also very cumbersome as you have to use the scroll wheels to enter a 6 digit code every time. It might help if the BLE displayed the name of the connected bluetooth device. But ultimately this device-switching has to improve to make bluetooth viable on the BLE. |
@alanrick, Thank you for your comment! This is a really big problem if you have more than one bluetooth connected device. I really look forward to and hope that the bluetooth section will be completely redesigned. |
It just dawned on me how inappropriate it is having a feature request rather than a bug for the inability of a device with Bluetooth in its name to connect to different devices reliably. All my other Bluetooth devices from headphones, car, locks... to key-finders can. Yes, I do take blame for not reporting it earlier. |
From some testing, while not perfect, there should be no reason to delete pairings as a workaround. I agree that some kind of in-device way to specify what to pair to would be ideal, but I'm not intimately familiar enough with Bluetooth LE to know how feasible this is. AFAICT the miniBLE will connect with the most recently connected device if its available and automatically connectable. I use it between an iPhone and a Linux laptop. The miniBLE generally prefers the iPhone. But if you go in to the Bluetooth menu on the miniBLE, you can select FWIW I've never come across any Bluetooth / LE device that can correctly/easily/functionally connect to a given partner from a list of paired/connectable devices. Mostly commonly I do it with a couple of BT audio devices and it takes minutes if not 10+ minutes to correctly get the device to re-connect to the partner of my choosing. Often I have to delete pairings from every device it could connect to and re-pair with what I want. Bluetooth is a lawless wasteland and the miniBLE is no exception. |
@kbembedded, an example of device. This is a mouse with a physical button to switch from one device to another. I would like the same thing to be implemented in MiniBLE only at the software level. This would be much more convenient than hoping that MiniBLE will connect to the device I need. I also found another problem. I connected my MiniBLE for charging to the laptop with which I use it via Bluetooth. After MiniBLE was charged, I disconnected it from USB and tried to use MiniBLE for its intended purpose. Unfortunately, I did not succeed until I completely removed the pairing in Windows 11 and on MiniBLE, and then reconnected them. Issues like this with Bluetooth are very disruptive to the user experience and put off using the device. |
@kbembedded I suspect I missed off one step in my description but I won’t be able to verify this for a few days. But I’m pretty sure I performed step in other words I’d expect the BLE to have no active connections because Bluetooth on all remote devices is off, but it should retain an internal bookkeeping list including both the iPad and iPhone pairing keys. So step 7 should allow the BLE to check this list, discover the iPhone pairing key, and pair with the iPhone, because no other Bluetooth devices are active. This is how my other Bluetooth devices behave. But unfortunately the BLE doesn’t pair. The workaround is to use a USB cable for a PC, or to delete all pairings and re-pair, which is awkward as you have to enter a 6 figure code on the BLE - an unnecessary and cumbersome activity with my fat fingers. I’ll check next week that I really did perform step 6.5. |
A suggestion from a customer: Ideally. P0: I want to see a list of paired devices. Name and ID some kind of friendly name and the mac address. Most basic level , re-connect to the last paired / active device, and NEVER CONNECT to a different device without notification or asking me even if it was previously paired. To start |
@limpkin, I agree completely that you can not automatically switch between devices. This does not need 100% since it is not safe.
This is a minimum implementation that is now very needed. |
I strongly disagree. I can imagine two scenarios.
My scenario is most definitely the latter, Home (also on the move). I want to connect to my iPhone or my iPad or PC. For this reason, I most definitely prefer auto-connection, because I can simply temporarily switch off the bluetooth on devices within range that I do NOT want to connect to, leaving one device (e.g. iPhone). This way I control which device I want to connect to without having to make a selection on my BLE. It's a question of usability. The iOS/PC is easier to control because of screen-estate, mouse... etc. If this is not the case, and a list is available to select from, then three fields are needed:
This is what's usually offered for wifi connections in iOS, Android and Windows, so it's been proved in practice. |
I could not reproduce this problem today. The only problem I had was that step 5 would not work unless I insert step 4.5 [BLE] Switch off Bluetooth and then switch on again. |
Reminder to myself... In the meantime I can toggle between BLE on my iPhone and iPad without problems. Fingers crossed it stays that way. |
I agree Bluetooth needs to be able to display the "name" or ID of the currently paired device and I should be able to switch to another device from the list of paired devices. I have had MANY occasions where I disconnect the Bluetooth device only to have it reconnect before I can connect to the device I want. Turning off Bluetooth on all devices except the one I want to connect to isn't a workable solution as this may mean disconnecting other devices as well. Just being able to name the connected devices and SEE what I have in my list is a great start. Being able to select a device to connect to would be high on the list of features. Perhaps asking which Bluetooth device to connect to after entering the PIN when the card was inserted would be a good compromise with auto connect from a security point. I've experienced my credentials appearing on another device because I didn't realize it connected to a different device than the one I was on. |
Missing feature
Justification
The bluetooth connection section in the form in which it currently exists and, in general, the MiniBLE connection to managed devices itself is unstable.
What do I mean by instability? I have two devices paired with MiniBLE - a laptop and a phone. Periodically, usually in the morning when MiniBLE is turned on for the first time, the device connects to the phone, although it was previously connected to a laptop, but, apparently due to a loss of connection due to rebooting or turning the laptop off and on, the device switches to the next one it has ever been paired with and work with him.
Workarounds
The current implementation, unfortunately, leaves much to be desired.
The text was updated successfully, but these errors were encountered: