SmartTiles and Rule Machine

daven · December 10, 2015, 6:13pm

I have removed most of my routines and created rules to replace them. The one thing I’m missing is the ability to run routines from SmartTiles as the “Hello Home” is now empty. I assume I have to create a virtual switch that can exist in ST and then attach it to a new rule that will run an existing rule when true/false happens. I have looked around but don’t see where the code is for a generic virtual switch, anyone have a link?
If my thought process is wrong on accomplishing this please shout loudly and bring out the coloured crayons
PS I want to do the basically same thing with the new DSC integration as well, I want Alarm/Disarm to appear on the ST screen for easy access.
Cheers!

625alex · December 10, 2015, 6:21pm

If that’s all you want, then I suggest to be patient for the next little while and stay tuned for announcements.

daven · December 10, 2015, 6:26pm

Yeah I knew that was missing from ST and assumed that was probably on your to-do list
I did find another threads that says use a Simulated Switch as that is the same thing so I’ll give that a whirl for the ST Hello Home/Rule Machine integration idea.

Can’t seem to find a virtual momentary. I tried button but that doesn’t show up in ST. Suggestions on creating a one touch tile?

JDRoberts · December 10, 2015, 7:00pm

Does this help?

daven · December 10, 2015, 7:14pm

Thanks, was there already. I did some more Googling and found someone with momentary device code. Created it and put it into ST, all good now. I have a push button to run rules

github.com

damonfloyd/SmartThings/blob/master/MomentaryNormallyOn.groovy

/**
 *  Copyright 2015 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 *  Momentary Button Tile - Normally on
 *
 *  Author: Damon Floyd
 *
 *  Date: 2015-09-08
 */
metadata {
	definition (name: "Momentary Button Tile Normally On", namespace: "dfloyd", author: "Damon Floyd") {

This file has been truncated. show original

tgauchat · December 10, 2015, 7:54pm

What do you mean, “empty”?

Hello Home is now officially called “Routines” and SmartTiles just renamed the Hello Home Tile accordingly…!

(Though if SmartThings had just waited for Adele, they would have named it “Hello. It’s me.”. )

daven · December 10, 2015, 8:39pm

What I did was remove all my “Routines” and implement them in RM. Doing that leaves you with no access to runs rule from the ST app or SmartTiles.

tgauchat · December 10, 2015, 9:29pm

What is “RM”??? Can’t you trigger RM from a Routine?

ashutosh1982 · December 10, 2015, 9:35pm

RM is Rule Machine. I think @daven is looking for a way to have the rules from rule machine show up like a drop down on SmartTiles.

tgauchat · December 10, 2015, 9:48pm

Oh… Not a bad idea; but it’s a leap for SmartTiles to support any or every arbitrary Community Developed SmartApp out there, especially those not yet in the Marketplace (it isn’t in the Marketplace, yet, right?)…

But if Rule Machine gives us some hooks to call (other than Virtual Switches, please?) to find all the triggers so we can build a “Trigger a Rule Tile”, then we’ll be on our way there…

Possibilities include @bravenel supplying a Rule Machine Trigger Virtual Device creator (gee… that calls for a new Capability!), and/or exposing a Web Service (REST-API Endpoints) for SmartTiles to query and call…

ashutosh1982 · December 10, 2015, 9:51pm

Excellent Idea! Rule Machine and SmartTiles are the two best apps on ST platform according to me. But I agree that it will be better if these apps get officially approved by ST. @bravenel are you planning to do that? Submit Rule Machine to ST for review?

bravenel · December 10, 2015, 9:53pm

None of this is going to happen. It’s not possible to link between SmartApps other than through some kludge using a device intermediary. Making Rules accessible to SmartTiles doesn’t make sense to me. SmartTiles doesn’t give you access to Smart Lighting, or to any other app. It gives access to devices.

Rule Machine has been submitted, but that process is broken. Don’t hold your breath!

Edited to add, seeing the whole thread: Routines have a special seat in the ST pantheon. They are lame SmartApps that get to have location events and access through location. No other app has that status. None of that functionality is available to ANY OTHER APP!

daven · December 10, 2015, 9:55pm

I now have 5 momentaries in my SmartTiles. 2 arm and disarm my DSC Alarm and 3 run rules in Rule Machine on demand. I created a new SmartTile child called Routines and linked the URL into the main page.

ashutosh1982 · December 10, 2015, 10:04pm

May be its time for you to add a 3rd item along with Rules and Triggers… .something like “Actions”. …just sayin…
Actions can be external triggers which will only execute on external triggers … either through REST API or some other way. You can always have the Actions show up in your Rules Machine and Trigger App. Not sure if this is feasible or makes sense…but just throwing it out there…

bravenel · December 10, 2015, 10:09pm

But, this would be an extension to the ST architecture. How would you pull that off? We need them to make these types of extensions. If they ever do, odds are it won’t resemble anything we might actually dream up.

tgauchat · December 10, 2015, 10:09pm

Well… Routines have a “trigger tile” built right into the SmartThings native mobile App.
And, based on this thread, some folks are starting to use Rule Machine as a replacement for Routines.

Perhaps someday SmartThings will offer Events similar to those that trigger Routines for general use; but in the meantime, the choices are custom “Trigger” Devices (virtual momentaries), which really ought to be put into the Marketplace along with Rule Machine, and/or REST-API web services endpoints (which are already included, for example, in the Marketplace published “Smart Alarm”).

tgauchat · December 10, 2015, 10:12pm

Lookup the code to Smart Alarm…

github.com

SmartThingsCommunity/SmartThingsPublic/blob/5f85cd287342e5a5ad11b2da69049bfc8a1afcb4/smartapps/statusbits/smart-alarm.src/smart-alarm.groovy#L962-L982


      
          // Show "REST API Options" page
          def pageRestApiOptions() {
              LOG("pageRestApiOptions()")
          
              def textHelp =
                  "Smart Alarm can be controlled remotely by any Web client using " +
                  "REST API. Please refer to Smart Alarm documentation for more " +
                  "information."
          
              def textPincode =
                  "You can specify optional PIN code to protect arming and disarming " +
                  "Smart Alarm via REST API from unauthorized access. If set, the " +
                  "PIN code is always required for disarming Smart Alarm, however " +
                  "you can optionally turn it off for arming Smart Alarm."
          
              def inputRestApi = [
                  name:           "restApiEnabled",
                  type:           "bool",
                  title:          "Enable REST API",
                  defaultValue:   false
              ]

github.com

SmartThingsCommunity/SmartThingsPublic/blob/5f85cd287342e5a5ad11b2da69049bfc8a1afcb4/smartapps/statusbits/smart-alarm.src/smart-alarm.groovy#L64-L96


      
          mappings {
              path("/armaway") {
                  action: [ GET: "apiArmAway" ]
              }
          
              path("/armaway/:pincode") {
                  action: [ GET: "apiArmAway" ]
              }
          
              path("/armstay") {
                  action: [ GET: "apiArmStay" ]
              }
          
              path("/armstay/:pincode") {
                  action: [ GET: "apiArmStay" ]
              }
          
              path("/disarm") {
                  action: [ GET: "apiDisarm" ]
              }

This file has been truncated. show original

Damon_Floyd · December 21, 2015, 11:26pm

If you need a switch that can always be turned either “on” or “off” at any time there is another switch in that directory, though it’s misnamed. I use it so that I can turn on/off individual/groups of lights whenever I want without regard to what was already on. For instance, I have living room lights, kitchen lights, and dining room lights all individually switched (with virtuals), but I also have a virtual switch that groups them. Since they are all virtual momentary double pole (again mislabeled), they normally sit in a NC state. I can turn “on” living room lights, then turn “on” all lights, then turn “off” kitchen lights- or whatever sequence I want regardless of what the current status is.

The GUI part of that switch is messed up though, but since I don’t use the GUI for those virtual switches (I use them with Echo), I haven’t bothered to fix it.

Lgkahn · December 22, 2015, 3:24am

routines for me and many others seem to work fine when triggered manually. just not well when triggered internally via thing start happening etc or whatever.

I have left my routines and just have rule machine call them and have no problems with all the stuff occurring.

Hendrixer · January 30, 2016, 1:34pm

This is actually pretty simple with Rule machine and Rules + a REST API. I am in the middle off adding a REST API to Rule machine to make this work. Basically exposing some endpoints in Rule that allows the manipulation of the state and then endpoints to list capabilities, triggers, etc. I MVP’d it and it works fine with my own custom dashboard I created with React, so it can work with Smart Tiles.

SmartTiles and Rule Machine

Customers

Developers

Download the SmartThings App