You have a different issue - that’s why the above fix didn’t work. DynamicCommandDescriptionProvider is in the core, so should be available unless you are upgrading the binding but still with an older core?
It looks like this was added in February. So if you’re running an older build, it’s not in the core?
1 Like
Sorry for the confusion - that’s what I meant. There’s a mismatch with an old core and a new binding.
I don‘t know why it is missing if it was working before. I‘ll have a look.
1 Like
Ok let me start from the begining of what I’m doing.
I’m testing a fresh new telegesis dongle with the Zigbee Binding.
I have a fresh openhab 2.5.0.M1 install.
I’ve seen that this binding seem to be in active developement so I wanted test the lastest release.
I’ve found this great script : https://github.com/openhab-5iver/openHAB-utils/releases/tag/1.1.0 and on friday, everything worked like a charm.
I’ve wiped out this install, restart from a fresh 2.5.0-M1 and tried this morning to reinstall zigbee binding from the script and figured out that the zsmartsystems part of the binding were correclty downloaded but the binding part failed because some paths in ci.openhab.org have changed.
ex: https://ci.openhab.org/job/openHAB2-Bundles/lastSuccessfulBuild/org.openhab.binding%24org.openhab.binding.zigbee.telegesis/artifact/org.openhab.binding/org.openhab.binding.zigbee.telegesis/2.5.0-SNAPSHOT/org.openhab.binding.zigbee.telegesis-2.5.0-SNAPSHOT.jar doesn’t work anymore.
So, I kept the zsmartsystems jar files and manually download the zigbee and zigbee.telegesis from https://ci.openhab.org/job/openHAB2-Bundles/lastSuccessfulBuild/
But, the binding doesn’t start, first error was with Xstream and your trick to add the .jar worked. next was with gnu.io and install the DSC Binding helped, and next the last errors.
So seem to be another world between friday and today 
That’s the problem then - it’s too old to be compatible with the latest binding.
oh ok … sorry for that …
so it seem that on friday I think that it work but maybe the official binding was not uninstall.
Thanks you.
@chris (or who else has the problem): can you do bundle:list -s | grep -i xstream? Is xstream installed?
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…
I‘m a little bit surprised, too.
Nothing on my system
openhab> list -s | grep xstream
openhab>
After Mark’s suggestion:
openhab> list -s | grep xstream
267 x Active x 80 x 1.4.7.1 x org.apache.servicemix.bundles.xstream
openhab>
Ok, then you need to install the jar as described here.
Edit: Ah, I see you already installed it. Then the zwave binding now should be working.
1 Like
Working, thank you sir!
1 Like
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 
.
Kris
battery devices need woken up
push button, poke with paper clip
hit + to start discovery then push wake up button
All good Chris, thank you for getting meter reset working for those nodes!
Andrew, yep but takes ages to do that. Ill just let them do their thing!
1 Like
OH does not use ESH any more… ESH is now OHC. 
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.