Commands, states and comparators in experimental rules engine

[Eseraz (Dominik Schlierf)]

@rlkoshak

I’ll start with the caution that “Experimental” is in the name for a reason. It is not complete and only available for experimental use and testing. There is no documentation and it is not feature complete.

Sure, my post was not meant to be criticism, I’m just trying to understand how things currently work and to avoid missing any functionality by accident.

@rlkoshak

Concerning the trigger, I am slightly confused, that i have to set a state at all, since I would expect, that any evaluation of the actual temperature would take place in the conditions part of the rule.

You don’t have to provide the State. Just leave it blank.

Even more confusing is that none of the given states make sense for a state of a temperature.

You can type in the state for String and Number states. So if you did want to trigger when the temp gets to a specific number just type in that Number.

Ah yeah, that makes sense. So in case I wanted to check if it is at a certain temperature i’d type in that Number. If I wanted to check if it is below a certain Number I’d leave it blank and do a separate check in the conditions section.

@rlkoshak

For a Color you can use 200,20,254 as the command.

Actually I tried that, but I seem to have run into the bug you mentioned:

@rlkoshak

As of this writing there is a bug that will wreck your Rule it if is not first triggered by an Item event the Rule will never correctly run. So we need to create a Test Switch Item which we will use to trigger the Rule.

Pointing this out really helped me a lot, thank you! I made sure now, that this is the case for every Rule I’m testing with.

@rlkoshak

Would it be possible to add a feature, that the UI gives you better command options for the actions?
So for example I click on the command SET_STATE when I selected my bulb and then I can set the parameters for the bulb as RGB or HSI values?

Probably. It’s still a work in progress, experimental. I don’t know what is planned for or what needs to be requested. It wouldn’t hurt to create an Issue over at Eclipse Smarthome.

Alright I will do so! Also when looking for the origin of these default values I found that in /rest/module-types the same values appear.

@rlkoshak

Beyond what I’ve mentioned above all I can offer is that the documentation for the Experimental Next-Gen Rules Engine was essentially started two days ago. I don’t think anyone on this forum really knows how this all works yet and it is very important to realize that it is not done being developed.

Thanks a lot, this is really useful to me!