Need to update zwave database with new Manufacturer for exisiting device

klee3d · November 21, 2021, 4:50pm

I have a Zwave Plus mini power meter plug from a company called Minoston that has the same model number (MP21ZP) as an existing device in the database ( NIE Technology MP21ZP Mini Plug with Power Meter) OpenSmartHouse Z-Wave Device Database

The Manufacturer number for my device is 786 versus the entry in the database of 0312

I already have access to the zwave database at Open Smart House but wanted to confirm the proper procedure for getting this addressed.

zwave_class_basic
BASIC_TYPE_ROUTING_SLAVE
zwave_class_generic
GENERIC_TYPE_SWITCH_BINARY
zwave_neighbours
zwave_frequent
false
zwave_version
1.0
zwave_listening
true
zwave_plus_devicetype
NODE_TYPE_ZWAVEPLUS_NODE
zwave_deviceid
65294
zwave_nodeid
84
zwave_routing
true
zwave_plus_roletype
ROLE_TYPE_SLAVE_ALWAYS_ON
zwave_beaming
true
zwave_secure
false
zwave_class_specific
SPECIFIC_TYPE_NOT_USED
zwave_manufacturer
786
zwave_devicetype
65280

apella12 · November 21, 2021, 7:03pm

I would be a little careful. 312 in hex is 786. What about the other numbers?

Bob

Edit: this looks like the same device FF00:FF0E. Did it not include?

klee3d · November 21, 2021, 8:03pm

Ah interesting (regarding the hex thing) Well to answer your question, yes it “includes” if includes means it shows as ONLINE in the things list after scanning and clicking “Add as Thing” (in openhab 3 which I think I failed to mention originally) but when i go to look at available channels to configure I always see “This thing has no channels. Either the thing type doesn’t define channels, or they may be detected and appear later.” even letting it sit for hours/days. Hence my question. Thank you for responding so quickly Bob.

anon71759204 · November 21, 2021, 8:45pm

Please post the XML file for your device (…/userdata/zwave/network_…xml). Before posting you might want to remove the homeID from the filename and from the file itself.

If the device identifies itself as FF00:FF0E, it should have channels, e.g.:

klee3d · November 21, 2021, 9:05pm

So here it is without my HomeID

NOTHINGTOSEEHERE

84

4

0x312

0xff0e

0xff00

true

false

true

false

true

40000

1000

<commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>

<commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>

<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>

<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>

<commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>

<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>

<commandClass>COMMAND_CLASS_METER</commandClass>

<commandClass>COMMAND_CLASS_ALARM</commandClass>

<commandClass>COMMAND_CLASS_TRANSPORT_SERVICE</commandClass>

<commandClass>COMMAND_CLASS_VERSION</commandClass>

<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>

<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>

<commandClass>COMMAND_CLASS_INDICATOR</commandClass>

<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>

<commandClass>COMMAND_CLASS_SECURITY_2</commandClass>

<commandClass>COMMAND_CLASS_SUPERVISION</commandClass>

<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>

<entry>

  <int>1</int>

  <associationGroup>

    <index>1</index>

    <maxNodes>0</maxNodes>

    <associations/>

  </associationGroup>

</entry>

<entry>

  <int>2</int>

  <associationGroup>

    <index>2</index>

    <maxNodes>0</maxNodes>

    <associations/>

  </associationGroup>

</entry>

<entry>

  <int>0</int>

  <endPoint>

    <deviceClass>

      <basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>

      <genericDeviceClass>GENERIC_TYPE_SWITCH_BINARY</genericDeviceClass>

      <specificDeviceClass>SPECIFIC_TYPE_NOT_USED</specificDeviceClass>

    </deviceClass>

    <endpointId>0</endpointId>

    <secureCommandClasses/>

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

      <entry>

        <commandClass>COMMAND_CLASS_BASIC</commandClass>

        <COMMAND__CLASS__BASIC>

          <version>1</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>2</versionSupported>

          <isGetSupported>true</isGetSupported>

        </COMMAND__CLASS__BASIC>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>

        <COMMAND__CLASS__CONFIGURATION>

          <version>1</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>4</versionSupported>

          <configParameters/>

        </COMMAND__CLASS__CONFIGURATION>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>

        <COMMAND__CLASS__MANUFACTURER__SPECIFIC>

          <version>1</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>2</versionSupported>

          <initSerialNumber>false</initSerialNumber>

          <deviceManufacturer>786</deviceManufacturer>

          <deviceType>65280</deviceType>

          <deviceId>65294</deviceId>

        </COMMAND__CLASS__MANUFACTURER__SPECIFIC>

      </entry>

      <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_INDICATOR</commandClass>

        <COMMAND__CLASS__INDICATOR>

          <version>3</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>3</versionSupported>

          <isGetSupported>true</isGetSupported>

          <supportedIndicatorsInitialised>true</supportedIndicatorsInitialised>

          <supportedIndicators>

            <ZWaveIndicator>

              <type>NODE_IDENTIFY</type>

            </ZWaveIndicator>

          </supportedIndicators>

        </COMMAND__CLASS__INDICATOR>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>

        <COMMAND__CLASS__ASSOCIATION__GRP__INFO>

          <version>1</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>3</versionSupported>

          <autoSubscribeGroups/>

        </COMMAND__CLASS__ASSOCIATION__GRP__INFO>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_ALARM</commandClass>

        <COMMAND__CLASS__ALARM>

          <version>8</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>8</versionSupported>

          <alarms>

            <entry>

              <alarmType>POWER_MANAGEMENT</alarmType>

              <alarmState>

                <alarmType>POWER_MANAGEMENT</alarmType>

                <reportedEvents/>

                <outer-class reference="../../../.."/>

              </alarmState>

            </entry>

          </alarms>

          <v1Supported>true</v1Supported>

          <isGetSupported>true</isGetSupported>

        </COMMAND__CLASS__ALARM>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_METER</commandClass>

        <COMMAND__CLASS__METER>

          <version>3</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>5</versionSupported>

          <meterType>ELECTRIC</meterType>

          <meterScales>

            <meterScale>E_W</meterScale>

            <meterScale>E_V</meterScale>

            <meterScale>E_KWh</meterScale>

            <meterScale>E_A</meterScale>

          </meterScales>

          <canReset>true</canReset>

          <isGetSupported>true</isGetSupported>

          <isSupportRequestSupported>true</isSupportRequestSupported>

        </COMMAND__CLASS__METER>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_VERSION</commandClass>

        <COMMAND__CLASS__VERSION>

          <version>2</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>3</versionSupported>

          <libraryType>LIB_SLAVE_ENHANCED</libraryType>

          <protocolVersion>7.13</protocolVersion>

          <applicationVersion>1.0</applicationVersion>

          <hardwareVersion>1</hardwareVersion>

        </COMMAND__CLASS__VERSION>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>

        <COMMAND__CLASS__DEVICE__RESET__LOCALLY>

          <version>1</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>1</versionSupported>

        </COMMAND__CLASS__DEVICE__RESET__LOCALLY>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>

        <COMMAND__CLASS__FIRMWARE__UPDATE__MD>

          <version>1</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>5</versionSupported>

        </COMMAND__CLASS__FIRMWARE__UPDATE__MD>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>

        <COMMAND__CLASS__POWERLEVEL>

          <version>1</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>1</versionSupported>

          <powerLevel>0</powerLevel>

          <powerTimeout>0</powerTimeout>

        </COMMAND__CLASS__POWERLEVEL>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>

        <COMMAND__CLASS__SWITCH__BINARY>

          <version>1</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>2</versionSupported>

          <isGetSupported>true</isGetSupported>

        </COMMAND__CLASS__SWITCH__BINARY>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>

        <COMMAND__CLASS__ZWAVEPLUS__INFO>

          <version>1</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>2</versionSupported>

          <zwPlusVersion>2</zwPlusVersion>

          <zwPlusRole>ROLE_TYPE_SLAVE_ALWAYS_ON</zwPlusRole>

          <zwPlusNodeType>NODE_TYPE_ZWAVEPLUS_NODE</zwPlusNodeType>

          <isGetSupported>true</isGetSupported>

        </COMMAND__CLASS__ZWAVEPLUS__INFO>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>

        <COMMAND__CLASS__MULTI__CHANNEL__ASSOCIATION>

          <version>3</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>4</versionSupported>

          <maxGroups>2</maxGroups>

        </COMMAND__CLASS__MULTI__CHANNEL__ASSOCIATION>

      </entry>

      <entry>

        <commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>

        <COMMAND__CLASS__ASSOCIATION>

          <version>2</version>

          <instances>1</instances>

          <control>false</control>

          <versionSupported>3</versionSupported>

          <maxGroups>2</maxGroups>

        </COMMAND__CLASS__ASSOCIATION>

      </entry>

    </supportedCommandClasses>

  </endPoint>

</entry>

2021-11-21 15:03:29.30 UTC

klee3d · November 21, 2021, 9:20pm

network__node_84 - Copy.xml (10.4 KB)

apella12 · November 21, 2021, 9:55pm

So the xml looks like there should be channels. Maybe something got hung up during initialization and maybe a communication issue. Could try reinitialize at the bottom of the Ui page of the thing.

Bob

Edit #1 Was working from my Ipad. Took a look at the Zwave database from my PC and had another thought. What date is on your zwave .jar? The device was just updated 11-16.

Edit#2 The latest .jar is here it contains the edits of the device from November 16, 2021.

anon71759204 · November 21, 2021, 10:40pm

As a last resort, you could do a factory reset:

Exclude/‘Remove the device from controller’:

Do a factory reset:

Remove the device from the socket, wait a few seconds, plug it into the socket.
Include/Add the device.

klee3d · November 22, 2021, 5:19pm

Well I tried the reset to factory defaults approach suggested by Ap15e but didnt work… turned debug mode on for the zwave log and this is what comes up when i chose to reinitialize device. Maybe it will provide a clue for you guys.

Zwave_Debug_log_reinitialize_node90.txt (214.7 KB)

apella12 · November 22, 2021, 10:12pm

I still think the latest snapshot .jar is the best shot. When things are modified in the device DB it is for a reason. If that doesn’t work the device may be defective. What version of OH3 are you on right now? Is the Zwave binding from the UI or do you have it in the addons?

Bob

anon71759204 · November 23, 2021, 1:02am

2021-11-22 12:10:52.246 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Checking zwave:leviton_vrcz4_00_000
2021-11-22 12:10:52.247 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Checking zwave:leviton_vrcz4_00_000
2021-11-22 12:10:52.247 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Checking zwave:leviton_vrcz4_00_000
2021-11-22 12:10:52.247 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 90: Unable to find thing type (0312:FF00:FF0E:1.0)

Your current Z-Wave Binding doesn’t support your device. Please upgrade to the latest snapshot: openHAB-ZWave [Jenkins] - you might have to wait for the next snapshot.

klee3d · November 23, 2021, 12:59pm

Well that did it. Thank you @anon71759204 and @apella12 for all the input. So I am wondering…what did you see in my Debug Log file that made you realize it was the binding that wasn’t up to date? Also I am curious, is the only way to stay up to date (at least for stable release bindings) is to do it through sudo openhabian-config ? I assume the main web UI for openhab3 will NOT show the user that there are newer versions of ones installed bindings?

apella12 · November 23, 2021, 3:39pm

I think @anon71759204 pointed out the Debug line. However, for me, although you never revealed the OH3 version or the Zwave .jar date, I strongly suspected the problem back at post #7 when I saw the device had been recently modified. When a device is modified, it is removed from any binding builds until those mods are approved. I looked at the recent DB changes and saw the device was restored with the build I referenced above. To be honest, I did not look to closely at your latest Debug file.

I can’t comment on other OH update methods. There are many depending on your setup. For Openhabian I think sudo openhabian-config is the supported way.

OH is in constant flux, but each build is a fixed point in time and is not patched or changed once built. There are daily snapshots with updates/changes.

As to zwave, the java part of the Zwave binding is very stable with very little change, however, the zwave binding is updated about 2x a week because of the DB changes. I make it a habit to check the approval dates on the devices I buy. If you buy the newest and latest, you might have to add it to the database and then update the .jar once it is approved. If it is an older device it will usually work on the last stable release (OH3.1 currently).

Glad you are up and running.

Bob

anon71759204 · November 23, 2021, 6:13pm

If a Z-Wave device is in the Z-Wave database (matching manufacturer ID, device type, device ID and version) and the Z-Wave binding nevertheless throws an Unable to find thing type error, chances are that it has been modified in the Z-Wave database, it is waiting for a review and it hasn’t made it into the latest snapshot.