Pointless Argument

This is why my lighting is basically all motion/mode/time based I rarely use my GH's for much. I have my garage doors setup to just notify me in case I forget to close them, then just whip out my phone and they are closed.

Edit: Hell both of our cars have the Homelink to close right from that, I can close the door like 4 different ways lol.

2 Likes

Same. It is all about automation with a few exceptions. Lighting is motion and contact controlled. I don't use Alexa for lights. If I'm watching a movie and I want to adjust the lighting I use my remote not yelling at a box with a movie playing.

Garage door is fully controlled for opening closing based on GPS (in vehicle) and Motion in garage and exterior cameras along with safety beams to prevent closing ON something...someone :slight_smile:

If the garage door is left open based upon lack of motion and timers the door is closed. My son who works nights always leaves it open so I don't care it closes.

Now there's more involved and gritty details to the whole setup for safety precautions but it's all solid and works with no hacked workarounds or bubble gum :slight_smile:

I yell at Alexa to set a cooking timer... that's about the most it gets used for :slight_smile:

1 Like

Same here.

I was using Automatic. Now I use OwnTracks for this - works great to open the door. The door closes when I open the door from the garage to the house.

Also use Owntracks to close the door when I exit the neighborhood.

1 Like

so.... what's all this about MyQ HE driver? I spent 30 mins reading and still confused. Can we start the conversation all over again please :wink:

Tried that... didn't work for us. Too many back and forth from the car to inside with groceries and stuff. Otherwise a great option.

Hmm, I know the guy who wrote that. :slight_smile: There is still no official way from within the platform to enable/disable apps/drivers by automated means, only manually checking the checkbox. (Could someone write an app that pretends to be a person checking the box, sort of like how Hubitat Package Manager pretends to be a user adding app or driver code? Probably. But I'd consider that pretty hack-y, too.) Given that the original intent of this feature was troubleshooting and not automation control, I'm not sure there ever will be. Can't speak for the platform devs, of course.

But @aaiyar basically mentioned above the workaround I mentioned there--just correctly mentioned that since Hubitat's Alexa integration (and maybe Alexa itself?) doesn't support garage doors natively, you'll have to use switches, locks, or some other thing it does support.

Personally, I'd do that with a Rule or something, a virtual/proxy device, and the unmodified MyQ integration. The alternative is modifying the MyQ app for mode restrictions, but unless you want to re-modify your fork every time a new version is released, sticking with this workaround would let you continue to use an unmodified version of that community app (unless you can convince the dev to add something like this, which they may or may not be willing to--I realize that was the original intent of your post, but since none of us can control that, I just figured I'd mention again something that is already possible today :slight_smile: ).

1 Like

At this point I would just put a controlable outlet on the garage door and turn that on and off based on modes. MyQ be damned if it works when unplugged.

Of course they sell ones with Battery backups and wifi and God knows what else attached.

3 Likes

I know you have a really nice GPS setup. I should look into that sometime. But I got to say this - for being free, OwnTracks works really well. I've got it setup such that the garage door starts going up when I reach my street (either end) and I'm about 20 seconds away ...

1 Like

@neonturbo made that suggestion earlier (in the parent thread). I think that's a reasonable solution as well for the conditions imposed.

1 Like

I tried automating my doors but the are open all the time and for different reasons there was no easy way to deal with this. So I just settled for being notified in case I forget to close them at night.

2 Likes

Or if you want to be damn sure. This looks like it could be automated with a dry contact.

https://www.amazon.com/gp/aw/d/B07PR81DSN/ref=mp_s_a_1_13?ie=UTF8&qid=1591934362&sr=1-13&pi=AC_SX236_SY340_QL65

1 Like

Yup... could be integrated... and pretty reasonable price too.

1 Like

@doctorkb, I think your request isn't unreasonable, but I can't help but think that you've misunderstood @aaiyar in one way or another, and I'm not sure why you've taken such offense to what he was saying to you. As many others have said, he's one of the most kind and helpful members of this community. And, to be honest, most of your posts in this thread seem to indicate that you're a pretty decent guy, too.

In my reading of his replies, he wasn't saying that your request as a whole (to disable door controls at the app OR driver level) would be a hack. I feel like he was pointing out that it wouldn't be right to do it at the driver level. But he did say that it was something that could be done at the app level.

And I think he's right; it probably could be added to the MyQ app, but I don't know that app at all, so I can't be sure.

2 Likes

Went to bed early last night and I miss all the fun. :wink:

4 Likes

@doctorkb, @jeubanks
Ok I sat down at a computer this morning it looks like it is disabled via an HTTP POST

POST HTTP://hubitat.local/device/disable?id={ID}&disable={true|false}

4 Likes

I submitted a feature request to the dev. My original request identified "driver/app" -- I don't care exactly where it would be implemented. He proceeded to start listing all sorts of hacks (which I identified to him as not desirable) that would solve it, then continued on to say why it wouldn't be an appropriate feature to add, which, frankly, isn't his decision to make.

It got to the point where his desire to have the last word went beyond my patience.

To be clear - I never perceived him calling my feature request a hack. The hacks were all the ridiculous ways he wanted to layer on additional functionality to accomplish it, rather than let the feature request stand. I've had enough issues with hub performance in the past (resolved as of late, thanks to a certain unnamed beta feature) to not want to introduce unnecessary processing when there'd be a simple solution that could resolve it.

Brilliant, thanks! This will certainly do for now!

Could I suggest posting that in my other thread from January about RM being able to disable/enable a device? Rule Machine disable / enable a device?

I was thinking it could be configured on a per-device basis.

That said, I'd settle for a flag that could be turned on and off via HSM or RM to say whether the device will execute actions or not.

I'm sorry, I have to agree with the others. If I have 20 dimmers (not unusual) that are partly "configured" in the "driver", for this type of platform I believe it it violates the original intent.
I asked a similar question and it was quickly pointed out that what I was asking for could easily be accomplished in an RM rule. I quite honestly had not considered the rule option and thanked the poster. This sounds similar.

You can disagree with me but you cannot discount me :slight_smile:

1 Like

So you're saying, that having a flag in the driver as to whether or not it should process requests violates the intent?

Perhaps some intent needs to be amended, then...

But hubitat staff have responded to say that the driver is the wrong place to do what you’re suggesting...

1 Like