#Custom sentence automation not returning conversation response

1 messages · Page 1 of 1 (latest)

nocturne helm
#

Hi all! I have been working on a custom automation to return the current weather of an arbitrary location from an assist device. I have gotten the automation to work correctly, though the assist pipeline does not respond with the converstation response and instead fails.

The automation uses these two rest commands:

  get_lat_long_of_place:
    headers:
      user-agent: HASSgeoencode/1.0
    url: https://nominatim.openstreetmap.org/search?q={{ place }}&format=json

  get_forecast_of_place:
    headers:
      user-agent: HASSsingleShotForecast/1.0
    url: https://api.met.no/weatherapi/locationforecast/2.0/complete?lat={{ lat }}&lon={{ lon }}```

When I activate the automation with assist, it looks like the automation is not working. However, when reviewing the trace of the automation, the conversation response is set and appears to be correct. The raw pipeline debug and the automation trace would be too long to post inline, so they I added them as files here.

I have a few other custom sentences that work correctly and are setup the same way as this one, so I am not sure if this is a bug or if I am doing something wrong. I have also included the raw yaml of the automation if that helps too! Please let me know if I need to include any other information.
knotty fiber
#

Very weird. I wonder where the "Unable to get forecast for ..." comes from. Looks like it interferes with another non-internal intent. It can't be an internal intent as none of them responds with "Unable to...". To further debug this I would try and define an additional pseudo sentence trigger in your automation that is definitely unique.

`yaml

  • trigger: conversation
    command:
    • advertising kidney {place}
      `

And then try "advertising kidney new york" in Assist debug.

nocturne helm
#

Ahh

#

I had this blueprint automation enabled:

#

I did not realize that two seperate assist automations could be triggered at once

#

Thank you for the help!

knotty fiber
#

Cool, glad you found the cause.