Has anybody successfully used a Hager dimmer actuator with the GIRA HS QuadClient? If so, how?
(FYI, some doc can be found here)
The default QC dimmer plugin has three fields: 1) switch, 2) dim and 3) brightness.
The first one does an ON/OFF - easy it maps to object 0.
The second is used for the "relative" dimming (i.e. when you a long-press on your wall button for example). It maps to object 1 of the dimmer
The third one is used for the "absolute" dimming i.e. it sets the %age of brightness directly. It map to object 2.
If I do that, it works fine AS LONG as there is no other device doing a RELATIVE dimm in parallel. The reason is that object 2 always return the last ABSOLUTE value that was set on this object and NOT the EFFECTIVE value that a relative dimming would have changed.
Let's go through a scenario:
- I open the QuadClient and set the dimmer (object 2) to 50% => fine, visu is up-to-date
- I do a long push on the wall button and do a RELATIVE dim, effectively reducing the dim to, say, 25%
- The Hager actuator sends a notification through object 7 with the new value of 25%, but this is not connected to the QC plugin
- If I set the object 7 (notification of REAL dim value) as a watch of object 2, the HS queries object 2 again to get the updated value and gets... 50%! Not 25% i.e. it gets the last ABSOLUTE value that was set in the register, not the actual one.
Questions:
- Is this the expected behavior of most Dim objects?
- How to fix this while keep the default plugin in QC? Would the Graphic Logic Editor help? But how?
- Do I have to create my own plugin with the HS SDK to get a correct behavior for Hager?
- Do you know if such a plugin would already exist?
Thanks!
Cal
(FYI, some doc can be found here)
The default QC dimmer plugin has three fields: 1) switch, 2) dim and 3) brightness.
The first one does an ON/OFF - easy it maps to object 0.
The second is used for the "relative" dimming (i.e. when you a long-press on your wall button for example). It maps to object 1 of the dimmer
The third one is used for the "absolute" dimming i.e. it sets the %age of brightness directly. It map to object 2.
If I do that, it works fine AS LONG as there is no other device doing a RELATIVE dimm in parallel. The reason is that object 2 always return the last ABSOLUTE value that was set on this object and NOT the EFFECTIVE value that a relative dimming would have changed.
Let's go through a scenario:
- I open the QuadClient and set the dimmer (object 2) to 50% => fine, visu is up-to-date
- I do a long push on the wall button and do a RELATIVE dim, effectively reducing the dim to, say, 25%
- The Hager actuator sends a notification through object 7 with the new value of 25%, but this is not connected to the QC plugin
- If I set the object 7 (notification of REAL dim value) as a watch of object 2, the HS queries object 2 again to get the updated value and gets... 50%! Not 25% i.e. it gets the last ABSOLUTE value that was set in the register, not the actual one.
Questions:
- Is this the expected behavior of most Dim objects?
- How to fix this while keep the default plugin in QC? Would the Graphic Logic Editor help? But how?
- Do I have to create my own plugin with the HS SDK to get a correct behavior for Hager?
- Do you know if such a plugin would already exist?
Thanks!
Cal
Kommentar