I’m trying to make a velbus input channel connected to an Ikea light. I created 2 rules (one stating -
if trigger CH1 received == IKEA ON IF IKEA=! ON
and rule numer 2 is
if trigger CH1 received == IKEA OFF IF IKEA=! OFF
I think the problem now is timing… in my log i get: #CH1 triggered PRESSED
‘IKEA’ received command OFF
‘IKEA’ received command ON
‘IKEA’ predicted to become OFF
‘IKEA’ predicted to become ON
‘IKEA’ changed from 0,0,0 to 0,0,100 #CH1 triggered RELEASED
‘IKEA’ changed from 0,0,100 to 72,100,100
so the light flashes a bit and either goes off or on…
how to make sure that only 1 rule is activated (either ON or OFF) instead of predictions and such…?
and anyone have an idea on how to do the DIM UP / DIM DOWN on these IKEA lights? (I want to make LONG_PRESS UP / LONG PRESS DOWN) and possibly COLOR ROTATE as well…
In general you’re going to get help much faster if instead of interpretations or abbreviated descriptions, you just include the actual code of your rules and the full log entries. Put them all in different code fences sections (how to use code fences) so that they can be easily read and then it should be pretty easy for us to find a solution for you.
You’ve hit on one of the most important distinctions to make as you get more and more into complex rules. In OH there are commands and there are states and even though some have the same terminology, they are not the same thing. This most often trips people up with ON and OFF as these can be either commands or states. The difference is that only certain item types have ON and OFF as their actual states, but many different items can handle ON and OFF commands in a sensible way.