Was just about to recreate a rule in RM which I quickly whipped up in Simple Automation just before cold weather set in. It's works great in Simple and I wouldn't bother to recreate in in RM if it weren't for one thing....
It dawned on me today that I have a freeze protection scenario dependent on ONE SINGLE BATTERY OPERATED Zigbee device passing through (and staying under) a specific temperature threshold. Obviously a vulnerability to reliability.
Before starting to recreate the rule in RM I looked again at how BLOOMING EASY it is to create a simple automation in Simple Automation....I opened up the drop down for the temperature sensors I could select and thought...gee, if I could only click multiple sensors and put an "OR" or maybe even an "AND" condition between them.
The "good automation habits" that would be prompted here would be to NOT rely on a single BATTERY OPERATED sensor to trigger important things such as freeze protection.
Just an idea, I am fully aware that what needs to be done here can be done in RM and this is in fact the quandary faced all the time...how much to put on the easier learning curve products/apps.
Ignoring the complexity to integrate this and taking the beginner user perspective,.....allowing multiple devices and specific conditions between them seems kinda slick.