Can't configure WOL for panasonic viera when configured via the UI flow

Particpant commented 1 year ago

The problem

When setting up the Panasonic Viera integration, it's not possible to set up the "power-on" key, and the TV is listed as unavailable, despite being active on the network at the configured IP address.

What version of Home Assistant Core has the issue?

core-2023.7.1

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

UI-based setup, no YAML.

Anything in the logs that might be useful for us?

No, just an omitted feature in the setup flow.

Additional information

It appears the settings for targeting a WoL packet for power-on are just missing from the UI setup flow. I'm suspecting the integration can't access the API when the TV is off, and that's why it's unavailable.

home-assistant[bot] commented 1 year ago

panasonic_viera documentation panasonic_viera source

Particpant commented 1 year ago

I previously filed https://github.com/home-assistant/core/issues/90019, but missed the stale bot's closure.

issue-triage-workflows[bot] commented 1 year 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.

joostlek commented 1 year ago

Linked issue

issue-triage-workflows[bot] commented 9 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.

Particpant commented 9 months ago

Linked issue was closed without being merged, problem still exists.

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.

Particpant commented 6 months ago

Still not fixed.

issue-triage-workflows[bot] commented 3 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.

Particpant commented 3 months ago

Unresolved.

issue-triage-workflows[bot] commented 2 weeks 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.

dxmnkd316 commented 1 week ago

Add this to your configuration.yaml

Fill in the info below (delete the brackets, keep the quotes)

panasonic_viera:
  host: <tv ip address>
  name: <Name of your TV>
  turn_on_action:
    - service: wake_on_lan.send_magic_packet
      data:
        mac: "<your tv's MAC>"

nikeshpurohit commented 1 week ago

This

Add this to your configuration.yaml

Fill in the info below (delete the brackets, keep the quotes)
panasonic_viera:
  host: <tv ip address>
  name: <Name of your TV>
  turn_on_action:
    - service: wake_on_lan.send_magic_packet
      data:
        mac: "<your tv's MAC>"

This is not the issue. The issue specifically states “when set up via the UI”. Secondly, this workaround brings about another bug where home assistant will keep discovering views TVs when set up via the yaml with no way to ignore the discovery.

dxmnkd316 commented 10 hours ago

issue specifically states “when set up via the UI”. Secondly, this workaround brings about another bug where home assistant will keep discovering views TVs when set up via the yaml with no way to ignore the disc

Yeah, I have that issue too. I just ignore it mentally. It's better to have a mildly annoying flag than not have functionality IMO. But your mileage may vary.

The bug had been opened for a year and a half. The workaround I posted will get you WOL capability. There was a separate issue for resolving the second device that gets discovered and is unable to be ignored, but it went stale earlier this year (https://github.com/home-assistant/core/issues/50231)

home-assistant / core