ariela
December 29, 2020, 3:50pm
21
6.0 is buggy
Andrea
TheJM
December 29, 2020, 4:29pm
22
Is there a link to that version of the binding? Is there an issue downgrading?
ariela
December 29, 2020, 4:35pm
23
Sorry, it was not clear enough … I was talking about Unifi Controller release, not OH Unifi Binding
TheJM
December 29, 2020, 4:37pm
24
Oh no thats my bad. I wasn’t paying close enough attention. So you think the issue is with the unified controller not the binding?
ariela
December 29, 2020, 4:53pm
25
What I know is the Unifi release 6.0 is definitely buggy
So perhaps they changed too many things …
Seaside
December 29, 2020, 7:54pm
26
The UniFi binding has not been updated to support devices running UniFi OS (Cloudkey gen2+ with new firmware), udm and udmp.
opened 03:02PM - 03 Sep 20 UTC
closed 04:55PM - 31 Jul 21 UTC
enhancement
bounty
<a alt="bounty" href="https://www.bountysource.com/issues/92746043-unifi-add-sup… port-for-dream-machine-pro"><img src="https://api.bountysource.com/badge/issue?issue_id=92746043"></a>
As far as i know currently the unifi Binding doesn't support the dream machine pro.
I got an 404 if i configure the unifi binding on my openhab installation. @ericsante on the openhab community forum experienced the same behaviour (https://community.openhab.org/t/ubiquiti-unifi-binding-feature-discussion/14520/1072?u=regnets).
opened 04:51PM - 18 Mar 20 UTC
bug
Discussed here:
https://community.openhab.org/t/ubiquiti-unifi-binding-featur… e-discussion/14520/1013?u=mgbowman
HoLiuS
January 1, 2021, 10:11am
27
I have a similar problem, ever since I have upgraded to a UDM Pro, the binding connection fails and I cannot retrieve any data from unifi.
My current workaround is to use the IoBroker Unifi Adapter and update the respective items in Openhab via the Openhab Adapter in IoBroker (Rest API).
A side benefit is that the Unifi Adapter in IoBroker has much more Data points exposed to use and react on.
Maybe this helps someone…
laursen
October 18, 2021, 9:07pm
28
For the original problem in this thread about client never being updated to offline, I finally took some time to analyze/understand the problem in-depth, so created a PR with a proposed fix:
main ← jlaur:7001-unifi-online-channel
opened 08:24PM - 18 Oct 21 UTC
Fixes #7001
Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk>
Fix pr… oblem with online channel never being updated to **OFF** after client disconnects. This was most likely introduced by Uni-Fi Controller 5.12.35.
Problem could be solved in different ways. In this PR I fixed it by keeping clients in the cache after they are no longer connected to the access point. A different approach could be to fix it through the insights cache, which might seem more correct at first glance. However, it would get messy (also) as the IP address is simply not available anymore (at least since 5.12.35). So the insights cache would need to be correlated with the client cache to add this information while it's still available, for example through **mac** or **_id**.
The chosen approach here is quite simple as `cache.put` will replace any existing client with same key (it's implemented as HashMap). So instead of flushing the entire cache after each call, clients are replaced one by one.
Best regards,
I stay with 5.14.23 for the moment