7.4.4 error on Catalina

Catalina 10.15.1 (19B88)

Dec 9, 2019 at 11:09:30 AM
Reloading plugin "MyQ 7.4.4"
Stopping plugin "MyQ 7.4.4" (pid 5586)
MyQ Shutting down MyQ
Stopped plugin "MyQ 7.4.4"
Starting plugin "MyQ 7.4.4" (pid 5590)
Started plugin "MyQ 7.4.4"
MyQ Starting MyQ
MyQ Error Garage Door : changeDevice failure, code: 400, response: {"code":"400.301","message":"Bad Request","description":"The serial number was invalid. Please try again."}

What exactly were you doing when that happened? Is it repeatable? If so, please turn on debug logging and repeat the steps to get the error, then post that log.

Trying to unlock the door from the device page. Let me do it again with logging

Code: Select all

MyQ Debug                       actionControlDevice: Unlock Garage Door
   MyQ Debug                       myqLogin response = {"SecurityToken":"a965d6cc-285f-4b65-ae59-a90c478ea0e5"}
   MyQ Debug                       myqLogin successful
   MyQ Threaddebug                 myqLogin account_info = {u'UserName': u'agggggg@gmail.com', u'Account': {u'Name': u"xxxxxxx's Account", u'Roles': {u'href': u'http://api.myqdevice.com/api/v5/Accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/Roles'}, u'UserAllowance': 4, u'DirectoryCodeLength': 0, u'AccessGroups': {u'href': u'http://api.myqdevice.com/api/v5/Accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/AccessGroups'}, u'Devices': {u'href': u'http://api.myqdevice.com/api/v5/Accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/Devices'}, u'Id': u'b9c7e13f-3499-4c75-9f89-46d119d86654', u'Zones': {u'href': u'http://api.myqdevice.com/api/v5/Accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/Zones'}, u'Phone': u'5555555555', u'href': u'http://api.myqdevice.com/api/v5/Accounts/b9c7e13f-3499-4c75-9f89-46d119d86654', u'ContactName': u'xxxxxxx, u'Address': {u'PostalCode': u'11111-1030', u'City': u'city', u'State': u'NY', u'Country': {u'href': u'http://api.myqdevice.com/api/v5/Countries/USA', u'Code': u'USA', u'IsEEACountry': False}, u'AddressLine1': u'xxxxxx'}, u'TimeZone': u'America/New_York', u'AccessSchedules': {u'href': u'http://api.myqdevice.com/api/v5/Accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/AccessSchedules'}, u'Email': u'axxxxxx@gmail.com', u'Users': {u'href': u'http://api.myqdevice.com/api/v5/Accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/Users'}}, u'Users': {u'href': u'http://api.myqdevice.com/api/v5/My/Users'}, u'FirstName': u'xxxxx', u'Admin': False, u'AnalyticsId': u'de2b3bb2-5732-4e92-a2c5-ebfed3980249', u'DiagnosticDataOptIn': True, u'Address': {u'PostalCode': u'11111-1030', u'City': u'city', u'Country': {u'href': u'http://api.myqdevice.com/api/v5/Countries/USA', u'Code': u'USA', u'IsEEACountry': False}, u'AddressLine1': u'xxxxxxx'}, u'UserId': u'b9c7e13f-3499-4c75-9f89-46d119d86654', u'RequestAccountLinkInfo': False, u'CultureCode': u'en', u'Phone': u'5555555555', u'LastName': u'xxxxx', u'TimeZone': {u'Id': u'America/New_York', u'Name': u'America/New_York'}, u'Email': u'xxxxx@gmail.com', u'MailingListOptIn': False}
   MyQ Debug                       Garage Door : changeDevice: new state = open
   MyQ Threaddebug                 Garage Door : changeDevice: url = https://api.myqdevice.com/api/v5/Accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/Devices//actions, data = = {'action_type': 'open'}, headers = = {'MyQApplicationId': 'JVM/G9Nwih5BwKgNCjLxiFUQxQijAebyyg8QUHr7JOrP+tuPb8iHfRHKwTmDzHOu', 'Content-Type': 'application/json', 'SecurityToken': u'a965d6cc-285f-4b65-ae59-a90c478ea0e5'}
   MyQ Error                       Garage Door : changeDevice failure, code: 400, response: {"code":"400.301","message":"Bad Request","description":"The serial number was invalid. Please try again."}

Was this previously working? What changed since it last worked?

With the logging still set to "Detailed Debugging", click on the status request button on the door device, then post that log segment. I specifically need the line that starts with:

MyQ Threaddebug getDevices device_info =

Thanks for response!
It was previously working. Catalina broke it and I wasn't able to login. New version of plugin allows me to login, but cannot control

Thanks for response!
It was previously working. Catalina broke it and I wasn't able to login. New version of plugin allows me to login, but cannot control

I can't imagine what the OS upgrade would change in the plugin. I'm running the same plugin version on my Catalina development server and it works fine.

Maybe the device info will help figure this out.

Code: Select all

MyQ Threaddebug                 getDevices device_info = {u'count': 2, u'items': [{u'name': u'Garage Door Opener', u'parent_device_id': u'GW0100018358', u'device_family': u'garagedoor', u'state': {u'use_aux_relay': False, u'max_invalid_attempts': 0, u'control_from_browser': False, u'close': u'http://api.myqdevice.com/api/v5/accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/devices/CG0810207427/close', u'open': u'http://api.myqdevice.com/api/v5/accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/devices/CG0810207427/open', u'aux_relay_behavior': u'None', u'invalid_shutout_period': u'00:00:00', u'rex_fires_door': False, u'last_update': u'2019-12-11T03:21:27.5176452Z', u'passthrough_interval': u'00:00:00', u'attached_work_light_error_present': False, u'online': True, u'report_ajar': False, u'door_state': u'closed', u'invalid_credential_window': u'00:00:00', u'report_forced': False, u'last_status': u'2019-12-11T11:30:49.8523524Z', u'command_channel_report_status': False, u'gdo_lock_connected': False, u'door_ajar_interval': u'00:00:00', u'is_unattended_open_allowed': True, u'aux_relay_delay': u'00:00:00', u'is_unattended_close_allowed': True}, u'href': u'http://api.myqdevice.com/api/v5/accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/devices/CG0810207427', u'parent_device': u'http://api.myqdevice.com/api/v5/accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/devices/GW0100018358', u'device_type': u'garagedooropener', u'created_date': u'2015-10-22T18:14:44.95', u'serial_number': u'CG0810207427', u'device_platform': u'myq'}, {u'name': u'Home', u'device_family': u'gateway', u'state': {u'updated_date': u'2019-12-11T11:30:49.8679742Z', u'physical_devices': [], u'learn_mode': False, u'homekit_enabled': False, u'online': True, u'homekit_capable': False, u'last_status': u'2019-12-11T11:30:49.8523524Z', u'learn': u'http://api.myqdevice.com/api/v5/accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/devices/GW0100018358/learn', u'firmware_version': u'4.2', u'pending_bootload_abandoned': False}, u'href': u'http://api.myqdevice.com/api/v5/accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/devices/GW0100018358', u'device_type': u'ethernetgateway', u'created_date': u'2015-10-22T17:42:45.007', u'serial_number': u'GW0100018358', u'device_platform': u'myq'}], u'href': u'http://api.myqdevice.com/api/v5/accounts/b9c7e13f-3499-4c75-9f89-46d119d86654/devices'}

I've created an issue to track this on GitHub: https://github.com/FlyingDiver/Indigo-MyQ/issues/12

Not sure I'll have time to dig into this soon. Got a week-long trip starting Friday, then holidays. There's nothing obviously wrong in the login info you submitted. So I'm afraid this is the symptom of some other change that MyQ is making on the back end.