Dygmalab / Bazecor

Graphical configurator for Dygma Products
https://dygma.com/
GNU General Public License v3.0
405 stars 90 forks source link

Bluetooth switch is ignored #909

Open benstor214 opened 1 month ago

benstor214 commented 1 month ago

Describe the bug What purpose does the switch on the underside of the keyboard serve when I have to fight the keyboard not to try establishing a bluetooth connection when it is switched to the OFF position? This happens regardless if the keyboard has been paired to any device or not, which makes the current behaviour particular silly when not paired to any device.

When this symbol 🛜 is next to this colour 🟥, it means to me that the wireless functionality is turned off. Am I wrong?

The fact that the wireless functionality is switched off by a hardware switch combined with the fact that the keyboard is plugged in to the PC by the USB cable* (via the neuron) should prevent the keyboard from trying to connect over bluetooth. This is made worse by the fact that I am not exaggerating when I write that I need to FIGHT the Dygma Defy to stop this silly, counterintuitive, illogical behaviour. This translates to me needing to hit the yellow glowing key several dozen times, EVERY time.

*notice wire =/= wireless

To Reproduce Steps to reproduce the behavior:

  1. Switch off wireless functionality
  2. Plug in the Dygma Defy by CABLE/WIRE to a USB socket on your PC
  3. Start your PC
  4. Despair and slowly start to hate the product you spend way too much money on. >:-(

Expected behavior When bluetooth switch off and wired to USB, bluetooth is ACTUALLY off!!!! Switch off, function off <-- seems logical to me

Desktop (please complete the following information):

MiquelDygma commented 1 month ago

Hi, Benstor

The ability to use Bluetooth when the keyboard is connected wired is a feature gone bad. It's useful when you want to connect to a Bluetooth device while keeping your keyboard connected to your main PC. You can access that feature by pressing the BT pairing button on your keyboard.

However, it's not perfect. On some computers, when the keyboard receives power but not signal, it switches to BT mode. Once you're logged into your computer, the top left key should switch you back to wired. If that doesn't work, you can unplug and replug the cables that go from the keyboard to the neuron.

Of course, this is far from ideal, so we're working on it. The new 2.0 firmware of the Defy that's in the works already fixes the accidental BT trigger, but it also eliminates the feature. We're working on having the feature without the bug.

The wireless switch at the bottom actually shuts the battery from powering the keyboard, which in 99% of scenarios means no wireless—except in the one you experienced. Since the neuron has the BT transmitter, and you're powering the keyboard with the computer, you can use BT.

As I said, we're on it.

benstor214 commented 1 month ago

Hello Miquel! Thank you for replying in such a quick and detailed way. After a quick read of your answer I feel like there should be a switch on the neuron for the Bluetooth function... maybe something like a pairing button: Long press = pair with new device, short press = try to connect. But then again, at the moment you can pair multiple devices and switch between them with the number keys. I'm just thinking out loud here... It just feels wrong. It feels like Bluetooth gets the right of way before the wired connection when it should be the other way around: the wired connection should take priority to Bluetooth. Auto-pairing is nice for headphones etc., but in the special use case of the Dygma Defy I feel like the Bluetooth connection should be initiated by the user. Because at the moment it feels like the keyboard is just not respecting me and only does what it wants. Being overruled by your own keyboard - it's a very frustrating user experience.

MiquelDygma commented 1 month ago

I completely agree.

The solution we're working on aligns with what you're mentioning. When the keyboard is wired, Bluetooth should only be triggered if the user purposely activates it by pressing a specific key.

That way, we could have the feature but not the frustrating bug.