Configuration suddenly broke due to an existing script?

@FaceBush wrote:

Hello all!

I am new to the Home Assistant game so I am learning as I go. I created a script a couple days ago and it was working as expected and I was getting no configuration errors. Then suddenly my configuration keeps giving me the following error:

"Invalid config for [script]: [action] is an invalid option for [script]. Check: script->script->1583173228512->action. (See /config/configuration.yaml, line 21). "

I am trying to have a script that toggles the mute on and off of a media player.

I did upgrade Home Assistant version and HassOS version when they appeared on the console. I have tried rolling back to 0.105.5 but the issue persists.

Here is my scripts.yaml config

'1583173228512':
  alias: 'Family Room Mute Toggle'
  sequence:
  action: call-service
  data_template:
    is_volume_muted: '{{ not state_attr(''media_player.family_room'', ''is_volume_muted'') }}'
    entity_id: media_player.family_room
    service: media_player.volume_mute 

Here is my main configuration.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

#Uncomment this if you are using SSL/TLS, running in Docker container, etc.
#http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

##Discovery##
discovery:

##Speedtest##
speedtestdotnet:

group: !include groups.yaml
automation: !include automations.yaml
scene: !include scenes.yaml
sensor: !include sensors.yaml
script: !include scripts.yaml

I have been reading through the forums and have worked through multiple issues that way but this one is stumping me. Mostly cause it worked fine for a day or 2 before it suddenly stopped.

Thanks so much for everyone’s help!

Posts: 4

Participants: 3

Read full topic