@andresg - Let’s start with this one. It uses math in the piston. Migrate a Webcore Automation with Maath to Routines
Then let’s do something simple. A simple lighting trigger. I want a light to turn on 90 minutes before sunset. I can’t do it. The trigger is limited to 60 minutes. Additionally, if I want to use a timeframe that utilizes sunset or sunrise, I need two routines. It is easy to do 5pm to 11pm in one routine, but I can’t do sunset to 11pm in one routine.
You cannot write a routine that requires two different inputs from the same capability on the same sensor; i.e. if the temperature is >x degrees or temp is < y degrees.
I live in a cold climate. I have a heat mat that keeps ice from building up on my porch. The trigger to turn it on is webcore is if the weather is snowing, sleeting, or freezing rain. In routines, I can only pick snowing.
I could go on, but you get the point. Routines are extremely rudimentary, and you are limited in how many you can write. My math example will require 10 routines to approximate what I did exactly with one piston.
I see conversations here about how it is just power users who may be disappointed. I am not a power user. I can’t code. I only install stuff that other people figured out. Even for us regular users, this is a huge step backwards.