Re: MyQ API down again
Posted:
Fri Oct 25, 2019 3:42 pm
by colovin
The device address is 0. Yes I'm running 7.1.1. 7.2 broke the airfoil plugin which does lots of things on my system. I finally got airfoil pro working (I'm an idiot, someone finally got it to make sense to my dim witted mind) I tried 7.2 but there are so many things that need to be reconfigured, I've set that aside until I can work on that. 7.1.1 is doing everything I need it to do.
Here is the log from reloading MyQ, re-saving the config file to running an action. The device address is still 0 and the garage door is still not saved in the config file.
- Code: Select all
MyQ Shutting down MyQ
Stopped plugin "MyQ 7.4.1"
Starting plugin "MyQ 7.4.1" (pid 10348)
Started plugin "MyQ 7.4.1"
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":"4fba2670-1363-4b79-ab98-3b53ceaae795"}
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
MyQ Debug availableDeviceList: retList = [(u'CG0810197CD1', u'Garage Door Opener')]
WebServer WD Weather Data Updated
Oct 25, 2019 at 2:32:27 PM
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":"An error occurred while processing the request.","description":"Server Error"}
Re: MyQ API down again
Posted:
Fri Oct 25, 2019 4:06 pm
by FlyingDiver
OK, I'll look at that code again tomorrow. This is what pre-releases are for.
Re: MyQ API down again
Posted:
Fri Oct 25, 2019 7:16 pm
by FlyingDiver
I hope this one finally fixes it. You will need to edit the devices to select the opener one more time...
https://github.com/FlyingDiver/Indigo-M ... /tag/7.4.2
Re: MyQ API down again
Posted:
Sat Oct 26, 2019 1:57 am
by colovin
That worked!!
Thank you for your diligence with keeping such a great tool working with the ever changing landscape in myQ land.
Re: MyQ API down again
Posted:
Sat Oct 26, 2019 6:01 pm
by colovin
It worked one time when I tested it. For actual use it failed with a new error.
- Code: Select all
MyQ Error Garage Door Opener (CG0810197CD1): changeDevice failure, code: 401, response: {"code":"401.101","message":"Unauthorized","description":"The Security Token has expired."}
Does the plugin have something to do with the security token? The phone app still works so my login is still valid.
Re: MyQ API down again
Posted:
Sat Oct 26, 2019 6:05 pm
by FlyingDiver
What happens if you restart the plugin, then try the command? Turn on debug logging first.
Re: MyQ API down again
Posted:
Sat Oct 26, 2019 6:26 pm
by colovin
Yeah, I had turned off the debug. Here it is reloading the the plugin
- Code: Select all
Stopped plugin "MyQ 7.4.2"
Starting plugin "MyQ 7.4.2" (pid 2303)
Started plugin "MyQ 7.4.2"
MyQ Starting MyQ
MyQ Debug statusFrequency = 86400.0
MyQ Debug Garage Door Opener (CG0810197CD1): deviceStartComm: Device version is up to date (2)
MyQ Debug Garage Door Opener (CG0810197CD1): deviceStartComm: Adding device (1079833865) to MyQ device list
MyQ Debug myqLogin response = {"SecurityToken":"2bf81284-150a-46de-855b-9907e94207a8"}
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) (CG0810197CD1) against CG0810197CD1
MyQ Debug getDevices: device_family = gateway, name = Oro Grande, serial_number = GW0200016E50
My run test does work
MyQ Debug myqLogin response = {"SecurityToken":"aa4fa555-326f-44aa-a891-e1c22537735f"}
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) (CG0810197CD1) against CG0810197CD1
MyQ Debug getDevices: device_family = gateway, name = Oro Grande, serial_number = GW0200016E50
But the actual doesn't which I can't recreate at the moment. When you open my mail box it opens the garage door for when I come back from running in the AM and walking in the PM (going for 10k steps a day
One of the conditions for it to work is the alarm has to be on. My wife is working on dinner at the moment so she wouldn't be happy if I were start screwing with turning on alarms and such. Not sure why I got the error on the real world application and not on the test because all actions are the same, I just changed the conditions which is a time frame (a AM window and a PM window) Alarm being on and the mail has to have been delivered in the PM so the mail man doesn't open my garage. Test eliminates those conditions. I'll leave the debug on for the next real world experience.
Re: MyQ API down again
Posted:
Sat Oct 26, 2019 6:31 pm
by FlyingDiver
Keep me posted. I might need to detect a failed login attempt and retry. I never did that, because I never had it fail on me.
Re: MyQ API down again
Posted:
Sun Oct 27, 2019 9:50 am
by colovin
Here's the whole routine. You can see lots of activities as someone approaches my house. Got the same MyQ error. Opening the mail box is what triggers MyQ. I opened it twice. Second set is running the test routine which worked when I first updated the plugin and after the first failure. This time, a few minutes after the first set it failed.
- Code: Select all
Oct 27, 2019 at 8:30:00 AM
WebServer WD Weather Data Updated
Received INSTEON "Garage I/O Fire - Mail" off
Trigger Running AM
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: 401, response: {"code":"401.101","message":"Unauthorized","description":"The Security Token has expired."}
MyQ Debug deviceUpdated: Garage I/O Fire - Mail has changed state: True
Received INSTEON "Garage I/O Fire - Mail" on
MyQ Debug deviceUpdated: Garage I/O Fire - Mail has changed state: False
Received INSTEON "Garage I/O Photobeam" off
Trigger Photo Beam play sound
Sent INSTEON "Alarm Monitor Delvcam" on
Sent INSTEON "Alert" on
Schedule Photo Beam play sound (delayed action)
Announcer Announcing message "i".
Received INSTEON "Garage I/O Photobeam" on
Received INSTEON "Garage I/O Fire - Mail" off
Trigger Running AM
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: 401, response: {"code":"401.101","message":"Unauthorized","description":"The Security Token has expired."}
MyQ Debug deviceUpdated: Garage I/O Fire - Mail has changed state: True
Received INSTEON "Garage I/O Fire - Mail" on
MyQ Debug deviceUpdated: Garage I/O Fire - Mail has changed state: False
Oct 27, 2019 at 8:34:38 AM
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: 401, response: {"code":"401.101","message":"Unauthorized","description":"The Security Token has expired."}
Re: MyQ API down again
Posted:
Sun Oct 27, 2019 10:08 am
by FlyingDiver
Wow, that's weird. It doesn't even look like it's trying to authenticate.
Re: MyQ API down again
Posted:
Sun Oct 27, 2019 10:24 am
by FlyingDiver
OK, that was totally my fault.
Grab 7.4.3 from GitHub or the plugin store.
Re: MyQ API down again
Posted:
Sun Oct 27, 2019 5:29 pm
by colovin
I'm not sure what happened to my morning post. Maybe I didn't hit submit??? (the mind is a terrible thing to waste) but this morning I had said that 7.4.3 had worked on the run test and I'd update you on the real world instance. Well it worked!
- Code: Select all
Oct 27, 2019 at 4:09:44 PM
MyQ Debug deviceUpdated: Garage I/O Fire - Mail has changed state: True
Trigger Running PM
Trigger Running PM Sunday
MyQ Debug changeDeviceAction, deviceId = 1079833865, actionId = openDoor
MyQ Debug myqLogin response = {"SecurityToken":"ef40fdaa-2e1f-48ab-bfd3-a472f1bbb7eb"}
MyQ Debug myqLogin successful
MyQ Debug Garage Door Opener (CG0810197CD1): changeDevice: new state = open
MyQ Debug changeDeviceAction, deviceId = 1079833865, actionId = openDoor
MyQ Debug myqLogin response = {"SecurityToken":"dfe843a1-fb8b-4d45-8dfc-9e43432ace2c"}
MyQ Debug myqLogin successful
MyQ Debug Garage Door Opener (CG0810197CD1): changeDevice: new state = open
MyQ Debug deviceUpdated: Garage I/O Fire - Mail has changed state: False
MyQ Debug myqLogin response = {"SecurityToken":"234db612-bc4d-45b3-bd16-3f6a3764818c"}
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) (CG0810197CD1) against CG0810197CD1
MyQ Debug getDevices: device_family = gateway, name = Oro Grande, serial_number = GW0200016E50
Sunday is a separate routine because there is no mail delivery to account for. It had the potential to fail because my computer was in VPN which sometimes the servers don't like. I've got an August lock that bitch and moans about it when I'm in VPN. I forgot to take it off. (please note the above, The mind is . .. .) MyQ worked fine. August finally got around to unlocking the door. I edited the log to just show the MyQ. I'll keep the debug menu on for awhile incase something changes.
Re: MyQ API down again
Posted:
Tue Oct 29, 2019 3:58 pm
by wideglidejrp
Things were working again after I installed 7.4.3 but now it is not working again. Here is what I am getting....
MyQ Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 79, in runConcurrentThread
File "plugin.py", line 379, in getDevices
File "plugin.py", line 351, in myqLogin
File "/Library/Application Support/Perceptive Automation/Indigo 7.4/IndigoPluginHost.app/Contents/Resources/PlugIns/requests/models.py", line 816, in json
File "/Library/Application Support/Perceptive Automation/Indigo 7.4/IndigoPluginHost.app/Contents/Resources/PlugIns/simplejson/__init__.py", line 307, in loads
File "/Library/Application Support/Perceptive Automation/Indigo 7.4/IndigoPluginHost.app/Contents/Resources/PlugIns/simplejson/decoder.py", line 335, in decode
File "/Library/Application Support/Perceptive Automation/Indigo 7.4/IndigoPluginHost.app/Contents/Resources/PlugIns/simplejson/decoder.py", line 353, in raw_decode
ValueError: No JSON object could be decoded
MyQ Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)