HomeKit Device integration recommended as a "fully functional" alternative

[BillWiegert]

Feedback

The warning blurb on this page recommends the HomeKit Device integration as a "fully functional" alternative now that ecobee developer accounts can no longer be created. I think this phrasing is misleading because the HomeKit integration lacks many features that would be of interest to a Home Assistant user.

Here are a few limitations of the HomeKit integration compared to the ecobee integration:

• No control over auxiliary heat
• No list of currently running equipment (can't tell when aux heat is running)
• No information from air quality sensors
• No support for vacation features

The HomeKit Device integration is certainly better than nothing, but its functionality is incomplete. As such I'd recommend changing the last sentence of the warning message to the following:

In the meantime, you can use the HomeKit Device integration as an alternative that provides basic functionality.

URL

https://www.home-assistant.io/integrations/ecobee/

Version

2024.11.2

Additional information

No response

[home-assistant]

Hey there @Jc2k, @bdraco, mind taking a look at this feedback as it has been labeled with an integration (homekit_controller) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homekit_controller can trigger bot actions by commenting:

• @home-assistant close Closes the feedback.
• @home-assistant rename Awesome new title Renames the feedback.
• @home-assistant reopen Reopen the feedback.
• @home-assistant unassign homekit_controller Removes the current integration label and assignees on the feedback, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.