Best practise regarding rules

[rlkoshak (Rich Koshak)]

You have to balance between two competing needs.

1. Rules should be short, easy to read and easy to understand.

2. Rule should run as fast as possible and you should have as few running at the same time as possible (see (OH 1.x and OH 2.x Rules DSL only] Why have my Rules stopped running? Why Thread::sleep is a bad idea)

@anonymous.one

Personally I look at rules as a learning experience, while I may not set them up in the best practice way; I do find ways to make my life way easier!

:+1 Writing Rules is a journey. It’s always worth revisiting Rules when you learn something new.

@MadFrankie

So the question is do I have one rule ie ‘when I am away do this this and this etc’ (ie turn on lights, stereo, and other looks like I’m home stuff), or do I have multiple separate rules all triggering off the presence dummy item?

It depends on the extent of the changes that take place when you come home or leave. If they are completely different I’d probably use two separate Rules. If they are largely the same with the differences being what commands get sent to the same Items, I’d do it in one Rule using Design Pattern: How to Structure a Rule.

If I have more than a couple of states (more than just home/away) and what is done in each state is pretty different, I’d use A simple scene management: finally a good use of scripts.