Thanks. I just looked at my log files and I was getting NPE’s but I also was getting all kind of errors with it trying to pull in dependencies as well.
2017-08-28 16:11:06.454 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.zwave-2.1.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [10]
Unresolved requirement: Import-Package: com.google.common.collect
at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1253) [8:org.apache.felix.fileinstall:3.6.0]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1225) [8:org.apache.felix.fileinstall:3.6.0]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:512) [8:org.apache.felix.fileinstall:3.6.0]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:361) [8:org.apache.felix.fileinstall:3.6.0]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:312) [8:org.apache.felix.fileinstall:3.6.0]
Build 1025 includes a new ESH stable version. Amongst the changes is a version bump of Xtext. Xtext is used for textual configuration.
In the past I’ve had issues with HTTP 500 Errors when my textual item definitions were incorrect. I’m not saying that the Xtext bump and the 500 errors you are seeing are related, but I would not rule it out either.
I don’t think it’s XText that’s causing the ZWave NPE at least. The problem seems to be with localisation and in any case XText reads the files during initialisation and not when the REST interface is read.
I added the additional channel into the binding yesterday and didn’t see any errors. Maybe my development environment doesn’t have all the latest updates in ESH so I’ll do a complete update tonight and see if I can find where this issue is.
Upgraded to build #1027 with development zwave binding 2.1.0.201708292314
There is still no NPE related to the zwave binding. Also there has not been an NPE with #1025 and zwave development binding from one day earlier before the fix was applied.
It looks like zwave NPE’s only occur with the snapshot zwave binding (can’t test, don’t use it).
Great, thanks!
Now as this is a ESH fix, how and when will it be forward-propagated into a new OH snapshot build ?
ESH-stable is still on #225 and Cloudbees is still on #1029.
Please pardon my lack of knowledge on the full dependency chain. Has anybody written down how it’s getting processed ?
If not, doing so would probably make sense to keep more people like me from annoying you hard working guys with more questions like this one.
Just upgraded to #1030, and things are back in habmin ! Also no NPE so far (I’m running the dev zwave binding, though).
Will check in more detail tomorrow. Thanks a lot @lolodomo and @kai.
Just to add 1030 has fixed for me also, 500’s in paperui (though items tab seems to have disappeared - not sure when that happened) and no items in habmin. i wasnt experiencing the zwave error running standard binding.
wierd, it was switched OFF, and I checked an item that I had added this morning and it had every channel linked, so the runtime obviously thought it was in simple mode. I switched it on, saved it and then switched it back off and now I have items again.
seems like another bug, the items show up but then when i reload the page, the items link is gone again. I think my system is stuck in simple mode. I’ll see if I can figure out whats wrong.
turns out I had an old ‘org.eclipse.smarthome.links.cfg’ file in my userdata\etc which though it had autolinks=false set, once I deleted it and reset the value it stuck but the file wasn’t recreated. that file must not be valid anymore but since paperUI was using it to set/get the flag but the framework doesn’t use that file.
edit: nope that wasn’t it, things are still be created in simple mode.