kvj / hass_nuki_ng

Better support for Nuki devices in the Home Assistant
MIT License
176 stars 33 forks source link

Nuki 3.0 Pro Lock #67

Open clipse2004 opened 2 years ago

clipse2004 commented 2 years ago

Hello dude,

i have a 3.0 Pro Lock and also a Bridge for the Opener. How can i connect these together with your App? If i delete and reinstall your App, only my old lock Shows up :/

thanks

erazorv commented 2 years ago

same problem no 3.0 pro received via cloud api

clipse2004 commented 2 years ago

Now i connected my pro to the Bridge without wlan. It Works

erazorv commented 2 years ago

but how does this work with nuke_ng? > Cloud Web API, without Nuki bridge (Nuki Lock 3.0 Pro). Polling only

ppurice commented 2 years ago

same problem , nuki 3.0 pro , but with Home Assistant Core 2022.6.7 after loaded the component with hacs , i dont see nuki lock as integration but only nuki.

ppurice commented 2 years ago

problem resolved ! the problem of the integration was the cache of the browser, after cleanup ha showed it. integration done with cloud web API

alexdelprete commented 2 years ago

the problem of the integration was the cache of the browser

it's not a problem of the integration, it's a well known issue with HA: it is always recommended to do hard-refresh of the browser cache (ctrl-F5) if you don't see an integration just installed through HACS in the list.

integration done with cloud web API

When you configured the integration, did you fill in only the web token? did it give you any error regarding the bridge address field?

erazorv commented 2 years ago

I tried both. If i filled it completely it found only the bridge connected lock. With only the web api I got the error.

User input malformed: string value is None for dictionary value @ data['address']

jmcollin78 commented 2 years ago

Hi @erazorv

I tried both. If i filled it completely it found only the bridge connected lock. With only the web api I got the error. User input malformed: string value is None for dictionary value @ data['address']

Same issue for me. I just type "localhost" on the URL or IP address field as a workaround and it have work for me

alexdelprete commented 2 years ago

@erazorv @jmcollin78 localhost creates problems because the integration would try to contact the bridge. try to put None in that field.

jmcollin78 commented 2 years ago

Hello, thank you for your reply. I didn't find how to change this parameter once the installation is done. I rather prefer not to remove and resintall the integration because the Nuki is added to automation and scene.

Is there an easy way to reconfigure the integration without removing it ?

kvj commented 2 years ago

localhost creates problems because the integration would try to contact the bridge

It won't, unless you entered both token and address fields. In such case the input will be validated.

kvj commented 2 years ago

Is there an easy way to reconfigure the integration without removing it ?

Unfortunately no, but if you keep entity IDs unchanged, then your scenes/automations should work after the integration reset

erazorv commented 2 years ago

I added in IP address of the bridge a "." and I got it working now

kvj commented 2 years ago

Version 0.3.5 addressed the issue with empty bridge address field