The myQ app doesn’t seem to ask for re-authentication so they might have a long lived refresh token or something. If that is the case we could use Charles Proxy or similar tools to sniff the official app authentication flow traffic and capture the credentials and refresh token + initial access token. We could then add these details to HA config and could get this working again.
It would be a bit cumbersome to setup but might be a one time setup.
I don’t have the time to look into the app traffic this weekend but might have it next week.
Done with MyQ. I bought a Refoss with HomeKit on Amazon. Set up with HA as a HomeKit device and made it available to iOS via HomeKit Bridge. Local control, no cloud this way. Took a little futzing but so far so good. The wireless door sensor of MyQ is nicer than the wired door sensor of Refoss.
I have Liftmaster 8500 jackshaft openers. I’ve been using a combination of HA MyQ and HomeKit integrations for several years. The MyQ integration has had its ups and downs, but generally was able to keep up with Chamberlain. Thanks to all who’ve worked on it over the years.
Recently I’ve been exploring options to migrate to another platform. Unfortunately nearly all options are currently sold out. I’m certainly late to the party. In the meantime, I need to use the existing hardware reconfigured to not use the MyQ integration. This took some effort as the MyQ App was unwilling to add the existing doors to Apple Home, and Apple Home wouldn’t discover the already configured MyQ bridge.
So after several days of research and hand wringing I decided to take the plunge and reconfigure the doors. My previous configuration exposed scripts to Apple Home calling the cover.open service to avoid having to open the phone to actuate the doors.
Briefly, here are the steps I used:
Use iPhone settings to give access to Apple Home data.
Use the MyQ App to delete the bridge. This removes the bridge and all bridge-associated accessoris from your MyQ account.
Factory reset the 819LMB.
Use the MyQ App to discover, not add, the 819LMB device.
Connect the bridge to your WiFi (2.4Ghz) network. I selected the bridge SSID in iPhone settings.
Use the bridge button 1 and wall control Learn button to pair the doors.
The bridge and doors now appear in iPhone Home App.
I added the bridge and doors to HA with HomeKit Device.
Deleted the MyQ integration.
There’s more detail surrounding each of these steps. I had to factory reset the bridge once and start over as the firmware isn’t as robust as it could be. This works until stocks of other platforms are replenished .
The answer is that you can use the other side of the board to have additional dry contact controls or to work with doors that don’t use the serial protocol.
Thank you for a clear summary, and for all you have done. It’s time that when we as consumers BUY things we stop buying from vendors who force us to be consumers of their cloud services only. I wish someone would build a dedicated web page to try the bad and good, i.e. the vendors who tie you to their cloud, and the alternative products to replace them with.
Not quite sure why he didn’t open source the schematics and recently set up an LLC for it then.
I would personally love the idea of a company that makes devices that allow you to de-cloud your smart devices. I’m guessing it’s a legal minefield, especially in the US. Not so much because of the reverse engineering (that is legally protected for interoperability purposes) aspect but because of copyright and breach of contract angles to shutting down these types of businesses.
Hence the LLC, I assume.
I really hope this will turn out a positive venture for Paul and we’ll see more of his work in the community. He’s on the right side of things with this.
He’s bringing in money from it. And he deserves it IMHO. Making an LLC is the right way for him to go for tax purposes. As long as the software is open source
YoLink has been really good with HomeBridge integration. They have a Discord for both community users and developers.
I know, they brought myself in and a developer of the YoLink Homebridge integration work. Sometimes, they even send us deals, but no freebie hardware. Sad face.
Compared to MyQ’s behavior this is a complete reversal. We talk to their product managers and share technical issues. I even debugged their MQTT gateway for a new device on the market. They fixed it within about 48 hours of me emailing their engineering team.
So, if you are going to throw in with someone in the cloud front they are very open.
The guy spent the time and effort to figure out the protocol, design the device and test it. So I’m totally ok with him wanting to profit from it. That without talking of the copyright implications from Chamberlain’s point of view.
Seemed in his interview that he was careful about finding a different way to generate the security+2.0 rolling codes without recycling code from the opener so they couldn’t go after him for it. Of course when someone wants to get at you, they’ll just throw everything at you regardless just to waste your time and money.
If they are using AI and machine learning to block these API requests then lets use AI and machine learning to continuously call and complain to their customer support teams until they determine it is more cost efficient to fix the problem.
As someone with a MyQ garage opener with built in camera this is super frustrating. It is a nice opener otherwise.
Folks - Is there any cloud-based solution that can be integrated with HA to make this work? I have added the Myq integration with Ring, but you cannot open or close the door from that.
IFTTT seems to require a premium paid subscription.
Unfortunately, no. No good cloud solution that is being approved by MyQ.
You cannot open using IFTTT either.
You can close only - Yup - Seriously MyQ? How twisted is that? This is the kind of company that actively / intentionally being unfriendly to users.
Or put it another way, to remove MyQ from the equation altogether, no matter how difficult or how simple it is, would still be a better solution than MyQ.
I bet this is a legal liability thing. They want to avoid situations where people who don’t really know what they’re doing do something stupid in their automations and then proceed to rage post on social media and/or sue Chamberlain or IFTTT because their garage door ended up open for two weeks and their house got ransacked while they were on vacation.
I tried with both Ring and IFTTT.
Ring just a solid no-go. The devices don’t appear in home assistant. Although maybe there is a way around that somehow.
IFTTT… Besides only being able to close the garage… I remember when IFTTT used let you create some automations. At some point they limited you to like 10. And now it’s 2. I’ve never really liked IFTTT either because it was always way too limited.
I’ve NDP poisoned my GDOs, and routed their outbound MQTTS traffic to a MITM proxy. trying to get sslstrip working with MQTT packets and just route that data right to my home assistant MQTT server. It would need IP tables configured to keep that traffic NAT’d permanently to home assistant which i keep in a separate VLAN, otherwise i’d need to keep the MITM running constantly