#Error executing `media_player.turn_off` since upgrade to 2025.02

1 messages · Page 1 of 1 (latest)

merry imp
#

Since upgrading, a script that has been working fine for years has now stopped working because one of the steps throws an error and the script aborts.

The step code in the script is:

data: {}
target:
  entity_id: media_player.lounge_tv
action: media_player.turn_off

and the error received is:

Error: Error calling async_turn_off for device [LG] webOS TV SJ800V: Device is off and cannot be controlled

This has worked fine for some years until this recent upgrade and the script has executed whether the TV was already off or whether it was on (and therefore got turned off).

The script also turns another TV off in the same way and this is not throwing the same error, so it could be integration specific (webostv)

Any ideas?

wanton flame
#

does setting continue_on_error: true help?

merry imp
#

will try, one sec (nevere used that before!)

wanton flame
#

you could maybe also just put that in a condition that the tv is not already off.

merry imp
#

yeah, continue_on_error fixed it, thanks! Wonder why that has only just happened though 🤔

wanton flame
#

maybe just changes/improvements to the error handling in the integration

merry imp
#

maybe, but the inconsistency is not great and will lead to a lot of confusion if this is the reason.

This is called via a media_player service and all other media players (including another TV) do not exhibit this behaviour