# Home Connect Integration: Oven cavity temperature sensor stuck at constant value (20/47°C)

[marck479]

The problem

The Problem

I am using a Bosch oven with the Home Connect integration. The cavity temperature sensor in Home Assistant is completely stuck and not updating:

1. The sensor is showing a static temperature of at first 20°C and then randomly switched to constant 47°C
2. As visible in the attached screenshot, the temperature graph shows a perfectly flat line at 47°C throughout the entire day
3. The oven has not been in use during this time, and the reported temperature does not change regardless of oven status
4. This is not an accuracy issue as mentioned in the documentation, but a complete failure to update the temperature value

The documentation states "It is not recommended to use the Current cavity temperature sensor because the temperature might not provide the necessary accuracy" - however, this is a different issue. The sensor is not updating at all rather than being inaccurate.

Environment

• Device: Bosch Oven (HBG7764)
• Integration: Home Connect
• Version: Core 2025.4.3 Supervisor 2025.04.0 Operating System 15.2 Frontend 20250411.0

Additional Notes

The oven itself functions correctly and shows proper temperature readings on its own display. Only the Home Assistant integration is affected.

Screenshot

What version of Home Assistant Core has the issue?

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

Home Connect

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of home_connect 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 home_connect 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)}}

---

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

[Diegorro98]

Hi

Yes, the documentation does not recommend using it. So, because of that, we don't recommend using it neither.

Maybe it is not a integration problem, maybe it is a problem with the API or the appliance where the stop sending updates about that value for some reason...

To know if it is an integration problem or an API / appliance problem, we should inspect the debug logs.

Please enable the debug logs and try to repeat the same scenario.

If you find that new values for Cooking.Oven.Status.CurrentCavityTemperature are present in the logs but the values aren't updated on the integration, then yes, we have an integration issue. Otherwise, if the debug logs repeat the same pattern than the integration... Bad news, it is an API / appliance problem.

You can also attach the logs to allow us to verify it too.

[Diegorro98]

@home-assistant add-label needs-more-information

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