Aeotec Nano Dimmer ZW111 XML Bitmask

Begonnen von Damu, 26 Mai 2024, 21:10:56

Vorheriges Thema - Nächstes Thema

Damu

Hallo

Ich habe bemerkt das fast alle XML in ZWave Fehler haben.
Die Fehler bemerkt mann oft nicht.
Teils sind Parameter falsch begrenzt etc...
Es sind oft nur kleinigkeiten.
Beim Qubino Mini Dimmer gibt es (irgendwie) zwei Parameter für die Umstellung Dimmer-Switch.
Beim Aeotec Nano Dimmer (andre auch) gibt es Parameter die schwer einzustellen sind.
Der Parameter 86 hat zb 4 Bitmask.
1-7 Bitmask Einstellbereich aber nur 0-99
9-14 Bitmask Einstellbereich 0-59
17-21 Bitmask Einstellbereich 0-23

Gibt es eine Möglichkeit das zu begrenzen?
Oder Mehrere Fenster 1-7,9-14,17-21, die Anzeigen wieviel total eingestellt ist?

<Value bitmask="2141167551" genre="config" index="86" label="086 State appointment 2" size="4" type="bitset" value="1507328">
       <Help>State appointment. Set the ON time of output load.
1-7 Bitmask ON (brightness level) (0-99)
9-14 Bitmask (Minute ON 0-59)
17-21 Bitmask (Hour ON 0-23)
25-31 Bitmask (Mon-Sun ON)
   </Help>
  <BitSet id="1">
<Label>+1 br</Label>
<Help>+1 brightness level</Help>
</BitSet>
  <BitSet id="2">
<Label>+2 br</Label>
        <Help>+2 brightness level</Help>
      </BitSet>
      <BitSet id="3">
        <Label>+4 br</Label>
        <Help>+4 brightness level</Help>
      </BitSet>
      <BitSet id="4">
        <Label>+8 br</Label>
        <Help>+8 brightness level</Help>
  </BitSet>
  <BitSet id="5">
<Label>+16 br</Label>
<Help>+16 brightness level</Help>
</BitSet>
  <BitSet id="6">
<Label>+32 br</Label>
        <Help>+32 brightness level</Help>
      </BitSet>
      <BitSet id="7">
        <Label>+64 br</Label>
        <Help>+64 brightness level</Help>
      </BitSet>
      <BitSet id="9">
        <Label>+1 Min</Label>
        <Help>+1 Minuten</Help>
  </BitSet>
    <BitSet id="10">
<Label>+2 Min</Label>
<Help>+2 Minuten</Help>
</BitSet>
  <BitSet id="11">
<Label>+4 Min</Label>
        <Help>+4 Minuten</Help>
      </BitSet>
      <BitSet id="12">
        <Label>+8 Min</Label>
        <Help>+8 Minuten</Help>
      </BitSet>
      <BitSet id="13">
        <Label>+16 Min</Label>
        <Help>+16 Minuten</Help>
  </BitSet>
  <BitSet id="14">
<Label>+32</Label>
<Help>+32 Minuten</Help>
</BitSet>
  <BitSet id="17">
<Label>+1 Hour</Label>
        <Help>+1 Hour</Help>
      </BitSet>
      <BitSet id="18">
        <Label>+2 Hour</Label>
        <Help>+2 Hour</Help>
      </BitSet>
      <BitSet id="19">
        <Label>+4 Hour</Label>
        <Help>+4 Hour</Help>
  </BitSet>
  <BitSet id="20">
<Label>+8 Hour</Label>
        <Help>+8 Hour</Help>
      </BitSet>
      <BitSet id="21">
        <Label>+16 Hour</Label>
        <Help>+16 Hour</Help>
      </BitSet>
      <BitSet id="25">
        <Label>Mon ON</Label>
        <Help>Monday ON</Help>
  </BitSet>
  <BitSet id="26">
        <Label>Tue ON</Label>
        <Help>Tuesday ON</Help>
  </BitSet>
   <BitSet id="27">
        <Label>Wed ON</Label>
        <Help>Wednesday ON</Help>
  </BitSet>
  <BitSet id="28">
        <Label>Thu ON</Label>
        <Help>Thursday ON</Help>
  </BitSet>
    <BitSet id="29">
        <Label>Fri ON</Label>
        <Help>Friday ON</Help>
  </BitSet>
   <BitSet id="30">
        <Label>Sat ON</Label>
        <Help>Saturday ON</Help>
  </BitSet>
  <BitSet id="31">
        <Label>Sun ON</Label>
        <Help>Sunday ON</Help>
  </BitSet>
    </Value>

rudolfkoenig

ZitatGibt es eine Möglichkeit das zu begrenzen?
Oder Mehrere Fenster 1-7,9-14,17-21, die Anzeigen wieviel total eingestellt ist?
Aktuell nicht.
Gibt es oefters solche Konstrukte, oder ist das ein Unikat?
Ist sonst noch jemand an sowas interessiert?

Damu

ZitatGibt es oefters solche Konstrukte, oder ist das ein Unikat?
Kenne das so extrem nur von Aeotec und Heltun.
Kenne aber eigentlich nur meine ZWave Devices
Solche Parameter sind so total aber nutzlos.
Aber wenn FHEM das in der Darstellung hinkriegt kann mann es wirklich gebrauchen.
Ist es eventuell möglich die zwei XML von https://forum.fhem.de/index.php?topic=137992.15



einzufügen/ersetzen.

rudolfkoenig

Aber wenn FHEM das in der Darstellung hinkriegt kann mann es wirklich gebrauchen.
Ich wuerde die BitSet Tags durchlesen, und alles mit dem gleichen Label (^[+0-9]+ wird ignoriert) zusammenfassen.
Damit wuerde es folgende Felder geben:
br
Min
Hour
Mon ON
Tue ON
...
Ich wuerde das aber nur dann tun, wenn wirklich Interesse daran besteht.


ZitatIst es eventuell möglich die zwei XML von https://forum.fhem.de/index.php?topic=137992.15 einzufügen/ersetzen.
Habs gemacht.
Sorry fuer die Verspaetung, bei Beitragsaenderung werde ich nicht benachrichtigt.

Damu

ZitatIch wuerde die BitSet Tags durchlesen, und alles mit dem gleichen Label (^[+0-9]+ wird ignoriert) zusammenfassen.
Damit wuerde es folgende Felder geben:

Wo finde ich das??

Habe jetzt gesehen wie das mit den Bitset dargestellt wird.

Zitat<Value bitmask="7" genre="config" index="9" label="9_Slave Mode" size="1" type="bitset"  value="7">
         <Help>
            "Stupid" mode ( bit 2 = 1 ):
               - has higher priority then slave mode.
               - LED is permanently on ( for simple power wall switch controlling ).
            Slave mode ( bit 0 = 1 ):
               - only if included in Z-Wave network
               - useful for controlling via third-party sensor
               - LED is directly controlled via Z-Wave, internal sensors are not used for controlling it
            Central unit checking ( bit 1 = 1 ): ( useful especially for controlling via gateway )
               When slave bit is 0:
               - device signalises fail of lifeline connection ( if this bit is zero, fail of lifeline connec-
               tion is not signalised )
               When slave bit is 1:
               - device checks presence of Z-Wave device in lifeline group ( gateway ). If it is not
               present for 2 minutes ( testing repeatedly every 30 seconds ) device switches
               to normal mode in the same way as after the end of local disabled mode
               ( ON_BEHAVIOUR )
               - the device checks every 1 minute for recovery of Lifeline connection.
               - if no lifeline specified - it works in normal mode      
         </Help>
     <BitSet id="1">
      <Label>Slave</Label>
      <Help>Slave Mode</Help>
      </BitSet>
     <BitSet id="2">
      <Label>Central unit checking</Label>
        <Help>Central Mode</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Stupid</Label>
        <Help>Stupid Mode</Help>
      </BitSet>
         </Value>   
Die drei Label finde ich nirgens (<Label>Central unit checking</Label>),(<Label>Slave</Label>),(<Label>Stupid</Label>).

Ist die Darstellung so gewollt?

Ist es Möglich ein Parameter mit vier Byte jeden Byte Block einzeln auszulesen und zu beschreiben?
Dann würde er ein Parameter 4.1 bis 4.4 geben?



rudolfkoenig

ZitatWo finde ich das??
In deinem ersten Beitrag.

ZitatIst die Darstellung so gewollt?
So in der Art, natuerlich mit passenden Anzahl von Checkboxen / Dropdowns hinter jedem Label.


ZitatIst es Möglich ein Parameter mit vier Byte jeden Byte Block einzeln auszulesen und zu beschreiben?
Z.Zt. nicht, wenn ich was bastele, und passende BitSet Eintraege im XML vorhanden sind, dann schon.

ZitatDann würde er ein Parameter 4.1 bis 4.4 geben?
Sagt mir nichts.
Ich plane z.Zt. mit BitSet, d.h. fuer dein Fall braucht man 32 BitSet Tags, von denen jeweils 8 den gleichen Label haben.

Damu

#6
ZitatSo in der Art, natuerlich mit passenden Anzahl von Checkboxen / Dropdowns hinter jedem Label.
Ich meine zb: <Label>Slave</Label>
"Slave" wird nirgens angezeigt.
Wenn ich mit der Maus über das Bit Quadrat fahre wird 1-8 angezeigt.
Die Bit Quadrate die nicht Aktiv sind sind Grau (etwas Heller).
Ich meine wenn <Label>xxx</Label> nicht angezeigt lase ich es das nächste mal weg?

Sehe gerade bei einer XML wurde es so gelöst ("aeotec/zw122.xml")
Zitat<Value bitmask="55" genre="config" index="87" instance="1" label="Sensor is triggered the buzzer will alarm" max="55" min="0" size="4" type="bitset" value="55">
      <Help>What Sensors Trigger the Buzzer</Help>
      <BitSet id="1">
        <Label>Water Leak</Label>
        <Help>If the Water leak is triggered, the buzzer will alarm.</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Vibration</Label>
        <Help>If the vibration is triggered, the buzzer will alarm.</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Tilt Sensor</Label>
        <Help>If the Tilt Sensor is triggered, the buzzer will alarm.</Help>
      </BitSet>
      <BitSet id="5">
        <Label>UnderHeat</Label>
        <Help>If the Under Heat Temperature is triggered, the buzzer will alarm.</Help>
      </BitSet>
      <BitSet id="6">
        <Label>OverHeat</Label>
        <Help>If the Over Heat Temperature is triggered, the buzzer will alarm.</Help>
      </BitSet>
    </Value>

Da wäre es besser wenn im Hilfetext zuerst das "Label" und mit etwas Abstand dahinter der Hilfetext zum "Label" wäre.

rudolfkoenig

Soweit ich sehe, passt in den in den 9 "BitSet" Product Eintraegen in openzwave_deviceconfig.xml und 3 aus fhem_zwave_deviceconfig.xml keiner auf das Vorhaben.
Woher stammt dein Beispiel aus dem ersten Beitrag?

ZitatIch meine wenn <Label>xxx</Label> nicht angezeigt lase ich es das nächste mal weg?
Das koennte man machen, ich wuerde aber zwecks Kompatibilitaet beim alten Syntax bleiben, fuer Label kann man auch kurze Texte nehmen.

Bevor ich es implementiere, braueche ich Eintraege zum ueben in fhem_zwave_deviceconfig.xml, am besten mehr als einen.

Damu

ZitatSoweit ich sehe, passt in den in den 9 "BitSet" Product Eintraegen in openzwave_deviceconfig.xml und 3 aus fhem_zwave_deviceconfig.xml keiner auf das Vorhaben.
Woher stammt dein Beispiel aus dem ersten Beitrag?
Auf das XML in fhem_zwave_deviceconfig.xml (aeotec/zw111.xml)
Auf den Parameter 86 in dieser XML den ich bearbeite weil ich bemerkt habe das da so einiges nicht passt und auch fehlerhaft ist.
Das heist ich teste die eingestelleten Werte am Device. (Auf Beschreibbarkeit und manchmal auch auf die Funktion).
Der Parameter 86 (andere auch) habe ich aber nur in der XML gefunden, dh in keiner Anleitung??
Die Werte lassen sich aber so beschreiben wie es in der XML steht.

ZitatBevor ich es implementiere, braueche ich Eintraege zum ueben in fhem_zwave_deviceconfig.xml, am besten mehr als einen.
aeotec/zwa009V2.xml
    <Value bitmask="15" genre="config" index="65" label="65 Sensor report after inclusion (Mask) (V2)" max="15" min="0" size="1" type="bitset" value="15">
      <Help>This value determines which sensor report will be sent after the inclusion is complete.
            (ZWA039 V2.0 or higher)
            (Default = 15)
      </Help>
      <BitSet id="1">
        <Label>Battery report</Label>
        <Help>Battery report.</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Temperature sensor report</Label>
        <Help>Temperature sensor report</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Humidity sensor report</Label>
        <Help>IHumidity sensor report</Help>
      </BitSet>
      <BitSet id="4">
        <Label>Dew point sensor report</Label>
        <Help>Dew point sensor report</Help>
      </BitSet>
    </Value>

aeotec/zwa024.xml

<Value bitmask="255" genre="config" index="48" label="048 Sensor Limit Control" size="1" type="bitset" units="" value="0">
       <Help> This value is bit mask. Used to enable/disable measurement reports for various sensors that is more than the upper limit value or less than the lower limit value.   </Help>
  <BitSet id="1">
<Label>Temperature upper level</Label>
<Help>Temperature upper level</Help>
</BitSet>
  <BitSet id="2">
<Label>Humidity upper level</Label>
        <Help>Humidity upper level</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Lux upper level</Label>
        <Help>Lux upper level</Help>
      </BitSet>
      <BitSet id="4">
        <Label>UV upper level</Label>
        <Help>UV upper level</Help>
      </BitSet>     
  <BitSet id="5">
        <Label>Temperature lower level</Label>
        <Help>Temperature lover level</Help>
      </BitSet>
      <BitSet id="6">
        <Label>Humidity lower level</Label>
        <Help>Humidity lower level</Help>
      </BitSet>
      <BitSet id="7">
        <Label>Lux lower level</Label>
        <Help>Lux lower level</Help>
      </BitSet>
      <BitSet id="8">
        <Label>UV lower level</Label>
        <Help>UV lower level</Help>
      </BitSet>       
  </Value>

<Value bitmask="255" genre="config" index="061" label="061 Out-of-limit State" size="1" type="bitset" read_only="true">
<Help> This value is bit mask. Used to enable/disable measurement reports for various sensors that is more than the upper limit value or less than the lower limit value.
0 - within limit 1 - out of limit </Help>
  <BitSet id="1">
<Label>Temperature upper level</Label>
<Help>Temperature upper level</Help>
</BitSet>
  <BitSet id="2">
<Label>Humidity upper level</Label>
        <Help>Humidity upper level</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Lux upper level</Label>
        <Help>Lux upper level</Help>
      </BitSet>
      <BitSet id="4">
        <Label>UV upper level</Label>
        <Help>UV upper level</Help>
      </BitSet>     
  <BitSet id="5">
        <Label>Temperature lower level</Label>
        <Help>Temperature lower level</Help>
      </BitSet>
      <BitSet id="6">
        <Label>Humidity lower level</Label>
        <Help>Humidity lower level</Help>
      </BitSet>
      <BitSet id="7">
        <Label>Lux lower level</Label>
        <Help>Lux lower level</Help>
      </BitSet>
      <BitSet id="8">
        <Label>UV lower level</Label>
        <Help>UV lower level</Help>
      </BitSet>       
  </Value>

<Value bit<Value bitmask="241" genre="config" index="101" label="101 Automatic Report Checklist 1" size="1" type="bitset"  value="241">
       <Help>Checklist 1 for automatic timed report. When the corresponding item is selected, it will be checked when timeout setting by Param 111.</Help>
  <BitSet id="1">
<Label>Battery</Label>
<Help>Send Battery Report</Help>
</BitSet>
  <BitSet id="5">
<Label>UV</Label>
        <Help>Send UV Report</Help>
      </BitSet>
      <BitSet id="6">
        <Label>Temperature</Label>
        <Help>Send Temperature Report</Help>
      </BitSet>
      <BitSet id="7">
        <Label>Humidity</Label>
        <Help>Send Humidity Report</Help>
      </BitSet>     
  <BitSet id="8">
        <Label>Lux</Label>
        <Help>Send Luminance Report</Help>
  </BitSet> 
  </Value>
<Value bitmask="241" genre="config" index="102" label="102 Automatic Report Checklist 2" size="1" type="bitset" value="0">
       <Help>Checklist 2 for automatic timed report. When the corresponding item is selected, it will be checked when timeout setting by Param 112.</Help>
  <BitSet id="1">
<Label>Battery</Label>
<Help>Send Battery Report</Help>
</BitSet>
  <BitSet id="5">
<Label>UV</Label>
        <Help>Send UV Report</Help>
      </BitSet>
      <BitSet id="6">
        <Label>Temperature</Label>
        <Help>Send Temperature Report</Help>
      </BitSet>
      <BitSet id="7">
        <Label>Humidity</Label>
        <Help>Send Humidity Report</Help>
      </BitSet>     
  <BitSet id="8">
        <Label>Lux</Label>
        <Help>Send Luminance Report</Help>
  </BitSet> 
  </Value>mask="241" genre="config" index="103" label="103 Automatic Report Checklist 3" size="1" type="bitset" value="0">
       <Help>Checklist 3 for automatic timed report. When the corresponding item is selected, it will be checked when timeout setting by Param 113.</Help>
  <BitSet id="1">
<Label>Battery</Label>
<Help>Send Battery Report</Help>
</BitSet>
  <BitSet id="5">
<Label>UV</Label>
        <Help>Send UV Report</Help>
      </BitSet>
      <BitSet id="6">
        <Label>Temperature</Label>
        <Help>Send Temperature Report</Help>
      </BitSet>
      <BitSet id="7">
        <Label>Humidity</Label>
        <Help>Send Humidity Report</Help>
      </BitSet>     
  <BitSet id="8">
        <Label>Lux</Label>
        <Help>Send Luminance ReportHelp</Help>
  </BitSet> 
  </Value>

MotionSwitch.xml
<Value bitmask="7" genre="config" index="9" label="9_Slave Mode" size="1" type="bitset"  value="7">
<Help>
"Stupid" mode ( bit 2 = 1 ):
- has higher priority then slave mode.
- LED is permanently on ( for simple power wall switch controlling ).
Slave mode ( bit 0 = 1 ):
- only if included in Z-Wave network
- useful for controlling via third-party sensor
- LED is directly controlled via Z-Wave, internal sensors are not used for controlling it
Central unit checking ( bit 1 = 1 ): ( useful especially for controlling via gateway )
When slave bit is 0:
- device signalises fail of lifeline connection ( if this bit is zero, fail of lifeline connec-
tion is not signalised )
When slave bit is 1:
- device checks presence of Z-Wave device in lifeline group ( gateway ). If it is not
present for 2 minutes ( testing repeatedly every 30 seconds ) device switches
to normal mode in the same way as after the end of local disabled mode
( ON_BEHAVIOUR )
- the device checks every 1 minute for recovery of Lifeline connection.
- if no lifeline specified - it works in normal mode    
</Help>
  <BitSet id="1">
<Label>Slave</Label>
<Help>Slave Mode</Help>
</BitSet>
  <BitSet id="2">
<Label>Central unit checking</Label>
        <Help>Central Mode</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Stupid</Label>
        <Help>Stupid Mode</Help>
      </BitSet>
      </Value>
<Value bitmask="31" genre="config" index="17" label="17_Button behaviour" size="1" type="bitset"  value="8">
<Help>
(0) Dim increase (bit 0): (0) long press of button does dim decreasing (0 = default)
(1)long press of button does dim increasing (1)
(1) Scene switch (bit 1): (0) short press of button does toggle � on/off (0 = default)
(1) short press of button does scene switch (1)
(2) Standalone behaviour (bit 2): (0) using "legacy" sensor deactivity after button press (0 = default)
(1) using "cfg 10-14" sensor deactivity after button press (1)
(3) Network behaviour (bit 3): (0) using "legacy" sensor deactivity after button press (0)
(1) using "cfg 10-14" sensor deactivity after button press (1 = default)
(4) Dim disable (bit 4): (0) dim events ( long press ) are used (0 = default)
(1) dim events ( long press ) are ignored (1)
"legacy" sensor deactivity behaviour does this:
- Pressing push button when LED is OFF: LED will switch on as long as there is movement and the delay time runs of
- Pressing push button when LED is ON: LED will switch off as long as there is movement ans the delay time runs of (invers logic).
"cfg 10-14" sensor deactivity behaviour uses behaviour specified in parameters 10-14.
(the same behaviour as pressing of external switch using BASIC ON/OFF unctions)    
</Help>
  <BitSet id="1">
<Label>Dim increase</Label>
<Help>Dim increase</Help>
</BitSet>
  <BitSet id="2">
<Label>Scene switch</Label>
        <Help>Scene switch</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Standalone behaviour</Label>
        <Help>Standalone behaviour</Help>
      </BitSet>
   <BitSet id="4">
<Label>Network behaviour</Label>
<Help>Network behaviour</Help>
</BitSet>
  <BitSet id="5">
<Label>Dim disable</Label>
        <Help>Dim disable</Help>
</BitSet>
        </Value>

Damu

#9
Und in der openzwave_deviceconfig.xml

zooz/zen31.xml

<Value type="bitset" genre="config" index="40" label="Scene Control for IN1" size="1" bitmask="255" units="" value="15">
      <Help>Assign scene activation trigger for IN1 terminal.  Default: Everything</Help>
      <BitSet id="1">
        <Label>click/toggle 1 time to trigger</Label>
  <Help>Click/toggle the connected switch 1 time to trigger a scene.</Help>
      </BitSet>
      <BitSet id="2">
        <Label>click/toggle 2 times to trigger</Label>
  <Help>Click/toggle the connected switch 2 times to trigger a scene.</Help>
      </BitSet>
      <BitSet id="3">
        <Label>click/toggle 3 times to trigger</Label>
  <Help>Click/toggle the connected switch 3 times to trigger a scene.</Help>
      </BitSet>
      <BitSet id="4">
        <Label>click/toggle 4 times to trigger</Label>
  <Help>Click/toggle the connected switch 4 times to trigger a scene.</Help>
      </BitSet>
    </Value>
    <Value type="bitset" genre="config" index="41" label="Scene Control for IN2" size="1" bitmask="255" units="" value="15">
      <Help>Assign scene activation trigger for IN2 terminal.  Default: Everything</Help>
      <BitSet id="1">
        <Label>click/toggle 1 time to trigger</Label>
  <Help>Click/toggle the connected switch 1 time to trigger a scene.</Help>
      </BitSet>
      <BitSet id="2">
        <Label>click/toggle 2 times to trigger</Label>
  <Help>Click/toggle the connected switch 2 times to trigger a scene.</Help>
      </BitSet>
      <BitSet id="3">
        <Label>click/toggle 3 times to trigger</Label>
  <Help>Click/toggle the connected switch 3 times to trigger a scene.</Help>
      </BitSet>
      <BitSet id="4">
        <Label>click/toggle 4 times to trigger</Label>
  <Help>Click/toggle the connected switch 4 times to trigger a scene.</Help>
      </BitSet>
    </Value>
    <Value type="bitset" genre="config" index="42" label="Scene Control for IN3" size="1" bitmask="255" units="" value="15">
      <Help>Assign scene activation trigger for IN3 terminal.  Default: Everything</Help>
      <BitSet id="1">
        <Label>click/toggle 1 time to trigger</Label>
  <Help>Click/toggle the connected switch 1 time to trigger a scene.</Help>
      </BitSet>
      <BitSet id="2">
        <Label>click/toggle 2 times to trigger</Label>
  <Help>Click/toggle the connected switch 2 times to trigger a scene.</Help>
      </BitSet>
      <BitSet id="3">
        <Label>click/toggle 3 times to trigger</Label>
  <Help>Click/toggle the connected switch 3 times to trigger a scene.</Help>
      </BitSet>
      <BitSet id="4">
        <Label>click/toggle 4 times to trigger</Label>
  <Help>Click/toggle the connected switch 4 times to trigger a scene.</Help>
      </BitSet>
    </Value>
    <Value type="bitset" genre="config" index="43" label="Scene Control for IN4" size="1" bitmask="255" units="" value="15">
      <Help>Assign scene activation trigger for IN4 terminal.  Default: Everything</Help>
      <BitSet id="1">
        <Label>click/toggle 1 time to trigger</Label>
  <Help>Click/toggle the connected switch 1 time to trigger a scene.</Help>
      </BitSet>
      <BitSet id="2">
        <Label>click/toggle 2 times to trigger</Label>
  <Help>Click/toggle the connected switch 2 times to trigger a scene.</Help>
      </BitSet>
      <BitSet id="3">
        <Label>click/toggle 3 times to trigger</Label>
  <Help>Click/toggle the connected switch 3 times to trigger a scene.</Help>
      </BitSet>
      <BitSet id="4">
        <Label>click/toggle 4 times to trigger</Label>
  <Help>Click/toggle the connected switch 4 times to trigger a scene.</Help>
      </BitSet>
    </Value>

aeotec/zwa019.xml

    <Value genre="config" index="3" instance="1" label="Visual LED indications" max="7" min="0" size="1" type="bitset" value="7" bitmask="23">
       <Help>This parameter defines when the red LED will indicate events. Disabling all indications may extend battery life.       </Help>
      <BitSet id="1">
        <Label>No Indications</Label>
        <Help>No Indications</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Water Leakage Status Change</Label>
        <Help>Water Leakage Status Change</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Wake Up</Label>
        <Help>Wake Up</Help>
      </BitSet>
      <BitSet id="5">
        <Label>Device Tampering</Label>
        <Help>Device Tampering</Help>
      </BitSet>
    </Value>

aeotec/zw122.xml

    <Value bitmask="55" genre="config" index="87" instance="1" label="Sensor is triggered the buzzer will alarm" max="55" min="0" size="4" type="bitset" value="55">
      <Help>What Sensors Trigger the Buzzer</Help>
      <BitSet id="1">
        <Label>Water Leak</Label>
        <Help>If the Water leak is triggered, the buzzer will alarm.</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Vibration</Label>
        <Help>If the vibration is triggered, the buzzer will alarm.</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Tilt Sensor</Label>
        <Help>If the Tilt Sensor is triggered, the buzzer will alarm.</Help>
      </BitSet>
      <BitSet id="5">
        <Label>UnderHeat</Label>
        <Help>If the Under Heat Temperature is triggered, the buzzer will alarm.</Help>
      </BitSet>
      <BitSet id="6">
        <Label>OverHeat</Label>
        <Help>If the Over Heat Temperature is triggered, the buzzer will alarm.</Help>
      </BitSet>
    </Value>

aeotec/zwa012.xml

    <Value genre="config" index="3" instance="1" label="Visual LED indications" max="7" min="0" size="1" type="bitset" value="7" bitmask="23">
       <Help>This parameter defines when the red LED will indicate events. Disabling all indications may extend battery life.       </Help>
      <BitSet id="1">
        <Label>No Indications</Label>
        <Help>No Indications</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Open/Close Status Change</Label>
        <Help>Open/Close Status Change</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Wake Up</Label>
        <Help>Wake Up</Help>
      </BitSet>
      <BitSet id="5">
        <Label>Device Tampering</Label>
        <Help>Device Tampering</Help>
      </BitSet>
    </Value>

aeotec/zwa023.xml

        <Value genre="config" index="30" label="Alarm Settings" max="255" min="0" size="1" type="bitset" bitmask="255" units="" value="0">
             <Help>         Bitfield.  Determines if alarms are enabled in Switch, and what Switch will react to which alarms.         0 - Disable all alarm settings         1 - Smoke Alarm         2 - CO Alarm         4 - CO2 Alarm         8 - Heat Alarm         16 - Water Alarm         32 - Access Control (DW Sensor open)         64 - Home Security (intrusion)         128 - Motion Sensor trigger             </Help>
      <BitSet id="1">
        <Label>Smoke Alarm</Label>
        <Help>Smoke Alarm</Help>
      </BitSet>
      <BitSet id="2">
        <Label>CO Alarm</Label>
        <Help>CO Alarm</Help>
      </BitSet>
      <BitSet id="3">
        <Label>CO2 Alarm</Label>
        <Help>CO2 Alarm</Help>
      </BitSet>
      <BitSet id="4">
        <Label>Heat Alarm</Label>
        <Help>Heat Alarm</Help>
      </BitSet>
      <BitSet id="5">
        <Label>Water Alarm</Label>
        <Help>Water Alarm</Help>
      </BitSet>
      <BitSet id="6">
        <Label>Access Control (DW Sensor open)</Label>
        <Help>Access Control (DW Sensor open)</Help>
      </BitSet>
      <BitSet id="7">
        <Label>Home Security (intrusion)</Label>
        <Help>Home Security (intrusion)</Help>
      </BitSet>
      <BitSet id="8">
        <Label>Motion Sensor trigger</Label>
        <Help>Motion Sensor trigger</Help>
      </BitSet>
        </Value>

aeotec/zw139.xml

    <Value bitmask="255" genre="config" index="48" label="Enable/disable to send a report on Threshold" size="1" type="bitset" units="" value="0">
       <Help>       Enable/disable to send a report when the measurement is more than the upper limit value or less than the lower limit value.       Note:       If USB power, the Sensor will check the limit every 10 seconds. If battery power, the Sensor will check the limit when it is waken up.       </Help>
      <Help lang="fr">French Help</Help>
      <Label lang="fr">Enable/disable to send a report on Threshold-fr</Label>
      <BitSet id="1">
        <Label>Lower Temperature</Label>
        <Label lang="fr">Lower Temperature-fr</Label>
        <Help>Lower Temperature Threshold</Help>
        <Help lang="fr">Lower Temperature Threshold-fr</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Lower Humidity</Label>
        <Label lang="fr">Lower Humidity-fr</Label>
        <Help>Lower Humdity Threshold</Help>
        <Help lang="fr">Lower Humdity Threshold-fr</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Lower Luminance</Label>
        <Label lang="fr">Lower Luminance-fr</Label>
        <Help>Lower Luminance Threshold</Help>
        <Help lang="fr">Lower Luminance Threshold</Help>
      </BitSet>
      <BitSet id="4">
        <Label>Lower Ultraviolet</Label>
        <Label lang="fr">Lower Ultraviolet-fr</Label>
        <Help>Lower Ultraviolet Threshold</Help>
        <Help lang="fr">Lower Ultraviolet Threshold-fr</Help>
      </BitSet>
      <BitSet id="5">
        <Label>Upper Temperature</Label>
        <Label lang="fr">Upper Temperature-fr</Label>
        <Help>Upper Temerature Threshold</Help>
        <Help lang="fr">Upper Temerature Threshold-fr</Help>
      </BitSet>
      <BitSet id="6">
        <Label>Upper Humidity</Label>
        <Label lang="fr">Upper Humidity-fr</Label>
        <Help>Upper Humdity Threshold</Help>
        <Help lang="fr">Upper Humdity Threshold-fr</Help>
      </BitSet>
      <BitSet id="7">
        <Label>Upper Luminance</Label>
        <Label lang="fr">Upper Luminance-fr</Label>
        <Help>Upper Luminance Threshold</Help>
        <Help lang="fr">Upper Luminance Threshold-fr</Help>
      </BitSet>
      <BitSet id="8">
        <Label>Upper Ultraviolet</Label>
        <Label lang="fr">Upper Ultraviolet-fr</Label>
        <Help>Upper Ultraviolet Threshold</Help>
        <Help lang="fr">Upper Ultraviolet Threshold-fr</Help>
      </BitSet>
    </Value>
<Value bitmask="241" genre="config" index="101" label="Group 1 Reports" size="4" type="bitset" value="241">
       <Help>Which reports need to send automatically in timing intervals for group 1.         Bitmask:         10000000 - 128 - Luminance         01000000 - 64 - Humidity         00100000 - 32 - Temperature         00010000 - 16 - Ultraviolet         00000001 - 1 - Battery         10100000 - 160 - Luminance and Temperature (32+128)         11110001 - 241 - All (1+16+32+64+128)       </Help>
      <BitSet id="1">
        <Label>Battery</Label>
        <Help>Send Battery Report</Help>
      </BitSet>
      <BitSet id="5">
        <Label>Ultraviolet</Label>
        <Help>Send Ultraviolet Report</Help>
      </BitSet>
      <BitSet id="6">
        <Label>Temperature</Label>
        <Help>Send Temperature Report</Help>
      </BitSet>
      <BitSet id="7">
        <Label>Humidity</Label>
        <Help>Send Humidity Report</Help>
      </BitSet>
      <BitSet id="8">
        <Label>Luminance</Label>
        <Help>Send Luminance Report</Help>
      </BitSet>
    </Value>

aeotec/zw162.xml

<Value bitmask="4287037440" genre="config" index="1" label="Light Effect and Tone Play Mode for Browse" size="4" type="bitset" value="16777216">
       <Help>Light Effect and PlayTone configuration for Browse Endping       </Help>
      <BitSet id="32">
        <Label>Last Valid Configuration (Light Effect)</Label>
        <Help>Use the Last Valid Configuration Value for the Light Effect</Help>
      </BitSet>
      <BitSet id="31">
        <Label>Light Effect #7</Label>
        <Help>Use Light Effect #7, Defined in Parameter 22</Help>
      </BitSet>
      <BitSet id="30">
        <Label>Light Effect #6</Label>
        <Help>Use Light Effect #6, Defined in Parameter 21</Help>
      </BitSet>
      <BitSet id="29">
        <Label>Light Effect #5</Label>
        <Help>Use Light Effect #5, Defined in Parameter 20</Help>
      </BitSet>
      <BitSet id="28">
        <Label>Light Effect #4</Label>
        <Help>Use Light Effect #4, Defined in Parameter 19</Help>
      </BitSet>
      <BitSet id="27">
        <Label>Light Effect #3</Label>
        <Help>Use Light Effect #3, Defined in Parameter 18</Help>
      </BitSet>
      <BitSet id="26">
        <Label>Light Effect #2</Label>
        <Help>Use Light Effect #2, Defined in Parameter 17</Help>
      </BitSet>
      <BitSet id="25">
        <Label>Light Effect #1</Label>
        <Help>Use Light Effect #1, Defined in Parameter 16</Help>
      </BitSet>
      <BitSet id="24">
        <Label>Last Valid Configuration (Tone Mode)</Label>
        <Help>Use the Last Valid Configuration Value for the Tone</Help>
      </BitSet>
      <BitSet id="19">
        <Label>List Random Playback</Label>
         <Help>If you're not sure which tone to use, you can configure the value of Tone Play Mode to be 3. Then send Basic Set 0xFF to Endpoint 1 or Root Device to trigger auto-selecting tone function. Chime will play built-in tones randomly and the Default Tone Identifier will be changed each time a new tone is played. When send Basic Set 0x00 to Endpoint 1 or Root Device to stop playing tone, the Default Tone Identifier will store, which means the tone has been selected. Please note that the Tone Play Mode needs to be configured to be 0 or 1 after the tone is selected, otherwise the automatic selection tone function will be retriggered when the Endpoint 1 or Root Device is triggered to play tone and light again.</Help>
      </BitSet>
      <BitSet id="18">
        <Label>List Loop Playback</Label>
         <Help>If you're not sure which tone to use, you can configure the value of Tone Play Mode to be 2. Then send Basic Set 0xFF to Endpoint 1 or Root Device to trigger auto-selecting tone function. Chime will play built-in tones in order and the Default Tone Identifier will be changed each time a new tone is played. When send Basic Set 0x00 to Endpoint 1 or Root Device to stop playing tone, the Default Tone Identifier will store, which means the tone has been selected. Please note that the Tone Play Mode needs to be configured to be 0 or 1 after the tone is selected, otherwise the automatic selection tone function will be retriggered when the Endpoint 1 or Root Device is triggered to play tone and light again.</Help>
      </BitSet>
      <BitSet id="17">
        <Label>Single Loop Playback</Label>
        <Help>Use a single loop playback for the Tone</Help>
      </BitSet>
    </Value>

logicsoft/ZDB5100.xml

<Value genre="config" index="1" instance="1" label="Operating pushbutton(s) for dimmer" size="1" type="bitset" bitmask="15" value="1">
      <Help>This parameter specifies which pushbutton(s) that shall be used to control the built-in dimmer.</Help>
      <BitSet id="0">
        <Label>No local operation of the dimmer</Label>
        <Help>No local operation of the dimmer</Help>
      </BitSet>
      <BitSet id="1">
        <Label>Pushbutton 1</Label>
        <Help>Pushbutton 1 controls the dimmer</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Pushbutton 2</Label>
        <Help>Pushbutton 2 controls the dimmer</Help>
      </BitSet>
      <BitSet id="4">
        <Label>Pushbutton 3</Label>
        <Help>Pushbutton 3 controls the dimmer</Help>
      </BitSet>
      <BitSet id="8">
        <Label>Pushbutton 4</Label>
        <Help>Pushbutton 4 controls the dimmer</Help>
      </BitSet>
    </Value>
<Value genre="config" index="15" label="Associations groups, transmission when included secure" size="2" type="bitset" bitmask="8191" value="8191">
       <Help>This parameter specifies if commands are transmitted as a secure message for each of the association groups.         Bitmask:         0: All messages in all groups are sent as insecure.         1: Messages in association group 2 aresent as secure.         2: Messages in association group 3 aresent as secure.         4: Messages in association group 4 aresent as secure.         8: Messages in association group 5 aresent as secure.         16: Messages in association group 6 aresent as secure.         32: Messages in association group 7 aresent as secure.         64: Messages in association group 8 aresent as secure.         128: Messages in association group 9 aresent as secure.         256: Messages in association group 10 aresent as secure.         512: Messages in association group 11 aresent as secure.         1024: Messages in association group 12 aresent as secure.         2048: Messages in association group 13 aresent as secure.         4096: Messages in association group 14 aresent as secure.         8191: Messages in allassociation groups are sent as secure. (Default)       </Help>
      <BitSet id="1">
        <Label>Bit#0. All commands are sent unencrypted</Label>
        <Help>All messages in all groups are sent as insecure.</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Bit#1. Send Basic Report to association group 2 encrypted.</Label>
        <Help>Messages in association group 2 are sent as secure.</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Bit#2. Send Binary Switch Set to association group 3 encrypted.</Label>
        <Help>Messages in association group 3 are sent as secure.</Help>
      </BitSet>
      <BitSet id="4">
        <Label>Bit#4. Send Multi-LevelSwitch to association group 4 encrypted.</Label>
        <Help>Messages in association group 4 are sent as secure.</Help>
      </BitSet>
      <BitSet id="5">
        <Label>Bit#8. Send Basic Report to association group 5 encrypted.</Label>
        <Help>Messages in association group 5 are sent as secure.</Help>
      </BitSet>
      <BitSet id="6">
        <Label>Bit#16. Send Binary Switch Set to association group 6 encrypted.</Label>
        <Help>Messages in association group 6 are sent as secure.</Help>
      </BitSet>
      <BitSet id="7">
        <Label>Bit#32. Send Multi-LevelSwitch to association group 7 encrypted.</Label>
        <Help>Messages in association group 7 are sent as secure.</Help>
      </BitSet>
      <BitSet id="8">
        <Label>Bit#64. Send Basic Report to association group 8 encrypted.</Label>
        <Help>Messages in association group 8 are sent as secure.</Help>
      </BitSet>
      <BitSet id="9">
        <Label>Bit#128. Send Binary Switch Set to association group 9 encrypted.</Label>
        <Help>Messages in association group 9 are sent as secure.</Help>
      </BitSet>
      <BitSet id="10">
        <Label>Bit#256. Send Multi-LevelSwitch to association group 10 encrypted.</Label>
        <Help>Messages in association group 10 are sent as secure.</Help>
      </BitSet>
      <BitSet id="11">
        <Label>Bit#512. Send Basic Report to association group 11 encrypted.</Label>
        <Help>Messages in association group 11 are sent as secure.</Help>
      </BitSet>
      <BitSet id="12">
        <Label>Bit#1024. Send Binary Switch Set to association group 12 encrypted.</Label>
        <Help>Messages in association group 12 are sent as secure.</Help>
      </BitSet>
      <BitSet id="13">
        <Label>Bit#2048. Send Multi-LevelSwitch to association group 10 encrypted.</Label>
        <Help>Messages in association group 13 are sent as secure.</Help>
      </BitSet>
      <BitSet id="14">
        <Label>Bit#4096. Send Basic Report to association group 14 encrypted.</Label>
        <Help>Messages in association group 14 are sent as secure.</Help>
      </BitSet>
      <BitSet id="15">
        <Label>Bit#8191. All commands are sent encrypted (default).</Label>
        <Help>Messages in all association groups are sent as secure.</Help>
      </BitSet>
    </Value>


mcohome/mhs513.xml

  <Value genre="config" index="16" label="Scene response" size="1" type="bitset" bitmask="7" value="0">
      <Help>Scene response</Help>
      <BitSet id="1">
        <Label>Key 1</Label>
        <Help>Key 1 scene response</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Key 2</Label>
        <Help>Key 2 scene response</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Key 3</Label>
        <Help>Key 3 scene response</Help>
      </BitSet>
    </Value>
 <Value genre="config" index="32" label="Scene response ID 1 - 50" size="1" type="bitset" bitmask="7" value="0">
       <Help>       Scene response  ID 1 - 50       Valid only when the default is 0 (0x00) for Scene response (parameter 16 | 0x10)       </Help>
      <BitSet id="1">
        <Label>Key 1</Label>
        <Help>Key 1 scene response</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Key 2</Label>
        <Help>Key 2 scene response</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Key 3</Label>
        <Help>Key 3 scene response</Help>
      </BitSet>
    </Value>
    <Value genre="config" index="33" label="Scene response ID 51 - 100" size="1" type="bitset" bitmask="7" value="0">
       <Help>       Scene response  ID 51 - 100       Valid only when the default is 0 (0x00) for Scene response (parameter 16 | 0x10)       </Help>
      <BitSet id="1">
        <Label>Key 1</Label>
        <Help>Key 1 scene response</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Key 2</Label>
        <Help>Key 2 scene response</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Key 3</Label>
        <Help>Key 3 scene response</Help>
      </BitSet>
    </Value>
    <Value genre="config" index="34" label="Scene response ID 101 - 150" size="1" type="bitset" bitmask="7" value="0">
       <Help>       Scene response  ID 101 - 150       Valid only when the default is 0 (0x00) for Scene response (parameter 16 | 0x10)       </Help>
      <BitSet id="1">
        <Label>Key 1</Label>
        <Help>Key 1 scene response</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Key 2</Label>
        <Help>Key 2 scene response</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Key 3</Label>
        <Help>Key 3 scene response</Help>
      </BitSet>
    </Value>
    <Value genre="config" index="35" label="Scene response ID 151 - 200" size="1" type="bitset" bitmask="7" value="0">
       <Help>       Scene response  ID 151 - 200       Valid only when the default is 0 (0x00) for Scene response (parameter 16 | 0x10)       </Help>
      <BitSet id="1">
        <Label>Key 1</Label>
        <Help>Key 1 scene response</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Key 2</Label>
        <Help>Key 2 scene response</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Key 3</Label>
        <Help>Key 3 scene response</Help>
      </BitSet>
    </Value>
    <Value genre="config" index="36" label="Scene response ID 201 - 250" size="1" type="bitset" bitmask="7" value="0">
       <Help>       Scene response  ID 201 - 250       Valid only when the default is 0 (0x00) for Scene response (parameter 16 | 0x10)       </Help>
      <BitSet id="1">
        <Label>Key 1</Label>
        <Help>Key 1 scene response</Help>
      </BitSet>
      <BitSet id="2">
        <Label>Key 2</Label>
        <Help>Key 2 scene response</Help>
      </BitSet>
      <BitSet id="3">
        <Label>Key 3</Label>
        <Help>Key 3 scene response</Help>
      </BitSet>
    </Value>
    <Value genre="config" index="255" label="Restore factory setting" max="85" min="0" size="1" type="list" value="0">
      <Help>Restore factory setting</Help>
      <Item label="Normal" value="0"/>
      <Item label="Reset to factory defaults" value="85"/>
    </Value>


rudolfkoenig

Ich glaube wir sprechen ueber unterschiedliche Dinger.

Die von Dir angehaengten BitSets habe ich auch gefunden (und gezaehlt, s.o), mir ging es eher um die, wo man nicht einzelne Bits aendern will (das geht ja auch jetzt, und das will ich nicht aendern), sondern Bitfelder (mehrere Bits gehoeren zu einem Wert), wie in deinem ersten Beispiel.

Damu

#11
Kenne nur meine Eigenen Devices:
Sind Heltun Devices:
HE-RS01 und HE-HLS01,
ZitatParameters 111-120 – Relay Control by Scenario
In these parameters, the relay state changes depending on day and time. For these
configurations, parameter values are encoded as 7-digit numbers (ABCDEFG).
A: State. 0 = Disabled, 1 = Enabled
B: Day of week
0 = every day
1-7 = corresponding day (1 is Monday, 7 is Sunday)
8 = every weekday (Monday - Friday)
9 = every weekend (Saturday and Sunday)
C: Change state to
0 = Switch OFF
1 = Switch ON
DEFG: Time
DE represents Hour (from 0 to 23),
FG represents Minutes (from 0 to 59).
All other numbers are reserved and will not affect the operation. To disable this option simply
set this parameter to 0.
The factory default value is 0.
Example: Parameter value 1210350 means A=1 (the scenario is enabled), B=2 (Tuesday),
C=1 (switch the relay On), DEFG=0350 (time 03:50). In this case each Tuesday at 03:50 the

HE-HLS01 USER MANUAL 24
relay output will be switched On. To disable the scenario, change the first digit to 0. In this
example it will be 0210350.
≡ Note: The relays still can be controlled manually using External Inputs or via
controller/gateway.
≡ Note: The logic will implement the operation when the time crosses the value in the
Parameter. Meaning, that if the logic switches On the relay and you manually switch
it Off, the relay will switch On next time when the value crosses the set parameter.
≡ Note: Parameters 111-120 are representing independent scenarios.

HE-TPS05
ZitatParameters 111-120- Relays Control by Sensors
In these Parameters, the relay state changes depending on sensor threshold value. For these
configurations, Parameter values are encoded as 8-digit numbers (ABCDEFGH):
A = Relay number (1 through 5)
B = Control Mode
0-Temperature Sensor,
1-Humidity Sensor,
2-Light Sensor,
3-Time control
C = State change relative to value in EFGH Condition Value fields (see below)
0-Equal or lower than
1-Equal or higher than
D: State Change,
0-Switch OFF
1-Switch ON
EFGH: Condition Value
"Sensor Value" for Control modes 0, 1, and 2, or "Time" for Control mode 3.
If Temperature sensor has been chosen as a source in the control mode, the value should
be x10, e.g. for 24.5°C use the value 0245.
If Time control has been chosen as a source in the control mode, the device logic will
process values EFGH from 0 to 23:59 (in time measure), all other values will be ignored.
EF represents Hour (0 through 23), GH represents Minutes (0 through 59).
All other numbers are reserved and will not affect the operation. To disable this option simply
set this Parameter to 0.
The factory-default value: "0"
Example: Parameter value 12010050 means A=1 (relay 1 output), B=2 (light sensor), C=0
(value lower than), D=1 (switch relay On), EFGH=0050. In this case if light sensor reading
drops below 50 lum, the relay 1 output will be switched On.

HE-TPS05 USER MANUAL 30
≡ Note: The relays still can be controlled manually using touch buttons according to
Parameters 41-45 and 51-55 or via gateway.
≡ Note: The logic will implement the operation when the sensor value crosses the value
in the Parameter. Meaning, that if the logic switches ON the relay and you manually
switch it OFF, the relay will switch ON next time when the value crosses the set
Parameter.
Bei Heltun ist es aber Anders

rudolfkoenig

Zitat...parameter values are encoded as 7-digit numbers (ABCDEFG).
Das kann man aber mit BitSet nicht implementieren, da BitSet binaer arbeitet, und das hier aller Anschein nach dezimal.
Analog zu BitSet koennten wir dafuer DecNrSet einfuegen :)

Damu

#13
In der Anzeige beim Bitfeld steht "Bit 8" dann kommt das 8er Bitfeld, nach dem Feld würde eine "1" es etwas übersichtlicher machen.

Das im Helfertext eine neue Zeile geschrieben wird ist nicht möglich?
Die meisten machen 9 Leerschläge (Tab) für eine neue Zeile.
FHEM ignoriert das aber alles.
Wenn ich abere mehrere Helfertexte nacheinander schreibe wie würde das dan dargestellt?

Zitat<Help>
"Stupid" mode = (bit 2 = 1):
- has higher priority then slave mode.
- LED is permanently on (for simple power wall switch controlling).
Slave mode = (bit 0 = 1):
only if included in Z-Wave network.
- useful for controlling via third-party sensor.
- LED is directly controlled via Z-Wave, internal sensors are not used for controlling it.
Central Mode = (bit 1 = 1) Central unit checking:
(useful especially for controlling via gateway).
When slave bit is 0:
- device signalises fail of lifeline connection (if this bit is zero, fail of lifeline connection is not  signalised).
When slave bit is 1:
- device checks presence of Z-Wave device in lifeline group (gateway).
If it is not    present for 2 minutes (testing repeatedly every 30 seconds).
device switches to normal mode in the same way as after the end of local disabled mode (ON_BEHAVIOUR).
- the device checks every 1 minute for recovery of Lifeline connection.
- if no lifeline specified.
- it works in normal mode.
</Help>
Zitat<Help>
"Stupid" mode = (bit 2 = 1):</Help>
<Help>
- has higher priority then slave mode.
- LED is permanently on (for simple power wall switch controlling).</Help>
<Help>
Slave mode = (bit 0 = 1):</Help>
<Help>
only if included in Z-Wave network.
- useful for controlling via third-party sensor.
- LED is directly controlled via Z-Wave, internal sensors are not used for controlling it.</Help>
<Help>
Central Mode = (bit 1 = 1) Central unit checking:</Help>
........................
 

Binn immer noch dafür eine User_ZWave.xml einzuführen.
    

rudolfkoenig

ZitatDas im Helfertext eine neue Zeile geschrieben wird ist nicht möglich?
Die meisten machen 9 Leerschläge (Tab) für eine neue Zeile.
FHEM ignoriert das aber alles.
FHEM fuegt alles, was es zwischen <Help>...</Help> findet, mit einem <br> (HTML fuer neue Zeile) zum internen Hilfe-Puffer, dieser wird im Browser angezeigt.
Der Browser ignoriert die Text-uebliche Formatierungen wie mehrfache Leerzeichen, TAB und NL.
Fuer eine neue Zeile kannst Du entweder mehrere <Help>...</Help> Konstrukte einfuegen, oder gleich HTML verwenden.
Ab sofort werden 9 Leerzeichen aber auch nach <br> konvertiert.

ZitatBinn immer noch dafür eine User_ZWave.xml einzuführen.
Habs gemacht:
user_zwave_manufacturer_specific.xml wird vor openzwave_manufacturer_specific.xml durchgesucht.
user_zwave_deviceconfig.xml.gz wird vor fhem_zwave_deviceconfig.xml.gz und openzwave_deviceconfig.xml.gz durchgesucht.

Damu

ZitatHabs gemacht:

Super vielen Dank.
Die muss sicher in /opt/fhem/FHEM/lib hin?
Welche Rechte muss die Datei haben?

rudolfkoenig

ZitatDie muss sicher in /opt/fhem/FHEM/lib hin?
Ja, genau wie die anderen Dateien "gleicher Bauart", die verteilt werden.

ZitatWelche Rechte muss die Datei haben?
FHEM muss sie lesen koennen.

Damu