-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Vial not working with BLE #182
Comments
It's a known issue. vial over BLE does work, but very unstable. It seems that it's affected by the network environment, signal strength, etc. I would recommend to use USB when updating keymap for now |
That makes sense! I hope you don’t mind me making all these issues! I am REALLY enjoying working with rmk, and I am so satisfied with making my own keyboard. |
Not at all! I'm happy to hear feedback from users, whether it’s positive or negative :D |
I managed to get this branch/PR of vial working (with quite a bit of trouble), and it works well with bluetooth :) |
Interesting, I don't see anything changed that would fix the BLE connection failure. Any ideas? |
No. I was thinking initially that updating vial from Python 3.6 to anything else was bound to bring a lot of under-the-hood improvements, but there wasn't really anything standing out massively. But I haven't tested a lot. |
I've just got my BLE keyboard working with rmk 0.4.4 (hooray!), but when I try to use vial to adjust the keymap, I get this error:
It still works with USB, so it isn't a problem for me, but it might be nice to add to the docs if this is intentional / only USB is supported for vial realtime updates.
The text was updated successfully, but these errors were encountered: