home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.09k stars 31.09k forks source link

Panasonic Viera turn_on_action not working with 2024.8.0 #123484

Closed peteS-UK closed 3 months ago

peteS-UK commented 3 months ago

The problem

The Panasonic Viera integration supports a custom turn_on_action, defined in configuration.yaml, where you can define a service (aka action) call to turn on a tv which requires WOL for example. This worked fine with 2024.7, but doesn't work with 2024.8.

This was previously defined with a service: entry in yaml, which is changed to action: in 2024.8 documention. If you change the yaml to action:, this is ignored by the integration completely. If you leave it as service:, you get the error.

Having deleted the config and re-added with either service: or action: in the yaml the entity is always Unavailable - with 2024.8 it doesn't process the turn_on_action at all

What version of Home Assistant Core has the issue?

core-2024.8.0

What was the last working version of Home Assistant Core?

core-2024.7.4

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

panasonic_viera:
  host: 192.168.3.43
  name: Gym TV
  turn_on_action:
    - service: remote.send_command
      target:
        entity_id: remote.rm_mini_4
      data:
        device: TV
        command: power

Anything in the logs that might be useful for us?

Log entry was that CONFIG[....] had unknown key "service_template" but having deleted and re-added the configuration, the On action isn't available at all in 2024.

Additional information

No response

home-assistant[bot] commented 3 months ago

panasonic_viera documentation panasonic_viera source

peteS-UK commented 3 months ago

After deleting the config, rebooting, adding the config to yaml (with either service: or action:), and rebotting again with the tv turned on, it works again. So, I guess you need to read a new config for the service to action changes perhaps. Anyway, working again, so closing now.