I don't want to get into a debate about this, but if the device has problems, their testing process clearly wasn't sufficient. I don't think you'll be able to persuade me otherwise.
So you're saying that I shouldn't expect to be able to use timers? How do I implement a central heating boost button without a timer? How do I do A, B and C x seconds after somebody leaves a room without a timer? How do I count how long a device has been turned on for? Timers are a pretty fundamental part of any automated system and to suggest that they shouldn't be used is a little bizarre.
However, I wasn't asking for comment about the functionality. As I have already said, it was a small test that let me see how rules, variables, timers and the dashboard all work - as such, it served its purpose.
Raw power? No, I don't think so. But even if it did, if that power comes at a cost of my time, then it's something I'd generally avoid.
Respectfully, I disagree. Not having to move from page to page to page would reduce the number of clicks.
If the end result is the same, then it is always better to have fewer clicks.
Then clearly I'm missing something. I wanted to test rules, variables, timers, the dashboard and actions in the easiest way possible.
How should I have done it?
Which was how my post started - I was trying to learn the Hubitat dashboard and every single comment told me to use something else.
I'm sorry, but I'm one of the (seemingly few) people who just don't get the attraction of the Raspberry Pi boards. As for NodeRed, I already use it. I was hoping to move to one platform that could do everything in one box.
Nicholas.