ConnectHome CH-601 - The device is not in the database

Hello, I’m trying to add a valve switch ConnectHome CH-601, but with no success yet. It was added as unknown device. When I click ‘reinitialize the device’ I see following error in the log:
2018-06-11 18:34:13.858 [ERROR] [st.core.internal.thing.ThingResource] - Exception during HTTP PUT request for update config at ‘things/zwave:device:780891b5:node12/config’
java.lang.NullPointerException: null

I checked the Z-wave binding database and didn’t find this device there. So I suppose this is the reason.

How it can be added to the database?
Here is the link to the device:

Thanks in advance,

You need to upload your nodes xml file to the database (after you registered and granted edit access from the maintainer):


The device is in database now, but I still can’t make it work.
Here is the device:
When I add or reinitialise I see following in the log:

2018-07-24 09:28:11.048 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.

==> /var/log/openhab2/events.log <==

2018-07-24 09:28:28.145 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:780891b5:node15’ has been updated.

2018-07-24 09:28:28.148 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]

==> /var/log/openhab2/openhab.log <==

2018-07-24 09:28:33.646 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 15: setupNetworkKey useSchemeZero=false

2018-07-24 09:28:34.015 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! 0179:0021:0011::1.2

==> /var/log/openhab2/events.log <==

2018-07-24 09:28:35.526 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:780891b5:node15’ has been updated.

0179:0021:0011::1.2 - the device number seems correct, but why it can’t find it in database?

The database gets merged into the bimding, so you need to upgrade to the latest snapshot of the zwave binding.

The problem has been solved. Thanks for your help!