The above WARN message is not unique to this binding. I’ve seen it before with other bindings in the addons folder after a clean install and/or upgrade. It seems that the bindings in the addons folder get activated before all the dependencies are available.
Once the binding is merged into the build, and can be installed using Paper UI or added to conf/services/addons.cfg, I believe the above WARN message should go away.
@mgbowman I’m still having the jackson.core dependency issue. I tried wgetting them in the addons folder but it doesn’t help.
I guess everyone has an addon installed which also installs the jackson.core library, but I don’t have it.
It should be easily reproducible using a clean OpenHAB 2.1 install and trying to add the Unifi Binding.
just fyi: I just uped the Unifi controller from 5.4.16 to 5.4.18 and all is good
Running on OH 2.2.0 Snapshot #978 with 2.1.0.201706081307 org.openhab.binding.unifi (shouldn’t this go to 2.2.0.x snapshot versioning also? )
Another data point: with Unifi 5.5.11 and OH 2.2.0 Build #977, the binding works fine too.
But yes, the binding should be rebased against the master (and then force pushed), then we will get a 2.2.0-compliant version. Not that there are many changes in the core since the 2.1.0-RELEASE…
But now I added the controller but I get communication errors:
When it calls: https://myunificontroller:8443/api/s/null/stat/device
I see it logs in fine, and discovers that I have a default site, but that the path is null and then calls the above adres which gives this if I call it using my own browser:
I got the versions from a post in a bug report (the thread is in the related section of this thread)
I’ve being going through the code of the binding. And it looks like the path property of a site is never set. The response to get the sites doesn’t contain a path element in the json either. So the weird thing is, how does this binding work for anybody? This this path property is used to make up the url’s to get devices.
Are you guys using the latest build (from the url in my previous post)? Or the pre-release from github?
Any update to this binding? *I’m on the 2.1-SNAPSHOT.jar. I was hoping to use it. I notice it’s still trying to access https://mycontroller:8443/api/s/null/stat/device
Hi @martinvw, I’ve been away for the last month now I’m finally back home. I will try and find some free time this coming week. There’s 2 things I want to do before I squash and rebase:
Look into the **null** issue @psyciknz is experiencing
Change the online channel to a Contact (instead of a Switch as it’s read-only)
I will make these changes and post a new build (with a 2.2.0-SNAPSHOT version) to see if we can get this in OH 2.2.
Download the latest *.jar file from: https://jenkins.otr.mx/job/openhab2-unifi-binding/
Place it in your $OPENHAB_RUNTIME/addons folder (in Linux apt: /usr/share/openhab2/addons/)
Use discovery in PaperUI or manually define your things and items (see this thread for example configs)
edit: forgot the link to the UniFi Binding Readme for config info