Do I need to Authorize my RESTful command with EcoBee even though its integrated

I want to set up an automation that will change my EcoBee Climate (Home, Away, Sleep, ect) temperature ranges based on the current outside temperature. I live in Texas and with the wild freezes and insane heat I want it to adapt the Climate settings automatically throughout the year. Also my house has a crappy HVAC system and cools/heats parts of the house differently depending on the outside temp, my main focus is keeping the baby’s room a specific temperature.

For example when its below 35 degrees outside I want the “Home” Climate to be heat below 72, and AC above 79, but when its over 74 degrees outside I want “Home” Climate to be heat comes on below 65 and AC comes on if inside over 73.

I haven’t figured the trigger out yet, whether or not I am going to use just a conditional trigger or a template, maybe check once a day for the daily high, or every 6 hours or something but the trigger is not my main issue. I had some questions about the action/RESTful Command

I have all my API calls figured out already in Postman, I was going to build a Python/Flask app to do this but I was hoping Home Assistant would be able to do it.

I know Home Assistant has some integration that would let me do this with Climate calls, and I might have to resort to that, but because I have everything already done in Postman with EcoBee APIs, I want to go that route.

Main question/TL;DR: When I am building the RESTful command out, do I have to pass in authentication even though I already have Home Assistant integrated into my EcoBee?

Is there a way I can reference the accessToken already generated by the Home Assistant/Ecobee connection? I have access to the bearer token in Postman, but all my Postman API work was done with a different EcoBee PIN/authentication code, I can use it once or twice during testing but it needs to refresh every 6 hours.

How can I reference bearer token that Home Assistant uses to talk to EcoBee in my RESTful API calls? (or do I not even have to reference them)

Thank you, (first post, I hope I labelled it correctly)

I’m not familiar with ecobbe specifically, but, generically, you have no access to the internal data generated by the integration.

I think the real question is: What would you want to do directly by API that the ecobee integration cannot do?

The EcoBee integration cannot change the temperatures of a given climate. I just want to change the high temp/low temp of each climate, not the schedule I already have set up of when each climate runs.

The schedule is something I have configured inside of EcoBee. If I use HA’s climate integration I would have to build out the temps AND the schedule and have HA initiate when to switch from “Home” to “Sleep”… if i understand HA’s documentation on EcoBee integration correctly.

Also I want to build a program that changes what EcoBee sensor particpates in the “Home” climate. I 100% know that cannot be accomplished with HA’s EcoBee Integration.

And according to the documentation there is only 7 services it can do on EcoBee outside of basic Thermostat stuff

  • ecobee.create_vacation
  • ecobee.delete_vacation
  • ecobee.resume_program
  • ecobee.set_fan_min_on_time
  • ecobee.set_dst_mode
  • ecobee.set_mic_mode
  • ecobee.set_occupancy_modes

After looking more at the Climate features. It looks like I could use 3 or 4 Climate.set_temperature actions at different time triggers to set up a schedule in HA.

…but then the issue becomes, what EcoBee sensor is being used by EcoBee when the set_temperature service defines a temperatures range. I have 2 thermostats (upstairs and downstairs) and each has 2 sensors (the main thermostat sensor and a an external sensor in a bedroom) I want to be able to control which EcoBee sensor associated with each climate.

I think I am going to have to beef up my python/flask skills and build my own app out. Thankfully EcoBee does have a weather/forecast call in its API so I can get outside temp data from EcoBee