Getting device list

[seemmichael]

I have followed the readme on both Mac and raspberry pi, and the console stops on "Getting device list..." every time. I have refreshed/reinstalled/deleted/etc, but I cannot get past this step.

[BoPeng]

I am in the same situation. The node server says

=== === === MyQ Controller === === ===
[04/04 21:43:58] Retrieved config for server: 192.168.0.170:39500
[04/04 21:43:59] Config loaded
[04/04 21:46:43] Handling request for: /ping
[04/04 21:46:43] Getting ping... replying pong
[04/04 21:47:04] Handling request for: /ping
[04/04 21:47:04] Getting ping... replying pong
[04/04 21:47:10] Handling request for: /init
[04/04 21:47:10] Received init request
[04/04 21:47:10] Initializing...
[04/04 21:47:10] Getting device list...
[04/04 21:47:10] Handling request for: /init
[04/04 21:47:10] Received init request
[04/04 21:47:10] Initializing...
[04/04 21:47:10] Getting device list...

and no device is added to My Things. Note that I have a driveway gate in myQ, but it should be recognized as a garage door opener AFAIK.

[BoPeng]

Checking the code, it appears that it only works for garage door and switch, not gate.... Not sure if gate can be easily supported. Note that MyQ Lite's garage door opener device can be used for my gate.

[gwilli]

I also have the same issue. @seemmichael and @BoPeng when you went to the My Hubs section in SmartThings IDE, were you able to see a port number? There's no port number listed for my hub so I left it as the default. I wonder if that has something to do with it?

[BoPeng]

No. The default port works. You will see some error message if you change to another port. I could actually add some console.log(...) statements and see where the code went wrong but making the whole thing work would be extremely time consuming.

So in the end I switched back to myQ Lite.

[gwilli]

@BoPeng Thanks for the suggestions. I was able to debug it and fix the issue for my garage door. It's working now for me.

The problem is an age old problem: how to match on string data? Line 138 of myq.js is looking at the MyQDeviceTypeName and attempting to replace all or part of the string containing VGDO with GarageDoorOpener. For my garage door, the garage door device from the device list has the name Garage Door Opener WGDO. I'd guess that for @aromka's garage door, the value of MyQDeviceTypeName is just VGDO and that worked. Looks like MyQ/Chamberlain/LiftMaster keeps changing it up to keep this app from working.

I might see if I can come up with a better way of identifying the garage door opener from the device list response and submit a pull request. We'll see. Thanks again for pointing me in the right direction.

[BoPeng]

My problem is a bit more complicated as I have a lift master driveway gate. MyQ lite's garage door device works for me but this one does not. I might be able to make it work by comparing the code against MyQ lite but I do not have time for that now. I am also a bit discouraged on the node server side because it is difficult to run the server automatically on my qnap NAS.

[perpetualbliss84]

This just started happening to me out of the blue the other day. Cannot get it to work at all. has anyone sorted this out? Thanks.

@aromka Any idea why this would have stopped working suddenly? SmartApp communicates with the server and such but just sitting at getting device list.

[nickfoti]

@perpetualbliss84 I've been having the same issue for months but finally had a chance to take a look at why today. From the looks of it, the https://myqexternal.myqdevice.com/api/v4/userdevicedetails/get call is returning unauthorized:

{ "ReturnCode": "216", "ErrorMessage": "Unauthorized (216)", "CorrelationId": "244827af-610a-4e3e-865e-8627f4b60286" }

Perhaps the AppID is no longer valid or has been blocked?

[perpetualbliss84]

I kinda that same conclusion. Doesn't seem like the app is being supported anymore. I changed to something else for the time being.

---

From: Nick Foti notifications@github.com Sent: September 21, 2018 4:51 PM To: aromka/myqcontroller Cc: perpetualbliss84; Mention Subject: Re: [aromka/myqcontroller] Getting device list (#1)

@perpetualbliss84https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fperpetualbliss84&data=02%7C01%7C%7C10fdbcd6e93d496c846308d61ffb92f5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636731562686792819&sdata=krQ44zAYvtJUOECxLD59P9KxlJEq0%2Fj9aoQp9TeQfZE%3D&reserved=0 I've been having the same issue for months but finally had a chance to take a look at why today. From the looks of it, the https://myqexternal.myqdevice.com/api/v4/userdevicedetails/gethttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmyqexternal.myqdevice.com%2Fapi%2Fv4%2Fuserdevicedetails%2Fget&data=02%7C01%7C%7C10fdbcd6e93d496c846308d61ffb92f5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636731562686792819&sdata=BzRnm94tYOCwxFmbBjuMBvr3DcwIdQMblgbP88k%2FyfQ%3D&reserved=0 call is returning unauthorized:

{ "ReturnCode": "216", "ErrorMessage": "Unauthorized (216)", "CorrelationId": "244827af-610a-4e3e-865e-8627f4b60286" }

Perhaps the AppID is no longer valid or has been blocked?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Faromka%2Fmyqcontroller%2Fissues%2F1%23issuecomment-423652355&data=02%7C01%7C%7C10fdbcd6e93d496c846308d61ffb92f5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636731562686792819&sdata=0UNfTD4DeHWFM%2BDTzC2BpAu8PBX5o4NL1curl5Im7zE%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAej1x0TTmFKthClnbCuSlorh5HP0rq1Iks5udUMrgaJpZM4MnHtJ&data=02%7C01%7C%7C10fdbcd6e93d496c846308d61ffb92f5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636731562686792819&sdata=W3b37S0LuAjhj3ETzk7ii2PEsjDP19O34TCjeXMBuqs%3D&reserved=0.

[nickfoti]

@perpetualbliss84 It seems like several other projects popped up in the last year using the same AppID. I'm unclear on how you obtain one to begin with, but that could be the reason why it no longer works. Did you switch to MyQ Lite? I'm interested to know what you have currently working.

[perpetualbliss84]

Yes, thats what I switched to. Bought a few multipurpose sensors as well just to know if it actually is closed or open. I am hoping in the near future that Chamberlain releases for Smartthings again as they have for almost every other platform.

---

From: Nick Foti notifications@github.com Sent: September 21, 2018 5:37 PM To: aromka/myqcontroller Cc: perpetualbliss84; Mention Subject: Re: [aromka/myqcontroller] Getting device list (#1)

@perpetualbliss84https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fperpetualbliss84&data=02%7C01%7C%7C78e1d2b4110343b6c96908d62001feec%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636731590270579501&sdata=YdE%2FTmeLzcJcl78S6hubUVAi7f%2FqYhWoMRi05bVwTS4%3D&reserved=0 It seems like several other projects popped up in the last year using the same AppID. I'm unclear on how you obtain one to begin with, but that could be the reason why it no longer works. Did you switch to MyQ Lite? I'm interested to know what you have currently working.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Faromka%2Fmyqcontroller%2Fissues%2F1%23issuecomment-423663434&data=02%7C01%7C%7C78e1d2b4110343b6c96908d62001feec%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636731590270579501&sdata=KOHvFq%2F%2BaHYN8SQjJSxpONEewxd%2BoSL0klLOLj%2FnOv8%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAej1x3UQxzaNUdritR0E36yS1NequFxyks5udU3ygaJpZM4MnHtJ&data=02%7C01%7C%7C78e1d2b4110343b6c96908d62001feec%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636731590270579501&sdata=lHVtUdiSYBHnXge3zj6cSX92EI3%2Fb%2BddZdh5C%2FIEuDk%3D&reserved=0.

[nickfoti]

Gotcha, that would be nice - not holding my breath though. I begrudgingly reinstalled the MyQ app and have been using that since this stopped working.