Well then their solution is to show the devs how their push works. That will reduce their load. Co-operation not wankerishness.
2 Likes
Yes that would have been a good way to handle the situation. I think the HA MyQ integration guy actually asked them for a partnership but they declined / did not respond. Maybe this is something a corporate entity like NC should initiate.
According to the developer working on the myq integration the official app uses mqtt somehow and doesnāt poll. He makes a lot of good points on this post about how this whole mess could have been avoided.
And on that note, Iāve definitely pulled mine off line. Wouldnāt be the first time a firmware update ended local control
2 Likes
They donāt have a web app, just mobile apps. My guess is they rely completely on iOS / Android push notifications, which HA canāt hook into.
Another way to look at it is at those numbers, the integration would be responsible for ~218 requests per second. Thatās not that manyā¦ but if they didnāt design their services to expect that, that could easily hit a slow path. Of course, they could throttle it without completely blocking, or make their service more performant, or even consider charging users a monthly fee for API access.
Whatās interesting is between this and the Mazda integration, thereās been broader press coverage of the existence of these sorts of cloud integrations. What happens to adoption of systems like Home Assistant if the majority of cloud polling / push integrations get blocked over the long run? It seems like a real threat to the project.
It makes sense the bridges use mqtt to publish states and listen to commands, but I doubt they listen to states of other garage doors. Even if the app uses mqtt when open, it canāt maintain a persistent connection for more than a few minutes once itās closed.
Regardless, based on Chamberlainās past history of trying to use the DMCA to block universal garage door remotes, itās clear theyāre not a good actor in this space.
https://scholarship.law.marquette.edu/cgi/viewcontent.cgi?article=1233&context=iplr
2 Likes
As a point of clarification - the app uses rest to communicate with the myq server and the myq server uses mqtt to communicate with the myq device.
2 Likes
From what I can see, The Chamberlain Group isnāt interested in any sort of home automation server integration. They are seeking multi-year subscriptions tied to each vehicle app as their angle: Connected Car Services & Solutions | myQ
I considered a Meross MSG100HK (with the free yellow button adapter) connected to Home Assistant. But instead I got a Security+ 2.0 Dry Contact adapter from EBay (basically a modified 883LM button) wired to a WiFi relay and Iām hoping to integrate that from Home Assistant to CarPlay.
Iām leaving the MyQ there to see what happens with Amazon delivery and the car apps I use (which arenāt supported yet), but Iām not excited about having to pay for a 3-year or 5-year subscription to use MyQ in my car. Iād love to be able to talk from my Home Assistant to the MyQ device via mqtt, but I donāt think thatās going to happen.
Can you give some more info on this? What opener did you have - Security +1 vs 2? What kind of MQTT commands? I know that the door buttons at my house simply put different value capacitors across the two wires for the lock and light buttons, and I could duplicate that if I had to, but if at all possible, I would like to just be able to do it directly.
The problem is the communication beween the opener and the gateway is secure and proprietary, so you are unable to acess it or control it.
You need the ratgdo, use the specs linked to make your own, or one of the other suggested alternate methods. Iām using the ratgdo.
My Homebridge hasnāt connected to the internet since the day I set it up, so I could care less if I loose access to the cloud. My concern was with the removal of the MyQ integration.
Iām hoping since Iām using HomeKit iām not affected and this is only for the cloud connection.
Iāll get RatGDOs at some point but so far homebridge has been okay and was easy to setup.
Will the ratgo device also handle the video feed from the opener?
Will tge ratgo also allow you access to video feed from garage door opener
No, unfortunately ratgdo doesnt support video.
Iām unaware of any way to get video outside of myqs apps for their video products- their system by design does not play well with other options. They want you to have to buy their video subscription and not be able to use the camera with anything else.
I would recommend installing a generic ip camera nearby that uses a universal protocol like mjpeg or onvif that will easily integrate with home assistant
I have a foscam g2 on my garage but see this post for some other camera suggestions
I ended up using the Konnected garage door control. I also purchased a Security 2.0 compatible button from Amazon for $11. Toss in a little soldering and I have a complete, local control solution to replace the crappy MyQ. The Konnected box has a door open sensor that measures the distance from the ceiling so it can tell when the door is open. Itās not as well instrumented as MyQ was but it works.
Itās also running esphome so you can customize it if you want. Highly recommended
1 Like
It wonāt. But you are much better off getting an IP camera with standard protocols like ONVIF. Iāve had several Amcrest and canāt complain about them.
And when it comes to IP camera, outside of the typical options of a dedicated camera in the garage, there is also the option of installing IP Webcam Pro onto almost all unused Android phone, if you have any in your junk drawer.
Over the years I have gathered 3 old Android phones from my family. So I paid for the Pro version of the app, which would turn all my unused Android phones as regular IP cams.
1 Like
The problem is the communication beween the opener and the gateway is secure and proprietary, so you are unable to acess it or control it.
Yeah, I know that I need something else, and Iām planning on removing the MyQ gateway, since the company seems insistent on basically making it useless to me.
So Iām thinking Iāll go with a ratgdo also, but Iām trying to figure out what the likelihood is of success in getting the lockout to work on the remotes, since I have the v1, and the docs say it doesnāt work, but you seemed to say that you got it to. So Iām trying to mainly get more info on what you did before moving ahead with this. I want to do my homework, and if I need to build a custom board to support the āLockā feature then I will do that.
Thanks!
Oh I was mixing up which post you replied to. Initially with the MQTT firmware of the ratgdo I had to create a template device to create the lock entity. My yaml for it is below:
mqtt:
lock:
- name: Garage Control Lockout
state_topic: "garagedoorGarageDoor/status/lock"
command_topic: "garagedoorGarageDoor/command/lock"
payload_lock: "lock"
payload_unlock: "unlock"
state_locked: "locked"
state_unlocked: "unlocked"
optimistic: false
qos: 1
retain: false
Iāve since switched to the ESPHome firmware for the ratgdo and I like it a lot more - there are more options and the lockout function is automatically exposed to home assistant with no extra yaml. I do have security 2.0 though - I doubt it will expose the lockout with the v1 version and youād likely need extra hardware. Where is your lockout button on the v1?
This is everything showing with the ESP firmware for the ratgdo:
This is what the ratgdoās webpage looks like using esphome
Well when MyQ first came out they were touting how much liability there was about closing a door remotely without all of the lights flashing and beeping. There is no local API, and the solution to be able to use MyQ locally is to use a solution that doesnāt activate the lights and beeping. I wonder since they have decided to block people from using that functionality, they have some legal exposure. Iām not a fan of legal bullying, but it seems like they have removed from 0.2% of their users the access to they safety system, that they tout properly remotely notifies someone that the door is about to close. Where ever this goes, a local integration is what most people would prefer, with real time status.