Skip to content
This repository has been archived by the owner on Dec 1, 2020. It is now read-only.

Getting device list #1

Open
seemmichael opened this issue Mar 23, 2017 · 12 comments
Open

Getting device list #1

seemmichael opened this issue Mar 23, 2017 · 12 comments

Comments

@seemmichael
Copy link

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
Copy link

BoPeng commented May 5, 2017

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
Copy link

BoPeng commented May 5, 2017 •
edited
Loading

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
Copy link

gwilli commented May 6, 2017

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
Copy link

BoPeng commented May 6, 2017 •
edited
Loading

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
Copy link

gwilli commented May 6, 2017

@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
Copy link

BoPeng commented May 6, 2017

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.

aromka pushed a commit that referenced this issue Jul 12, 2017
@natejgreene
Merge pull request #1 from natejgreene/use_result_and_atomicstate
eb047de 
Use result and atomicstate.  also remove ssdp leftovers for now
@perpetualbliss84
Copy link

perpetualbliss84 commented Jun 1, 2018 •
edited
Loading

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
Copy link

@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
Copy link

perpetualbliss84 commented Sep 21, 2018 via email

@nickfoti
Copy link

@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
Copy link

perpetualbliss84 commented Sep 21, 2018 via email

@nickfoti
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nickfoti @gwilli @BoPeng @seemmichael @perpetualbliss84