-
Notifications
You must be signed in to change notification settings - Fork 153
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
Bluetooth udev script regex breaking logic #147
Comments
Hm, yes that check is a bit odd. None of my phones or computers that connected have a @elderlabs a device connection sound? I never heard one, and didn't see anything in the scripts, what did I miss... |
I also doubt my udev triggers the script. I got:
I would expect to hear a sound, but I do not:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This refers to
/usr/local/bin/bluetooth-udev
.With the regex device name check
if [[ ! $NAME =~ ^\"([0-9A-F]{2}[:-]){5}([0-9A-F]{2})\"$ ]]; then exit 0; fi
enabled, devices that connect to Debian 11 do not match a mac address naming scheme -- or at the very least, a Windows device doesn't. The device connects with its hostname.This breaks the logic flow the script intends as it doesn't disable discovery upon connection, doesn't disable wifi for those that have issues with it (wifi doesn't cause an issue on my end), and doesn't play a device connection sound upon add/remove.
My solution for this was to comment out the name check, which allowed the script to run as intended. Given we're filtering for input devices. I suppose that'd possibly catch other input devices, like a keyboard/mouse, but as this is an audio sink, other devices will likely never be connected to it.
The text was updated successfully, but these errors were encountered: