ZHA - Support outdoor_temperature for thermostats

[alexpomsft]

The problem

Howdy, this is very similar to #78797, but for the ZHA integration. In short, there are scenarios where thermostats such as the Namron Zigbee Touch Thermostat 16A are used for bathroom floor heat with the device physically installed outside of the bathroom. The thermostat can be configured to use the floor heat temperature to turn on/off. The floor heat temperature is correctly reported through the outdoor_temperature (id: 0x001) attribute.

ZHA doesn't currently read, display or connect this information to Home Assistant. ZHA only uses the local_temperature (id: 0x0000) attribute, which doesn't make sense for this scenario. The ZWave and Zigbee2Mqtt integrations seem to have ways of achieving this.

It would be great to understand how we can get this scenario to work for the ZHA integration! :)

What version of Home Assistant Core has the issue?

2023.7.3

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

ZHA

Link to integration documentation on our website

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

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]

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

Code owner commands

Code owners of zha 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 zha Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[issue-triage-workflows]

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.

[crom1e]

Still no fix in 2023.11.3