Ecobee API change

I’m planning to look at this for the OH2/3 version of the binding. I don’t know the implications yet. If they aren’t planning to support backwards compatibility, I doubt that the existing OH1 and OH2 bindings will work after the change.

Well, after 4 days they have not responded to my request to be added to the Early Access Program. Pretty sad actually.

Sad indeed…they seemed to be getting better after their stability issues with the servers last last year…but in my mind i keep thinking they will fold someday…if you can’t keep servers up…your product is doomed…i wish they’d release a local API to build your own server with…that would be the ideal option.

Nothing would please me more than being able to control the devices directly without having to go through their cloud service. I still see bursts of errors in my logs every few days. So they likely haven’t sorted out all their infrastructure issues…

Any reply from Ecobee on your request for a Dev account?

Yes. I finally got a response after tweeting to their VP of Technology. :wink:

As soon as the test environment is ready, they’ll give me access.

Note that I’ll be posting updates on the main Ecobee binding forum thread.

Please tell me the change, if viable, will come to the latest stable 2.x line of openhab as well and not just 3.x

Only if you say pretty please. :wink: :laughing:

If any changes are required (which at the moment I don’t think there will be), I’ll make the change in 2.5.x and 3.0.

1 Like

Pretty please :slight_smile:

1 Like

Pretty please (still running v2.4) that you helped me out with many months ago.

Best, Jay

As soon as they get back to me with a test environment, I’ll verify what needs to change, if anything. It’s getting late. I pinged them again a couple days ago.

The plan is to change both 2.5.x and 3.0 (assuming a change is necessary). @jwiseman Are you running the 2.5.x version on 2.4?

I made a mistake stating 2.4, I’m still running the 1.x version of Ecobee. I understand I’ll need to upgrade to 2.5 when the API is fixed and change some items to get it working again.

openhab> list -s | grep ecobee
289 │ Active │ 80 │ 1.13.0 │ org.openhab.action.ecobee
290 │ Active │ 80 │ 1.13.0 │ org.openhab.binding.ecobee

Best, Jay

I’m running 3.0.0-SNAPSHOT - Build #2039 which has the new api changes and I’m getting errors when trying to enter the pin in My Apps on the ecobee website. They pin is in the format ‘XXXX-YYYY’:

image

Thats the correct format for the new PINs. I have no idea Ecobee would be throwing an error.

The interface for entering the PIN has changed. Are you seeing that new interface?

No I still see the old interface. I’ll email ecobee support

After you enter the XXXX-XXXX PIN, you should see this.

Followed by this.

Followed by this.

I don’t see anything like that. BTW, I have one of the original smart thermostats. This is the My Apps panel:

Then I get this when I enter the pin and press the “Install App” button:

Hmm. What app is that that you’re using?

Have you tried doing it from the Ecobee web portal, or does that not work for that model thermostat?

https://www.ecobee.com/consumerportal/index.html

I go to https://www.ecobee.com/en-us/, and sign in the upper hand corner. Once I login it goes to https://www.ecobee.com/home/secure/heatingAndCooling.jsf, which appears is what I get with the original smart thermostat. Once I log in I can go to https://www.ecobee.com/consumerportal/index.html and get the new portal. I also found a way to get to if from the old portal:

Select Add Thermostat to open the thermostat panel and select ecobee 3:

Then select Proceed:

This switches to the new portal, press X on the ADD THERMOSTAT panel, and then I get the new portal. If I log out and back in. I’m back to the old portal.

Using either approach, I was able to complete the steps in the documentation and got it to work again.