[SOLVED] Z-Wave unreliable in 2.5.0.M4

Add-ons Bindings
142

.

I’ve checked all XML files again. It seems to be mixture of old and new binding.

I have 5 identical “Smoke Sensors” (same firmware/type) (=node3, 4, 5, 6, 7) and 3 identical “Motion Sensors” (same firmware/type) (=node 8, 9, 10).

But there are a lot of differences between the XML files. While node3, 4, 5, 7 have almost the same entries, in node6 the following is missing:

  <associationGroups class="concurrent-hash-map">
    <entry>
      <int>1</int>
      <associationGroup>
        <index>1</index>
        <maxNodes>0</maxNodes>
 !!       <name>Lifeline</name>
 !!       <profile1>0x0</profile1>
 !!       <profile2>0x1</profile2>
 !!       <commands>
 !!         <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
 !!         <commandClass>COMMAND_CLASS_BATTERY</commandClass>
 !!         <commandClass>COMMAND_CLASS_ALARM</commandClass>
 !!         <commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>
 !!         <commandClass>COMMAND_CLASS_SENSOR_BINARY</commandClass>
 !!       </commands>
 $       <associations>
 $         <associationMember>
 $           <node>1</node>
 $         </associationMember>
        </associations>
      </associationGroup>
    </entry>
    <entry>
      <int>2</int>
      <associationGroup>
        <index>2</index>
        <maxNodes>0</maxNodes>
 !!       <name>Smoke alarm action</name>
 !!       <profile1>0x71</profile1>
 !!       <profile2>0x1</profile2>
 !!       <commands>
 !!         <commandClass>COMMAND_CLASS_ALARM</commandClass>
 !!       </commands>
        <associations/>
      </associationGroup>
    </entry>
    <entry>
      <int>3</int>
      <associationGroup>
        <index>3</index>
        <maxNodes>0</maxNodes>
!!        <name>Smoke basic action</name>
!!        <profile1>0x71</profile1>
!!        <profile2>0x1</profile2>
!!        <commands>
!!          <commandClass>COMMAND_CLASS_BASIC</commandClass>
!!        </commands>
        <associations/>
      </associationGroup>
    </entry>
  </associationGroups>


<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>
 !!            <int>1</int>
 !!            <int>2</int>
         </autoSubscribeGroups>
     </COMMAND__CLASS__ASSOCIATION__GRP__INFO>
</entry>

   <entry>
    </entry>
 §    <commandClass>COMMAND_CLASS_SECURITY</commandClass>
 §    <COMMAND__CLASS__SECURITY>
 §       <version>1</version>
 §       <instances>1</instances>
 §       <control>false</control>
 §       <versionSupported>1</versionSupported>
 §    </COMMAND__CLASS__SECURITY>
 §   </entry>
 § <entry>

.
You can see the missing entries (node6) by the two exclamation marks → !!

And it was missing the “lifeline node” in node4 and 5: see → $

And in node3 was missing “COMMAND_CLASS_SECURITY”: see → §
.
.
Following is missing in node8 and node10:

<entry>
  <multilevelSensorType>DEW_POINT</multilevelSensorType>
  <multilevelSensor>
     <sensorType>DEW_POINT</sensorType>
     <initialised>false</initialised>
  </multilevelSensor>
</entry>

node9 contains above entry . DEW_POINT ?? How comes??
.
.

I then have done a “Reinitialise Device”. Now the entries are all the same for each “device group”.

Wonder why the entries were different. Have deleted the things many times with PaperUI or have reinitialised the nodes (many times).

Next step will be: testing “daily heal” again with “zwave binding 1731”, but now with correct initialised nodes…

To be continued.