MyQ Plugin discussion

[FlyingDiver]

OK, that's a typo. Not going to roll an immediate fix because it's self correcting on next poll of the device status.

[Bollar]

It turns out the plug-in isn't actually controlling the doors. It gets status okay, but when I try to lock or unlock, I get the following:

Code: Select all

2016-11-25 08:12:32.640	MyQ Debug	actionControlDevice: "Range Rover" Unlock
2016-11-25 08:12:32.643	MyQ Debug	changeDevice: Range Rover, state = 1
2016-11-25 08:12:32.835	MyQ Debug	myqLogin: response = <Response [200]>
2016-11-25 08:12:32.838	MyQ Debug	myqLogin: content = {"UserId":0,"SecurityToken":"xxx","ReturnCode":"0","ErrorMessage":"","BrandId":2,"BrandName":"Chamberlain","RegionId":1}
2016-11-25 08:12:32.840	MyQ Debug	myqLogin: Success, Brand = Chamberlain, SecurityToken = xxx
2016-11-25 08:12:33.025	MyQ Debug	changeDevice: Bad return code: MyQ Application ID unrecognized. (1001)


2016-11-25 08:13:30.993	MyQ Debug	actionControlDevice: "Tesla" Lock
2016-11-25 08:13:30.995	MyQ Debug	changeDevice: Tesla, state = 0
2016-11-25 08:13:31.230	MyQ Debug	myqLogin: response = <Response [200]>
2016-11-25 08:13:31.233	MyQ Debug	myqLogin: content = {"UserId":0,"SecurityToken":"xxx","ReturnCode":"0","ErrorMessage":"","BrandId":2,"BrandName":"Chamberlain","RegionId":1}
2016-11-25 08:13:31.236	MyQ Debug	myqLogin: Success, Brand = Chamberlain, SecurityToken = xxx
2016-11-25 08:13:31.445	MyQ Debug	changeDevice: Bad return code: MyQ Application ID unrecognized. (1001)

[FlyingDiver]

That's odd. Grab this version:

https://github.com/FlyingDiver/Indigo-M ... 8b3787.zip

Then in the plugin config dialog, change the Brand to "Chamberlain v4". See if that works.

There's two sets of API keys floating around the Internet. I've been using the older one, but I found a newer set associated with the SmartThings plugin. I've tried both, and not sure what if anything is different. That's the problem with using a reverse engineered API. There's no definitive source.

[Bollar]

That's odd. Grab this version:

That works. I was using 7.1 and didn't notice if there was a v4 in that version.

[FlyingDiver]

That works. I was using 7.1 and didn't notice if there was a v4 in that version.

No, I still had the old one in there. Now I need to find out if I can switch them all to the new API key or if I need to keep them both.

[Bollar]

Also, I don't know if this is important or not, but the Device Details: Last Update doesn't change when I Send Status Request. I see it's successful in the log.

[FlyingDiver]

Also, I don't know if this is important or not, but the Device Details: Last Update doesn't change when I Send Status Request. I see it's successful in the log.

I don't explicitly set that in the plugin. I think the Indigo server does, based on actual changes to the device state. Are you saying that the door states did change but the Last Update did not?

[Bollar]

Also, I don't know if this is important or not, but the Device Details: Last Update doesn't change when I Send Status Request. I see it's successful in the log.

I don't explicitly set that in the plugin. I think the Indigo server does, based on actual changes to the device state. Are you saying that the door states did change but the Last Update did not?

Sorry, when I manually send a status request (not when I open or close a door), the last update time doesn't update. IMO, it should.

[FlyingDiver]

Sorry, when I manually send a status request (not when I open or close a door), the last update time doesn't update. IMO, it should.

Well, I'm writing the current door states back to the Indigo server on every status report or check. If the update time isn't changing, it's because Indigo isn't doing so when the states haven't actually changed. I think you 're going to need to do a feature request to Matt & Jay to change that.

[Bollar]

Sorry, when I manually send a status request (not when I open or close a door), the last update time doesn't update. IMO, it should.

Well, I'm writing the current door states back to the Indigo server on every status report or check. If the update time isn't changing, it's because Indigo isn't doing so when the states haven't actually changed. I think you 're going to need to do a feature request to Matt & Jay to change that.

Cool, I'll take it up with management.

[dougkillmer]

I'm running 7.0.1 and I've noticed these errors once in a while.

Code: Select all

Nov 27, 2016, 3:52:03 PM
   MyQ Debug                       myqLogin: response = <Response [200]>
   MyQ Debug                       myqLogin: content = {"UserId":0,"SecurityToken":"71836042...","ReturnCode":"0","ErrorMessage":"","BrandId":1,"BrandName":"Liftmaster","RegionId":1}
   MyQ Debug                       myqLogin: Success, Brand = Liftmaster, SecurityToken = 71836042...
   MyQ Debug                       getDevices: 3 Devices
   MyQ Debug                       getDevices: MyQDeviceTypeId = 1, DeviceId = 50360411
   MyQ Debug                       getDevices: MyQDeviceTypeId = 7, DeviceId = 251758172
   MyQ Error                       getDevices: Opener North Door (251758172), state out of range: 9
   MyQ                             MyQ Device North Door is now Unknown
   MyQ Debug                       getDevices: MyQDeviceTypeId = 7, DeviceId = 251758173
   MyQ Error                       getDevices: Opener South Door (251758173), state out of range: 9
   MyQ                             MyQ Device South Door is now Unknown

Nov 27, 2016, 4:02:37 PM
   MyQ Debug                       myqLogin: response = <Response [200]>
   MyQ Debug                       myqLogin: content = {"UserId":0,"SecurityToken":"a4574d3f...","ReturnCode":"0","ErrorMessage":"","BrandId":1,"BrandName":"Liftmaster","RegionId":1}
   MyQ Debug                       myqLogin: Success, Brand = Liftmaster, SecurityToken = a4574d3f...
   MyQ Debug                       getDevices: 3 Devices
   MyQ Debug                       getDevices: MyQDeviceTypeId = 1, DeviceId = 50360411
   MyQ Debug                       getDevices: MyQDeviceTypeId = 7, DeviceId = 251758172
   MyQ Error                       getDevices: Opener North Door (251758172), state out of range: 8
   MyQ Debug                       getDevices: MyQDeviceTypeId = 7, DeviceId = 251758173
   MyQ Error                       getDevices: Opener South Door (251758173), state out of range: 8

Nov 27, 2016, 4:13:10 PM
   MyQ Debug                       myqLogin: response = <Response [200]>
   MyQ Debug                       myqLogin: content = {"UserId":0,"SecurityToken":"8f6dd356...","ReturnCode":"0","ErrorMessage":"","BrandId":1,"BrandName":"Liftmaster","RegionId":1}
   MyQ Debug                       myqLogin: Success, Brand = Liftmaster, SecurityToken = 8f6dd356...
   MyQ Debug                       getDevices: 3 Devices
   MyQ Debug                       getDevices: MyQDeviceTypeId = 1, DeviceId = 50360411
   MyQ Debug                       getDevices: MyQDeviceTypeId = 7, DeviceId = 251758172
   MyQ Error                       getDevices: Opener North Door (251758172), state out of range: 9
   MyQ Debug                       getDevices: MyQDeviceTypeId = 7, DeviceId = 251758173
   MyQ Error                       getDevices: Opener South Door (251758173), state out of range: 8

[FlyingDiver]

Do you have any idea what's going on with the doors when you get state 8 or 9? They're not on the list of known states that I have.

The states I know are:

Code: Select all

doorStateNames = ["Unknown", "Open", "Closed", "Stopped", "Opening", "Closing", "Unknown", "Disconnected"]

That's 0 through 7. I can add 8 and 9 in as "Unknown", but that's just masking the problem.

[dougkillmer]

Thanks, I believe the doors were open when 8 and 9 were received..

I decided to remove the Indigo devices and let the plug-in create new ones for now. Maybe I caused the problem by upgrading and downgrading the plugin a number of times. I'll let you know if I see it again with these new devices.

[FlyingDiver]

No, I don't see any way you could cause that problem. The number is taken directly from the API call to the MyQ servers.

[dougkillmer]

I received 9 again with one door open.

Code: Select all

Nov 27, 2016, 5:29:45 PM
   MyQ Debug                       myqLogin: response = <Response [200]>
   MyQ Debug                       myqLogin: content = {"UserId":0,"SecurityToken":"a861a310...","ReturnCode":"0","ErrorMessage":"","BrandId":1,"BrandName":"Liftmaster","RegionId":1}
   MyQ Debug                       myqLogin: Success, Brand = Liftmaster, SecurityToken = a861a310...
   MyQ Debug                       getDevices: 3 Devices
   MyQ Debug                       getDevices: MyQDeviceTypeId = 1, DeviceId = 50360411
   MyQ Debug                       getDevices: MyQDeviceTypeId = 7, DeviceId = 251758172
   MyQ Error                       getDevices: Opener North Door (251758172), state out of range: 9
   MyQ                             MyQ Device North Door is now Unknown
   MyQ Debug                       getDevices: MyQDeviceTypeId = 7, DeviceId = 251758173
   MyQ Debug                       getDevices: Opener South Door (251758173), state = 2