Giters

technyon / nuki_hub

Use an ESP32 as a Hub between a NUKI Lock and your smarthome.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Issue with Opener: Only Ring to Open is working not Open directly

riyas1980 opened this issue · comments

commented

Hello,

First of all, thanks for your great work. I am trying nuki hub with my opener. I am using version 8.32

When added, my MQTT shows 2 entities (1 is enabled and 1 is disabled)

Intercom is enabled with Unlock as option
Unlatch is disabled

When I click on Unlock, it doesn't open my entrance door. The state change to Ring to Open. So If I ring my intercom, it's opening.

I want to directly open the door without Ring to open. Is that possible ?

Thanks for your help.

Kind Regards,

commented

And I've enabled the unlatch button in Home Assistant. But when I press, it doesn't do anything

commented

Unlock enables Ring to Open and lock disables Ring to Open.
Unlatch (equals Electronic Strike Actuation for the opener) opens a door.

The Unlatch button in Home Assistant only works when unlatch is enabled in the Nuki Hub configuration (Nuki Configuration -> Advanced Nuki Configuration). Set access level to "Full"

image

commented

Unlock enables Ring to Open and lock disables Ring to Open. Unlatch (equals Electronic Strike Actuation for the opener) opens a door.

The Unlatch button in Home Assistant only works when unlatch is enabled in the Nuki Hub configuration (Nuki Configuration -> Advanced Nuki Configuration). Set access level to "Full"

Hi,

Thanks for your reply. Actually it is already in Full Access level. But When I press the Unlatch button, Opener doesn't do anything. But in logbook, we can see that : "Unlatch changed to February 28, 2024 at 12:28 PM triggered by service Button: Press 12:28:42 PM - 21 hours ago".

For your information, when MQTT discovered Nuki Hub, only "Unlock" button was visible. Unlatch was disabled by default. I've enabled it but unfortunately it's not working.

Nuki_settings

commented

Unlatch button is disabled in HA by default. This is by design as a security measure.

The Home Assistant log will probably not be very helpfull here as it is only able to tell if it published something to the MQTT topic, what Nuki Hub does or doesn't do based on this can not really be discerned from within Home Assistant.

Just to make sure: You are able to unlatch/open your door without ringing using the Nuki smartphone app?

commented

Unlatch button is disabled in HA by default. This is by design as a security measure.

The Home Assistant log will probably not be very helpfull here as it is only able to tell if it published something to the MQTT topic, what Nuki Hub does or doesn't do based on this can not really be discerned from within Home Assistant.

Just to make sure: You are able to unlatch/open your door without ringing using the Nuki smartphone app?

Yes I am able to unlatch/open my door without ringing from my Nuki app. I really don't know what's wrong with my HA and Nuki Hub

commented

Have you tried setting nukiopener/lock/action to electricStrikeActuation manually (using an app like MQTT Explorer)?
To rule out an issue with Home Assistant.
Please also check nukiopener/lock/action changes to electricStrikeActuation when pushing the Home Assistant "Unlatch" button.

What does nukiopener/lock/completionStatus and nukiopener/lock/commandResult show after setting action to electricStrikeActuation?
And does the door open when setting action to electricStrikeActuation manually?

commented

Have you tried setting nukiopener/lock/action to electricStrikeActuation manually (using an app like MQTT Explorer)? To rule out an issue with Home Assistant. Please also check nukiopener/lock/action changes to electricStrikeActuation when pushing the Home Assistant "Unlatch" button.

What does nukiopener/lock/completionStatus and nukiopener/lock/commandResult show after setting action to electricStrikeActuation? And does the door open when setting action to electricStrikeActuation manually?

Thanks for your help. I am out of town. Tomorrow I'll try and inform you. Thanks again

commented

I am trying to change the setting to electricStrikeActuation with MQTT Explorer but I don't know where exactly I need to change. I am sorry. I am new to MQTT.

Nuki_Edit

I've even updated the Nuki Hub to 8.33 and I can see the continuous mode also.

With MQTT explorer, this is what I get, when I click on unlock (action : ack)

Nuki_Unlock

But when I click on Unlatch, I have this message (action = Unknown_action):

Nuki_Unlatch1

In the history, I have 2 lines : First one is Unlatch and second one is Unknown_action

Nuki_Unlatch2

I don't know if my message is clear to you. I don't know how to edit the setting to "electricStrikeActuation"

Thanks again for your help

commented

There is a bug in the code that exposes the "Unlatch" button in Home Assistant for the opener.

When using a Opener Home Assistant should not sent a "unlatch" command but the "electricStrikeActuation" command.

PR #316 should fix this bug.

You can download the binary that is created by GitHub with these changes from https://github.com/technyon/nuki_hub/actions/runs/8147478237/artifacts/1296509546

Please try the binary and report back if your issue is solved. You will know Home Assistant has picked up the changes if the name of the "Unlatch" button has changed to "Open".

commented

You can download the binary that is created by GitHub with these changes from https://github.com/technyon/nuki_hub/actions/runs/8147478237/artifacts/1296509546

Thanks for your help. Tried the new binary file. But unfortunately, I only have Unlock this time. There is no Unlatch/Open (nothing is disabled, I checked it many times), and no continous mode also.

Nukihub_newbinary

I even deleted the old one from MQTT and unpaired and repaired again. The result is same.

commented

In MQTT explorer, you should set lock/action to unlatch. When correct, Nuki Hub will respond with "ack" to the same topic.

commented

@technyon: True for the Lock, but not for the Opener, then it should be "electricStrikeActuation" or you will get "unknown_action" instead of "ack". #316 fixes this for the unlatch button.

@riyas1980: You now seem to have an issue with auto discovery which I can't explain from the changes in #316 which are very minor. I have noticed in the past that sometimes (especially around firmware updates) multiple locks with different/incorrect ID's can be created.

Are you sure you don't have duplicate MQTT devices for the Opener in Home Assistant, some of which include the missing entities?
Is Home Assistant discovery topic still set to homeassistant in Nuki Hub Advanced MQTT and Network Configuration
?
What does homeassistant/sensor/[8 DIGIT ALPHANUMERIC CODE CORRESPONDING TO THE LOCK ID] show in MQTT Explorer?

commented

@iranl you know what ? I didn't do anything. But now I have 2 disabled entities: 1 is Open and 1 is continuous mode.

It's working almost perfectly. There is a slight delay between the open button and the door open (around 5 to 6 seconds). There is maybe some settings to change. I'll try to check the settings.

Thank you very much again for your great help @iranl

commented

Good to hear it works as expected now.

Nuki Hub is known to have varying delay of a couple of seconds between issueing a command and it's execution.
This is due to the nature of the bluetooth communication between the ESP and the lock/opener.