I have a Chamberlain. WD1000, I think. It has WiFi built in and doesn’t use the add-on adapter.
Have to admire the persistence! Kudos to you!
3 Likes
I am not sure what automation folks are building off of their MyQ plug, but for me I realized the only automation I was looking for was to trigger a close in certain situations (like we are going into sleep mode and want to ensure all the doors are closed). As the MyQ app already has notifications for doors left open etc.
So instead of trying to punch it a system that MyQ is clearly trying to close, I just connected MyQ to IFTTT and trigger a door close using Vera + WebHooks. If Vera ever got their act together and finished the IFTTT integration than you could also listen to door open and close actions, but for now this was all I needed.
For me it was triggering a zwave light to turn on and off. I’m now using my motion detector instead and will soon remove the app and files from Vera.
The scene with motion detection is limited without using things like reactor which I haven’t had time to explore.
The myq iftt webhooks though is another hack too because garbage myq charges a fee to interface directly which is preposterous for the functionality you would actually get.
And lastly the go control or linear zwave garage door opener has terrible reviews across Amazon and there’s no other US zwave choice. Kind of aggravating
It’s silly these goofy manufacturer’s will offer 1,000 zwave lights but only 2 choices for zwave garage. Depressing actually.
I have mine tied in with different lights to manage them. For example:
-
Exterior lights that are turned on if a car enters the driveway after dark. If the garage door opens within a minute of this, the lights remain on until after the door closes. Otherwise, the lights go off in a few minutes.
-
Garage lights (LED shop lights) come on with opening of the door after dark and go out after the door closes.
-
At a certain time at night, the door is triggered to close if it’s open (ensuring that the door is never left open overnight).
You could also use it to flash a light inside the house to alert that the door was just opened or possibly closed.
It’s also a “second source” of historical data of when the door was opened and closed and provides actual details over time as opposed to the “open for three minutes” output of the MyQ app that only shows time since last status change and current status.
I’m guessing this means that you did not get this working again? Did you try removing the door and re-adding it through MyQ and then attempting a fresh install of the door in Vera?
Hi @ember1205
I did not try, I lost my appetite for it and I could just as easily be back in this spot again so I’ll skip it. Bit I thank you and everyone for the help.
I’ll look at reactor for better scene setup as I have another one I’d like to fix.
MyQ IFTTT integrations was free for me? Maybe they changed their mind and made if free. But I am not using IFTTT for buisness… maybe they charge on that one.
I had a flakey MyQ opener on one of my doors, so I actually installed one of these https://www.amazon.com/Honeywell-Ademco-958-Overhead-Contacts/dp/B0006M1I1W/ref=sr_1_19?dchild=1&keywords=garage%2Bsecurity%2Bsensor&qid=1586553051&sr=8-19&th=1 to my door using a wirelless sensor (for my security system) to get an open/close signal. Eventually I replaced the faulty Opener so it is reliable now, but I am betting that magnetic sensor wired into a z-wave sensor would work just as well (better than those stupid read switches that never work right).
I’m curious why you are opting to NOT try what should be a few minutes of your time to remove and re-add the opener. If this DOES fix it, it’s a zero cost solution and you go back to where things were. If it doesn’t, it’s a few minutes of your time spent.
FWIW - Mine started working today, for no known reason.
My Myq stopped working. Wont login and get updates any more. No control over my doors. Anyone else have this issue?
Just checked, mine still works. Chamberlain brand.
Thats odd for me than. Mine seems to log in fine now after reinstalling the plugin. But wont update the status or control the doors. Mine are saying they are both open when they are closed.
Mine is also working fine, Chamberlain.
Thanks, I installed the Homebridge plugin for IOS and I wonder if that had screwed up any of the API keys or anything for the Vera
Around 9:48am PDT today two separate Vera units on different ISPs started failing the status check on the MyQ plugin. “Error Could not Initialize Connection” Verified id/password for both, access to MyQ app on phone and website is fine. Haven’t had time yet to pull logs and see what’s going on but looks just like what happened last time with the change to TLS. Seems like another protocol change? Anyone else seeing issues?
I can confirm I am also having issues as well… this doesn’t look good
Unfortunately Chamberlain is at it again. Mine stopped at the 1:48pm ADT. Hope a fix will come soon. As someone has said before, reverse decompiling the Android app is not a sustainable model.
Tested my MyQ today, and it is not functioning.
“ERROR: Could not initialize connection.”
It was working a couple of days ago. Working fine from the Andriod app.
I just updated to firmware 1.7.4970 on my V+, and don’t know if that had anything to do with it.
Here are some logs, I’ve tried logging in and out no help.
50 07/04/20 10:08:51.102 luup_log:139: (MyQGateway::MYQ_API::retrieveSecurityToken): called <0x754ab520>
02 07/04/20 10:08:51.102 luup_log:139: (MyQGateway::MYQ_API::retrieveSecurityToken): POST request URL: [https://myqexternal.myqdevice.com/api/v4/User/Validate] Headers [{ ["Host"] = myqexternal.myqdevice.com,["Content-Type"] = application/json; charset=utf-8,["Content-Length"] = 62,["Accept"] = */*,["ApiVersion"] = 4.1,["App-Version"] = 3.88.30470,["MyQApplicationId"] = NWknvuBd7LoFHfXmKNMBcgajXtZEgKUh4V7WNzMidrpUUluDpVYVZx+xT4PCM5Kx,["Culture"] = en,} ] Data [{"username":"********","password":"********"}] <0x754ab520>
02 07/04/20 10:08:51.313 luup_log:139: (MyQGateway::MYQ_API::retrieveSecurityToken): received response: {
"SecurityToken": "",
"ReturnCode": "0",
"ErrorMessage": "please contact customer care, supportID: 11621071380447938643",
"CorrelationId": ""
} <0x754ab520>
02 07/04/20 10:08:51.314 luup_log:139: (MyQGateway::MYQ_API::retrieveSecurityToken): Retrieved security token! <0x754ab520>
02 07/04/20 10:08:51.315 luup_log:139: (MyQGateway::MYQ_API::getUserData): called. <0x754ab520>
02 07/04/20 10:08:51.489 luup_log:139: (MyQGateway::MYQ_API::getUserData): GET request [https://myqexternal.myqdevice.com/api/v4/User/GetUser] Headers [{ ["Host"] = myqexternal.myqdevice.com,["App-Version"] = 3.88.30470,["Accept"] = */*,["ApiVersion"] = 4.1,["Culture"] = en,["MyQApplicationId"] = NWknvuBd7LoFHfXmKNMBcgajXtZEgKUh4V7WNzMidrpUUluDpVYVZx+xT4PCM5Kx,["SecurityToken"] = ,} ]. <0x754ab520>
02 07/04/20 10:08:51.491 luup_log:139: (MyQGateway::MYQ_API::getUserData): response [{"ReturnCode":"216","ErrorMessage":"Unauthorized (216)","CorrelationId":"d6cdd6e3-e0ce-4089-a722-bcbc068d1997"}] <0x754ab520>
01 07/04/20 10:08:51.491 luup_log:139: (MyQGateway::MYQ_API::getUserData): Authentication error. <0x754ab520>
01 07/04/20 10:08:51.491 luup_log:139: (MyQGateway::MYQ_API::getUserData): finished - UserData [Authentication Error!] <0x754ab520>
06 07/04/20 10:08:51.492 Device_Variable::m_szValue_set device: 139 service: urn:macrho-com:serviceId:MyQGateway1 variable: Timestamp was: Sat Jul 04 2020, 10:08:23 now: Sat Jul 04 2020, 10:08:51 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x754ab520>
06 07/04/20 10:08:51.493 Device_Variable::m_szValue_set device: 139 service: urn:macrho-com:serviceId:MyQGateway1 variable: Timestamp was: Sat Jul 04 2020, 10:08:51 now: Sat Jul 04 2020, 10:08:51 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x754ab520>
50 07/04/20 10:08:51.493 luup_log:139: (MyQGateway::task): task [Clearing...] <0x754ab520>
50 07/04/20 10:08:51.494 luup_log:139: (MyQGateway::MYQ_API::inspectDevices): called - SecurityToken [] <0x754ab520>
02 07/04/20 10:08:51.495 luup_log:139: (MyQGateway::MYQ_API::inspectDevices): GET request [https://myqexternal.myqdevice.com/api/v4/UserDeviceDetails/Get] headers [{ ["Host"] = myqexternal.myqdevice.com,["Content-Type"] = application/json,["App-Version"] = 3.88.30470,["Accept"] = */*,["ApiVersion"] = 4.1,["Culture"] = en,["MyQApplicationId"] = NWknvuBd7LoFHfXmKNMBcgajXtZEgKUh4V7WNzMidrpUUluDpVYVZx+xT4PCM5Kx,["SecurityToken"] = ,} ]. <0x754ab520>
02 07/04/20 10:08:51.671 luup_log:139: (MyQGateway::MYQ_API::inspectDevices): response [{"ReturnCode":"216","ErrorMessage":"Unauthorized (216)","CorrelationId":"c67d7877-e4e6-412c-a078-bd8a9f595aed"}] <0x754ab520>
01 07/04/20 10:08:51.674 luup_log:139: (MyQGateway::MYQ_API::inspectDevices): deviceContent: [{ ["ReturnCode"] = 216,["CorrelationId"] = c67d7877-e4e6-412c-a078-bd8a9f595aed,["ErrorMessage"] = Unauthorized (216),} ]. <0x754ab520>
01 07/04/20 10:08:51.676 luup_log:139: (MyQGateway::MYQ_API::inspectDevices): Failed call to the MyQ API, perhaps refresh of token needed? <0x754ab520>
06 07/04/20 10:08:51.676 Device_Variable::m_szValue_set device: 139 service: urn:macrho-com:serviceId:MyQGateway1 variable: numDoors was: ERROR: Could not initialize connection. now: ERROR: Could not initialize connection. #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x754ab520>
06 07/04/20 10:08:51.677 Device_Variable::m_szValue_set device: 139 service: urn:macrho-com:serviceId:MyQGateway1 variable: numLights was: Check brand, username and password. now: Check brand, username and password. #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x754ab520>
01 07/04/20 10:08:51.677 luup_log:139: (MyQGateway::MYQ_API::inspectDevices): FAILED to Retreived device data <0x754ab520>
01 07/04/20 10:08:51.677 luup_log:139: (MyQGateway::justRefreshDevices): Error on refreash doors, Exiting. <0x754ab520> ```