I much prefer the Scratch interface for graphical program design. Why isn't SmartThings using it? It's FREE!
The SmartThings line/block interface is unreadable in comparison, and makes complex decision trees painful to design, much less implement. Hopefully its usability will evolve and mature.
Can their interface get state information from other rules? If not, then it's really too simple to be worth using in any real-world setup. It just doesn't scale. Subroutines baby, subroutines.
For example, there may be a bunch of ways to determine if a person may be present:
- PIR sensor
- BT/WiFi Phone MAC address
- Phone GPS position
- Voice Recognition
- Fingerprint sensor
- Video face recognition
- Iris detection
You get the idea. Ideally, I'd like to be able to make a "Person Present" state item that I can rework as new state hardware or software becomes available. But rules that depend on "Person Present" shouldn't care how that determination is made.
But if the distinction is needed, it is straightforward to make rules for "Known Person Present" and "Unknown Person Present". It scales.
How would the SmartThings Rule Builder handle such distinctions?
Actually, now that I think about it, does the WigWag rule builder support making input state objects? (Synthetic high-level sensors.) I thought it did, but I'm far from certain.