Error getting MyQ devices: undefined

[RCdiy]

Was working yesterday.

[7/1/2020, 13:33:20] [MyQ2] Error getting MyQ devices: undefined [7/1/2020, 13:33:36] [MyQ2] Error getting MyQ devices: undefined [7/1/2020, 13:33:44] [Config] Starting terminal session

[33racerx]

[7/1/2020, 11:04:54 AM] [MyQ] Error getting MyQ devices: Unauthorized (216)

Similar message, just started getting this today.

[cryptobrian]

Same here. I also tried using the chamberlain plugin, and it is also not working. Looks like Chamberlain changed something on their side again.

MyQ2 plugin error: Error getting MyQ devices: undefined

Chamberlain plugin error: Error: invalid response, got HTTP 401: {"code":"401.203","message":"Unauthorized","description":"The username or password you entered is incorrect. Try again."}

[RyanRadly]

I'm getting the same message @33racerx is getting, verbatim.

[armandr]

Same here:

[MyQ2] Error getting MyQ devices: undefined [MyQ2] Error getting MyQ devices: Unauthorized (216)

Running the latest version. It was working yesterday.

[whreams]

Same here. I’m sure the HB developer team is on it! Thanks guys!!!

On Jul 1, 2020, at 1:17 PM, armandr notifications@github.com wrote:

Same here:

[MyQ2] Error getting MyQ devices: undefined [MyQ2] Error getting MyQ devices: Unauthorized (216)

Running the latest version. It was working yesterday.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/hjdhjd/homebridge-myq2/issues/44#issuecomment-652573627, or unsubscribe https://github.com/notifications/unsubscribe-auth/APK2HVXAD4HFFZO73GWSGI3RZN4SNANCNFSM4ONUTWYQ.

[kydav]

I'm having the same issue, but it could be an issue with Chamberlain. I am able to get in through the app, but if I try the same login on their site, it says it is incorrect.

[LordZork]

I'm having the same issue as others here... probably everyone...

@kydav This may be a dumb question, but what site did you try logging into – chamberlain.com? That's the only site I'm aware of (since you can't log into their myQ site), and I had the same experience ("Your username or password was incorrect"). I tried the "Forgot your password?" option (even though I know my password and know it's correct), but haven't received a password-reset email.

Chamberlain is super annoying...

[kydav]

@LordZork I tried the same things, still no password reset email and it's been several hours. I tried to log in here: https://www.chamberlain.com/login

[LordZork]

Note regarding website login issues...

Working (successful login and password-reset): https://www.mychamberlain.com/ https://www.myliftmaster.com/ [These urls are essentially the same site/service, for myQ web-app access]

Not working (unsuccessful login and password-reset): https://www.chamberlain.com/

The plugin has been broken twice in less than a month. I am nervous that myQ is actually making efforts to thwart Homebridge support, since they can't profit from it. They have their own HomeKit-enabled hub, which is an extra and otherwise-unneeded device and expense. Hopefully this is not the case, and hopefully we get a fix/updated plugin that resolves the issue.

Regardless, Chamberlain/myQ has the most limited and cost-restrictive third-party support, integration, and "partnerships." They are terrible. They charge their customers for IFTTT integration and recently lost Wink support – one of the few partnerships they've had – because of their stupid and excessive partner requirements and fees.

[DMBlakeley]

myQ updated the iOS app to version 5.158 on June 29. How do you find out the build number for this version?

[DMBlakeley]

Found the build number, it is at the bottom of the myQ app Account page. Current build is 19859. Unfortunately, this change does not fix the issue.

[TheEngineerGuy]

Hey @DMBlakeley Any speculation on this one?

I am beginning to agree with @LordZork , this is starting look malicious. Their own HB product was so bad I gave it away, and now they are perpetually in a broken state for HB plugin. Doesn't seem very promising.

EDIT: Could it be because we are still using 4.1 API which they might be working on deprecating?

[Danimal4326]

Did` some digging, looks like they aren't letting the login go through, so there is no token passed:

{ SecurityToken: '', ReturnCode: '0', ErrorMessage: 'please contact customer care, supportID: 712915074050492145', CorrelationId: '' }';

[TheEngineerGuy]

So two possibilities that I can think of:

1. They did it only to the URL that we are using. Which can be fixed by using other URLs like connect.mydevice.com.

2. They cut off 4.1 calls off as part of their deprecation measures. Assuming that you made 4.1 call to get that response.

[pponce]

I was able to authenticate/login with v5.1 api call. Also able to pull list of devices with v5.1 api call. Your hunch about deprecating v4 is probably right.

[Danimal4326]

This is from the plugin (just added some extra logging), so yes api v4

@pponce how did you do the v5.1 api call?

[pponce]

here are the two api calls i was able to make.

myq login https://api.myqdevice.com/api/v5/Login

headers: Content-Type:application/json User-Agent:myQ/19569 CFNetwork/1107.1 Darwin/19.0.0 MyQApplicationId:JVM/G9Nwih5BwKgNCjLxiFUQxQijAebyyg8QUHr7JOrP+tuPb8iHfRHKwTmDzHOu ApiVersion:5.1

get devices and status http://api.myqdevice.com/api/v5.1/Accounts/{{AccountID}}/Devices

headers: Content-Type:application/json User-Agent:myQ/19569 CFNetwork/1107.1 Darwin/19.0.0 MyQApplicationId:JVM/G9Nwih5BwKgNCjLxiFUQxQijAebyyg8QUHr7JOrP+tuPb8iHfRHKwTmDzHOu ApiVersion:5.1

[shamoon]

https://api.myqdevice.com/api/v5/My headers: {{security-token}}

I'll see if I can get things back on track...

[TheEngineerGuy]

Ok good. So we know what the problem is. Let’s get going on the api v5. Easy for me to say. But looks like that is the only way forward.

[shamoon]

I have not extensively tested this (its the middle of the night! 🤪 ) but I have updated the current plugin to work with v5 API, see PR #47. We'll need @hjdhjd to merge when he's available.

[hjdhjd]

I appreciate the time you took to take this on, but I won't be merging this. I'm in the midst of refactoring this plugin and I'll be publishing something in the next day or two. Bear with me guys, it's a huge update and I want to ensure it's working well before I publish it.

[hjdhjd]

For those experiencing errors: myQ deprecated most non-v5 APIs on July 1. It's not a coincidence. :smile: Just a few hours more I hope and I'll have an update here. I have this working well on my own development tree.

[LordZork]

@hjdhjd Thanks for chiming in and letting us know, and for your efforts in updating your plugin. I'm sure I speak for many when I say, the plugin and the work that goes into it is very much appreciated!! Thank you!!

[TheEngineerGuy]

All good @hjdhjd . Take your time, we can wait for it to be done right.

[DMBlakeley]

@hjdhjd, thanks for your efforts! I am sure that if you were looking for a limited test group there would be a couple of regulars that would be happy to volunteer.

[hjdhjd]

Thanks all. I'll be posting something later today. Hopefully it all goes off without a hitch. :smile:

[DMBlakeley]

One suggestion I might make is to add the build number as a config parameter as this seems to be the most frequent breaking change.

[Gilmargolin]

I am getting this error: [MyQ2] Error: Couldn't find a MyQ door device.

[TheEngineerGuy]

I am getting this error: [MyQ2] Error: Couldn't find a MyQ door device.

Sorry, I fail to see how your issue is related to this thread. Check for another thread which is more relevant, if not please create a new thread.

[Gilmargolin]

I updated to the v5-api branch and I am now getting a new error, all was working fine two days ago.

[shamoon]

@Gilmargolin the repo owner has said he won’t be merging that branch in because he has been working on a larger revamp of the plugin which presumably includes the v5 API. As such, unless we hear otherwise, it’s probably not worth tracking down that error since he said he would be publishing his update today.

[joeria100]

Thanks hjdhjd. Appreciate your work on this and really appreciate the functionality!

[jiniej]

I would like to second joeria100, thanks hjdhjd!

[hjdhjd]

Thanks all. Just a quick update...making good progress and hoping to get this released today or tomorrow. Real life interferes at times. :)

Oh...and getting repeatedly locked out of myQ servers for polling too much. Seems that they've at least improved the auto banning they use to falloff after 10-15 minutes. But...you can imagine when you hit it, having to wait feels like an eternity.

[bwoodruff]

Thank you for the update @hjdhjd. Would it be possible along with these changes to make it such that API changes don't cause the accessory to be removed from HomeKit (causing automations to break)? This behavior is better than the previous behavior of breaking all HomeBridge accessories, I suppose, but I'd think the ideal outcome would be for just the garage door accessories added by myq2 to go 'not responding' (yet remain in HomeKit).

Many thanks for building this. Despite the few recent problems because of API changes I've found it to be more reliable than Chamberlain's "Home Bridge" hardware.

[christianguitarfreak]

Thanks @hjdhjd for your work on this! I really appreciate it.

[hjdhjd]

@bwoodruff I have the hardware device too and specifically use this plugin because it's such an unreliable device. In a separate thread we can commiserate on the badness of the hardware bridge. On the plus side...I've inadvertently discovered how to make it more stable when doing some other network upgrades over the past few weeks.

As to the ask on automations...I have the same issue and it's something I'm hoping to address, but unlikely in the first release or two of the refactored plugin. It's very high on my list though...I have automations and I hate redoing them too. :smile:

[shamoon]

@hjdhjd Obviously appreciate your work and if you prefer to wait for your update to be ready thats your call. But I will say there are two PRs currently pending which address both the lockout (PR #41) and v5 API (PR #47). Obviously those might bring their own bugs so again, I get it if not, but just sayin if you think you need more time...

[seanxushen]

@hjdhjd Any update when you will post fixed plugin ?

[hjdhjd]

Alright all, v2.0 of the plugin is out. Hopefully all goes well. :smile:

[cryptobrian]

Wow! You’re awesome. Thanks so much! Upgrading now!

[hjdhjd]

All, given how long this thread is now, I'm going to close out this issue and ask that you guys beat on v2.0 and open new issues for anything you uncover.

Thanks!

[guppstir]

Thank You for the update. Tip: You'll want to make sure you uninstall and reinstall or just delete the old config settings first.

[kbrashears5]

Something to note - in your config.json you need to change platform from MyQ2 to myQ - and it is case sensitive for when you upgrade to latest version

[RCdiy]

Using the web ui I clicked update. It started immediately without first showing the release notes. After the update the settings link is missing. Web ui iPod touch Safari

[whreams]

I did the below and all is working as expected.

On Jul 4, 2020, at 6:46 AM, guppstir notifications@github.com wrote:

Thank You for the update. Tip: You'll want to make sure you uninstall and reinstall or just delete the old config settings first.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/hjdhjd/homebridge-myq2/issues/44#issuecomment-653755837, or unsubscribe https://github.com/notifications/unsubscribe-auth/APK2HVWIZ4HYUKN3SZSWAZ3RZ4JCHANCNFSM4ONUTWYQ.

[DMBlakeley]

I waited for the overnight dust to settle. This morning, uninstalled previous version via web interface (which also removes config.json settings), restarted Homebridge, installed latest myq2 version (2.0.8), entered credentials, restarted Homebridge, and MyQ started up very smoothly with the garage door being added in seconds.

Yes, by uninstalling you will lose your present garage door in any Favorite Scenes or Automations but this step ensures that all the naming conventions are correct.

[joeria100]

Hi,

Sorry to bug you. I uninstalled and reinstalled on Polisy and readded my credentials, yet the garage door nodes do not populate in polisy. Continue to get no devices message in the log (attached). Ive double checked my credentials and they are correct.

What should I look at?

Thanks, Joe

Joseph R. Iantosca, CRISC, CDPSE JRIantosca@gmail.commailto:JRIantosca@gmail.com | 732-616-7770

From: hjdhjd notifications@github.com Reply-To: hjdhjd/homebridge-myq2 reply@reply.github.com Date: Friday, July 3, 2020 at 9:45 PM To: hjdhjd/homebridge-myq2 homebridge-myq2@noreply.github.com Cc: Joseph Iantosca jriantosca@gmail.com, Comment comment@noreply.github.com Subject: Re: [hjdhjd/homebridge-myq2] Error getting MyQ devices: undefined (#44)

Closed #44https://github.com/hjdhjd/homebridge-myq2/issues/44.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/hjdhjd/homebridge-myq2/issues/44#event-3512195719, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQE7L4LDGJTOVU2IPICL6YLRZ2CVBANCNFSM4ONUTWYQ.

[github-actions[bot]]

This issue is locked to prevent necroposting on closed issues. Please create a new issue for related support requests, bug reports, or feature suggestions.