Anova integration: documented sensors are missing (Cook Time Remaining, State)

Configuration
, ,
1

Hi everyone,

I'm looking for some guidance regarding the Anova integration.

According to the documentation:

the integration should expose sensors such as:

  • Cook Time Remaining
  • State
  • Heater Temperature
  • Triac Temperature

However, with my Anova Precision Cooker , Home Assistant only creates these four sensors:

  • sensor.anova_precision_cooker_mode
  • sensor.anova_precision_cooker_water_temperature
  • sensor.anova_precision_cooker_target_temperature
  • sensor.anova_precision_cooker_cook_time

The last sensor (cook_time ) contains the configured cooking duration and remains constant throughout the cooking process.

The device itself behaves like this:

  1. The user sets the target temperature and cooking duration.
  2. The mode changes from idle to Cooking .
  3. The water heats up to the target temperature.
  4. Only after the target temperature is reached does the cooking timer actually begin.

Because Home Assistant does not expose either the timer start, the remaining time, or a cooking-complete state, it is impossible to create reliable automations such as:

  • notify when 5 minutes remain;
  • notify when cooking is finished.

I already opened a GitHub issue:

Unfortunately, it has not received any feedback yet.

Before trying to implement this myself, I'd like to ask the community:

  • Is this the expected behavior of the current integration?
  • Is the documentation outdated?
  • Has anyone already solved this problem?
  • Would a pull request adding these sensors be welcome if the API already provides the necessary data?

I have the device available, diagnostics, and I'm happy to test any proposed changes.

Thank you!

2

Feature Requests are handled here.

3

Silly question, but have you checked if those "missing" entities are disabled by default?

Also, a couple of years ago Anova switched to some kind of new model for their API for new users. Don't remember the details but it's in these forums it you wanna search. Anova Sous Vide Integration - #38 by skorpioskorpio

Maybe the new API simply doesn't contain that data?

4

Thanks. I don't think this is a feature request.

The sensors are already documented and already implemented in the Home Assistant Anova integration, including Cook Time Remaining and State. The issue is that for A6/A7 devices the underlying anova_wifi library receives the raw websocket payload but does not map the relevant A6/A7 timer fields into the existing sensor model.

So this looks like a bug in the existing integration/library support for A6/A7 devices, not a request for new entities or new functionality.

5

Yes, I checked that. The entities were not disabled by default — they were not created at all.

The reason seems to be that Home Assistant only creates Anova sensor entities when the underlying anova_wifi library returns a non-None value for them. The HA integration already defines the documented sensors such as Cook Time Remaining and State, but for A6/A7 devices the current anova_wifi parser does not populate those fields.

I also checked the raw websocket payload. The new A6/A7 API does contain the needed timer/state data. So the data is present in the websocket payload.

So this looks like incomplete A6/A7 payload parsing in anova_wifi, not a new feature request and not disabled entities.

6

If HA is getting a none value (or no value at all) from the API on setup, how do you expect it to show you that data?

I had a quick look at the Anova Dev Docs. The API for the A6/A7 devices contains way less options. There are no get/read options in the commands - the closest thing there is is the Show message stream option, and even that won't help much if HA has no initial values to create your "missing" entities.

A2/A3 commands (on which the HA integration is based): Available Commands | Anova Developer Documentation

A6/A7 commands (your device): Precision Cooker Commands | Anova Developer Documentation

7

Sorry if my original explanation was confusing.

The data is actually coming from the Anova API / websocket. I can see it when debug logging is enabled.

The issue seems to be in the processing layer. Home Assistant uses the anova_wifi Python library, and for A6/A7 devices the library currently receives the raw websocket payload but does not map some of the A6/A7 fields into the existing sensor model. Because of that, Home Assistant never gets values for some of the documented sensors.

So, in short: the data exists in the API payload, but it is effectively discarded while being parsed by integration for my A7 device.

Here is a shortened example from my real A7 websocket payload:" 
{
  "command": "EVENT_APC_STATE",
  "payload": {
    "type": "a7",
    "state": {
      "nodes": {
        "waterTemperatureSensor": {
          "current": {
            "celsius": 49.27
          },
          "setpoint": {
            "celsius": 54
          },
          "enabled": true
        },
        "lowWater": {
          "empty": false,
          "warning": false
        },
        "timer": {
          "mode": "running",
          "startedAtTimestamp": "2026-06-11T22:46:35Z",
          "initial": 1200
        }
      },
      "cook": {
        "activeStageMode": "entering",
        "activeStageStartedTimestamp": "2026-06-11T22:46:35Z",
        "startedTimestamp": "2026-06-11T22:46:35Z"
      },
      "state": {
        "mode": "cook",
        "temperatureUnit": "C"
      },
      "updatedTimestamp": "2026-06-11T22:46:35Z"
    }
  }
}
8

Look here at the difference in sensors between the build_a3_payload & build_a6_a7_payload. You're getting exactly what the a6/a7 code is supposed to provide.

If your model number (ANxxx) does not match any of the 3 officially supported devices in the documentation, then what you are asking for is a feature request, not a bug.

image
image611×252 17.7 KB

9

Thank you. I understand your point.

For my own setup, I have already solved the issue locally. ChatGPT helped me create a local patch, and after applying it my device works very well in Home Assistant.

My real problem was that my own development level was not high enough to correctly understand where the problem was in the code. I am mostly a user, not a developer. I opened an issue on GitHub about the problem, but unfortunately the integration owner did not respond for several months. That is why I decided to post in the community forum.

However, I do not think the forum is the right place to continue discussing this. From the replies so far, I mostly received comments about the wording and form of my message, but very little constructive discussion about the actual technical problem.

So this will be my last message here.

My logic is simple:

If the documentation says that only these three devices are supported:

  • AN500-10 (Anova Precision Cooker)
  • AN500-US00 (Anova Precision Cooker)
  • AN600-10 (Anova Precision Cooker Pro)

and all other devices should be treated as feature requests, then the integration is no longer relevant in its current documented form.

The reason is that Anova announced that the original Anova Precision Cooker Bluetooth and Bluetooth+WiFi models would no longer be able to connect to the Anova app after September 28, 2025:

“We're saying goodbye to our original cookers next year. After September 28, 2025, you will no longer be able to connect your original Anova Precision Cooker Bluetooth or Bluetooth+WiFi to the Anova app. We've been supporting these cookers for 10 years, but now it's time to retire them.”

So, as I understand it, the devices documented as supported are legacy devices that are being retired from the manufacturer’s cloud/app ecosystem, while newer devices that still connect to the API and provide data are considered unsupported feature requests.

That makes the current state of the integration confusing and, in my opinion, no longer valid as documented.

I will stop discussing this here. The next step will be a pull request to anova_wifi. If it is accepted, great. If not, the local patch is enough for my own setup.