That explains things a little bit. As an android user I’ve yet to see the new layout with recipes so I can’t comment too much on those other than to say that I’ve always been a bit leery of how much recipes can or can’t do. Some of the logic of what I want to do can start to be complex pretty quick.
For example: When my side door opens I want a light to turn on if it’s after sunset or before sunrise, and then go out 5 minutes later. Okay, no problem a recipe can handle that I think.
Next, if it’s after 11pm and before 6:00am and motion is detected in my upstairs hallway I want the dimmer to come on at 10%, then shut off 5 minutes later… unless the right is already on, then don’t do that. This is a much more complex situation and going to be harder to do with recipes because we’re talking about multiple conditionals (time, current state of lights) as well as different device times (light switch and motion sensor). How can a recipe account for which devices you want to combine and how can it handle things like check if it’s on or off?
Or worse yet… I have a program running that watches for my presence tag to come home. When it does it first checks to make sure I’ve been gone at least 10 minutes (to avoid a false leaving). If I’ve been gone more than 10 minutes it’ll open the garage, assuming it’s closed, then 30 seconds later it unlocks my side door. Then, for the next 10 minutes it’ll watch for my side door to open, then close. When it does, it’ll shut my garage. I can’t imagine how a recipe would handle a situation like this. Now we’re talking something that incorporates a presence tag, a Z-wave outlet (to run the relay to open the garage door), a garage door position sensor, a z-wave door lock, and a door open/close sensor.
For basic things recipes are great and the iOS version of the Mobile App does have recipe functions build in (coming eventually to Android… not sure when though). But for complex think I don’t think you can ever get away from SmartApps.
Are you aware that you can write your own SmartApps?