Implement direction and command Sensor Data differentiation

[anesmemisevic]

It's possible to differentiate between different sensor data sets according to the direction/command provided.
Applicable to a low number of EEPs.

Example from the schema:

    <profiles func="0x20" description="HVAC Components">
      <profile type="0x01" description="Battery Powered Actuator (BI-DIR)">
        <data direction="1">
          <value shortcut="CV" description="Current Value" offset="0" size="8" unit="%">
            <range>
              <min>0</min>
              <max>100</max>
            </range>
            <scale>
              <min>0</min>
              <max>100</max>
            </scale>
          </value>
            .
            .
            .

and

        </data>
        <data direction="2">
          <value shortcut="SP" description="Valve Position or Temperature Setpoint" offset="0" size="8" unit="%">
            <range>
              <min>0</min>
              <max>100</max>
            </range>
            <scale>
              <min>0</min>
              <max>100</max>
            </scale>
          </value>
          <value shortcut="TMP" 
            .
            .
            .

or for Command:

    <profiles func="0x38" description="Central Command">
      <profile type="0x08" description="Gateway">
        <command description="Command ID" shortcut="COM" offset="0" size="8">
          <item description="Switching" value="1" />
          <item description="Dimming" value="2" />
        </command>
        <data command="1">
          <enum shortcut="COM" description="Command ID" offset="0" size="8">
            <rangeitem description="Command ID {value}" start="0" end="13" />
          </enum>
          <value shortcut="TIM" description="Time in 1/10 seconds. 0 = no time specifed" offset="8" size="16" unit="s">
            <range>
              <min>1</min>
              <max>65535</max>
            </range>
            <scale>
              <min>0.1</min>
              <max>6553.5</max>
            </scale>
          </value>
           .
           .
           .