What to do with new product definition file?

My Greenwave Powernode-1 NS310F shows up in habmin as node 4, NS210. I see this post where a request was to put the ns310-info in the product database. But until that is done, how do I do this myself? I found the new xml here.
I already tried to put this into the xml-file /var/lib/openhab/zwave/node4.xml but this is overwritten as soon as habmin detects the node as NS210 again.
What should I do?

Please can you provide the device type and device ID that HABmin should report - or post the XML file (node4) here.

Note that the node4 XML file that you mention is not the same format etc as the ones in the database, so you can’t replace them like you’re trying to do. They both serve different functions…

@chris Here is my node4.xml from /var/lib/openhab/zwave:

<node>
  <deviceClass>
    <basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
    <genericDeviceClass>BINARY_SWITCH</genericDeviceClass>
    <specificDeviceClass>POWER_SWITCH_BINARY</specificDeviceClass>
  </deviceClass>
  <homeId>0xe9348327</homeId>
  <nodeId>4</nodeId>
  <version>4</version>
  <name>Schakelaar vloerverwarming</name>
  <location>trapkast</location>
  <manufacturer>0x99</manufacturer>
  <deviceId>0x2</deviceId>
  <deviceType>0x2</deviceType>
  <listening>true</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <supportedCommandClasses>
    <entry>
      <commandClass>ASSOCIATION</commandClass>
      <associationCommandClass>
        <version>1</version>
        <instances>1</instances>
        <configAssociations/>
        <maxGroups>4</maxGroups>
      </associationCommandClass>
    </entry>
    <entry>
      <commandClass>NO_OPERATION</commandClass>
      <noOperationCommandClass>
        <version>1</version>
        <instances>1</instances>
      </noOperationCommandClass>
    </entry>
    <entry>
      <commandClass>ALARM</commandClass>
      <alarmCommandClass>
        <version>1</version>
        <instances>1</instances>
        <alarms/>
        <isGetSupported>true</isGetSupported>
      </alarmCommandClass>
    </entry>
    <entry>
      <commandClass>CRC_16_ENCAP</commandClass>
      <crc16EncapsulationCommandClass>
        <version>1</version>
        <instances>1</instances>
      </crc16EncapsulationCommandClass>
    </entry>
    <entry>
      <commandClass>METER</commandClass>
      <meterCommandClass>
        <version>2</version>
        <instances>1</instances>
        <meterType>ELECTRIC</meterType>
        <meterScales>
          <meterScale>E_KWh</meterScale>
          <meterScale>E_W</meterScale>
        </meterScales>
        <canReset>true</canReset>
        <isGetSupported>true</isGetSupported>
        <isSupportRequestSupported>true</isSupportRequestSupported>
      </meterCommandClass>
    </entry>
    <entry>
      <commandClass>CONFIGURATION</commandClass>
      <configurationCommandClass>
        <version>1</version>
        <instances>1</instances>
        <configParameters>
          <entry>
            <int>1</int>
            <configurationParameter>
              <index>1</index>
              <size>1</size>
              <value>2</value>
              <readOnly>false</readOnly>
              <writeOnly>false</writeOnly>
            </configurationParameter>
          </entry>
          <entry>
            <int>2</int>
            <configurationParameter>
              <index>2</index>
              <size>1</size>
              <value>-127</value>
              <readOnly>false</readOnly>
              <writeOnly>false</writeOnly>
            </configurationParameter>
          </entry>
        </configParameters>
      </configurationCommandClass>
    </entry>
    <entry>
      <commandClass>SWITCH_BINARY</commandClass>
      <binarySwitchCommandClass>
        <version>1</version>
        <instances>1</instances>
        <isGetSupported>true</isGetSupported>
      </binarySwitchCommandClass>
    </entry>
    <entry>
      <commandClass>VERSION</commandClass>
      <versionCommandClass>
        <version>1</version>
        <instances>1</instances>
        <libraryType>LIB_SLAVE_ENHANCED</libraryType>
        <protocolVersion>3.33</protocolVersion>
        <applicationVersion>4.21</applicationVersion>
      </versionCommandClass>
    </entry>
    <entry>
      <commandClass>BASIC</commandClass>
      <basicCommandClass>
        <version>1</version>
        <instances>1</instances>
        <isGetSupported>true</isGetSupported>
      </basicCommandClass>
    </entry>
    <entry>
      <commandClass>MANUFACTURER_SPECIFIC</commandClass>
      <manufacturerSpecificCommandClass>
        <version>1</version>
        <instances>1</instances>
      </manufacturerSpecificCommandClass>
    </entry>
  </supportedCommandClasses>
  <nodeNeighbors>
    <int>1</int>
    <int>3</int>
  </nodeNeighbors>
  <lastSent>2016-02-27 14:45:58.363 UTC</lastSent>
  <lastReceived>2016-02-27 14:45:58.407 UTC</lastReceived>
  <applicationUpdateReceived>true</applicationUpdateReceived>
</node>

That explains a lot :wink:

I’m not sure of the difference between the 210 and the 310 to be honest - the manual doesn’t make it too clear… In the online database (which will become the master), they have been renamed as below -:

Other than the name, does it make any difference?

Ok,
I walked through both the 210- and the 310-xml at github, and it looks like you are right. The only difference is the name 210/310 and the version number. I thought maybe my errors in the log file and problems making the items-file were coming from this 210/310-version problem. But since they are the same, that is just nonsense. I will concentrate on the items file now and see if I get things going from there. Thanks for your help!