TKB TZ68E unknown device (TZ68 is in device db)

Add-ons Bindings
1

Hi everyone

My zwave power plug TZ68E is listed as unknown device, however there is a corresponding main device TZ68 in the database. How can I help to get it recognize?

TZ68
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/159

TZ68E
http://www.tkbhome.com/Z-WAVE-UK-Type-Plug-in-Socket_012_82.html

Log File
2018-06-24 10:35:06.333 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0

OS: Windows 10 [Version 10.0.17134.112]
JDK: Zulu 8.30.0.1
OHAB: 2.30 stable release
COM: Port4

2

If the devices are identical… channels, config parameters, etc. (check the manuals), then post the type:id from the XML file (userdata/zwave) so someone can add it to the existing device. Actually, just post the whole XML. Or request access (can’t find the link from my phone but it’s on Chris’ site) and you can do it yourself. Otherwise, a new entry would be needed.

3

Hi Scott

The variant is due to region classifcation (EU/US/UK etc) but I am quite sure the base function is exactly the same.

I cant see any useful details in the xml. Node1 being the ZWave controller, and Node2 has no info at all.

<node>
  <deviceClass>
    <basicDeviceClass>STATIC_CONTROLLER</basicDeviceClass>
    <genericDeviceClass>STATIC_CONTROLLER</genericDeviceClass>
    <specificDeviceClass>PC_CONTROLLER</specificDeviceClass>
  </deviceClass>
  <homeId>MASKED</homeId>
  <nodeId>1</nodeId>
  <version>4</version>
  <manufacturer>0x86</manufacturer>
  <deviceId>0x5a</deviceId>
  <deviceType>0x1</deviceType>
  <listening>true</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>false</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <supportedCommandClasses>
    <entry>
      <commandClass>NO_OPERATION</commandClass>
      <noOperationCommandClass>
        <version>1</version>
        <instances>0</instances>
        <versionSupported>1</versionSupported>
      </noOperationCommandClass>
    </entry>
    <entry>
      <commandClass>BASIC</commandClass>
      <basicCommandClass>
        <version>0</version>
        <instances>0</instances>
        <versionSupported>0</versionSupported>
        <isGetSupported>true</isGetSupported>
      </basicCommandClass>
    </entry>
  </supportedCommandClasses>
  <securedCommandClasses/>
  <associationGroups/>
  <nodeNeighbors>
    <int>2</int>
  </nodeNeighbors>
</node>

image
image.png1131×440 17 KB

4

It sounds like they are the same then. But there’s a roadblock if you don’t have an XML for the device to get the type:id. It looks as through the device has not completed initialization. Let’s see what @chris says.

5

The PID and VID from Windows if this is useful.

image

6

No, it is the type:id for the TZ68E that would be needed. There will be an XML for the node when it completes initialization. Your screenshot shows it is not communicating… maybe your using the dead node build of the dev binding? If so, manually turning it on/off might get it back online and initialized.

7

As @5iver said, it looks like the device is not communicating - I’d suggest to check the debug logs to see what is happening, or exclude it and add it again.

I don’t see how this can affect it? If by “dead node build” you mean the recent changes in the dev binding, then this definately won’t be an issue as the binding polls the device no matter what - unlike the previous build which used the controller to check the failed status.

8

Me either… faulty logic on my part, since manually triggering the device would get it back online with any version of the binding. I was tired. :roll_eyes:

9

Hi @Chris @5iver

Happy to report back that this is now working.

You are right about device not communicating.

I kept getting usb connect/disconnect (looking at Device Manager) issue and decided to change the ZStick to another USB port and viola… the ZStick now works well and reporting back all the stats and connected devices without issue.

image
image.png689×588 19.2 KB