Unifi controller is OFFLINE after upgrading OpenHab to v5.2.1 (from v5.1.3)

I just upgraded to OpenHab v5.2.1.

The Bridge reports always as offline and the openhab admin console suggess it is a configuration error / authentication problem. Note that the authentication has not changed (and I can login with the same credentials via the https interface).

I use the following .things to configure the bridge.

Bridge unifi:controller:home "UniFi Controller" [ host="unifi-network-application", port=8443, username="<hidden>", password="<hidden>", refresh=10 ] {
	Thing wirelessClient phone1 "Phone 1" [ cid="<hidden>", considerHome=180 ]
}

I am using unifi-network-application:10.4.57

I did enable Trace logging on the addon and that looks not helpful. The only thing in the log I see (when disabling and re-enabling the bridge):

2026-08-19 02:29:29.121 [TRACE] [rk.handler.NetworkRefreshCoordinator] - Bridge session not available yet; skipping refresh
2026-08-19 02:29:31.591 [DEBUG] [work.handler.UniFiClientThingHandler] - Initializing the UniFi Client Handler with config = UniFiClientConfig{cid: '<hidden>', site: '', considerHome: 180}
2026-08-19 02:29:39.121 [TRACE] [rk.handler.NetworkRefreshCoordinator] - Bridge session not available yet; skipping refresh

Any suggestion how I can fix this issue?

Thanks!

I’d first double-check whether anything changed in the UniFi binding between openHAB 5.1.3 and 5.2.1, since the same credentials still work through the web interface. The “Bridge session not available yet” message makes me think the problem may be with the binding establishing its session rather than the username or password. Checking the binding release notes or trying a clean reconfiguration might help narrow it down.