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

Must reconnect keyboard on start up #978

Open
weagle08 opened this issue Jan 3, 2025 · 7 comments
Open

Must reconnect keyboard on start up #978

weagle08 opened this issue Jan 3, 2025 · 7 comments
Labels
bug Something isn't working

Comments

@weagle08
Copy link

weagle08 commented Jan 3, 2025

Describe the bug
Every time I power cycle my computer, I have to reconnect the Raise 2 keyboard.

To Reproduce
Steps to reproduce the behavior:

  1. Have Dygma Raise 2 plugged in to Ubuntu 24.04 machine
  2. Boot computer
  3. Observe keyboard is unresponsive until it is disconnected and reconnected

Expected behavior
Keyboard should be responsive on boot without reconnect

Desktop (please complete the following information):

  • OS: Ubuntu 24.04
  • Raise 2 FW: v1.1.1
  • Bazecor Version: 1.6.1

Additional context
Not sure this is the appropriate bug board for this report, but unsure of where the board for the Raise 2 is located.

@weagle08 weagle08 added the bug Something isn't working label Jan 3, 2025
@MiquelDygma
Copy link

Could you describe what the keyboard does when it's unresponsive?

Is it:

  • Flashing red
  • Flashing blue
  • With the LEDs on but it does not type

Thank you

@weagle08
Copy link
Author

weagle08 commented Jan 6, 2025

On initial power, top row of keys is purple and far top left key on each half is yellow. After post, and when login screen is up the keyboard stays in this state. I cannot use the keyboard until I unplug the USB-C and replug it. It does flash red momentarily, but then just goes back to this purple top row.

@MiquelDygma
Copy link

Thank you! That's a current bug we have on the firmware on cold boot for some computers. That's the BT pairing mode that's triggered accidentally when the keyboard has power but not connection to the computer yet.

While we fix it, there are two workarounds:

  • Press the yellow key once the computer is on the login screen
  • Unplug the cables from both sides of the keyboard and plug them again

Let me know if that works. We'll continue working to fix it.

@weagle08
Copy link
Author

weagle08 commented Jan 7, 2025

I can confirm that for me pressing the yellow key at the login screen does put the keyboard into a usable state! Thanks! Will leave this open until firmware update unless there is another bug to link to? Why would my wired keyboard go into a BT pairing mode?

@MiquelDygma
Copy link

I'm glad to hear it worked.

The thing is that the wired Raise 2 uses the wireless neuron, which has BT capabilities. We did this because we want to add a feature where you can use BT with your keyboard wired, even if you got the wired only keyboard.

The problem is that it's triggering on boot for some users. We're on it.

@johnbherring
Copy link

I also see this on a Win11 PC. Usually, I have to disconnect the keyboard (PowerCycle). I am using a wired version of the Dygma Raise 2 V 1.6.1. Upon initial wake, it "blinks" the expected bottom glow but goes into the search (chasing blue glow). Occasionally this will resolve itself in about 15 - 20 seconds

@MiquelDygma
Copy link

Hi @johnbherring

As I mentioned above: that's a current bug we have on the firmware on cold boot for some computers. That's the BT pairing mode that's triggered accidentally when the keyboard has power but not connection to the computer yet.

While we fix it, there are two workarounds:

  1. Press the yellow key once the computer is on the login screen
  2. Unplug the cables from both sides of the keyboard and plug them again

Let me know if that works. We'll continue working to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants