myQ

Will there be an update from SimpleCommands for myQ? My account will no longer “link”. Hopefully so! 😀
12

Comments

330 comments
  • The irony in all of this is that SC should not even be necessary when you think about it. MyQ already interfaces with Amazon to allow for "Key Delivery" effectively allowing us to provide that service. If they don't want 3rd party apps to interfere with their relationship, then just give us a gosh dern MyQ skill that we can install in our Alexa app and allow voice control. The relationship is already there, so why not just extend the capability. Then we wouldn't even be here in the first place. Thank heavens for SC for being able to give us an avenue to voice control, but Chamberlain/MyQ should just seal the deal with Amazon to allow a skill with no middle man....My two cents anyways..

    4
  • I am having the same issues as well

    3
  • Yeah, the instructions on that package make some assumptions.  Hopefully, these are a little clearer.  It's a little long, but it's spelled out step by step...

    1. Download the code (makes things easier).
    - Go to https://github.com/spenwall/myq-alexa
    - Click the green "Code" button and click Download ZIP.
    - Unzip the downloaded file.

    2. Go to the Alexa Developer page
    - Go to https://developer.amazon.com/alexa/console/ask
    - You'll need to login to your Amazon account. I'm not sure, but you MAY need to register for a developer account as well. (I already had one, so I'm not sure if you need to or not.)

    3. Create a skill
    The link above will take you to the Developer Console page. On this page...
    - Click the Create Skill button.
    - On the Create a new skill page, enter/select the following...

    • Skill name: Enter a name for your skill. For example, "MyQ Garage Door".
    • Primary locale: English (US) (this is the default)
    • Choose a model to add to your skill: Custom (this is the default)
    • Choose a method to host your skill's backend resources: Alexa-hosted (Node.js) (this is the default)
    • Click the "Create skill" button at the top right of the page.

    4. Add Interaction Model
    At this point, you'll be on the Custom Skill Builder page.
    - On the menu on the left side of the page...

    • Click Invocations > Skill Invocation Name. Under "Skill Invocation Name", enter "garage door".
    • Click Intents > JSON Editor.
    • Open the alexa.json file (downloaded in step 1) in Notepad (or your favorite text editor). Select all the text in the file, and hit Copy (Ctrl-C).
    • In the JSON Editor, Select all the text in the editor and hit Paste (Ctrl-V) to replace all the text in the window with the text from alexa.json.
    • You may optionally change the invocation name to something like "garage door" (or whatever you like) by editing line 4 in the window to say...
      "invocationName": "garage door",

    - Finally, click the "Build Model" button at the top of the page.

    5. Add the Code
    - Click on the word Code at the top of the page.

    - On the list of files at the left side of the page, double-click on index.js.
    - As above, open the downloaded file "index.js" in Notepad, and Copy all the text from the file. (Select all then Ctrl-C.) Then paste the text into the window. (Select all then Ctrl-V.)
    - In the window, on lines 8 & 9, enter your email & password for your MyQ account.
    - Click the Save button at the top of the page.

    - On the list of files at the left side of the page, double-click on package.json.
    - As above open the downloaded file "package.json" in Notepad, and Copy all the text from the file. (Select all then Ctrl-C.) Then paste the text into the window. (Select all then Ctrl-V.)
    - IF you changed the "invocationName" in step 4, you'll edit line 2 in the window and paste the same name in. For example, if you changed the invocation name to the following:
        "invocationName": "garage door",
    Then you'll need to change line 2 to the following:
        "name": "garage-door",
    (Note that it's the same name, but all spaces are replaced with hyphens.)
    - Click the Save button at the top of the page.

    6. Deploy
    Hit the Deploy button at the top of the page and let it build.

    7. Test
    - Click on the word Code at the top of the page.
    - Next to "Skill testing is enabled in:", select "Development".
    - In the "Type of click and hold the mic" button, enter a command like "Ask garage door to open". (You can also use a mic to say this command.)
    - You should hear your garage door open.

    This didn't work at first for me. So I had to do the following...
    - Click on the word Code at the top of the page.
    - On the list of files at the left side of the page, double-click on index.js.
    - Change line 28
        From...
          return result.devices[1].serial_number;
        To...
          return result.devices[0].serial_number;
    - Try step 7 again. It worked for me after doing this.

    8. Use it on Alexa
    At this point, your skill is attached to your Amazon account. All Alexa devices that are registered to this account automatically have access to this skill. You can say the following commands:
    - "Alexa ask garage door to open"
    - "Alexa ask garage door to close"
    - "Alexa ask garage door status"

    You can see your skill by...
    - Open the Alexa app.
    - Go to Skills & Games
    - Click on Your Skills.
    - At the top, where it has boxes for Enabled, Updated, etc, scroll the boxes to the left until you see Dev and touch that box.
    - You should see your new MyQ Garage Door skill.

    Your skill is in Developer mode which means it's private. It has not been published to the Skills section of Alexa so nobody else can get to it. (Make sure that you do not go into the Distribution section and Distribute your skill. That would enable others to open and close your garage door!

    Finally, if you want to create a Routine in Alexa, the actual skill will not be available because it's in Developer mode.  So for the Action, instead of using a Skill, you'll need to use a Custom Action and type in "Ask garage door to open".  It works fine.

    I hope this helps (even if it was a bit long).

     

     

     

     

    3
  • Same issues. I deleted the connection and it won’t reconnect. SimpleCommands what’s happening? When can we expect a fix for this?

    2
  • Finally an update per SC specialist:
    "Hi:

    Sorry for the troubles. The myq auth api has changed. We have the fix working in dev and will have the fix moved to our production servers by Mon/Tues at the latest."

    2
  • This issue happens way too often. Integrating MyQ with Simple Commands is the only thing I use this app for. I get the feeling SC is not authorized to link up with MyQ and Liftmaster keeps shutting them out, blocking the hack, etc.

    2
  • Well, count me as one of the disgruntled. Except I don’t have as much patience as many of you. Putting MyQ on Kijiji and that will be that once and for all. I did some research and have ordered this one. https://gotailwind.com

    And no, I don’t work for them or anything like that.

    2
  • YESSSSSS!  Thank you SO MUCH Salam and SwiftRox!

    2
  • As for the light control…  The skill that we’re using references the myq-api npm package (https://www.npmjs.com/package/myq-api).  This myq-api package is the code that does all the work of actually communicating with MyQ.  The code for the skill simply calls methods in myq-api, like login(), getDoorState() to get the current state of the door, and setDoorState() to actually open and close the door.  The skill wraps these calls in a little bit of logic so that if the door is already open or currently you opening, it won’t try to open it again (and same for closing it).

    The myq-api also has methods for getLightState() and setLightState().  So it would be pretty simple to add a new intent like “turn on” that calls setLightState() instead of setDoorState().  The official MyQ app doesn’t have a way of turning the light on or off, so I don’t know if setLightState() actually works or not.  But it would be easy to try.  Maybe on the next quiet day.  😀

    2
  • Jason....Stop following the thread then...nobody here is complaining except you.....

    2
  • I'm sure myQ has changed something on their end, hopefully SimpleCommands will be updated so it will continue to work.  

    1
  • Ed L, yeah same here..  unable to link the myQ account, I'm positive myQ has changed something and the SimpleCommands app will have to be updated.. hopefully that will happen, it's a great piece of software.  

    1
  • Same issue here. SC it's an awesome app for shortcuts through Alexa. Hope they find a solution soon.

    1
  • Clicking on the Garage Door (myQ) item in the app home screen generates a pop up box with this dialog:

    "We cannot connect to your myQ account, but the fix should be easy. Please click the fix connection button to re-enable the connection."  [Cancel]  [Fix Connection]

    Clicking the Fix Connection button dismisses the pop up box, and clicking on the Garage Door (myQ) item again causes the same pop up box to reappear – nothing was fixed!

    Please help!

    1
  • I think more of us should reach out to MyQ to complain. I just sent them an email. We SHOULD be able to link MyQ directly to Alexa, so instead of blaming SC, we should really be harassing MyQ to get moving on this. In the MyQ app, tap your initials on the top left, then tap Support, then on the bottom right tap Contact Us and send an email.

    Here’s what I wrote: Why don’t you integrate directly with Amazon Alexa devices for voice control of garage doors? You have a lot of unhappy customers who use a service called SimpleCommands to perform this functionality using Alexa and when you modify your API (like you did last week), you break other services like SC which must then make changes to re-allow users to open their doors with Alexa. MyQ users spend a lot of money on your equipment and integration with Amazon Alexa is table stakes for any product that connects via wifi these days, so why don’t you support this feature directly? This rigamarole your customers have to go through every 6 months because we rely on 3rd party services to allow integration with Alexa is hugely frustrating when you could simply add this functionality to Alexa yourself without any 3rd party hacks.

    1
  • That that was my thought too - that this is a hack and MyQ is trying to keep them out.  MyQ has actual partners and official integrations, and SimpleCommands is not on the list.  https://www.myq.com/works-with-myq. IF MyQ was changing their API, I doubt they’d do it in a way that broke all the integrations for all their customers.  so my assumption is that SimpleCommands keeps finding ways around their rules and MyQ keeps locking them out.

    The only other option I’ve seen is to get a device like this one which hooks into the opener and integrates with Alexa, basically bypassing MyQ. https://www.amazon.com/Refoss-Garage-Control-Compatible-Assistant/dp/B07PM59X4J

    I wish MyQ would simply integrate directly with Alexa (I believe it actually did when I bought it).  They integrate with Google Home and even with Amazon Key. 

    1
  • I wrote an email to Sc Wednesday about giving us an update on what's going on and when it possibly was gonna be fixed since the late Tuesday deadline has passed and wasn't fixed, I still yet have received a reply, there not very good at keeping us upd all they would have to do is post on here or Facebook and we would see it and not be left in the dark

    1
  • As mentioned, no blame to SC, but I’d just like to know if they have waved the white flag and this extremely convenient functionality is forever gone and unsupported. It’s beginning to seem that way. Just want to know if it’s time to buy an actual new opener that natively supports Alexa.

    1
  • It’s been over a week now. They got the error message fixed but still getting Invalid Credentials when trying to log into MyQ. I’m not sure how many people are still working at SC but I’ll give them the time as Chamberlain obviously is trying to lock them out as they are not a certified partner. The app has been great because it circumvents the limitations that Chamberlain has made. If SC can’t get it back I thank them for doing what they could and making the app so user friendly and integrated with so many different things. There are many other options out there but they will require a physical device to bypass Chamberlains limitations. Fortunately these devices are rather inexpensive. My worry is they are smaller companies and I am concerned about their security practices.

    1
  • I’ve got to agree. I’ve got to agree with you all.  Not slamming SC (all blame rests on MyQ - I’ll NEVER have another of their products in my home), but *I suspect* (I don’t actually know) that SC is trying to get around a restriction imposed by MyQ.  Each time they find a way, MyQ finds out and blocks it.  It’ll stay that way until SC (or Amazon Echo) becomes an official partner with MyQ.  I don’t know what’s involved in that but it hasn’t happened.  I’m also concerned that other noname, relatively small companies, like Refoss and Meross, could go out of business, or stop supporting Amazon Echo integration, or Amazon could cut them off, or any number of scenarios that would make them stop working.  Not to mention the security exposure with handing over the credentials for my garage door to these companies.  (Of course, I assume that SC is probably a very small company and we all went ahead and handed them access.)  But that seems like it might be the best way to go because it totally bypasses MyQ.  And at around $20, it sounds like an easier way to go than to continue messing with SC and MyQ.  

    1
  • Yeah myq might have finally did it and totally blocked them out, you would think myq would want people to use there devices interactivity with alexa unles they only want people using their app

    1
  • I am stuck here:

     

    - IF you changed the "invocationName" in step 4, you'll edit line 2 in the window and paste the same name in. For example, if you changed the invocation name to the following:
        "invocationName": "garage door",
    Then you'll need to change line 2 to the following:
        "name": "garage-door",
    (Note that it's the same name, but all spaces are replaced with hyphens.)
    - Click the Save button at the top of the page.

     

    Did you mean line 2?  I can't find this line to edit?

    1
  • That's correct.  Line 2 of package.json says the following
        "name": "my-garage",

    If you changed the invocation name in step 4 to "garage door", then you'll want to change line 2 of package.json to:
        "name": "garage-door",

    You can either change that line in Notepad, then copy/paste it into the Code page on the Developer Console.  Or you can change it directly in the Code page after you've copy/pasted it in.

    If you didn't change the name in step 4, then just leave that line alone.  (And your Alexa command would be:  "Alexa, ask My Garage to open".)  My preference was "Alexa, ask Garage Door to open".  I also wanted to provide an example on how to change the name.

     

    1
  • Zook33....the line 2 is in the "package.json" tab.....You change that to "garage-door" or whatever you optionally changed the invocation name in the final instruction of (4) Interaction Model....I did make the change...so I had to update the package.json line 2...You must also use a hyphen between the two words....he said spaces are replaced with a hyphen....

    {
    "name": "garage-door", 
    "version": "1.0.0",
    "description": "MyQ garage door opener for alexa",
    "main": "index.js",
    "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
    },
    "author": "Amazon Alexa",
    "license": "Apache License",
    "dependencies": {
    "ask-sdk-core": "^2.7.0",
    "ask-sdk-model": "^1.19.0",
    "aws-sdk": "^2.326.0",
    "myq-api": "^2.0"
    }
    }

    Salam...You are the man!! It worked for me....The garage is now opening and closing!!

     

    1
  • Did you try the follow up steps he gave when he said it didn't work for him? Also...he made one mistake...he said after "Deploy" then you choose "Code" at the top, but that was wrong...hit "Test" and then follow the steps to

    7. Test
    - Click on the word Code at the top of the page.
    - Next to "Skill testing is enabled in:", select "Development".
    - In the "Type of click and hold the mic" button, enter a command like "Ask garage door to open". (You can also use a mic to say this command.)
    - You should hear your garage door open. 

    1
  • Salam...I have one question. I setup a MyQ configuration at a friend's house to use SC for two separate garage doors. So (1) MyQ, and (2) Sensors....How do you write this skill to control those doors independently? Do you create a skill for each door? For example...Bay 1 and Bay 2?

    1
  • Swiftyrox… The code in this is only setup for a single door.  If I had two doors, I’d probably setup two skills - one for “garage door left”, and one for “garage door right” (or however you want to name them).  You’d need to change line 28 (see step 7) on the left one to:
        return result.devices[0].serial_number;

    and the right one to:
        return result.devices[1].serial_number;

    (or maybe the reverse of that).

    Or if you have a little coding ability, you can change the json and js files to accept different “intents”, like “a open left” and “open right” (or whatever).  That way you could say “Alexa, ask garage door to open left”. It would actually be pretty easy to do.  (Although I only have one wide door, so I can’t really test it.)

    1
  • Correct, which was the message Alexa gave me on testing before I changed it.

    1
  • OMG! I had a pretty quiet day so I decided to give the custom skill a go. So easy! I added a few notes to Salam Dahbour's break down for clarity. Happy to post that here if someone wants. But really, great job Salam Dahbour et. al!

    1
  • I’m selfishly hoping this skill doesn’t catch on too much so MyQ won’t notice and shut us down. Hopefully they don’t peruse this board but I bet they do.

    1

Please sign in to leave a comment.

Didn't find what you were looking for?

New post