Mode for Return from Away Mode

So I created a related post requesting an option be added to the mode manager so that I can return from away mode when a lock is unlocked. I was told to "just make a rule for that". But I cannot.. because there is no "return from away mode" option when setting a mode... I mean you can set "Away" but no way to signal the Mode Manager that I have returned from away.

I am requesting a Feature to add "Not Away" from the list of Modes in the rule manager. Then the Mode Manager can see that and set the appropriate mode it should be in based on the time of day or whatever.

Mode Manager (new) will return from away via Presence.

Create a virtual device, using the Virtual Presence driver. "just make a rule for that" tracking your Lock.
Screenshot 2023-01-02 at 1.21.31 PM

3 Likes

Just tagging @bravenel so that he can consider/answer/clarify your feature request.

1 Like

I appreciate your helpfulness here. I am trying to create a feature request. Not work around my request. I am sure there are lots of rubber bands and paperclips we could use to get around this. However, just as there is a need for "Away" in the rules.. there is also a need for "Not Away".. in the rules. (: I am sure we could work around the use of "Away" in the rules... and yet it exists!!!

This is why I am posting in the "Feature Requests" area and not the support (I need help) area.

Thank you.

This rule uses a Virtual Presence device; this device would be included in Mode Manager Presence table for Return from Away...

This could as easily be done with a Virtual Switch...

1 Like

Our generic approach for apps like Mode Manager is not to load them up with additional features. Most things outside the 4 corners of Mode Manager can be accomplished in other simple ways. So, if you want to call that a work-around, that's fine. But our preference is not to feature-creep these apps. Many users find them hard to understand as they are. More features make them harder.

7 Likes

A lock is a switch with an "on" and "off" position. Not including this feature literally makes it much harder and requires that I create more rules and more paths I have to track to fix things.

No matter. I am not going to tell you how to do your job. Hubitat is an amazing product. I am very happy with it. I am, as a user, simply telling you what I want/need. Add the Features, or do not.

Let me give you a little more feedback/information....
There is no physical lock. I want to be able to turn off my Security System and return to whatever normal operating mode exists via voice through my Alexa. I do not want just any one to be able to yell into my house to control it. So by setting it as a "Lock" Alexa allows me to code a voice code before locking/unlocking it. I imagine many others would use this if it were easier to reach configuration wise.

Also you closed my other feature request which is a VERY different request than this one.

Yes, and a contact sensor is a switch with Open / Closed, etc. You'd have to add a single rule.

We're sticking to our strategy of not adding features to apps when adding a simple rule accomplishes the desired outcome. We just don't see the burden this places on edge-case users as sufficient cause to make the core apps more complex for everybody.

It appeared to be along the same lines of extending Mode Manager to include locks. So, the same response as above is equally applicable.

Why don't you create a special virtual device driver that has both Lock and Switch capabilities, and ties the two together.

There is a Virtual Lock in our public repo, here: HubitatPublic/examples/drivers/virtualLock.groovy at master · hubitat/HubitatPublic · GitHub

Adding Switch to that would pretty easy. So when you lock the lock, it turns the switch on, and unlock turns it off. Then you wouldn't need any extra rule.

Actually, to make it into a hybrid with PresenseSensor would be even easier: 3 lines of code.

2 Likes

Looks like it already has switch capability:

on() locks and off() unlocks.

It's two lines of code to throw switch events from lock/unlock:

in lock:

sendEvent(name:"switch",value:"on")

in unlock:

sendEvent(name:"switch",value:"off")

The driver already has capability switch, so it's good to go with those two lines added. Then it could be used in MM as a switch for Return from Away.

1 Like

This feature request has nothing to do with locks. This is simply a request to create a way back from a feature that you already created. You have a created a feature to set an "Away" mode but there is no way to return from that away mode with a simple rule. I think see screenshots of somehow creating actions that will signal the mode manager to return me from away mode.. But I have no idea how to execute that. In your quest for simplicity you have made it more complicated and above my head with your app. I will need step by step directions on how to impose that code into the system.

Two ways:

  1. Above I posted a rule that would do it with a Virtual Presence sensor (you'd have to create the virtual presence device). You would include that presence device in Mode Manager as a presence device for Return from Away.

  2. Take the code from the link above and put it into Drivers Code in your hub. Add the two lines of code I posted just above, and hit Save. Then change the driver for your existing 'lock' to that driver, listed in Type under User on the device page. After that you would add your 'lock' device as a switch into Mode Manager.

The simplest way to do Return from Away is to use Mode Manager to do it, with a Switch or Presence sensor. It already allows Return from Away for those.

4 Likes

One of the things I did to get around my wife’s android phone going from present to not present within 5 secs was to when we are present coming back from away to set mode manager/hsm to disabled and then do a x amount of time to wait then set it back to home mode/home arm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.