Passing a dimmer value to a comparison when simply turning it on or off ( not dimming )

74 views
Skip to first unread message

Joeri

unread,
Nov 27, 2017, 3:02:06 PM11/27/17
to Loxone English
Quick little question:

Does anyone know why the value doesn't get passed when I just enable the dimmer? If I change the dimmers value, so brighter or dimmer, then the value is passed. But a simple on or off does nothing.

Is there a sane explanation for this? Or a better method I could use instead of the Greater Then block.

All advise is welcome.


Joeri

unread,
Nov 27, 2017, 3:21:44 PM11/27/17
to Loxone English
I think my question would be more correct if I would ask how I can detect the on and off state that's passed to a dimmer. Because I just noticed that the value you can see while dimming or making it brighter is the value to add to the dimmer, so in this example 2.0 is added when I long press the button. So I see "2.0" on the line. But nothing happens when you simply turn it on or off. So ... am I correct to presume that although the line presumes a value is passed, the value to activated and deactivate the dimmer doens't pass through that line at all? 

Question remains how I can detect it ... 

Duncan

unread,
Nov 28, 2017, 6:04:46 AM11/28/17
to Loxone English
 this is related to using a smart actuator- there is dimming rate as well as brightness passed to the actuator

if you set the lightiong block so that output type is a normal 0-100% actuator then the value gets passed to the comparison block without problems

Joeri

unread,
Nov 29, 2017, 7:10:07 AM11/29/17
to Loxone English
That did the trick indeed. Too bad we can't read the same values from the Smart Actuator, in the end they are all the same I guess, but still :) 
Reply all
Reply to author
Forward
0 new messages