Can I manually create Z Wave device from information in the database

I have tried to discover a Schlage Link Power Socket using the Z wave binding. The binding reports that its is an unknown device. The xml file that is generated has a bunch of things in there but the manufacturer, device and type are all reported as ox7FFFFF.

<?xml version="1.0"?>

-<node>

<homeId>0xc186a966</homeId>

<nodeId>17</nodeId>

<version>3</version>

<manufacturer>0x7fffffff</manufacturer>

<deviceId>0x7fffffff</deviceId>

<deviceType>0x7fffffff</deviceType>

<listening>true</listening>

<frequentlyListening>false</frequentlyListening>

<routing>true</routing>

<security>false</security>

<beaming>true</beaming>

<maxBaudRate>40000</maxBaudRate>

<sleepDelay>1000</sleepDelay>


-<nodeInformationFrame>

<commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>

<commandClass>COMMAND_CLASS_SWITCH_ALL</commandClass>

</nodeInformationFrame>

<associationGroups class="concurrent-hash-map"/>


-<endpoints class="concurrent-hash-map">


-<entry>

<int>0</int>


-<endPoint>


-<deviceClass>

<basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>

<genericDeviceClass>GENERIC_TYPE_SWITCH_BINARY</genericDeviceClass>

<specificDeviceClass>SPECIFIC_TYPE_POWER_SWITCH_BINARY</specificDeviceClass>

</deviceClass>

<endpointId>0</endpointId>

<secureCommandClasses/>


-<supportedCommandClasses class="concurrent-hash-map">


-<entry>

<commandClass>COMMAND_CLASS_NO_OPERATION</commandClass>


-<COMMAND__CLASS__NO__OPERATION>

<version>1</version>

<instances>1</instances>

<control>false</control>

<versionSupported>1</versionSupported>

</COMMAND__CLASS__NO__OPERATION>

</entry>


-<entry>

<commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>


-<COMMAND__CLASS__SWITCH__BINARY>

<version>0</version>

<instances>1</instances>

<control>false</control>

<versionSupported>0</versionSupported>

<isGetSupported>true</isGetSupported>

</COMMAND__CLASS__SWITCH__BINARY>

</entry>


-<entry>

<commandClass>COMMAND_CLASS_SWITCH_ALL</commandClass>


-<COMMAND__CLASS__SWITCH__ALL>

<version>0</version>

<instances>1</instances>

<control>false</control>

<versionSupported>0</versionSupported>

<isGetSupported>true</isGetSupported>

<mode>SWITCH_ALL_INCLUDE_ON_OFF</mode>

</COMMAND__CLASS__SWITCH__ALL>

</entry>


-<entry>

<commandClass>COMMAND_CLASS_BASIC</commandClass>


-<COMMAND__CLASS__BASIC>

<version>0</version>

<instances>1</instances>

<control>false</control>

<versionSupported>0</versionSupported>

<isGetSupported>true</isGetSupported>

</COMMAND__CLASS__BASIC>

</entry>

</supportedCommandClasses>

</endPoint>

</entry>

</endpoints>

<nodeNeighbors/>

<lastReceived>2019-10-14 01:56:11.435 UTC</lastReceived>

</node>your code goes here

Looking at the Z wave database, there is a similar switch which appears to be manufactured by Wintop and is also sold under the brand DHS pty. Is there a way to manually configure this device using the information from the database? I also have a problem discovering two Heiman smoke detectors which also appear to be in the database. Other devices are working ok.

I am using a recent snapshot of the 2.5 Z wave binding.

Welcome to openHAB.

You definitely need to find the root cause. If initialization does not work, for example an xml is not created, you or your installation are doing something wrong.

First: make sure you are including through the binding. Don’t remove the zwave controller from your computer during inclusion.
Second: if battery operated devices don’t initialize, you need to wake them up, sometimes several times. This is a special button sequence, please look it up in your manual.
For locks: those must be included securely. If an inclusion fails you need to factory reset the lock and include it again. Inclusion must be finished within 15 seconds and the inclusion must be performed through the binding, don’t remove the stick.

Good luck.

Thanks. The Heiman smoke sensors seem problematic because they are battery powered, but I did previously have one of them working on Z-Way.

I think the Schlage device isn’t reporting good information. Following the article https://www.openhab.org/docs/configuration/things.html I seem to have got the device working by creating a manual .thing file using the information from the database for the Wintop device which looks similar.

My thing file looks like this

Thing zwave:wintop_le120_00_000:5501:node24  "ZWave Node 24: Schlage Link" (zwave:serial_zstick:f7d410f4) [ node_id=24 ]

In paper UI the Schlage thing then reports a switch channel which I can link an item to.

This is not the way how to do it and you will get problems in the future.
You need to find your initial problem.

Please provide a DEBUG log during inclusion of the device (remove the security key before posting!).

1 Like