Honeywell evohome climate entity shows state 'heat' instead of 'unavailable'

[Ghannes]

The problem

If a Honeywell evohome radiatorregulator can't connect, i.e. when battery is empy; then HA still shows that the entity is available with state 'heat' - it should be 'unavailable'.

What version of Home Assistant Core has the issue?

core-2023.6.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

evohome

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of `evohome` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign evohome` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

evohome documentation evohome source _{^{(message by IssueLinks)}}

[zxdavb]

Hello, thanks for your submission.

If a Honeywell evohome radiatorregulator can't connect, i.e. when battery is empy; then HA still shows that the entity is available with state 'heat' - it should be 'unavailable'.

~Please provide the entity_id of the entity that you refer to.~

~In particular, please be sure to differentiate between a zone, and its corresponding TRV (assuming a 1-to-1 relationship).~

[Ghannes]

Hi,

The entityID is climate.room: in my case climate.kelder. ‘Kelder’ translates to basement in English.

Thanks, Hans

Op vr 30 jun. 2023 om 14:53 schreef David Bonnes @.***>

Hello, thanks for your submission.

If a Honeywell evohome radiatorregulator can't connect, i.e. when battery is empy; then HA still shows that the entity is available with state 'heat'

• it should be 'unavailable'.

Please provide the entity_id of the entity that you refer to.

In particular, please be sure to differentiate between a zone, and its corresponding TRV (assuming a 1-to-1 relationship).

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/95612#issuecomment-1614610290, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVH7F2YOB7V65NZLISYU2DXN3D55ANCNFSM6AAAAAAZZSU2EY . You are receiving this because you authored the thread.Message ID: @.***>

[zxdavb]

I have edited the above, because I am afraid I was briefly confused between two closely related integrations...

The answer is: the evohome integration is limited by the information it receives from the vendor API.

In addition, there is a distinction between a zone (climate.kelder, the Climate entity that is in heat mode), and the corresponding TRV, which is not exposed in this integration.

IIRC, the evohome integration is telling you what the vendor's API is telling it: the zone is available, and is in heat mode.

I would need to see the JSON from the vendor's API to see if the JSON contains any information that can be leveraged for this (e.g. zone['isavailable']), but I suspect not.

[Ghannes]

I noticed that in case of battery empty, the climate.current_temperature was 'unknown' instead of a decimal number. That could be a way to detect that radiatorregulator isn't connected.

[zxdavb]

Unfortunately, that wouldn't work in all cases.

I assume (correct me if I am wrong) that you have a zone with a TRV and no other devices. In this case, the TRV is also the zone sensor (as well as the actuator), which is why the current_temperature is unavailable.

But think of scenarios where the zone has multiple TRVs, only one (or none) of which can be the sensor.

Regardless of all that - the controller is still calling for heat of behalf of that zone, or not, according to its own opinion - that's what the integration is reflecting.

I'm inclined to close this issue as a wont_fix, I'm sorry that wont be what you're hoping for.

[zxdavb]

Question: what is the the controller saying for that zone?

[Ghannes]

hi, I have ~6 TRVs and a central unit just like the usual evoHome kit. All had enough battery power, except for kelder. Therefore I think we can use that check on current_temperature to determine if the TRV is unavailable.

Op vr 30 jun 2023 om 16:03 schreef David Bonnes @.***>:

Question: what is the the controller saying for that zone?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/95612#issuecomment-1614701325, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVH7F2TUYZAPXAIEECAYVTXN3MDXANCNFSM6AAAAAAZZSU2EY . You are receiving this because you authored the thread.Message ID: @.***>

[Ghannes]

Question: what is the the controller saying for that zone?

Think it was showing sth like 'connecting' and an hourglass icon

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Ghannes]

issue is still present in 2023.9.0

Op do 28 sep 2023 om 17:06 schreef issue-triage-workflows[bot] < @.***>:

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/95612#issuecomment-1739477050, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVH7FY52UPJUWOBC46LV53X4WG73ANCNFSM6AAAAAAZZSU2EY . You are receiving this because you authored the thread.Message ID: @.***>

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Ghannes]

Issue still exists on latest version!

Op wo 27 dec 2023 om 18:05 schreef issue-triage-workflows[bot] < @.***>

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/95612#issuecomment-1870480571, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVH7FYB26E5QFDS7AGELG3YLRIN7AVCNFSM6AAAAAAZZSU2E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGQ4DANJXGE . You are receiving this because you authored the thread.Message ID: @.***>

[zxdavb]

I must admit, I am inclined to close this issue as wontfix.

However, I am prepared to have one more look at it.

It would be really helpful if you could provide the following JSON, so I can determine what is going wrong:

1. Add this logging to configuration.json and restart HA:

   logger:
   logs:
   homeassistant.components.evohome: debug

2. Pull these two lines from home-assistant.log:

   
   2023-11-02 11:24:05.950 DEBUG (MainThread) [homeassistant.components.evohome] Config = {...

2023-11-02 11:24:07.256 DEBUG (MainThread) [homeassistant.components.evohome] Status = {...

Note that personally-identifiable information is redacted from these JSON, except for zone names.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Ghannes]

What came out of the additional one more look?

Op do 9 mei 2024 om 10:07 schreef issue-triage-workflows[bot] < @.***>

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/95612#issuecomment-2102165169, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVH7FYSLGPNZGQKTUNIBXLZBMVDNAVCNFSM6AAAAAAZZSU2E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBSGE3DKMJWHE . You are receiving this because you authored the thread.Message ID: @.***>

[zxdavb]

What came out of the additional one more look?

I am sorry, the system is behaving as expected. I am sorry that this is not the answer you want.

You can create a custom sensor that may come close to the feature you require.

This is a 'wontfix', and I am closing this issue.