Unifi Protect integration "Attention Required"

Hi,

I have the Unifi Protect integration running for my Cloud Key Gen2 Plus and G4 Doorbell.
But every 2 or 3 weeks my integration ‘expires’.
image

I need to re-enter the credentials and then it’s working again. But I don’t get notified about this ‘expiry’ and it breaks my doorbell automations (e.g. even ringing my doorbell is depended on it) so I don’t know when someone’s at my door. Any way to get rid of this ‘expiring’ policy? Or get notified when my integration stops working?

1 Like

I have this integration running on my system, & it doesn’t ‘expiry’ for me.
I think you need to tweak your settings on the ‘Cloud Key Gen2 Plus’.

The thing is, you can’t really tweak anything on local access admins.

For my set up, I have two different accounts on the CLK2+ for HAss. One for network & one for Protect (Security thing, don’t have admin [just a viewer account] access for protect) both have local access only. Perhaps that is why I don’t get the issue you are describing.
Another thing I thought of, is do you have your CLK2+ on DHCP assigned IP, if so is it that your ip is changing? just a thought.
& I assume you are running the latest versions of everything?

You could set up an automation to do this with device.tracker…
I do this for an iffy Unifi switch I own, when ever it goes unavailable for more than 20min’s A zigbee smart switch restarts the switch.

It might be a good idea to change the account to just viewer permissions. Thanks and I’ll update this thread in a few days / weeks with the outcome.

I had this issue too, the problem was in Unifi OS, that somehow, with an update, it changed my previous role I had for my local hass user.

Go to

Users > Roles > Edit the role you assigned for your local user

Make sure you have at least “Viewer” for both “Protect” and “Network”

After changing that and reintroducing password on hass, everything worked again.

1 Like

Changing the local access user rights from admin to viewer seems to have fixed the problem. Thanks for the suggestion.

Another update; it in fact did not solve the problem. I now scheduled a daily restart of my HomeAssistant in the hopes that this will fix the problem because I noticed that restarting the integration gets rid of the error.