Konstantin

in 0.2.1 I've added hass URL pre-check, to avoid the confusion

Hey That shouldn't happen. Was callback successfully set? There's a binary sensor being exposed for that. Have you modified the polling interval?

> so it's definetly regarding internet-access of the bridge Well, in this case, Nuki NG integration can't do anything. Web API is optional, and configured Web API means that the...

Now I understand what you mean. You can make a very simple test: just try to access `/info` bridge API without an internet connection: smth. like: `curl "http://:8080/info?token="` if the...

That's interesting. Could you please make one more test? Please go to `nuki_ng` source code and change the line https://github.com/kvj/hass_nuki_ng/blob/c9c0531239720135a009c7c800c8c65a2e96a2c9/custom_components/nuki_ng/nuki.py#L33 to `self.use_hashed = False` And restart your HASS and try...

There's a bigger problem here, I'll try to address it. Generally speaking, the connection between the integration and the bridge isn't always reliable, so errors could happen. In the way...

not yet, but good idea to have it

There's a service for that: ```yaml service: nuki_ng.execute_action data: action: lock_n_go target: device_id: 83f592f5c6d885fe4698618afb5cb129 ``` 

Added in 0.3.8

Strictly speaking, as the component supports Web API endpoints, it should be `cloud_polling`. But, as this value is **not** dynamic and doesn't change anything, it doesn't matter which value to...