#Can't define REST command?

1 messages · Page 1 of 1 (latest)

vernal wraith
#

I'm working on setting up an emergency camera record system for my sister between HA and Frigate. End goal is 'hit a button in HA, Frigate pulls it's record buffer and records all cameras until the button is pressed again'. Buffer is right in Frigate, but when I try to add the rest command in configuration.yaml, I get Error: Action rest_command.frigate_manual_event_start not found in the automation trace. Sure enough, can't find the command anywhere in HA, but it appears to be defined correctly in config (and lints properly)

default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 192.168.254.100
ffmpeg:

rest_command:
  frigate_manual_event_start:
    url: "http://10.0.0.95:5000/api/{{ camera }}/start"
    method: POST
  frigate_manual_event_end:
    url: "http://10.0.0.95:5000/api/{{ camera }}/end"
    method: POST```
hard gulch
#

Did you check the config in HA and restart HA?

vernal wraith
#

Keeps passing, and I've done multiple restarts from inside HA as well as at the container level (docker version)

#

the only real errors in the logs are about opower, which i know will be fixed next week in the new stable release (power company changed the api)

hard gulch
#

I just copied and pasted exactly that block into my configuration.yaml and it worked fine:

#

after restarting HA

vernal wraith
#

let me restart the whole server then. that's strange

hard gulch
#

If not, it probably means you have an issue elsewhere in your config

vernal wraith
#

I am -so- confused. I also just pulled the logs and zero reference to 'rest'. As far as an issue elsewhere in my config, that's the entire config I posted.

hard gulch
#

No idea. You're probably modifying the wrong configuration.yaml or something

vernal wraith
#

I'm trying to put it in my personal HA instance to see what happens (though the commands won't work)

hard gulch
#

Or you didn't map the config dir properly

#

Put a typo in there and check the config

vernal wraith
#

uhhh ... give me a minute

#

sighs you called it. I made a screwup when I built out this server, and had two copies of HA on the disk, /homeassistant and /docker-homeassistant ... I was editing the wrong one