Well, I don’t have the problem exactly. But I do have two builds, one of which has it installed and one that doesn’t.
In a very recent 2.5 snapshot (build 1587), I see this.
openhab> list -s | grep -i xstream
65 │ Active │ 80 │ 1.4.7.1 │ org.apache.servicemix.bundles.xstream
In an older 2.5 snapshot (build 1502), that bundle is not installed.
I don’t recall exactly when 1502 was built. Definitely after 2.4 stable and before the ESH integration work started. I expect that I’d see the problem if I dropped the latest zwave binding into the addons directory in this system. I’m reluctant to do this though, because it’s one of my production OH instances.
Thanks, no need for further confirmation. Then it won‘t work without manual installation of the xstream bundle on older builds. I don‘t think it‘s worth Investigating why it is not available on older systems if recent builds are ok and a workaround for older systems is available.
This is a bit strange since XStream is used by the core to read the XML files for all bindings, so I’m a bit surprised to find it’s not available… Or maybe in the recent changes ESH changed to use a different XML parser…
Not a great start with the new binding, most nodes stuck in NIF. Previous one i used was perfect! @chris any suggestions? Or does this take longer now when the binding is restarted/new.
The good news is meter reset works for the ZW111 YAY!
EDIT: Seems all battery devices, ill give them a while and see what happens.
Please note that the binding has not changed - all the code is exactly the same and I have not made any changes. Only the build system has changed, and there seem to be some teething issues with getting the whole system running. Sorry for the hassles, but it’s not really in my control .
I was having issues due to using my script. When zigbee and zwave were migrated to BND, the directories changed. The script still downloaded something, but they were not jars , so OH did nothing when they were copied to addons. I’ve updated the script and included the xstream jar. BTW, zigbee also required openhab-core-config-discovery-usbserial and seems to need an OH restart after installing/upgrading.
Sure, I understand that, but the same point exists. Unless this has been refactored out ing the move, it really should still be there.
Yep - I saw your comment on the other thread. I’m not sure why it should be different now than it was previously, but we seem to be living in an ever changing world . I’m looking forward to the day when openHAB actually has some stability .
Hi,
I’m trying to update my z-wave bindings on OH 2.4.
Is the actual last version this one?
238 x Active x 80 x 2.4.0.201812141755 x org.openhab.binding.zwave
@chris It looks like the Zigbee M2 release does specify a version 1.4,2 of xstream, and it is breaking my system even thou I have org.eclipse.smarthome.config.xml binding installed. (I am running a custom distro so you might not need to care about this if it is running normally on openhab. I just wanted to mention it)
for anyone who is interested this is how I set it up.
I am running openhab 2.4 and I had to install the latest z-wave binding (2.5.1.201912300340 │ org.openhab.binding.zwave) in order to get a Fibaro RGBW controller running (FGRGBW-442 RGBW) which is not included in the zwave 2.4 binding.
I just dropped the latest snapshot 2.5.1 into my addons folder which failed in the first since it was missing another lib - org.apache.servicemix.bundles.xstream .
In case you stumble upon the same issue. Just put version 1.4.7_1 also into the addons folder and openhab will be able to set up the updated binding on restart.
Have fun.
Philip