-
Notifications
You must be signed in to change notification settings - Fork 40
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
Opener and KeyPad 2.0 - no KeyPad entities visible #298
Comments
Try this binary. |
I think the answer is unfortunately not as easy as adding the auto discovery topics for home assistant. Checking the code again, the keypad is actually not yet implemented for the opener - mostly because it's a rare thing that someone want's to use an opener and a keypad together. I'll have to go through the code and see what's necessary to add keypad support for the opener - it's mostly duplicating some code. |
Thank you for your efforts. If there's anything I can do to help, I'm very happy to do it! |
with FingerPrint: [ |
With Pin: [ |
Hi, I think first thing to do is to add the missing code, not that much you can do. |
Hi |
Hi, actually there's not as much missing as I thought. I think I only have to recheck all auto discoveries for the opener keypad |
Check this binary please |
Is this working as expected? @technyon: Has this been merged into master yet? |
I've manually build a
|
Merged into master |
Hello
Thank you very much for the great work. I'm currently experimenting a bit.
I have an opener running via the ESP hub in the Home Assistant (2024.2.1). These entities are all displayed. But now I have also connected a KeyPad 2.0. Unfortunately, its entities are not displayed. I have already reset everything several times, reinstalled, recoupled... Without success. In other articles, I could see in pictures that entries such as "KeyPad status" should appear under "Diagnostic". In MQTT I receive corresponding messages from the KeyPad.
What am I doing wrong or what have I overlooked?
Thank you for your help.
The text was updated successfully, but these errors were encountered: