Patterns proposal: item states delay management and items dependencies (cascading)

[wawa79 (Yann)]

@rlkoshak

NOTE: I can think of some very elegant ways to implement this in Scripted Automation that might make it worth pursuing. For example, using Item Metatada you can define metadata that defines which Items to wait until they reach which states before commanding another Item.

JSR223 is finally running so give me some days (or weeks) before I get all potential benefits from it and start implemeting

• [+] it is much faster (but slower than DSL would have been difficult)

• [+] tags on items and rules

• [+] more control over rules. I am thinking about a useful item.SendCommandWhen(command, Item received command/changed/updated to, triggeringStrategy) which could be volatile (trigger once only) or persistent until a RemoveCommandWhen() call

• [-] rules running synchroneously. Is this a joke? So everything will have to be put into threads. See my reply here