Repository navigation
Duplicate Panasonic Viera discovery not ignorable #139159
Description
The problem
I have the following YAML in my configuration.yaml file:
panasonic_viera:
host: 10.1.1.15
name: Lounge TV
turn_on_action:
- action: script.lounge_tv_on
I switched to using YAML instead of the config flow because of this issue that was never addressed: #124883 It does not occur when using YAML.
However, now whenever I restart Home Assistant the following unignorable discovery message is received:
The only way to dismiss it is to turn on the TV and go through the config flow at which point I am advised that the device is already configured:
Could you please stop the duplicate discovery for the YAML configured device.
What version of Home Assistant Core has the issue?
core-2025.2.5
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
Panasonic Viera
Link to integration documentation on our website
https://www.home-assistant.io/integrations/panasonic_viera
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Logger: homeassistant.components.panasonic_viera.config_flow
Source: components/panasonic_viera/config_flow.py:64
integration: Panasonic Viera (documentation, issues)
First occurred: 09:29:02 (1 occurrences)
Last logged: 09:29:02
Could not establish remote connection: <urlopen error [Errno 113] Host is unreachable>Additional information
No response
Activity
home-assistant commentedon Feb 24, 2025
panasonic_viera documentation
panasonic_viera source
hole222 commentedon Feb 25, 2025
issue-triage-workflows commentedon May 27, 2025
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.
hole222 commentedon May 27, 2025
Still an issue
issue-triage-workflows commentedon Aug 25, 2025
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.
hole222 commentedon Aug 25, 2025
I'm back on the config flow integration instead of YAML config but assume this is still an issue as nothing has been done.
dxmnkd316 commentedon Sep 13, 2025
Still an issue.
issue-triage-workflows commentedon Dec 13, 2025
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.
hole222 commentedon Dec 13, 2025
Still an issue.
3 remaining items
hole222 commentedon Mar 13, 2026
Still an issue.
dxmnkd316 commentedon Mar 16, 2026
Looks like frenck might have submitted a PR to fix this. Hoping to see this resolved in April's release
issue-triage-workflows commentedon Jun 14, 2026
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.
hole222 commentedon Jun 14, 2026
Is it resolved for you?
dxmnkd316 commentedon Jul 5, 2026
Still an issue.
issue-triage-workflows commentedon Oct 4, 2026
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.
hole222 commentedon Oct 4, 2026
Still an issue.
jerome-pouiller commentedon Oct 22, 2026
@hole222 if you copy
components/panasonic_vieraof #188097 in<your config path>/custom_components, do you still have the issue?jerome-pouiller commentedon Oct 22, 2026
@hole222, BTW I believe #183194 fixes #124883.
hole222 commentedon Oct 22, 2026
Thanks for your work on this. Unfortunately I'm not sure how to grab that folder. All I can see is Files Changed.
Nice. Thanks.
I no longer need to use the YAML config as I now have CEC control of the TV power from my apple tv. So could move to the UI config flow to add it instead.