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

Is keyboard-state compatible with ZMK powered keyboards? #3796

Open
Kylar514 opened this issue Nov 28, 2024 · 0 comments
Open

Is keyboard-state compatible with ZMK powered keyboards? #3796

Kylar514 opened this issue Nov 28, 2024 · 0 comments
Labels
bug Something isn't working inhibitor keyboard

Comments

@Kylar514
Copy link

Kylar514 commented Nov 28, 2024

I am running the latest waybar. I have the following in my config.

"keyboard-state": {
  "device-path": "/dev/input/event8",
	//"numlock": true,
	"capslock": true,
	"format": {
		"numlock": "N {icon}",
		"capslock": "󰪛 {icon}",
	},
  "format-icons": {
      "locked": "",
      "unlocked": ""
    },
  },

Event8 is active, and i can run a evtest and see when capslock is pressed. Its just waybar says it can't find a device at event8. I can change this to event3, and it detects and reads my MX Masters 3 mouse, I can also plug in any other keyboard and it properly reads the caps lock in the waybar.

I think its a compatibility issue? idk.

I did add my user to the group. So it shouldnt be a permissions issue, especially since waybar can accurately detect other devices.

event8 is the zmk keyboard on this boot, it changes everyboot, that device-path line was just added for debugging purposes.

@github-actions github-actions bot added bug Something isn't working inhibitor keyboard labels Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working inhibitor keyboard
Projects
None yet
Development

No branches or pull requests

1 participant