search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.52k stars 30.71k forks source link

ecobee integration - notifications about disabling legacy ecobee set_aux_heat service keep appearing as of 2024.7 #121722

Open robertoleonardo opened 4 months ago

robertoleonardo commented 4 months ago

The problem

when i upgraded to the first 2024.7 version last week, i started periodically getting this warning from the ecobee integration:

image

as far as i can tell, i don't have any automations, scripts, etc. using the set_aux_heat service (i've run a search across all text-searchable file formats (yaml, json, py, js, lovelace*, among others) in my config folder -- no hits). i initially figured everyone got this warning once, so i just hit submit and it said it was successfully repaired. but then the issue reappeared randomly a few hours later and has been reappearing ever since. it's happening maybe every 4-6 hours or so.

it seems to be convinced that i still have an automation or something using that service, except i don't think i do (and i don't think i ever did).

it's odd and a bit hard to pinpoint exactly what triggers it to reappear -- it happens on some reboots, but not others. and sometimes it just happens even when i didn't restart.

i tried removing and re-adding the integration -- issue persists. I just updated to 7.2 this am hoping that would fix it -- but it just happened again.

i don't see anything pertinent in the core logs (searching for ecobee just gives me a huge json string with all my device info; and searching set_aux_heat gives me nothing) -- but let me know if there's something else i should search for.

i just enabled debug logging so next time it happens, i'll upload the diagnostics file -- just wanted to type this out in the meantime while i had a few minutes.

What version of Home Assistant Core has the issue?

2024.7.*

What was the last working version of Home Assistant Core?

2024.6.*

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ecobee

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

home-assistant[bot] commented 4 months ago

ecobee documentation ecobee source

bjpetit commented 3 months ago

Interesting. That repair item only shows up if the legacy set_aux_heat service is called. Looks like you did a through sweep of your automations. So I expect something more subtle is calling that service. A couple questions.

  1. You are running with an ecobee that includes a heat pump, correct? So, AuxHeatOnly is a valid HVAC mode on your thermostat.
  2. Do you have any scenes defined that may be modifying the thermostat settings? (Even if it isn't touching the aux_heat)
  3. Any custom components installed?
robertoleonardo commented 3 months ago

ah ha! your questions led me to it -- it's the scene issue. i do in fact have several scenes that change thermostat and i just manually tested and can confirm that's what's triggering the error. not clear why given that they still don't call the referenced service (directly, at least), but presumably i can find a workaround. i won't have time to tinker for a few days but couple things come to mind for me to try:

  1. have the scenes set temps directly instead of comfort settings as they're currently defined
  2. move the thermostat changes from scene definitions to automations triggered by those scenes.

if you have any other suggestions, i'm all ears -- thanks for the help and i'll report back when i have time to mess around with it in a few days.

oh and to (unhelpfully) answer the question re heat pump in case it is still relevant. honestly i dont know. i dont remember having to do anything other than follow the default instructions when installing my ecobee, so i think my system is whatever is most common. i assume that's something that i can figure out by taking the face plate off and looking at which wires are connected to the back plate --- i'll do that as well when i experiment this weekend.

thanks again!

-- rob lee m: 310.431.1619

From: Brent Petit @.> Sent: Friday, July 12, 2024 11:12:41 AM To: home-assistant/core @.> Cc: robertoleonardo @.>; Author @.> Subject: Re: [home-assistant/core] ecobee integration - notifications about disabling legacy ecobee set_aux_heat service keep appearing as of 2024.7 (Issue #121722)

Interesting. That repair item only shows up if the legacy set_aux_heat service is called. Looks like you did a through sweep of your automations. So I expect something more subtle is calling that service. A couple questions.

  1. You are running with an ecobee that includes a heat pump, correct? So, AuxHeatOnly is a valid HVAC mode on your thermostat.
  2. Do you have any scenes defined that may be modifying the thermostat settings? (Even if it isn't touching the aux_heat)
  3. Any custom components installed?

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/121722#issuecomment-2226127306, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADELGE4IUMXGV5J2URQS7GTZMAMBTAVCNFSM6AAAAABKVWYJMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRWGEZDOMZQGY. You are receiving this because you authored the thread.Message ID: @.***>

robertoleonardo commented 3 months ago

and rereading the heat pump question, i might have over complicated it: if the question boils down to whether i have heat in addition to cooling, the answer is yes.

-- rob lee m: 310.431.1619

From: Rob Lee @.> Sent: Friday, July 12, 2024 11:28:12 AM To: home-assistant/core @.>; home-assistant/core @.> Cc: Author @.> Subject: Re: [home-assistant/core] ecobee integration - notifications about disabling legacy ecobee set_aux_heat service keep appearing as of 2024.7 (Issue #121722)

ah ha! your questions led me to it -- it's the scene issue. i do in fact have several scenes that change thermostat and i just manually tested and can confirm that's what's triggering the error. not clear why given that they still don't call the referenced service (directly, at least), but presumably i can find a workaround. i won't have time to tinker for a few days but couple things come to mind for me to try:

  1. have the scenes set temps directly instead of comfort settings as they're currently defined
  2. move the thermostat changes from scene definitions to automations triggered by those scenes.

if you have any other suggestions, i'm all ears -- thanks for the help and i'll report back when i have time to mess around with it in a few days.

oh and to (unhelpfully) answer the question re heat pump in case it is still relevant. honestly i dont know. i dont remember having to do anything other than follow the default instructions when installing my ecobee, so i think my system is whatever is most common. i assume that's something that i can figure out by taking the face plate off and looking at which wires are connected to the back plate --- i'll do that as well when i experiment this weekend.

thanks again!

-- rob lee m: 310.431.1619

From: Brent Petit @.> Sent: Friday, July 12, 2024 11:12:41 AM To: home-assistant/core @.> Cc: robertoleonardo @.>; Author @.> Subject: Re: [home-assistant/core] ecobee integration - notifications about disabling legacy ecobee set_aux_heat service keep appearing as of 2024.7 (Issue #121722)

Interesting. That repair item only shows up if the legacy set_aux_heat service is called. Looks like you did a through sweep of your automations. So I expect something more subtle is calling that service. A couple questions.

  1. You are running with an ecobee that includes a heat pump, correct? So, AuxHeatOnly is a valid HVAC mode on your thermostat.
  2. Do you have any scenes defined that may be modifying the thermostat settings? (Even if it isn't touching the aux_heat)
  3. Any custom components installed?

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/121722#issuecomment-2226127306, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADELGE4IUMXGV5J2URQS7GTZMAMBTAVCNFSM6AAAAABKVWYJMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRWGEZDOMZQGY. You are receiving this because you authored the thread.Message ID: @.***>

bjpetit commented 3 months ago

Glad I could help. I was able to reproduce this issue as well here by creating a scene with a thermostat included.

I've submitted a PR to remove the deprecated call from the scene handling. Hopefully that can roll out in a minor update before too long.

BTW. For a quick check regarding my heat pump question. If you go to the "Developer Tools->states" page. Look at your climate. entity. The right column has a number of attributes. If one of those is aux_heat, then you have a heat pump configured.

robertoleonardo commented 3 months ago

Ahhh - Yep, it says aux_heat: off. So there you have it, i guess i have a heat pump (the more you know...).

Knowing that it should be addressed soonish, i'll probably just leave my scenes configured as they are and just wait on the minor update.

You've been very helpful -- really appreciate it. Take care

bjpetit commented 3 months ago

The recent 2024.8 release addresses this issue.

fermulator commented 1 week ago

(stumbled over this) FYI #129294 - i think it's a different situation