Unifi cannot send command after a while

HangGliderz · October 10, 2025, 4:53pm

I have an UCG Ultra.
It is possible to send a command to it when the Unifi-controller-thing-bridge has been disabled/enabled. But then it stops working after a while. A disable/enable makes it work again, for a while.
WARN: “Not Authorized! Please make sure your controller credentials have administrator rights”
I have tried to re-install the binding, but nothing helps.

It has been like this since I got the UCG Ultra a year ago. Please help!

seime · October 11, 2025, 7:43am

Can confirm

HangGliderz · October 11, 2025, 7:35pm

Was thinking of running a rule periodically to disable / enable the bridge thing.
However, I can’t really make out how long it takes for the binding to ‘fail’.
Do you know what interval the disable / enable cycle should be triggered at?

Frasier · December 27, 2025, 10:22pm

Edit: I’ve created an issue over at github for this bug. Hopefully it can be resolved. I’m happy to assist eg. if further logging is needed.

github.com/openhab/openhab-addons

[unifi] Binding complains about controller credentials

opened 04:23PM - 28 Dec 25 UTC

NickBuilder

bug

[logfile.csv](https://github.com/user-attachments/files/24360944/logfile.csv) #…# Expected Behavior Commands issued through the binding should be "authorized" continuously. ## Current Behavior As the behavior is now the binding is only authorized to issue commands initially and during some duration, I haven't investigated at what point the bridge loses authorization. But at some point the commands are failing and I get the warning message _"Not Authorized! Please make sure your controller credentials have administrator rights"_ from logger class org.openhab.binding.unifi.internal.api.UniFiController. Log (some sensitive data has been removed) is attached as a CSV-file. ## Possible Solution Somehow ensure that the authorization is kept intact. ## Steps to Reproduce (for Bugs) 1. Install the latest Unifi binding through the add-on store (5.0.3). 2. Make sure that you use a dedicated Unifi network controller user, with local credentials, and with admin permissions. 3. Configure a bridge with UniFi OS. 4. Setup a Unifi thing with a switch linked to the "Blocked" channel. 5. Try to issue a "blocked" command by activating the switch after a couple of hours. ## Context I'm trying to limit the up time of the computer my son is using so that he'll go to sleep. :) ## Your Environment Raspberry Pi 4 Model B Rev 1.5 "Debian GNU/Linux 12 (bookworm)", 64 bit, installed through openhabian-image openHAB 5.0.3 Release Build (updated through openhabian-config) UniFi Binding version 5.0.3 Unifi Cloud Gateway Ultra running UniFi OS version 4.4.9 and Network controller version 10.0.162. A dedicated Unifi network controller user, with local credentials, and with admin permissions.

I also have the issue that the command part of this binding is faulty. It looses authorization after some time.

But as others has mentioned, by dissabling and reenabling the bridge thing the commands start to work again.

So, how do I in a rule disable and enable a thing?
If I do this before issuing my commands it would work and I would be happy.

Matthias_Kaufmann · January 16, 2026, 5:07pm

How often do you re-activate the binding as a workaround?

tcgerhard · January 16, 2026, 8:37pm

Here is a Javascript rule that I use to reset an Ecobee thing:

var ecobeeAccountThingId = "(your thing ID)";

var ecobeeAccountThing = things.getThing(ecobeeAccountThingId);

ecobeeAccountThing.setEnabled(false);
ecobeeAccountThing.setEnabled(true);

HangGliderz · January 17, 2026, 6:45am

I started with 30 min but that was not often enough.
Have now run with 15 min interval for a few months, and that seems to be working.

Matthias_Kaufmann · January 18, 2026, 10:19am

What Unify Network version are you using? With Openhab 5.1.1 and Unify Network 10 I do not get offline change of devices any more, even after binding restart (also every 15 min).

TheNetStriker · February 17, 2026, 12:03pm

I also noticed this problem after updating to Unifi OS Server with Unifi Network 10.1.85.

After restarting the controller thing I can send commands, but shortly after it does not work anymore.

Maybe something has changed regarding the api token lifetime?

I found this in the log:

2026-02-17 12:20:22.002 [DEBUG] [ternal.handler.UniFiBaseThingHandler] - Handling command = ON for channel = unifi:accessPoint:masshardt:71a76710:enable
2026-02-17 12:20:22.002 [DEBUG] [.internal.api.UniFiControllerRequest] - Body parameters for request ‘/proxy/network/api/s/gvxbs9uw/rest/device/69924dc25846be6071a76710’: {“disabled”:“false”,“_id”:“69924dc25846be6071a76710”}
2026-02-17 12:20:22.008 [WARN ] [g.unifi.internal.api.UniFiController] - Not Authorized! Please make sure your controller credentials have administrator rights