-
Notifications
You must be signed in to change notification settings - Fork 10
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
No connection with ESPHome 2024.2.0 #11
Comments
Fyi, going back to legacy 2023.12.9 and it immediately connects again to the lock. |
Yup looks like it. Will have to modify my code. Will update this issue once I found the time. |
Unfortunately, this is still the case with ESPHome 2024.2.1. I think, if, a fix in the underlying keyble code is the only thing that could help? |
Well, it was closed - unsure, why, as esphome seems to he breaking it. Kindly asked for reconsidering. |
As the esphome maintainer mentioned it has to be resolved on my side. It is unfortunate that they introduced a breaking change but this can happen and I will update my code when I find the time. Until then you could still specify a different esphome version for the ble client component. See here for more details: |
Thank you for the hint. Like this?
|
Have not tried it but looks good |
Workaround :) I checked the compiler run for the used dependencies and also realized that we are using the esp32_ble components. This is a workaround, again thanks to digaus for making all of this possible :)
|
I just stumbled upon this issue as well after updating my ESP devices to the latest esphome version. @digaus can you check whether this has some unwanted side-effects or is needed in other parts of the code as well?
|
While this might work I think it is better to change my plugin to use the new connect / disconnect / write functions directly from the ble_client implementation. This should reduce my code and hopefully also work better. I will see if I can do it this week. Maybe I will modify it to be able to connect to two devices like in the ble_client example. |
Thanks @paul-leitner this solution works for me aswell! |
Hi everyone. First of all, big thanks to @digaus for the hard work, and taking time to share it. I've been wanting to take on previous work from Marius, tc-maxx and lumokitho but never found the time. I started testing on a NodeMCU and since it all went well i went on and purchased a Sonoff NSPanel, which i'm planing on deploying the solution. Things went great on the NodeMCU (previous version of esphome) and when i got the NSPanel i got pretty frustrated because it wasn't working. My first thought was it had something to do with the new hardware and didn't cross my mind it could be a breaking change from esphome. Fast forward, i was pleased to find this issue and had some success with @paul-leitner solution. It wasn't always fluid and connection got dropped once in a while. Also, the proposed change is a breaking change for earlier esphome versions. A workaround which has been working pretty nice to me, keeping original repo, i suggest
|
Does not work for me, the only way it works is reverting back to the 2023 revision using the addon. If I do like you propsed the lock is not fully connecting:
|
Weird ...
My full yaml is
Wonder if that's hw related... I'll try this later on my old NodeMCU. |
NodeMCU
and respective yaml
I did get a bit of trouble getting it going but after a factory reset on the lock things started working properly. |
Please use this workaround until I find time to update: |
Updated and should work again with latest esphome version. |
Thanks a lot, dear digaus. Tested it by removing the workaround and can confirm that it is working as intended with ESPHome 2024.4.1. Thank you very much! |
For me it is not working instantly, but also last time I had to flash the ESP32 again using USB (and remove pairing, redo everything, have to try that later...):
|
Hello, it works for me but now in HA I have to update to version 2024.4.1 and it won't let me and I get this when trying to look. Compiling .pioenvs/esphome-eqiva-lock/src/main.o Any solution for this? thank you |
Have you removed the workaround from post #11? |
Hi.
Make sure that you're no longer using the workaround, and that you clean
your build files before building again.
…On Mon, Apr 29, 2024, 21:09 sobrarbe ***@***.***> wrote:
Hello, it works for me but now in HA I have to update to version 2024.4.1
and it won't let me and I get this when trying to look.
Compiling .pioenvs/esphome-eqiva-lock/src/main.o
src/main.cpp: In function 'void setup()':
src/main.cpp:636:12: error: 'class esphome::eqiva_key_ble::EqivaKeyBle'
has no member named 'set_auto_connect'; did you mean 'set_turn_left'?
key_ble->set_auto_connect(true);
^~~~~~~~~~~~~~~~
set_turn_left
Compiling .pioenvs/esphome-eqiva-lock/bt/host/bluedroid/stack/btm/btm_sec.o
Compiling
.pioenvs/esphome-eqiva-lock/bt/host/bluedroid/stack/btu/btu_hcif.o
Compiling
.pioenvs/esphome-eqiva-lock/bt/host/bluedroid/stack/btu/btu_init.o
Compiling
.pioenvs/esphome-eqiva-lock/bt/host/bluedroid/stack/btu/btu_task.o
*** [.pioenvs/esphome-eqiva-lock/src/main.o] Error 1
========================== [FAILED] Took 6.69 seconds ====================
========
Any solution for this? thank you
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFPFVJ3UV4RQQWESTSWJXTY72SHRAVCNFSM6AAAAABDTF7RJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBTGU3TEMZVGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Working like a charm on my NSPanel. Cheers! |
It works, but only for some days, then I get the same issues again as before (cannot connect to the lock). Requires to wipe the ESP. Never had this issue with the "old" implementation before: `
|
Are you staying connected to the lock? Or are you always connecting/disconnecting ? Found a related issue: espressif/esp-idf#2810 Maybe the reception is not good enough to connect with 100% reliability? What is the RSSI value ? |
Usually I stay connected all the time and it works, but after some time (days/weeks) it seems it is no longer able to connect at all. I am behind a wall with the ESP32, but only about <1.5m away from the lock. I will check if it improves if I put it directly next to the lock, thanks! |
Hello,
I have update to ESPHome 2024.2.0 today, and after this the ESP32 is no longer connecting to the lock.
Also a new pairing is not successful (nothing happens).
Any ideas?
Maybe due to this change?
esphome/esphome#5277
This is all one can see basically:
![Screenshot 2024-02-21 15 44 57](https://private-user-images.githubusercontent.com/82153569/306663880-0ef7f598-30d5-48f6-9b76-27bac3905cea.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMwOTY5NjgsIm5iZiI6MTcyMzA5NjY2OCwicGF0aCI6Ii84MjE1MzU2OS8zMDY2NjM4ODAtMGVmN2Y1OTgtMzBkNS00OGY2LTliNzYtMjdiYWMzOTA1Y2VhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODA4VDA1NTc0OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI4YzZmMzE5Zjg2MWE3ZTc0ZTUzNDVlYmQ4ZGI3MGFlYTcwYmRmYjMzMTE4OWMzOTMwMDNmNzJkM2YwMGE1MTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.P-UiGMocTbXlIPd7RA0jBvecmOPi42GO1nTyQdr3lK4)
The text was updated successfully, but these errors were encountered: