Core: Conversation component - Wrong configuration

[andyinno]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version): 0.50

Python release (python3 --version): hass.io default version

Component/platform: Conversation

Description of problem:
Copy and paste the example in the documentation

conversation:
boolean_test:
sentence: switch boolean # The phrase it will recognize
action:
service: input_boolean.toggle

gives

ERROR (MainThread) [homeassistant.config] Invalid config for [conversation]: [boolean_test] is an invalid option for [conversation]. Check: conversation->conversation-boolean_test. (See /config/configuration.yaml, line 37). Please check the docs at https://home-assistant.io/components/conversation/
2017-07-30 22:48:14 ERROR (MainThread) [homeassistant.setup] Setup failed for conversation: Invalid config.

Failed config
conversation:
boolean_test: [source /config/configuration.yaml:38]
action: [source /config/configuration.yaml:40]
service: input_boolean.toggle
sentence: switch boolean

Expected:

To not see any error message in the log and the new command available in the html page.
I don't know if the new changes in this plugin invalidated this config. In this case I would like to expect to not see a legacy example in the documentation

Problem-relevant configuration.yaml entries and steps to reproduce:

1. Add the example in the documentation to configuration.yaml
2. check the log for the presence of the error

Traceback (if applicable):

 ERROR (MainThread) [homeassistant.config] Invalid config for [conversation]: [boolean_test] is an invalid option for [conversation]. Check: conversation->conversation->boolean_test. (See /config/configuration.yaml, line 37). Please check the docs at https://home-assistant.io/components/conversation/
2017-07-30 22:48:14 ERROR (MainThread) [homeassistant.setup] Setup failed for conversation: Invalid config.


Failed config
  conversation: 
    boolean_test: [source /config/configuration.yaml:38]
      action: [source /config/configuration.yaml:40]
        service: input_boolean.toggle
      sentence: switch boolean

  General Errors: 
    - Setup failed for conversation: Invalid config.

Additional info:

[kmdm]

(I got a similar-ish error for one of my automations that loaded fine in 0.48 but not in 0.50)

[MartinHjelmare]

There was a breaking change for conversation component in the last release:
https://home-assistant.io/blog/2017/07/29/release-50/#breaking-changes

The docs are not all updated yet, it seems.

[andyinno]

Yes, I read the breaking change too.
I just wanted to point out that there is a difference between the documentation and the code. Nothing else.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[Vanuan]

Have this error on Hassbian. What is a new config?

[muspelheim]

@Vanuan same here

[Vanuan]

@muspelheim
I've figured it out:

intent_script:
  TellTime:
    speech:
      text: "Current local time is {{now().hour}}:{{now().minute}}"
    action:
      service: tts.google_say
      data_template:
        message: "Current local time is {{now().hour}}:{{now().minute}}"
        cache: false

conversation:
  intents:
    TellTime:
      - What time is it

Documentation for intents here:
https://home-assistant.io/components/intent_script/

For conversation it's still not up to date:
https://home-assistant.io/components/conversation/

You might want to edit it here:
https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_components/conversation.markdown

[tschmidty69]

@Vanuan can you submit a pull request on the documentation tree? Or spell out exactly what should be change in the doc to make it work. FWIW, I am not sure the last line of your config is valid since it is not defining a variable to be passed tto the intent so looks like just an orphan there.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍