Ecobee Essential Thermostat Successfully Paired With HomeKit Controller App

I just bought two of them. One I have in my possession and the other on the way. Apparently it's a new model. Cheapest and smallest of the Ecobee offerings, but same overall format and HomeKit compatible.

I powered the one I got with a 24VAC power supply, but it knew other wires needed to be connected so I went to the wall. Of course, some spackling and touchup needed to be done.

I managed to pair it to WiFi, but it wouldn't serve up the QR code until it was properly installed. Currently, and literally, waiting for the paint to dry.

Anyone else have experience with this model?

I'm getting this:

Don't know how to reset an Ecobee thermostat, except to factory settings.
Thing worked fine in Home, before I removed it per directions.
I'll try cycling power to the device, see if that helps.
edit: And the Ecobee app over WiFi worked fine.
edit2: That worked. Had to get another pairing code, for which the app prompted.
edit3: Now what? Lol.

image

Cool.
I wonder if it works, lol?
Hopefully before heating season starts, I'll find out.
Interesting.
Kudos to Staff.

Here's Ecobee's comparo page:

The essential doesn't do any HVAC accessories. I'm assuming that could mean humidifier? I don't use one anyway. I do believe my old Ecobee t'stat had that capability.

1 Like

My Ecobee also paired via Homekit w/out issue (I'm on 2.4.2.125, C8-Pro). Still also have my thermostat integrated via the community Ecobee app, which does bring in the remote sensors that the Hubitat HomeKit integration doesn't support (yet).

@gopher.ny - wondering whether HE HomeKit Controller support for Ecobee remote sensors is "on the short-list" or on the "something we're not sure about yet" list? :slight_smile: Really like the local control provided by the HomeKit integration.

Curious if you have no problems with bumping the set point via the legacy dashboard? I've been having some problems with the Ecobee Essential. @gopher.ny said it's a F vs C issue and is going to look at. Curious also what model Ecobee you have?

Changing set point from a legacy dashboard worked for me...went from 86 to 87 cooling setpoint and the thermostat and info on the Ecobee device page also updated. It started at 86.1 so the increase was to 87.1. The Ecobee seems to only know about whole numbers, as it went to 87.

image

image

I have the "Ecobee Smart Thermostat Enhanced (Compatible with Alexa)."

The legacy dashboard doesn't know how to handle the HomeKit Ecobee thermostat Motion and Occupancy sensors, setting them to Motion and Presence devices doesn't do anything, and they also don't work from the their Device pages, regardless if you change their device driver to HomeKit Motion sensor.

image

One other anomaly - Hubitat Dashboard app lists two HomeKit thermostat devices for some reason, but only one HomeKit device for my Ecobee appears on my Devices tab. Maybe a "ghost" resulting from an initial failed pairing? I only tried pairing once, the screen stuck on the pairing dialog for over 10m so I finally went to my devices tab and the Ecobee was there. Maybe during that long wait an initial failed pairing was created and then the pairing process got it right afterwards. :man_shrugging:
25-07-05-3453

image

That doesn't seem right.
Dashboard set point should agree with device.
Whole numbers, not decimal points.

The tile increments on the dashboard are set to 1, so 86.1 became 87.1...i would expect the dashboard to retain a 10ths value.

However the ecobee app (and my ecobee thermostat itself) don't allow me to enter decimals, (at least not as far as I can tell), and the thermostat doesn't display them. Maybe the Hubitat drivers could find out if a thermostat supports decimal settings or not... Don't know.

That’s not how it should behave.

I’ve noticed that when pushing the arrow several times, the result isn’t even consistent.

The tile should read whole numbers just like the thermostat. Push the arrow up or down. It goes up or down 1°, just like the thermostat.

1 Like

Hadn't noticed that - you are correct. Madness ensues when clicking the arrows up or down: :wink:

25-07-06-3475

25-07-06-3476

25-07-06-3477

25-07-06-3478

25-07-06-3479

25-07-06-3480

25-07-06-3481

Maybe a long-hidden Y2K issue? :smiley:

1 Like

@gopher.ny 's on the case, but I thought I'd highlight the confirmation.
Thanks.

1 Like

Also did verify that the numbers that the dash is throwing out are getting rounded up/down by the thermostat, 88.4 becomes 88 on the thermostat, 88.5 becomes 89, etc.

You looked at the logs to see what's actually going on?
My glazed over. I just couldn't do it. :slight_smile:

1 Like

Watching Wimbledon so only allocating 1/10th of my brain to HE right now, so haven't bothered to look at logs. Looked and nothing very interesting, other than I don't really need / want so many temperature updates, particularly when the temp isn't changing. 7003 is the thermostat, 6574 is the thermostat sensor:

Then I saved a small change "Default Current State..."

image

...and now it's in "parse" mode doing this over and over:

Interesting enough, Victor? :slight_smile:

1 Like

I just paired the second Ecobee Essential Thermostat.

As a note to myself, and maybe others, lol, I had to restart the integration and get a new QR before it would pair.

Just noticed the downstairs t-stat went off line, ie, "no wifi", although it works fine through the Ecobee app.

Have reloaded devices and restarted integration from the integration app page.
Also, rebooted hub.

Remove child device, now I get this:

edit: Removed and reinstalled integration, likely unnecessary because I still got the crossed off handshake icon. I had to unpair from HomeKit at the thermostat. How it got re-paired, I don't know.

Re-paired both stats. Let's see how long they run.

Mine has been fine, no drop-offs.

Did you try the most recent beta where fixes to C>F are noted. I haven't yet, will have time later today.

not in beta