I got the MYQ homebridge. Its working fine but I want to block it from teh internet. When I do, the garage door constantly becomes unavailable. Does anybody know how to block it from the internet without the unavailable issue?
I like the idea of ratgdo over others purely because I only need to add that to the door opener to get access to all of the intelligence already built into the door opener.
Open/Close state is the big one - no need to add additional sensors.
Modifying a wall button will only let you open and close it - without knowing the state. For me, the state of the door is everything. Other solutions require adding a sensor to the door. I bought this MyQ door opener because it had all of that built in.
The MyQ Homebridge plugin is still using the internet API - if you block it youāll lose access. To be able to block it from the internet it would need to talk to the MyQ directly (locally) - none of the software only solutions can do that.
Many people have an extra garage opener remote and a cheap zigbee dry contact device (Amazon $17). So Ratgdo is not the one and only best thing for everyone. Actually there are dozens of ways to do this depending on the opener and the home automation setup. Another example is when you have a non-chamberlain opener with a myQ hub for Amazon deliveries. For them, they donāt even need to wire the remote control since they can connect the dry contact directly to their wall button wires.
For older or non Chamberlain units, ratgdo doesnāt offer much advantage, but that hasnāt been the conversation.
The comment was specific to security+. There is nothing else Iāve seen that gives all the functionality of ratgdo (or esphome fork)for security+ openers: discreet open and close commands, light control, obstruction state, and opener open/close/opening/closing state.
Anything else and you are at least adding reed switches or other sensors to get something close to a usable solution. All more complicated to install than ratgdoās simple three wire hookup.
Iām saying there are other options besides ratgdo, especially options that arenāt backordered and may have pieces at home they can put together (for free). I donāt want readers thinking they are stuck with only one option to get their automations working again. It would be dishonest to lead readers to that conclusion.
Hereās another Security+ 2.0 option for those who have a dry contact available. You can also get the button for $11 on amazon if you feel like adding your own wires to the solder pads.
Security+ 2.0 Wired Dry Contact Adapter ā Garadget
We all should complain on Twitter for sure. MyQ is active and responsive there.
The best solution is to force them into bringing Home Assistant in as a āpartnerā of theirs.
Thank you for your hard work on MyQ integration codeowner! You rock
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 .
I explain this on my open source schematic repo for ratgdo: GitHub - Kaldek/rat-ratgdo: Open source schematics for ratgdo PCB
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.
I removed the homebridge-myq plugin from Homebridge. Will you now be able to delete may account and remove the account?
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.