New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[unifi] OH 2.5 Binding broken for UniFi OS #10837
Comments
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/ubiquiti-unifi-binding-feature-discussion/14520/1175 |
Alright, I've narrowed down the problem somewhat, specifically, I downgraded my UniFi version to 5.14.23 again, but it still doesn't work. Now I think the problem is the update on the cloud key has moved the access IP from 192.168.1.xxx:8443 to 192.168.1.xxx/network. |
This is probably the fix that is missing: #10041 |
Is this an issue with 2.5 only? In which case this issue can be closed as there is no support for 2.5 issues here. |
@Hilbrand As far as I know, yes, although I ended up manually fixing it here: https://community.openhab.org/t/ubiquiti-unifi-binding-feature-discussion/14520/1179 The fix is simple enough that anyone who has the dev environment setup and can use git properly (I can't) should be able to fix it. |
As there is support for Unifi OS since version 3.1.0 of the binding i mark this as resolved. 2.5 is no longer supported. |
UPDATE:
The problem is that UniFi OS changed how auth works, and this issue has already been fixed in 3+ releases. Someone would need to back-port a patch for OH 2.5
After my local Unifi Network was updated to version 6+, the binding no longer connects to the controller. In the UI, this shows as OFFLINE - COMMUNICATION_ERROR
Expected Behavior
The bridge should connect to the UniFi software
Current Behavior
Attempted to change thing port to 443 in bridge Thing config, only result in this log error:
Unhandled exception while refreshing the UniFi Controller unifi:controller:a2bc7a83 - com.google.gson.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 2 column 12 path $
Steps to Reproduce (for Bugs)
Context
Without connection to the bridge, the entire binding is effectively non-functional.
Your Environment
The text was updated successfully, but these errors were encountered: