m50/ha-fallback-conversation

Issues

• "Not any" can sometimes be a valid answer

  #27 opened a month ago by jeffc
  2

• [Feature request] Add triggers/hooks/logic

  #24 opened a month ago by shaiger
  1

• broken in 2024.08?

  #26 opened 4 months ago by docNeptun
  14

• Its not working :(

  #25 opened 5 months ago by kuligs2
  1

• When use Google GenAI as primary agent, never have case falls back to 2nd agent.

  #23 opened 6 months ago by itispip
  1

• Make Conversation ID carry on

  #22 opened 6 months ago by itispip
  1

• Python error still Present?

  #17 opened 6 months ago by styphonthal
  19

• Home Assistant responded with: Not any

  #12 opened 6 months ago by Ricardo-Miguel-Caldeira
  4

• [Feature request] Stealth mode.

  #21 opened 6 months ago by maxi1134
  1

• [Bug] Error when trying to use with HomeLLM and LocalAI integration with Llama3

  #19 opened 6 months ago by maxi1134
  1

• Issues detecting error from built in OpenAI Agent

  #13 opened 6 months ago by m50
  3

• Unexpected error during intent recognition

  #16 opened 6 months ago by IoSonoAndreaZ
  4

• Fallback agent fails due to Python KeyError

  #14 opened 7 months ago by mwhdc
  4

• Google Assistant SDK Not Working

  #1 opened a year ago by guarddog13
  10

• Feature Request (Maybe?) - Voice per Conversation Agent

  #11 opened 8 months ago by mkammes
  1

• Feature Requeset: Google Search

  #9 opened 8 months ago by schniepp
  4

• Breaking change in HA 2024.5 beta

  #6 opened 8 months ago by mwhdc
  3

• error since 2024.5 - Config flow could not be loaded: {"message":"Invalid handler specified"}

  #10 opened 8 months ago by momoz
  2

• Custom sentences are ignored

  #8 opened 8 months ago by cooljimy84
  1

• Use ConversationAgentSelector instead of a custom select

  #2 opened a year ago by t0bst4r
  2