Nuki integration options cannot be modified in the UI #47393

kongo09 · 2021-03-04T17:38:01Z

The problem

With release core-2021.3.0 the Nuki integration has landed a UI configuration dialog. However, the paramters - once entered - cannot be modified anymore from the UI (or yaml).

What is version of Home Assistant Core has the issue?

core-2021.3.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

nuki

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nuki/

Example YAML snippet

# Put your YAML below this line

Anything in the logs that might be useful for us?

# Put your logs below this line

probot-home-assistant · 2021-03-04T17:38:04Z

nuki documentation
nuki source
_{^{(message by IssueLinks)}}

probot-home-assistant · 2021-03-04T17:44:34Z

Hey there @pschmitt, @pvizeli, @pree, mind taking a look at this issue as its been labeled with an integration (nuki) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

a-jey · 2021-03-05T00:48:17Z

I wanted to add the integration with the http-api credentials from my bridge app and even that doesn't work.
I get the message that I've entered the wrong credentials which I didn't.

SeraphimSerapis · 2021-03-05T07:44:14Z

I also noticed that Nuki gets discovered as new integration, even though I already set up Nuki via yaml before. I am unable to hide/ignore the newly discovered integration, too.

barto64 · 2021-03-05T08:06:47Z

I also found this error with the new integration:

2021-03-05 08:16:05 ERROR (MainThread) [homeassistant.components.nuki.config_flow] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/nuki/config_flow.py", line 92, in async_step_validate
info = await validate_input(self.hass, user_input)
File "/usr/src/homeassistant/homeassistant/components/nuki/config_flow.py", line 39, in validate_input
data[CONF_HOST],
KeyError: 'host'

I removed all YAML entries, but I see now 3 Nuki integration pending of configuration and 1 well configured on the integration's tab.

kongo09 · 2021-03-05T08:15:13Z

I also no 8000 ticed that Nuki gets discovered as new integration, even though I already set up Nuki via yaml before. I am unable to hide/ignore the newly discovered integration, too.

That seems to be normal. I copied my settings from YAML to the GUI of the "new integration" and then removed the YAML entries. That works well. Downside is, I cannot change these parameters anymore as there is no access to them on the GUI once entered. So if the host changes (e.g. the static IP of the bridge), you cannot change it in the integration.

masterfixedit · 2021-03-05T12:25:46Z

When i fill in the host and access token in the new Nuki integration, i get the error: aborted... My Nuki lock still works with the yaml i set up.

aimartin · 2021-03-11T21:20:34Z

I also noticed that Nuki gets discovered as new integration, even though I already set up Nuki via yaml before. I am unable to hide/ignore the newly discovered integration, too.

I'm having the same issue, integration was created with right configuration, and Nuki seems to be working fine, however, it says that "New Integration has been discovered" at all times, even if I delete the integration, restart, and create the integration again, the tile is still there.

pree · 2021-03-13T22:42:38Z

Yes, currently there is no support for modifying the integration. In #40933 I've implemented a reauth-flow which will be triggered when the http-api token is changed, otherwise you'll need to remove the integration and re-add it. As long as the ID's stay the same (which they should) the entity-id's will be the same.

The discovered integration is happening through the new DHCP-Discovery. If you have it integrated it shouldn't pop up and you should also be able to ignore it. Could you send me the Hostname of your bridge ('Nuki_Bridge_XXX') & the ID of the configured Nuki integration so I can have a look and try to debug it?

@masterfixedit if you have it in the yaml it should have been imported to the UI and be present there, the error probably throws since it's already there. Is this the case?

@a-jey is there anything special about your token? Any special characters or >20 characters long?

a-jey · 2021-03-14T00:16:39Z

@pree i had only numbers and letters.
I changed it to only 8 letters and tried with no success.
I deleted from yaml and restarted server, tried to configure by adding integration.
It say wrong authentication.
I entered all secrets into yaml and restartet server again.
Nuki appears on integration list but with no entry.
I also don't find Nuki in entities or devices.

But when I enter the following line in my browser:
http://192.168.6.128:8080/list?token='mytoken'
i immediately see the status of my nuki doorlock.
This worked with the old token and also with the new one.

I got no more idea what else I could try.

github-actions · 2021-06-23T14:09:37Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

kongo09 · 2021-06-23T14:24:11Z

The issue still exists. Parameters, once entered, cannot be changed anymore. The workaround to remove and recreate the integration is cumbersome. E.g. it would require a lookup of the token in case the static IP address changes, just to recreate the integration.

I don't consider this solved.

phm46 · 2021-08-30T18:07:20Z

@pree
I have similar issue. I tried API manually and it works. Then I looked in pynuki source code and saw that it has option to use plain/hashed token. After modifying source code to use plain token instead of hashed, it started to work. My bridge doesn't have internet connection (I don't know why) and because of that I think it has wrong internal time. When it internally compare send time vs. time in variable, it sees that it doesn't match and not allow token. Integration should have option to use plain token instead of hashed token. Currently, it has hardcoded option for hashed token (config_flow.py:40)

github-actions · 2021-11-28T19:04:47Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

kongo09 · 2021-11-28T19:18:55Z

Unfortunately, this is not solved in the latest release. I would like to keep this open.

pree · 2021-12-27T18:28:04Z

The discovery & missing logo issue should now be solved by the following PRs:
#62476
#62470
#62840

The authentication issue mentioned by @phm46 when the time mismatches is something I haven't considered. There could be a seperate checkbox on creation of the integration which then uses plain instead of a hashed token.

github-actions · 2022-04-30T18:07:21Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

kongo09 · 2022-04-30T18:10:59Z

This is still not fixed

github-actions · 2022-08-04T00:20:46Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

kongo09 · 2022-08-04T06:32:51Z

This is still not fixed

issue-triage-workflows · 2023-01-15T23:08:50Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

kongo09 · 2023-01-15T23:09:40Z

This is still not fixed

issue-triage-workflows · 2023-04-16T00:21:02Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

probot-home-assistant bot added the integration: nuki label Mar 4, 2021

probot-home-assistant bot assigned pvizeli Mar 4, 2021

kongo09 mentioned this issue Mar 7, 2021

Update info about UI configuration of integrations home-assistant/home-assistant.io#16903

Closed

8 tasks

github-actions bot added the stale label Jun 23, 2021

github-actions bot removed the stale label Jun 23, 2021

github-actions bot added the stale label Nov 28, 2021

github-actions bot removed the stale label Nov 28, 2021

github-actions bot added the stale label Apr 30, 2022

github-actions bot removed the stale label Apr 30, 2022

github-actions bot added the stale label Aug 4, 2022

github-actions bot removed the stale label Aug 4, 2022

issue-triage-workflows bot added the stale label Jan 15, 2023

issue-triage-workflows bot removed the stale label Jan 16, 2023

issue-triage-workflows bot added the stale label Apr 16, 2023

issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 23, 2023

github-actions bot locked and limited conversation to collaborators May 23, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Nuki integration options cannot be modified in the UI #47393

Nuki integration options cannot be modified in the UI #47393

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Nuki integration options cannot be modified in the UI #47393

Nuki integration options cannot be modified in the UI #47393

Comments

The problem

What is version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Example YAML snippet

Anything in the logs that might be useful for us?

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!