Page 1 of 1

Error

PostPosted: Wed Feb 13, 2019 4:44 pm
by jay (support)
I'm getting the following repeatedly in the log:

MyQ Error Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
File "plugin.py", line 85, in runConcurrentThread
File "plugin.py", line 407, in getDevices
ValueError: invalid literal for int() with base 10: ''

MyQ Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)


Latest version of the plugin from the store. Clues?

Re: Error

PostPosted: Wed Feb 13, 2019 4:50 pm
by jay (support)
I notice that the address is an empty string. I did switch this device to another device type then back - did that screw something up? Is there a way to fix it or do I just have to delete it (breaking all my triggers and actions) and recreate it?

Re: Error

PostPosted: Wed Feb 13, 2019 4:53 pm
by jay (support)
Debug info at startup:

Code: Select all
   MyQ                             Starting MyQ
   MyQ Debug                       statusFrequency = 300.0
   MyQ Debug                       deviceStartComm: Garage Door: Device Version is up to date
   MyQ Debug                       deviceStartComm: Adding Device Garage Door (150947178) to MyQ device list
   MyQ Debug                       deviceStartComm: Garage Door (CG081026926D): Device Version is up to date
   MyQ Debug                       deviceStartComm: Adding Device Garage Door (CG081026926D) (945135961) to MyQ device list
   MyQ Debug                       myqLogin successfull
   MyQ Debug                       getDevices: 2 Devices
   MyQ Debug                       getDevices: MyQDeviceTypeId = 2, MyQDeviceTypeName = GarageDoorOpener, DeviceId = 12773640
   MyQ Debug                       Checking Opener Device: Garage Door () against 12773640


which is immediately followed by the error above.

Re: Error

PostPosted: Wed Feb 13, 2019 5:00 pm
by FlyingDiver
Will look into this tomorrow.

Re: Error

PostPosted: Wed Feb 13, 2019 7:44 pm
by FlyingDiver

Re: Error

PostPosted: Thu Feb 14, 2019 9:29 am
by jay (support)
Cool. I'll be out of pocket for the next few days, but I can test after that (if it's ready).

Re: Error

PostPosted: Thu Feb 14, 2019 9:31 am
by FlyingDiver
Working on it now. Probably ready by tomorrow. To make sure this doesn't happen again, I'm removing the device auto-creation code and enabling normal device creation and editing.

Re: Error

PostPosted: Sat Feb 16, 2019 9:38 am
by FlyingDiver

Re: Error

PostPosted: Tue Feb 26, 2019 11:56 am
by jay (support)
(I just deleted a previous reply).

Seems to be working, thanks!

Re: Error

PostPosted: Tue Feb 26, 2019 12:16 pm
by FlyingDiver
Out of time for completing testing before I leave, so I'm letting this stay at pre-release until I get back.

Re: Error

PostPosted: Tue Feb 26, 2019 12:45 pm
by jay (support)
Yeah, sorry for the lateness. The old saying "what happens in Vega stays in Vegas" apparently doesn't cover the flu. We brought back a very nasty flu (I'm still actually recovering).

Re: Error

PostPosted: Wed Mar 27, 2019 2:38 pm
by FlyingDiver
Upgraded test release to final. Updated store.