The first step should be to check the zwave device database list and compare.
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list
@Bruce_Osborne To your point, the 3 similar dimmer switches show as ZW500DM in their properties, and in the database there is only the ZW500DM listed; however, there are Enerwave devices that all share the same config and work perfect such as my ZW15R and ZW15RM show up as their ZW20R and ZW20RM counterparts. Looking at the manuals, the configuration items are the same as far as I can tell, so the only difference is that the devices not working are zwave plus. I’m not familiar enough with the binding config to determine what can be changed to fix this, I searched though the community for help on this, and played around with the config for the last couple weeks with no luck.
I am assuming the Binding knows this is zwave plus based on info from the controller as the database doesn’t have the plus version, and it shows zwave_plus in the properties in the below screenshot.
Looking at the XML files below, and from what I’ve learned over the last week, I’m guessing it has something to do with the fact that the device meters not working do not have the COMMAND_CLASS_SENSOR_MULTILEVEL command class in the XML, but this is only speculation since I’m not too familiar. As can be seen in my XML files for the ZW500DM has this class (as do my other Enerwave meter devices), where as the ZW500DM-PLUS and ZW15SM-PLUS XML files do not.
EDITED XML FILES 2019-07-19 10:34 PM PT
ZW500DM (NON PLUS)
<node>
<homeId>xxxxxxxxxx</homeId>
<nodeId>6</nodeId>
<version>4</version>
<manufacturer>0x11a</manufacturer>
<deviceId>0x201</deviceId>
<deviceType>0x111</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_ALL</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_METER</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_SENSOR_MULTILEVEL</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map">
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<endpoints class="concurrent-hash-map">
<entry>
<int>0</int>
<endPoint>
<deviceClass>
<basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>GENERIC_TYPE_SWITCH_MULTILEVEL</genericDeviceClass>
<specificDeviceClass>SPECIFIC_TYPE_POWER_SWITCH_MULTILEVEL</specificDeviceClass>
</deviceClass>
<endpointId>0</endpointId>
<secureCommandClasses/>
<supportedCommandClasses class="concurrent-hash-map">
<entry>
<commandClass>COMMAND_CLASS_SWITCH_ALL</commandClass>
<COMMAND__CLASS__SWITCH__ALL>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
<mode>SWITCH_ALL_INCLUDE_ON_OFF</mode>
</COMMAND__CLASS__SWITCH__ALL>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SENSOR_MULTILEVEL</commandClass>
<COMMAND__CLASS__SENSOR__MULTILEVEL>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<sensors>
<entry>
<multilevelSensorType>POWER</multilevelSensorType>
<multilevelSensor>
<sensorType>POWER</sensorType>
<initialised>true</initialised>
</multilevelSensor>
</entry>
</sensors>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__SENSOR__MULTILEVEL>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<COMMAND__CLASS__ASSOCIATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<maxGroups>1</maxGroups>
</COMMAND__CLASS__ASSOCIATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<COMMAND__CLASS__CONFIGURATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<configParameters>
<entry>
<int>1</int>
<configurationParameter>
<index>1</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>8</int>
<configurationParameter>
<index>8</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>9</int>
<configurationParameter>
<index>9</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>10</int>
<configurationParameter>
<index>10</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>11</int>
<configurationParameter>
<index>11</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>12</int>
<configurationParameter>
<index>12</index>
<size>1</size>
<value>10</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
</configParameters>
</COMMAND__CLASS__CONFIGURATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<COMMAND__CLASS__VERSION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<libraryType>LIB_SLAVE_ROUTING</libraryType>
<protocolVersion>3.42</protocolVersion>
<applicationVersion>1.2</applicationVersion>
</COMMAND__CLASS__VERSION>
</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_BASIC</commandClass>
<COMMAND__CLASS__BASIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__BASIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<COMMAND__CLASS__MANUFACTURER__SPECIFIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>282</deviceManufacturer>
<deviceType>273</deviceType>
<deviceId>513</deviceId>
</COMMAND__CLASS__MANUFACTURER__SPECIFIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_METER</commandClass>
<COMMAND__CLASS__METER>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<meterType>ELECTRIC</meterType>
<meterScales>
<meterScale>E_KWh</meterScale>
<meterScale>E_W</meterScale>
</meterScales>
<canReset>true</canReset>
<isGetSupported>true</isGetSupported>
<isSupportRequestSupported>true</isSupportRequestSupported>
</COMMAND__CLASS__METER>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
<multiLevelSwitchCommandClass>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</multiLevelSwitchCommandClass>
</entry>
</supportedCommandClasses>
</endPoint>
</entry>
</endpoints>
<nodeNeighbors>
<int>1</int>
<int>2</int>
<int>4</int>
<int>9</int>
<int>12</int>
<int>13</int>
<int>20</int>
<int>21</int>
<int>23</int>
<int>33</int>
<int>37</int>
</nodeNeighbors>
<lastReceived>2019-07-19 03:31:30.124 UTC</lastReceived>
</node>
ZW500DM-PLUS XML File
<node>
<homeId>xxxxxxxxxx</homeId>
<nodeId>21</nodeId>
<version>4</version>
<manufacturer>0x11a</manufacturer>
<deviceId>0x201</deviceId>
<deviceType>0x111</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_ZWAVEPLUS_INFO</commandClass>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<commandClass>COMMAND_CLASS_METER</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_ALL</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map">
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<maxNodes>0</maxNodes>
<associations>
<associationMember>
<node>1</node>
</associationMember>
</associations>
</associationGroup>
</entry>
<entry>
<int>2</int>
<associationGroup>
<index>2</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
<entry>
<int>3</int>
<associationGroup>
<index>3</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<endpoints class="concurrent-hash-map">
<entry>
<int>0</int>
<endPoint>
<deviceClass>
<basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>GENERIC_TYPE_SWITCH_MULTILEVEL</genericDeviceClass>
<specificDeviceClass>SPECIFIC_TYPE_POWER_SWITCH_MULTILEVEL</specificDeviceClass>
</deviceClass>
<endpointId>0</endpointId>
<secureCommandClasses/>
<supportedCommandClasses class="concurrent-hash-map">
<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_ALL</commandClass>
<COMMAND__CLASS__SWITCH__ALL>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
<mode>SWITCH_ALL_INCLUDE_ON_OFF</mode>
</COMMAND__CLASS__SWITCH__ALL>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<COMMAND__CLASS__ASSOCIATION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<maxGroups>3</maxGroups>
</COMMAND__CLASS__ASSOCIATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<COMMAND__CLASS__VERSION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<libraryType>LIB_SLAVE_ROUTING</libraryType>
<protocolVersion>4.24</protocolVersion>
<applicationVersion>5.11</applicationVersion>
<hardwareVersion>1</hardwareVersion>
</COMMAND__CLASS__VERSION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_BASIC</commandClass>
<COMMAND__CLASS__BASIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__BASIC>
</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>282</deviceManufacturer>
<deviceType>273</deviceType>
<deviceId>513</deviceId>
</COMMAND__CLASS__MANUFACTURER__SPECIFIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_METER</commandClass>
<COMMAND__CLASS__METER>
<version>3</version>
<instances>1</instances>
<control>false</control>
<versionSupported>3</versionSupported>
<meterType>ELECTRIC</meterType>
<meterScales>
<meterScale>E_KWh</meterScale>
<meterScale>E_W</meterScale>
</meterScales>
<canReset>true</canReset>
<isGetSupported>true</isGetSupported>
<isSupportRequestSupported>true</isSupportRequestSupported>
</COMMAND__CLASS__METER>
</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>1</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_SWITCH_MULTILEVEL</commandClass>
<multiLevelSwitchCommandClass>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<isGetSupported>true</isGetSupported>
</multiLevelSwitchCommandClass>
</entry>
<entry>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<COMMAND__CLASS__CONFIGURATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<configParameters>
<entry>
<int>1</int>
<configurationParameter>
<index>1</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
</configParameters>
</COMMAND__CLASS__CONFIGURATION>
</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_ASSOCIATION_GRP_INFO</commandClass>
<COMMAND__CLASS__ASSOCIATION__GRP__INFO>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<autoSubscribeGroups/>
</COMMAND__CLASS__ASSOCIATION__GRP__INFO>
</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>
</supportedCommandClasses>
</endPoint>
</entry>
</endpoints>
<nodeNeighbors>
<int>1</int>
<int>2</int>
<int>4</int>
<int>6</int>
<int>7</int>
<int>8</int>
<int>9</int>
<int>10</int>
<int>11</int>
<int>12</int>
<int>13</int>
<int>19</int>
<int>20</int>
<int>23</int>
<int>37</int>
</nodeNeighbors>
<lastReceived>2019-07-19 03:33:35.577 UTC</lastReceived>
</node>
ZR15SM-PLUS XML File
<node>
<homeId>xxxxxxxxxx</homeId>
<nodeId>33</nodeId>
<version>4</version>
<manufacturer>0x11a</manufacturer>
<deviceId>0x102</deviceId>
<deviceType>0x111</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_ZWAVEPLUS_INFO</commandClass>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>
<commandClass>COMMAND_CLASS_METER</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_ALL</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map">
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<maxNodes>0</maxNodes>
<associations>
<associationMember>
<node>1</node>
</associationMember>
</associations>
</associationGroup>
</entry>
<entry>
<int>2</int>
<associationGroup>
<index>2</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
<entry>
<int>3</int>
<associationGroup>
<index>3</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
<entry>
<int>4</int>
<associationGroup>
<index>4</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<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_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_ALL</commandClass>
<COMMAND__CLASS__SWITCH__ALL>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
<mode>SWITCH_ALL_INCLUDE_ON_OFF</mode>
</COMMAND__CLASS__SWITCH__ALL>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<COMMAND__CLASS__ASSOCIATION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<maxGroups>4</maxGroups>
</COMMAND__CLASS__ASSOCIATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>
<COMMAND__CLASS__SWITCH__BINARY>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__SWITCH__BINARY>
</entry>
<entry>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<COMMAND__CLASS__VERSION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<libraryType>LIB_SLAVE_ROUTING</libraryType>
<protocolVersion>4.24</protocolVersion>
<applicationVersion>5.11</applicationVersion>
<hardwareVersion>1</hardwareVersion>
</COMMAND__CLASS__VERSION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_BASIC</commandClass>
<COMMAND__CLASS__BASIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__BASIC>
</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>282</deviceManufacturer>
<deviceType>273</deviceType>
<deviceId>258</deviceId>
</COMMAND__CLASS__MANUFACTURER__SPECIFIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_METER</commandClass>
<COMMAND__CLASS__METER>
<version>3</version>
<instances>1</instances>
<control>false</control>
<versionSupported>3</versionSupported>
<meterType>ELECTRIC</meterType>
<meterScales>
<meterScale>E_KWh</meterScale>
<meterScale>E_W</meterScale>
</meterScales>
<canReset>true</canReset>
<isGetSupported>true</isGetSupported>
<isSupportRequestSupported>true</isSupportRequestSupported>
</COMMAND__CLASS__METER>
</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>1</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_CONFIGURATION</commandClass>
<COMMAND__CLASS__CONFIGURATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<configParameters>
<entry>
<int>1</int>
<configurationParameter>
<index>1</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
</configParameters>
</COMMAND__CLASS__CONFIGURATION>
</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_ASSOCIATION_GRP_INFO</commandClass>
<COMMAND__CLASS__ASSOCIATION__GRP__INFO>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<autoSubscribeGroups/>
</COMMAND__CLASS__ASSOCIATION__GRP__INFO>
</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>
</supportedCommandClasses>
</endPoint>
</entry>
</endpoints>
<nodeNeighbors>
<int>2</int>
<int>4</int>
<int>6</int>
<int>11</int>
<int>23</int>
<int>37</int>
</nodeNeighbors>
<lastReceived>2019-07-19 05:19:30.175 UTC</lastReceived>
</node>
@chris or @sihui
To my eyes the xml files all look like 011a:0111:0102 with same firmware version 4 but different command classes.
Is that even be permitted by the Z-Wave specification?
ZW500DM-PLUS XML File
<manufacturer>0x11a</manufacturer>
<deviceId>0x201</deviceId>
<deviceType>0x111</deviceType>
<applicationVersion>1.2</applicationVersion>
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/382
Looks good to me
ZR15SM-PLUS XML File
<manufacturer>0x11a</manufacturer>
<deviceId>0x102</deviceId>
<deviceType>0x111</deviceType>
<applicationVersion>5.11</applicationVersion>
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/640
Looks good to me.
ZW500DM (NON PLUS)
<manufacturer>0x11a</manufacturer>
<deviceId>0x201</deviceId>
<deviceType>0x111</deviceType>
<applicationVersion>5.11</applicationVersion>
Is a different device from the one in the database, so needs to be added with a separate firmware version.
1 Like
@sihui the ZW500DM is the one that works all around, it dims, switches, gives readings for power, kwh, and watts. The ZW500DM-PLUS and the ZW15SM-PLUS work for the switch/dimmer, but do not give readings for power, kwh, or watts.
Make sure to set the correct association groups.
It is very unlikely that the manufacturer lowered the application version for a new plus device:
ZW500DM-PLUS XML File
<applicationVersion>1.2</applicationVersion>
ZW500DM (NON PLUS)
<applicationVersion>5.11</applicationVersion>
But if that is the case it still needs to be added to the database if command classes are different.
This is my fault, I think I mislabeled the XML Files in the above post, let me edit. I just seen that the one labeled NON-PLUS has the PLUS command set, I’ll re-paste them to be safe.
I think that is one of the things I tried, but I have reset it to controller on all 3 options, and will see if that makes a difference.
ZW500DM-PLUS
ZW15SM-PLUS
As you now know where to look I’m sure you will figure out yourself what needs to be changed in the database.
I’ve modified the post above with the right XML. I’m looking in the userdata/zwave folder for the devices XMLs. Can I manipulate the local database to test? The only thing I see that that is missing on the PLUS XML is the COMMAND_CLASS_SENSOR_MULTILEVEL, but that’s a guess, is this required for the sensors to work? If so, why would it be in the configuration for the ZW500DM and not the ZW500DM-PLUS when they both use the same database entry (both seem to be labeled ZW500DM).
After making the changes by assigning the Association Groups to the Controller, still not giving any meter readings. Also, you can see the second ZW15SM-PLUS doesn’t have a Power Sensor channel.
ZW500DM-PLUS
ZW15SM-PLUS
ZW500DM (NON-PLUS) WORKING METER
Yes.
1 Like
OK I searched but my old eyes missed the firmware version entries even though I was looking for something like that. Sorry.
1 Like
Thanks @sihui that is very informative, and once I get an understanding of the config and all I will have some fun altering and updating XMLs. As for the problem at hand, after finding the actual database XML, I do not know what would be wrong. I compared this XML to other Plus devices that work on my network as meters, and they look similar for the channel setup, any ideas? Is there a specific setting for Plus devices?
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0"
xsi:schemaLocation="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0
http://eclipse.org/smarthome/schemas/thing-description/v1.0.0">
<thing-type id="enerwave_zw500dm_00_000" listed="false">
<label>ZW500DM In-wall Smart Meter Dimmer Switch</label>
<description><![CDATA[
In-wall Smart Meter Dimmer Switch<br /><h1>Overview</h1><p>The ZW500DM Dimmer Switch is a perfect wireless manual and remote on/off/ dim brightness control replacement of regular switch, controlling incandescent, dimmable LED and CFL. This ZW500DM dimmer switch is fully compatible with other Z-Wave devices, provides programmable function creating a perfect ambiance such as scenes, association, schedule event, etc. Also it can be added to most Z-Wave compliant controllers.</p> <p>Sliding Air-Gap switch to totally disconnect power while replacing light bulbs and preventing from leakage current from the fixture(s). This ZW500DM dimmer works with ZW3K 3-Way Auxiliary Switch that reduces energy consumption, enhancing the value of technology of your home, condominiums and apartment.</p> <p>Features -:</p> <ul><li>Perfect Replacement for regular wall ON/OFF & Dim switch, 120VAC</li> <li>Wireless Z-Wave technology creates a mesh network for command and control interoperability with other Z-Wave compliant controller and devices</li> <li>Manual and Remote ON/OFF& Dim control of any permanently installed incandescent, dimmable LED and CFL lamp fixture</li> <li>Preset light level option allows the dimmer will turn on to the light level that it was adjusted to the previous time when the light was on</li> <li>Can be used for single pole or 3- Way (Multi-location) with ZW3K Auxiliary Switch (sold separately)</li> <li>Measures energy usage of the wired load</li> </ul><p>The ZW500DM Smart Meter Dimmer Switch enables you to measure the energy usage of your appliance. When added to a Z-Wave network, the ZW500DM reports real time data to your gateway or controller. It can also display actual consumption (in W) and the accumulated power used (in kWh) in the user interface of the gateway/remote. Please use the gateway installation manual for specific instructions on measuring the power.</p> <br /><h2>Inclusion Information</h2><p>When the primary controller is in the adding mode, flicks the paddle 3 times in the 1.5 second. The primary controller will verify the adding, assign a node ID number for the module.</p> <br /><h2>Exclusion Information</h2><p>When the primary controller is in the removing mode, flicks the paddle 3 times in the 1.5 second. The primary controller will verify the removing, remove the module from the current Z-Wave network, and the LED will blink when the module is on power.</p>
]]></description>
<category>WallSwitch</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_dimmer" typeId="switch_dimmer">
<label>Dimmer</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
</properties>
</channel>
<channel id="sensor_power" typeId="sensor_power">
<label>Sensor (power)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=POWER</property>
</properties>
</channel>
<channel id="meter_kwh" typeId="meter_kwh">
<label>Electric meter (kWh)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_KWh</property>
</properties>
</channel>
<channel id="meter_watts" typeId="meter_watts">
<label>Electric meter (watts)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_W</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Wenzhou MTLC Electric Appliances Co.,Ltd.</property>
<property name="modelId">ZW500DM</property>
<property name="manufacturerId">011A</property>
<property name="manufacturerRef">0111:0201</property>
<property name="dbReference">382</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration">
<label>1: LED is on when load is on</label>
<description>Synchronization of load power and LED indicator</description>
<default>0</default>
<options>
<option value="0">Power on, LED off</option>
<option value="1">Power on, LED on</option>
</options>
</parameter>
<parameter name="config_8_1" type="integer" groupName="configuration"
min="0" max="255">
<label>8: Instant Energy Autosend Interval</label>
<description>Instant Energy Autosend Interval (send METER_REPORT)</description>
<default>0</default>
</parameter>
<parameter name="config_9_1" type="integer" groupName="configuration"
min="0" max="255">
<label>9: Instant Power Autosend Interval</label>
<description>Instant Power Autosend interval (send SENSOR_MULTILEVEL_REPORT)</description>
<default>0</default>
</parameter>
<parameter name="config_10_1" type="integer" groupName="configuration"
min="0" max="255">
<label>10: Accumulated Energy Autosend Interval</label>
<description>Accumulated Energy Autosend Interval report (send METER_REPORT)</description>
<default>0</default>
</parameter>
<parameter name="config_11_1" type="integer" groupName="configuration">
<label>11: Enable automatic notifications</label>
<description><![CDATA[
Enable automatic notifications to associated device<br /><h1>Overview</h1><p>Device will send a notification whenever the is a wattage change</p>
]]></description>
<default>1</default>
<options>
<option value="0">Not report (METER_REPORT)</option>
<option value="1">Send (METER_REPORT) only</option>
<option value="2">Send (SENSOR_MULTI_LEVEL_REPORT) only</option>
<option value="3">Send both</option>
</options>
</parameter>
<parameter name="config_12_1" type="integer" groupName="configuration"
min="0" max="255">
<label>12: Minimum change in wattage triggering report</label>
<description><![CDATA[
Minimum change in wattage report<br /><h1>Overview</h1><p>0-255: 0.0-25.5W</p>
]]></description>
<default>10</default>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Notifications</label>
<description>Lifeline</description>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: StatusReport</label>
<description>Send basic report</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: PowerReport</label>
<description>PowerReport: Send meter power report</description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>
The XML files on your computer are auto generated as startup cache. They are not designed to be altered manually.
The real definitions are in the device database. You need to add a new entry for the new device firmware.
Here is one of your devices that works
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/382
You need to add a different database entry for the newer firmware.
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide
Thx @Bruce_Osborne, I created one locally to test earlier using the method @sihui posted, but didn’t have a clue what to change since everything looked good except obviously the name. I’ll try changing the firmware version and see if that helps, and I’ll add it to the online database after I confirm it works.
Ok, so I’ve read through the Device Database Guide, and it explicitly says, “If you have a different version of a device in the database, before adding another entry to the database, check that the association group configuration, parameters, and channels are the same. If they are, then it is only needed to update the device IDs of the existing device. If there is a new version required because the above data has changed, then first edit the exiting devices versions so that it does not conflict with the new device, then you can add the new device.”
Do I have to create a new device if they are basically the same? There is a single association group, and the 6 configuration parameters that match as far as I can tell. I’m not sure what would be required to change, and I don’t have the Add button yet after registering, ticket added for access.
ZW500DM Manual
ZW500DM-PLUS
ZW500DM Database XML
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0"
xsi:schemaLocation="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0
http://eclipse.org/smarthome/schemas/thing-description/v1.0.0">
<thing-type id="enerwave_zw500dm_00_000" listed="false">
<label>ZW500DM In-wall Smart Meter Dimmer Switch</label>
<description><![CDATA[
In-wall Smart Meter Dimmer Switch<br /><h1>Overview</h1><p>The ZW500DM Dimmer Switch is a perfect wireless manual and remote on/off/ dim brightness control replacement of regular switch, controlling incandescent, dimmable LED and CFL. This ZW500DM dimmer switch is fully compatible with other Z-Wave devices, provides programmable function creating a perfect ambiance such as scenes, association, schedule event, etc. Also it can be added to most Z-Wave compliant controllers.</p> <p>Sliding Air-Gap switch to totally disconnect power while replacing light bulbs and preventing from leakage current from the fixture(s). This ZW500DM dimmer works with ZW3K 3-Way Auxiliary Switch that reduces energy consumption, enhancing the value of technology of your home, condominiums and apartment.</p> <p>Features -:</p> <ul><li>Perfect Replacement for regular wall ON/OFF & Dim switch, 120VAC</li> <li>Wireless Z-Wave technology creates a mesh network for command and control interoperability with other Z-Wave compliant controller and devices</li> <li>Manual and Remote ON/OFF& Dim control of any permanently installed incandescent, dimmable LED and CFL lamp fixture</li> <li>Preset light level option allows the dimmer will turn on to the light level that it was adjusted to the previous time when the light was on</li> <li>Can be used for single pole or 3- Way (Multi-location) with ZW3K Auxiliary Switch (sold separately)</li> <li>Measures energy usage of the wired load</li> </ul><p>The ZW500DM Smart Meter Dimmer Switch enables you to measure the energy usage of your appliance. When added to a Z-Wave network, the ZW500DM reports real time data to your gateway or controller. It can also display actual consumption (in W) and the accumulated power used (in kWh) in the user interface of the gateway/remote. Please use the gateway installation manual for specific instructions on measuring the power.</p> <br /><h2>Inclusion Information</h2><p>When the primary controller is in the adding mode, flicks the paddle 3 times in the 1.5 second. The primary controller will verify the adding, assign a node ID number for the module.</p> <br /><h2>Exclusion Information</h2><p>When the primary controller is in the removing mode, flicks the paddle 3 times in the 1.5 second. The primary controller will verify the removing, remove the module from the current Z-Wave network, and the LED will blink when the module is on power.</p>
]]></description>
<category>WallSwitch</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_dimmer" typeId="switch_dimmer">
<label>Dimmer</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
</properties>
</channel>
<channel id="sensor_power" typeId="sensor_power">
<label>Sensor (power)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=POWER</property>
</properties>
</channel>
<channel id="meter_kwh" typeId="meter_kwh">
<label>Electric meter (kWh)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_KWh</property>
</properties>
</channel>
<channel id="meter_watts" typeId="meter_watts">
<label>Electric meter (watts)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_W</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Wenzhou MTLC Electric Appliances Co.,Ltd.</property>
<property name="modelId">ZW500DM</property>
<property name="manufacturerId">011A</property>
<property name="manufacturerRef">0111:0201</property>
<property name="dbReference">382</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration">
<label>1: LED is on when load is on</label>
<description>Synchronization of load power and LED indicator</description>
<default>0</default>
<options>
<option value="0">Power on, LED off</option>
<option value="1">Power on, LED on</option>
</options>
</parameter>
<parameter name="config_8_1" type="integer" groupName="configuration"
min="0" max="255">
<label>8: Instant Energy Autosend Interval</label>
<description>Instant Energy Autosend Interval (send METER_REPORT)</description>
<default>0</default>
</parameter>
<parameter name="config_9_1" type="integer" groupName="configuration"
min="0" max="255">
<label>9: Instant Power Autosend Interval</label>
<description>Instant Power Autosend interval (send SENSOR_MULTILEVEL_REPORT)</description>
<default>0</default>
</parameter>
<parameter name="config_10_1" type="integer" groupName="configuration"
min="0" max="255">
<label>10: Accumulated Energy Autosend Interval</label>
<description>Accumulated Energy Autosend Interval report (send METER_REPORT)</description>
<default>0</default>
</parameter>
<parameter name="config_11_1" type="integer" groupName="configuration">
<label>11: Enable automatic notifications</label>
<description><![CDATA[
Enable automatic notifications to associated device<br /><h1>Overview</h1><p>Device will send a notification whenever the is a wattage change</p>
]]></description>
<default>1</default>
<options>
<option value="0">Not report (METER_REPORT)</option>
<option value="1">Send (METER_REPORT) only</option>
<option value="2">Send (SENSOR_MULTI_LEVEL_REPORT) only</option>
<option value="3">Send both</option>
</options>
</parameter>
<parameter name="config_12_1" type="integer" groupName="configuration"
min="0" max="255">
<label>12: Minimum change in wattage triggering report</label>
<description><![CDATA[
Minimum change in wattage report<br /><h1>Overview</h1><p>0-255: 0.0-25.5W</p>
]]></description>
<default>10</default>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Notifications</label>
<description>Lifeline</description>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: StatusReport</label>
<description>Send basic report</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: PowerReport</label>
<description>PowerReport: Send meter power report</description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>
When I did mine. @sihui copied the old sensor & edited the old one to not conflict. I then worked from the new copy, with a higher firmware revision required.
As I wrote earlier, you need to create a new device if command classes which lead to channels are different and if more or less config parameters are present.
As you did not post correct contents of your xml files I won’t touch this issue unless you explicitly post your xml file which needs to be added.
1 Like
A follow-up, so it’s partially working. I didn’t make any changes to the database XML. The only thing I did yesterday was set the configuration parameters Association Groups to the controller (Notifications, StatusReport, PowerReport), this didn’t do anything immediately, but it did start reporting after I restarted (for another reason). As of now it’s reporting both Watts and kWh, but not Power (Number doesn’t look like Power Factor, know what it is?); however, this may eventually start reporting maybe?
ZW500DM-PLUS (Watts/kWh working, Power not working)
Reading the ZW500DM-PLUS Manual I don’t even see where it says it sends anything other than kWh and Watts, but on the ZW500DM it is reporting a number.
“Meter Switch enables you to measure the energy usage of your Lights. When added to a Z-Wave network, the ZW500DM-PLUS reports real time data to your gateway or controller. It can also display actual consumption (in W) and the accumulated power used (in kWh) in the user interface depending on the Hub. Please refer to your Hub manual for specific instructions on measuring the power.”
###############################################################
Just some extra info and a better understanding for me, below is my ZW500DM (non-Plus) with all 3 readings, but I’m not sure what Power is supposed to be as at 100% dimmer it says it’s using 21.4 Power and 21.4 Watts, but at 23% dimmer it is 12.5 Power and 8.6 Watts. I don’t think this could be power factor, so does anyone know what “Power” is supposed to be?
ZW500DM (Non-Plus Version)
ZW20RM is reporting the numbers below, quite different from the dimmer, so hopefully someone can answer what the “Power” number is.
