Just curious… Did you ask @gopher.ny if he could allow those?
Moot point now that you did it the long way, but Hubitat has been pretty responsive to allowing additional libraries where there is a use case and it doesn't impact hub functionality or security.
EDIT: Oh, and nice work! That is a really cool way to do it. Very impressive!
To be honest, I didn’t initially consider asking, since I recognize the complexity behind firmware development and the hub’s internal operations. I didn’t want to burden developers with an unsolicited or specialized request.
I also assume such features exist for purposes I might overlook, given my lack of direct involvement in firmware work.
Honestly, I don’t mind the longer approach. I’m genuinely excited to have found a solution without requiring a major firmware overhaul.
That was a missing event subscription. The fan-mode characteristic wasn’t in the live-update list, so external On/Auto changes only showed up after a manual Refresh. Fixed (re-import) — it now subscribes to fan-mode events, so it updates live like the rest.
While I was in there I fixed a related one: comfort profile and hold-end time also only updated on manual Refresh, because (unlike fan mode) those characteristics are read-only with no event support — so they can’t be subscribed. v0.11.4 reads them on the existing keepalive instead, so they self-refresh within ~5 min.
All can be done using other community or built-in apps on HE.
Well done! If this had existed a few years ago, I'd have gone for the more aesthetic Ecobee instead of the Honeywell T6 Pro!
In theory, doesn’t your approach make it possible to add other HomeKit devices to older hubs?
Never mind, I see this was addressed by @ramset earlier in this thread.
Very impressive!!
I was so ready to take your route also.
This was my last huzza regarding Ecobee.
I have a Pearl in standby, was honestly considering the Z-Wave Honeywell.
But the wife(and so do I to be honest) really likes the Ecobee (aesthetics, big touchscreen). My only beef was the cloud dependency which now, is history.
If it's any comfort, you can score Ecobees for ~$20 on ebay (lower also on Marketplace?)
Also check your utility. For example, my utility sponsors a program where I can get a base model ecobee for free, and their premium model for $80.
Our utility company requires you to let them control it if you use their program for a discounted price.... no thank you.
Luckily for us, there’s no such restriction. That would be horrible - especially given how hot and humid it is over here!
+ 1 to that. Hard pass.
In the southeast US here. It is also known for the humidity as a heat complication.
And just take a guess as to when they limit your HVAC..... you guessed it - peak hours. When it is the coldest and when it is the hottest.
Our utility is building new powerplants to meet the demand from data centers. The cost of that building has been passed on to their customers - residential and commercial, under the guise of infrastructure improvements. But at least so far they’re not restricting use.
SE Duke Energy customer here and I had thought this too and avoided their store until I reread their fine print and they don’t require control unless you sign up for their monthly bill discount program which I would never do
If you are a Costco member they have a great deal on the Ecobee Premium thermostat $190 (through June 30) and it comes with 2 sensors vs 1 like everywhere else.
Ping me if you still need those classes. Or other classes 
If there’s a reason we can’t include a class, fine, but generally it’s just a “forbidden unless explicitly permitted” sandbox approach.
My man!!! I appreciate you so much !!! True real-life testing!
I’m actually using it via the helpers below and didn’t quite pay attention to the status changes.
I fixed it but i also organized the repo a bit. So the links are updated in the original post.
Use those as a one-time source update.
I also couldn’t help notice the name of your automation…
You might want to take a look here 
Great set of drivers, Thanks, but (there’s always a but), why are motion and presence disabled for thermostat? Would leaving them enabled cause problems?
I use them and have to remember to uncomment the lines in the source every time I update.
Please consider making the change in the code.
In my selfishness (and personal use case) they are “in the way”.
I’ll make the change and enable them by default, leaving the comment for the optional “disable”.
Refresh, the capabilities are now enabled by default.
+1 !!
Ok I included everything that was obvious and available in the HAP protocol.
I still have 4 undocumented ones (not so obvious logic, ids that didn’t budge when I was probing/changing parameters initially), 4 which I’ll start poking at now.
For the curious:
iid 49 (0-4), 50 (0-3), 51 (bool), 53 (0-100)…
I’ll end up documenting and decoding the whole friggin’ thing. 
