(OH 1.x and OH 2.x Rules DSL only] Why have my Rules stopped running? Why Thread::sleep is a bad idea

[rlkoshak (Rich Koshak)]

@unparagoned

You recommend against lambdas yet your whole post is about how people should put stuff in lambdas

I recommend against using global lambdas. They are not thread safe and do not handle errors well. Lambdas used in timers or forEach or the like are OK because the thread safe problem goes away as a new lambda gets created each time rather than reusing the same lambda object across multiple threads.

@unparagoned

So I have both a long running script and locks. I think the script is run thought a lambda function, which probably helped. But how to I set up my rules so say I don’t hammer this device or hammer say the spotify api. What design pattern should I use to replace my locks? With say spotify, there are so many triggers, cron updates, manual buttons, motions sensors, voice, etc. I wanted to eliminate hammering the spotify api, also there are times when 10 rules get qued up and run together which I was trying to limit through locks.

Design Pattern: Gate Keeper Complex Examples using Queues.

Using Queues and a single Rule to work off that queue will allow you to queue up a backlog of commands if they occur too fast without consuming a Rules thread for each one waiting for it’s turn to run.