[OBSOLETE] MyQ Lite Door and Lamp Control (for Liftmaster/Chamberlain)

I see, I went back and tried it again. Now I can both close and open the garage doors. It’s a little awkward to say “Alexa turn on garage door CLOSE” but it works now. Thanks Brian!!

BTW, does this code support more than two garage doors? I have 3 doors in MyQ account but only two shown up in the config steps. I think the previous version shown all three.

Glad it’s working for you! I’m definitely going to rename those push button switches so by default you can say “Alexa, turn on the garage door closer” or “Alexa, turn on the garage door opener” - it’s still kind of awkward but probably as good as it gets for now.

And yes, this code currently supports up to 4 doors. If a door is missing from the config, it’s because it was somehow filtered out by the code when parsing the response from MyQ. I may have tweaked that in my case thinking I was getting an extra entry back that wasn’t needed, but I’m wondering if that is causing other people to be missing some doors. I’ll look into reverting that and see if your other door shows up again.

1 Like

Thanks for the NoSensor version. After your updates, I now see both garage doors (I only saw one before) and can open and close both of them. I had to add the momentary-button-tile DTH manually in the IDE like you had referenced. One other thing, the DTH for myq-garage-door-opener-NoSensor.groovy had to be manually added as well. Anytime I try to import it straight from your github repo, it errors even though the other one and the smart app from your github imported fine. Anyway, thanks for this improvement!!!

Installed this tonight as well. I had been using the original copy-ninja version still with a core piston set to poll & refresh the status of the door every 5 mins. It was working fine. I’ll let you know if I run into any issues.

I wasn’t able to get the github linked way to work, when I installed that way it would error out on the last smartapp setup screen. I had to install all the elements from code and it seems to be working now all though I haven’t tested it in any automation yet.

This is great, thank you for putting it together.

Were do I find logs for Devices that don’t get added?

Updated 0 devices and created 1 new devices, 1 published (1 skipped due to errors)

The device types can’t be added:
devicetypes/brbeaird/myq-garage-door-opener.src/myq-garage-door-opener-NoSensor.groovy

I think I pushed out an update last night that broke the tie between SmartApp and Device handler. Should have that fixed shortly.

Ok, update is published:

  • Fixed issue where sometimes not all doors were showing up as eligible to be added
  • Fixed issue where app was unable to create the child NoSensor door device
  • Push buttons are now named “[door name] Closer” and “[door name] Opener”
  • Updated instructions to include installing the required Momentary Tile Device

Word of warning - if you’re updating this through GitHub, make sure you’re adding both the SmartApp and Device Handler code from my brbeaird -> NoSensor branch of the repository.

Ok,

I went in and deleted everything I had previously.
Added the SmartApps first and that went fine.
I attempted to add both devices at the same time. The first one loaded fine, the second one did not.

Thanks

Just to clarify - are you seeing that problem when going through the setup in the mobile app or when adding the device handler code (through the github integration maybe)?

When attempting to add the device handler. I haven’t gotten far enough to add in the mobile app yet.

I did add your suggested Momentary button device

Which device handler is failing? The normal door opener or the NoSensor one? And is this manually copy/paste or from GitHub? If it’s GitHub, I’d suggest waiting an hour or so and then trying again - I’ve seen it cache some weird stuff and not properly pick up changes.

devicetypes/brbeaird/myq-garage-door-opener.src/myq-garage-door-opener-NoSensor.groovy

I’ll try again tomorrow.

I deleted everything and added everything back via Github integration and it worked fine.

Thank you for the work!

Hey all - I’ve gone ahead and merged the changes into the Master branch, so this update is officially live. I’ll go and update the original post of this thread later tonight to reflect the changes. Feel free to let me know if you run into bugs. Just make sure you have installed all 3 device handlers as that’ll be the most common error people run into.

No signature of method: script14816796241101829787121.metadata() is applicable for argument types: (script14816796241101829787121$_run_closure1) values: [script14816796241101829787121$_run_closure1@6537742a] Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)

error i get creating the app from code

Check and make sure you’re copying SmartApp code into a SmartApp and not a Device Handler (and the other way around).

Edit - was able to publish successfully from the Git repo, working great!

We’re good there, made the devices first, no issues. Go to make the app and get that error when i hit create

Thanks for the help, can’t wait to get this working!

@brbeaird

Nice thanks. I deleted all and hooked to master instead of NoSensor and re added everything again no issues. Also quick renamed my doors in myq as it was named “Garage Door Opener” and asking Google Home to turn on garage door opener garage opener was a bit too much. :slight_smile:

Thank you again for taking the time.

1 Like

Error when creating the SmartApp:

No signature of method: script14817241921581829787121.metadata() is applicable for argument types: (script14817241921581829787121$_run_closure1) values: [script14817241921581829787121$_run_closure1@2a0ddf08] Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)

I’m from Canada and GitHub integration doesn’t work from here, so I can’t try that method.

I’ve only seen that error when trying to paste Device Handler code into a SmartApp window. Would you be able to send a screenshot of that error as you’re seeing it?