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

Two questions #15

Open
tergontor opened this issue Apr 24, 2024 · 3 comments
Open

Two questions #15

tergontor opened this issue Apr 24, 2024 · 3 comments

Comments

@tergontor
Copy link

First of all, thank you very much for sharing your knowledge that helps the rest of us to be able to install these devices at home. I installed the Eqiva lock yesterday and it works quite well. I followed the steps in the video https://youtu.be/Ev7GehI4arM?si=q-5MG-ZeTJwoDtOR which explains it quite well, but there are two topics in which I have doubts:
1.It seems that the Eqiva and Esphome app are incompatible, or one or the other works but not both simultaneously. It's not that I care much because the one I really want to work well is with Esphome. The problem is that it randomly disconnects from esphome and then the app works. So that this does not happen and it is always connected to esphome, I have set the continuous parameter to true in the esp32_ble_tracker component at the risk of consuming more battery. I suppose the other option is to delete the app but I would like to have it as a backup just in case. Is that so or am I wrong?
2.The example code is based on Wi-Fi, in my case I installed it on an ESP32 WT32-ETH01 board so I modified the example code somewhat by removing the Wi-Fi component and adding the Ethernet. Do you know if we need to add something else that is not in the example code?

Again congratulations for your great work.
Greetings and thanks.

@KlausHans
Copy link

KlausHans commented Apr 26, 2024

I just added the lock with a WT32-ETH01. Here is my yaml: https://github.com/KlausHans/Esphome-Yamls/blob/main/eqiva-lock.yaml
I did:

  • continuous: false removed from esp32_ble_tracker
  • removed the wifi definitions
  • added ethernet definition for the WT32-ETH01
  • after initial pairing added mac_address, user_id and user_key to eqiva_key_ble

Works very well so far. I don't use the app though.

@tergontor
Copy link
Author

I just added the lock with a WT32-ETH01. Here is my yaml: https://github.com/KlausHans/Esphome-Yamls/blob/main/eqiva-lock.yaml I did:

  • continuous: false removed from esp32_ble_tracker
  • removed the wifi definitions
  • added ethernet definition for the WT32-ETH01
  • after initial pairing added mac_address, user_id and user_key to eqiva_key_ble

Works very well so far. I don't use the app though.

Thank you very much for your answer. Looking at your yaml it is almost the same as mine.
In esp32_ble_tracker: I have the continuous parameter set to true although I could remove it since it is the default.
So far it works fine but it hasn't been a month and it is already reporting that the battery is running out sensor.low_battry = true. I guess it's due to testing although it seems that continuous = true also helps.
I haven't touched the app again. I'll look into deleting the app and setting continuous to false in case it improves battery performance.
Greetings and thanks.

@dlbogdan
Copy link

I want the opposite of this. I want to be able to use the iPhone app just in case something goes wrong in the infrastructure and the lock cannot be triggered through the ESPHome device.
Any thoughts ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants