Everything working for me now
Sent from my iPad using Tapatalk
ECOBEE_MODELS = {
'idtSmart' : 'ecobee Smart',
'idtEms' : 'ecobee Smart EMS',
'siSmart' : 'ecobee Si Smart',
'siEms' : 'ecobee Si EMS',
'athenaSmart' : 'ecobee3 Smart',
'athenaEms' : 'ecobee3 EMS',
'corSmart' : 'Carrier or Bryant Cor',
'nikeSmart' : 'ecobee3 lite Smart',
'nikeEms' : 'ecobee3 lite EMS'
}
bhough17 wrote:I've just installed the 2.0.2 plugin.
1) I'm getting authentication errors with both 1.2.8 and 2.0.2 when I request a new PIN
- error message from 1.2.8 is "Ecobee Error Error connecting to Ecobee. Possible connectivity outage. Could not request pin."
- error message from 2.0.2 is "Ecobee 2 Error PIN Request Error, exception = EOF occurred in violation of protocol (_ssl.c:590)"
- in the "Configure Ecobee User Account" dialog for 2.0.2, after clicking "Get PIN" button, I see "PIN Request Failed" appears in the Authentication Status box
2) Are others seeing PIN Request errors right now (and since at least 10pm Eastern, October 24)
3) I fully expect the PIN Request error is on the ecobee side, but maybe it can help on the error handling checks
midd wrote:I've been getting the same connectivity error. I'm using Mountain Lion tho, 10.8.5.
FlyingDiver wrote:Everyone beta testing - I need some info.
There's a new device state for the Ecobee devices called "modelNumber". Which is a stupid name, but it's what Ecobee calls it. It's actually the model NAME.
Please post the modelNumber show for each of your devices, and the marketing model name as you know it.
FlyingDiver wrote:My conclusion is that Ecobee changed their server configuration this week to require TLS 1.2 or similar for the HTTPS connection for their API. Which is not available in any Apple supplied version of Python prior to 10.13 (High Sierra). So anyone running anything older than that should just delete the Ecobee plugin (old and new versions).
I've edited the plugin store description for the old plugin to reflect that restriction. The new version isn't on the store yet.
shumon1212 wrote:Concur w/ Joe regarding the TLS 1.2 changes. It should theoretically be possible to install a newer version of Python that supports TLS 1.2 and get Indigo to use that; though my guess is that may render Indigo in an unsupported state. Has anyone tried to download and run the installer from link below (I had upgraded to Mojave some time ago, so unable to test or support this theory, but I suspect there's some chance it may fix the issue):
https://www.python.org/downloads/release/python-2715/
Also, this is likely already impacting (or will be soon) other Indigo plugins that depend on HTTPS connectivity; but I couldn't find any official guidance - hoping the Indigo team can chime in?
shumon1212 wrote:Hi Joe and all, my first post here on the forums. I don’t own an Ecobee 4, but believe the model numbers you need are apolloSmart and apolloEms. [1]
Also, the full list of potential values is listed on the Ecobee API pages. [2]
[1] https://www.ecobee.com/home/developer/api/documentation/v1/change-log.shtml.
[2] https://www.ecobee.com/home/developer/api/documentation/v1/objects/Thermostat.shtml
FlyingDiver wrote:This has previously been discussed on the forums here, most specifically with regard to the GitHub updater communications. The net result is that anything you try to do installing an alternate version of Python will break Indigo or other plugins or both. Not worth the risk, IMO.
Users browsing this forum: No registered users and 2 guests