Closed GoogleCodeExporter closed 8 years ago
I found this interesting document by ABB:
http://www.knx-gebaeudesysteme.de/sto_g/English/APPLICATIONS/2CDC500051M0202_App
likationsHB_lightingcontrol_EN.pdf
On page 26, you see the 4 bit telegrams for KNX dimming. Moreover, as also
stated on this page, it seems that start/stop dimming is the todays standard
solution.
Maybe IncreaseDecreaseType could be extended with an additional STOP value.
This value shall be sent unconditionally when releasing the button after a long
operation (in both cyclic and "one-shot" cases). Using sendFrequency=0 shall
disable the cyclic sending of the INCREASE/DECREASE value.
Original comment by cyril.ja...@gmail.com
on 8 May 2013 at 6:01
[deleted comment]
Original comment by teichsta
on 21 May 2013 at 9:28
Original comment by teichsta
on 23 May 2013 at 3:49
My suggestion would be to handle these specifics in the KNX binding. With a
special configuration, the binding itself could regularly send
INCREASE/DECREASE to the event bus. The EnOcean binding already behaves this
way and we discussed to possibly extract the so-called "profiles" from it, so
that other bindings can use the same logic.
Original comment by kai.openhab
on 6 Dec 2013 at 4:53
has been migrated to https://github.com/openhab/openhab/issues/635
Original comment by teichsta
on 10 Dec 2013 at 10:08
Original issue reported on code.google.com by
udo1t...@gmail.com
on 15 Sep 2012 at 9:29