Loxone eib dimmer update#
Loxone eib dimmer manual#

The effect is that the lighting controller shows the current situation (if it matches a mood), or manual if it does not. I think this should clarify the figures below (2 EIB switches are missing as I could not fit them on the screenshot but they are similar). We also disable the lighting controller for 0.2 seconds as soon as any lights change due to the lighting controller (it is enough to test the on signal of each output, as the pushbutton translates both rising and falling edge to a pulse. (as a status block has just 4 inputs, I needed 2 of them) The output of the status block is compared against a memory block that holds the same value 50 cycles ago: the reason for this is that not all the lights switch at the same time, and we don't want any states during the transition of one mood to another mood to trigger the lighting controller.

In the first case, the current mood number (AQs on the lighting controller) will be negative in this case it means we don't want the lighting controller to change to manual, so we do not trigger I1 (nor do we send AIs).

Loxone eib dimmer update#

In the latter case, we want to update the lighting controller to tell it we are in manual mode this is done by making sure AQ1 is on, which is done by triggering I1 when needed. This can have 2 causes: we are mixing moods in the lighting controller, or we are making changes with the EIB switches. If the status number is 1, it means the combination does not match a mood. I have to retrigger the analog memory everytime a mood changes, which is why I have all the equal-blocks and the monoflops I could not find a better way. The fact that we use O and R to switch the EIB Switches means we will not get into an on/off loop. If the combination matches, we trigger an analog memory to send this mood number to the lighting controller (input AIs) this will make the lighting controller show the current mood. I use 0 for all off, 99 for all on, 1 to indicate that no mood matches, and then the numbers from 2 and up for to mood numbers. any combination of switches is translated into a status number this number matches with the numbers of the moods. The circuit I1-AQ1 is used as an indicator, AQ1 is connected to the disable of the retractive switch on the second page: if AQ1=1 and we need to have it on, it means I1 should not be triggered.Ģ. I do not use a trigger as it became too complicated. Both on/off are connected to the AQ output, but the off has a not. the lighting controller triggers the EIB switches using the R and O outputs of an EIB Switch function block. The idea of integrating the lighting controller is the following:ġ. As such, in Loxone, I have a memory flag that allows me to trigger an actor, and a memory flag that allows me to see if a light is on/off. Just to come back to this: my solution that seems to work.įirst off: in KNX, I have a message that allows me to trigger an actor, and there is a sensor that tells me the current status of an actor. I would have to check which addresses I have for the dimmers. Seems like something to test when I have the chance. But if that is the only issue, I could live with it. a physical knx light switch), and the loxone lighting controller would not know of this change and still assume it is in the same scene-mode.

It would of course still allow a person to change a light (using e.g. The first condition I should have in the memory flag, the second one I think can be achieved with a push switch ( ), to change the permanent on/off into a change. If (light is off) and (Aq of the lighting block changes from 1 to 0) then do not trigger (the light is already off) If (light is off) and (Aq of the lighting block changes from 0 to 1) then trigger (the light if off and should be switched on) If (light is on) and (Aq of the lighting block changes from 1 to 0) then trigger (the light is on and should be switched off) If (light is on) and (Aq of the lighting block changes from 0 to 1) then do not trigger (the light is already on) Just of the top of my head, I imagine something like: I suspect that it should be possible to create some logic that can trigger the TR input of my eib pushswitch block. At the moment, I store the states of a light in a memory flag (one for every light), which is then used as input to the S of a eib pushbutton (to show the correct status of the button in the loxone app). 1/1/1 switches a light whereas 1/2/1 gives me the status of the light), the leds on the switches are connected to sync with that. My installer configured all knx lights with an address from which I can get the status (e.g. As I do not know KNX (nor have the license), I will either have to contact my installer or try something in Loxone.

So either in ETS it is necessary to change things, similar to how Loxone shows it on their website for an extended knx sensor, or I have to come up with something else.