-
Notifications
You must be signed in to change notification settings - Fork 2
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
I dont know if there are multiple variant of the keyboard i get this error when trying to get the status #1
Comments
Hi. Do you always get that error? Do any of the other commands work? You may try to comment this line (gets profile name) and see if |
Hi, I have a similar issue to OP, though with a different code:
Commenting out line 120 in cli.py fixes that, but produces another unexpected value:
Trying to create a profile doesn't work either:
These seem to be consistent so far (errors pop up every time, with the same read codes). What is inconsistent (and is probably a separate issue, but mentioning it here just in case) is mapping (without creating a profile due to the issue above):
|
Hey @electronicgore. I've seen the protocol "misbehave" (or not act as I expect from reversing) sometimes. From what I remember turning of the keyboard helped reset things. Can you try the following steps please?
Do you know which firmware version the keyboard is using? |
Thanks for the response @goncalor! The results of my experiments so far are... weirdly inconsistent:
Here is a console log from one of my early attempts at following the procedure you suggested:
This output is largely consistent whenever I try to do all steps in one go. One exception is the Here is another attempt, this time with some resets along the way:
Apologies for the long and vague response, I understand it is not very helpful, I'm just really struggling to find any consistency and reproducibility in the keyboard's behavior. :/ |
I just updated my keyboard to the latest firmware version 1.77 and started getting this error.
If I change For example, when I try to map a button it shows the following error:
In spite of that, looks like it successfully remapped the button. Also, in the changelog it said that they implemented f13-f24 button mapping, but it seems that they used keycodes that are different from usb hid specification. |
Hi @qweryty. Thank you for the comment. That's interesting. And a pain, if they are changing the protocol... I understand you were using |
Sorry for late reply, I don't check github often. I don't really remember the firmware version. At that moment, I just got the keyboard so haven't used I figured that I could just quickly patch the program, but started having some problems(sorry, no logs), so I thought that a good course of action would be to just update the firmware(especially after reading change logs), but quickly found out that they are changing the protocol. |
|
❯ ./8bdkbd status
8BitDo connected: yes
Traceback (most recent call last):
File "/home/pierre/.local/bin/./8bdkbd", line 8, in
sys.exit(main())
^^^^^^
File "/home/pierre/.local/lib/python3.12/site-packages/eightbdkbd/cli.py", line 71, in main
args.func(args)
File "/home/pierre/.local/lib/python3.12/site-packages/eightbdkbd/cli.py", line 120, in cmd_status
print(" Profile name:", kbd.get_profile_name())
^^^^^^^^^^^^^^^^^^^^^^
File "/home/pierre/.local/lib/python3.12/site-packages/eightbdkbd/client.py", line 55, in get_profile_name
raise ValueError(
ValueError: Read unexpected value
Expected: 54800000 or
54801000
Read: 54800c000070006900650072007200650000000000000000000000000000000000
The text was updated successfully, but these errors were encountered: