-
Notifications
You must be signed in to change notification settings - Fork 20
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
WiFi and BLE at the same time possible with use of NimBLE #21
Comments
Hi @KlausMu, Greetings Marco |
What do you mean with "does it also work with ESPHome"? This project does not work directly with ESPHome. I saw that there are some ESPHome projects using the (more or less) same eQ3 library as the one from this repository: |
@smarthomebude |
Thank you! |
Hi @KlausMu! Could you please share your NimBLE version of the eQ3 lib? This would be awesome, it is exactly what I need for my project. I'm using my very own smarthome ecosystem, written from scratch and started way before HA was a thing. |
@wladimir-computin
to And this is the pull request: |
@KlausMu Thanks a lot! I built upon your work and made some additional changes to the lib. Since we don't need to switch between BT and WiFi, a lot of the complexity could be removed. Even the Semaphores are no longer necessary, at least according to my testing. Since I modded the library to my needs, it is no longer directly compatible with this project. Anyway, it might still be useful for someone. I also fixed the user registration / pairing, so no more node.js stuff is needed to get it up and running. |
Hi, is this repo still maintained?
I've been using the eQ3 lib for some years. It always was annoying that you have to disconnect WiFi before using BLE and vice versa. Establishing the connection always takes some time, both for WiFi and BLE. The keyBLE connection always took about 10-15 sec, sometimes even more.
Recently I integrated the use of NimBLE into the eQ3 lib. With that, WiFi and BLE both can stay connected all the time. Works now for some months without any problems.
Since the timeout for the BLE connection is 4 minutes, I do an
keyble->updateInfo();
each 3 min 50 sec. With that, the keyBLE stays super responsive all the time. You cannot recognize any delay.Interested in a pull request?
The text was updated successfully, but these errors were encountered: