Ecobee Version 2.0.3 Pre-release

[shumon1212]

Hi Joe, reverted back to 2.0.5. I get a different set of errors, mainly:

Code: Select all

Traceback (most recent call last):
  File "plugin.py", line 139, in runConcurrentThread
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/Ecobee 2 8.15.54 AM.indigoPlugin/Contents/Server Plugin/ecobee.py", line 538, in update
AttributeError: 'NoneType' object has no attribute 'get'

I've attached the relevant logs -- I configured my thermostats, disabled Indigo communication on all the devices, and then enabled them one at a time. The typeID = OccupancySensor devices load fine, but the typeID = EcobeeThermostat fail with the error above.

[FlyingDiver]

Hi Joe, reverted back to 2.0.5. I get a different set of errors, mainly:

Code: Select all

Traceback (most recent call last):
  File "plugin.py", line 139, in runConcurrentThread
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/Ecobee 2 8.15.54 AM.indigoPlugin/Contents/Server Plugin/ecobee.py", line 538, in update
AttributeError: 'NoneType' object has no attribute 'get'

I've attached the relevant logs -- I configured my thermostats, disabled Indigo communication on all the devices, and then enabled them one at a time. The typeID = OccupancySensor devices load fine, but the typeID = EcobeeThermostat fail with the error above.

2.0.6 probably broke your devices, if you created them with that version. Did you re-create them again with 2.0.5?

[shumon1212]

Yes Joe, I had deleted and recreated all the devices, including user account. Happy to do it again and provide the full log if it helps.

[shumon1212]

Hi Joe, I deleted all the Ecobee devices and recreated ... same exception ... please see attached logs.

[FlyingDiver]

I think I figured it out. https://github.com/FlyingDiver/Indigo-E ... /tag/2.0.7

[chobo]

I think I figured it out. https://github.com/FlyingDiver/Indigo-E ... /tag/2.0.7

I think you may be right!! Just installed 2.0.7 and all Ecobee 2 plugin devices immediately recovered. No errors so far — fingers crossed.

[FlyingDiver]

And the way to test for the situation you had was to disable the Account device, then restart the plugin. Then re-enable the Account. Everything updates in less than a minute.

[chobo]

Nice... Just tried that scenario and no issues at all. Thank you so much!