Pi-Hole Integration Issues?

matchmee commented 10 months ago

The problem

My logs give me this error with my update to the latest HA and Pi-Hole.

/Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/pi_hole/init.py", line 97, in async_setup_entry await er.async_migrate_entries(hass, entry.entry_id, update_unique_id) File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1363, in async_migrate_entries ent_reg.async_update_entity(entry.entity_id, **updates) File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 963, in async_update_entity return self._async_update_entity( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 908, in _async_update_entity raise ValueError( ValueError: Unique id '24475bea51067356663b48350d6327b4/core_update_available' is already in use by 'update.home_pi_hole_core_update_available'

What version of Home Assistant Core has the issue?

core-2024.1.4

What was the last working version of Home Assistant Core?

core-2023.12.3

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Pi-Hole

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

/Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/pi_hole/__init__.py", line 97, in async_setup_entry
    await er.async_migrate_entries(hass, entry.entry_id, update_unique_id)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1363, in async_migrate_entries
    ent_reg.async_update_entity(entry.entity_id, **updates)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 963, in async_update_entity
    return self._async_update_entity(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 908, in _async_update_entity
    raise ValueError(
ValueError: Unique id '24475bea51067356663b48350d6327b4/core_update_available' is already in use by 'update.home_pi_hole_core_update_available'

Additional information

No response

home-assistant[bot] commented 10 months ago

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

Code owner commands

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

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

matchmee commented 10 months ago

If it helps, I just updated my pi-hole today as well. It is on:

Docker Tag [2024.01.0] Pi-hole [v5.17.3] FTL [v5.24] Web Interface [v5.21]

matchmee commented 10 months ago

If I went in and manually deleted all entities, I was able to refresh and get back 13 of them. Before when it wasn't loading there were 32. It wasn't letting me delete 6 of the entities for a while, but after multiple restarts I was finally able to delete all entities.

gohakn commented 9 months ago

Not sure if this is the right place for my question but my PiHole integration in HA is howing me three updates should be available. grafik

HA is up to date and Pihole is " Pi-hole [v5.17.3] FTL [v5.24] Web Interface [v5.21]" When I try to update with pihole -up it ends with the following errormessage:

pi@pihole:~ $ pihole -up
  [✓] Update local cache of available packages
  [i] Existing PHP installation detected : PHP version 7.4.33
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for dialog
  [✓] Checking for ca-certificates

  [i] Checking for updates...
fatal: unable to access 'https://github.com/pi-hole/pi-hole.git/': Could not resolve host: github.com
  [i] Pi-hole Core:     up to date
fatal: unable to access 'https://github.com/pi-hole/web.git/': Could not resolve host: github.com
  [i] Web Interface:    up to date
  [i] FTL:              update available

  [i] FTL out of date, it will be updated by the installer.

  [✓] Root user check

  [i] SELinux not detected
  [✓] Update local cache of available packages
  [i] Existing PHP installation detected : PHP version 7.4.33

  [✓] Checking apt-get for upgraded packages... 9 updates available
  [i] It is recommended to update your OS after installing the Pi-hole!

  [i] Checking for / installing Required dependencies for OS Check...
  [✓] Checking for grep
  [✓] Checking for dnsutils

  [✗] Retrieval of supported OS list failed. dig failed with return code 10.
      Unable to determine if the detected OS (Raspbian 11) is supported
      Possible causes for this include:
        - Firewall blocking certain DNS lookups from Pi-hole device
        - ns1.pi-hole.net being blocked (required to obtain TXT record from versions.pi-hole.net containing supported operating systems)
        - Other internet connectivity issues

      https://docs.pi-hole.net/main/prerequisites/#supported-operating-systems

      If you wish to attempt to continue anyway, you can try one of the following commands to skip this check:

      e.g: If you are seeing this message on a fresh install, you can run:
             curl -sSL https://install.pi-hole.net | sudo PIHOLE_SKIP_OS_CHECK=true bash

           If you are seeing this message after having run pihole -up:
             sudo PIHOLE_SKIP_OS_CHECK=true pihole -r
           (In this case, your previous run of pihole -up will have already updated the local repository)

      It is possible that the installation will still fail at this stage due to an unsupported configuration.
      If that is the case, you can feel free to ask the community on Discourse with the Community Help category:
      https://discourse.pi-hole.net/c/bugs-problems-issues/community-help/

  Unable to complete update, please contact Pi-hole Support

The recommended sudo PIHOLE_SKIP_OS_CHECK=true pihole -r doesn`t help either... Any recomendations are welcome?

Thank you.

issue-triage-workflows[bot] commented 6 months ago

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.

home-assistant / core