MyQ API down again

[jay (support)]

This is what I'm getting when trying to open the door (with the new version of the plugin):

Code: Select all

   MyQ Debug                       actionControlDevice: Unlock Garage Door
   MyQ Debug                       Garage Door: changeDevice: new state = open
   MyQ Error                       Garage Door: changeDevice failure, Request error code: 400

I can email you the debugging information for the status request call if that would be useful.

[jay (support)]

BTW, I'm running the latest plugin version on Indigo 7.3 - would that make any difference?

[FlyingDiver]

This is what I'm getting when trying to open the door (with the new version of the plugin):

Code: Select all

   MyQ Debug                       actionControlDevice: Unlock Garage Door
   MyQ Debug                       Garage Door: changeDevice: new state = open
   MyQ Error                       Garage Door: changeDevice failure, Request error code: 400

I can email you the debugging information for the status request call if that would be useful.

Yes please. 400 is bad request, so there's something going wrong in there.

[FlyingDiver]

BTW, I'm running the latest plugin version on Indigo 7.3 - would that make any difference?

Can't think of any reason why it would.

[jay (support)]

Yes please. 400 is bad request, so there's something going wrong in there.

Sent.

[FlyingDiver]

Pre-release 7.4.1 now available - https://github.com/FlyingDiver/Indigo-M ... /tag/7.4.1

Note to all users: When you switch to the newer plugins, you will need to edit your door opener devices and re-select which door (as MyQ knows them) it is. The change in API changed the identifiers for the doors and the plugin has no way of knowing which is which. Yes, for single door installations I could have just used whatever I found, but that wouldn't work for more than one door and I didn't want to code that anyway.

[MKuchnic]

I downloaded the new plugin and once I configured the device again this is the error I received:

Error cannot update device state for key doorStatus to value closed (invalid enumeration value)

My IOLinc is setup up for open/closed instead of true/false.
Thanks
Mark

[FlyingDiver]

I downloaded the new plugin and once I configured the device again this is the error I received:

Code: Select all

 Error                           cannot update device state for key doorStatus to value closed (invalid enumeration value)

My IOLinc is setup up for open/closed instead of true/false.

That error has nothing to do with your sensor.

Redownload the plugin. I pulled the release and re-uploaded it this afternoon. You might have gotten the first version.

[colovin]

It hasn't been working for a few days now. I've updated to 7.4.0. Here is the error message

Trigger Running test
MyQ Error Error in plugin execution ExecuteAction:

Traceback (most recent call last):
File "plugin.py", line 428, in changeDeviceAction
File "plugin.py", line 439, in changeDevice
File "plugin.py", line 67, in account_id
KeyError: ('Account',)

Is there something that needs to be changed in the config file? Has the sign in changed? I'm using the sign in for the Craftsman's app which is still working. There's a notice that I need to move to myQ at the bottom but Craftsman is still working.

[FlyingDiver]

Is the Account device authenticating properly? Did you edit the opener devices to re-select the devices as mentioned above? And you should be using 7.4.1 (also above).

[colovin]

Wow, I thought I had read the latest posts to this thread which was the 7.4.0 update. Not sure how I missed the followups. Will follow those directions. Thanks!

[colovin]

When I go into device settings the MyQ Opener Device: "- select an item - " is ghosted with nothing available to be selected.

I was looking for setup directions but can't find any. It's been so long since I've done anything with this other than updating the plugin I've forgotten how to set it up.

[FlyingDiver]

First go into the plugin config dialog and check the login information. And set the logging level to "Debugging Messages". Then restart the plugin and post the log entries here.

If that doesn't work, you might need to switch to the MyQ site login info. If you can use the MyQ app to control the door, then that's the login info you should use.

[colovin]

OK, for anyone having trouble you have to update to the New myQ app. That took care of all my log in problems. I'm still having trouble getting the plugin to work. Now the Garage Door is showing up as an option in the device setting. I select it and hit save but it doesn't save. When I close the setting box and reopen it, nothing is saved in the MyQ Opener Device. Here is the plugin loading messages.

Code: Select all

 MyQ                             Starting MyQ
   MyQ Debug                       statusFrequency = 86400.0
   MyQ Debug                       deviceStartComm: Garage Door Opener (CG0810197CD1): Device Version is up to date
   MyQ Debug                       deviceStartComm: Adding Device Garage Door Opener (CG0810197CD1) (1079833865) to MyQ device list
   MyQ Debug                       myqLogin response = {"SecurityToken":"94c392ed-8043-45a7-b3f9-6ccfd9b9f380"}
   MyQ Debug                       myqLogin successful
   MyQ Debug                       getDevices: 2 Devices
   MyQ Debug                       getDevices: device_family = garagedoor, name = Garage Door Opener, serial_number = CG0810197CD1
   MyQ Debug                       Checking Opener Device: Garage Door Opener (CG0810197CD1) (0) against CG0810197CD1
   MyQ Debug                       getDevices: device_family = gateway, name = Oro Grande, serial_number = GW0200016E50

Here is messages when testing the action

Code: Select all

 Trigger                         Running test
   MyQ Debug                       changeDeviceAction, deviceId = 1079833865, actionId = openDoor
   MyQ Debug                       Garage Door Opener (CG0810197CD1): changeDevice: new state = open
   MyQ Error                       Garage Door Opener (CG0810197CD1): changeDevice failure, code: 500, response: {"code":"500.000","message

[FlyingDiver]

What's the address of the opener device in the Indigo UI? I'll bet it's 0 or none. That's the same bug Jay was having and I thought I fixed.

Try editing the device config and saving it again. See if the address changes.

And please show the complete log after a plugin restart.

One more thing - are you actually running Indigo 7.1.1 as your signature says?