HomeKit temperature device entities does not update

[Jogge]

The problem

Device Setup:

I have some Danfoss Link devices that only integrate to Amazon Alexa using the Danfoss Alexa Skill.
To add these devices to Home Assistant, the only way I've found possible was to install and use HomeBridge and install the plugin Homebridge Alexa Smart Home that exposes a HomeKit device which Home Assistant can integrate with.

Issue

As you can see from this graph, it all started just fine with frequent updates:

But there have been a lot of periods later on where the devices have not been updated for long periods.

Today around 09:30, I updated to the latest beta (2024.9.0b1) to see if this issue was already fixed.

But unfortunately, it has not been fixed. Here's the graph from today:

As you can see the warmest room is 25.5 degrees Celsius.

I have been debug logging this integration for a while. When I look at log messages from right after update, and a later one, one of the differences is that the room temperature should have been 25.8 degrees Celsius now:

But even after Home Assistant has received this change it still has not updated the entity.

Note: I have [CENSORED] multiple things in the debug log. Please let me know if I have censored too much...

What version of Home Assistant Core has the issue?

core-2024.9.0b1

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

homekit_controller

Link to integration documentation on our website

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

Diagnostics information

home-assistant_homekit_controller.log

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 @Jc2k, @bdraco, mind taking a look at this issue 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 issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign homekit_controller Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[Jogge]

This is still an issue in 2024.9.0b2.

[Jogge]

This is also an issue in 2024.9.0b3

[Jogge]

Also an issue in 2024.9.0b4

[Jogge]

Also an issue in 2024.9.0b5

[Jogge]

Also an issue in 2024.9.0

[Jogge]

Also an issue in 2024.9.1

[Jogge]

Also an issue in 2024.9.2

[jan2valenta]

Hello, I don't believe this is an issue of HomeKit integration in HA. I have the same and I take it from Danfoss Link via Alexa to HB and then directly to Homekit (skipping HA completely). Temperature in Alexa and Homebridge is exact as is measured by Danfoss but it is rounded to 0.5 degrees in Homekit what is ok. Unfortunately it can only show me the current temperature but if I change the target temperature, nothing happens.

[drakaz]

Hello, same issue on my installation. I have three TH1123WF, sometimes the temperature stop being updated on HA side on some of them. Temperature is still updated on Neviweb application. Rebooting/reloading integration fix it.

[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.