Review the use of async_get_entity_id() from entity_registry in eheimdigital

Open Beginner friendly
#175,703 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend, testing

Research direction

Open tests/components/eheimdigital/test_init.py and search for calls to entity_registry.async_get_entity_id(). Compare each argument with the documented domain, platform, and unique_id order, then run the eheimdigital tests; done means the calls match the signature and the tests pass.

Written by the indexing model from the issue text.

Description

integration: eheimdigital
The problem

The docstring for the entity registry's async_get_entity_id method has recently been revised to clarify its usage.

Since the parameters are subject to misinterpretation, we recommend carefully verifying usage according to the following method signature:

    def async_get_entity_id(
        self, domain: str, platform: str, unique_id: str
    ) -> str | None:
        """Check if an entity_id is currently registered.

        domain: entity platform domain (e.g. light, sensor)
        platform: integration domain (e.g. hue, zwave)
        """

Affected file(s):

  • tests/components/eheimdigital/test_init.py
What version of Home Assistant Core has the issue?

2026.7.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

eheimdigital

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

Dominant language
Python
Stars
90.8k
Forks
38.7k
Avg merge
1d 1h
Merged PRs (30d)
625

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from home-assistant/core

All issues in home-assistant/core

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.