Cannot add anything due to Zwave Automation

Hi,

I’m using HA with a Z-wave USB stick to control my window blinds via Homekit and everything works fine.
I’m using the ‘auto_start: false’ command to wait for the z-wave components to be ready and like I said, it all works fine.

But now I want to add my Sonos speakers to the configuration.yaml file, but whatever I change, not matter where I add some lines, I directly get errors that the config file is not ready and the blinds are not working anymore in Homekit.

Does anyone has a suggestion what goes wrong?
This is my configurations.yaml file:

# 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*

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

#Somfy configuration
somfy:

  • client_id: *
  • client_secret: *

#Spider configuration
spider:

  • username: *
  • password: *

# Homekit config
homekit:

  • auto_start: false*

automation:

    • alias: ‘Start HomeKit’*
  • trigger:*
  •  - platform: event*
    
  •    event_type: zwave.network_ready*
    
  •  - platform: event*
    
  •    event_type: zwave.network_complete*
    
  •  - platform: event*
    
  •    event_type: zwave.network_complete_some_dead*
    
  • action:*
  •  - service: homekit.start*

you’re going to properly format your code before we can help you.

put three back ticks (```) on a line before and after the code above.

Also post the text of the error you are getting (also code block formatted).

You can’t have both in your configuration.yaml.

Move your automation over to the automations.yaml or delete the reference to it in configuration.yaml

…and welcome to the HA forums ! :+1:

Jivesinger,

Thanks for the info…it worked to delete the reference in configurations.yaml, although I still not able to get my sonos speakers in homekit visible, but that’s another problem to be solved…

Thanks for the reply!

I always find it helpful after making changes to config files to hit the ‘Check Configuration’ button before rebooting.
Much easier to sort issues before they stop HA from booting :wink:

Maybe a stupid question, but where can I find that button? The configurator shows a green check mark, so it looks like the configuration file has no errors…

it’s found under the configuration->server controls section. but you have to enable advanced mode under your user before that is visible.

Also I still stand by my advice above even tho in this case the problem was obvious even with the incorrect formatting and lack of error logs. In the future it might not be that way and standard protocol is to post your code correctly by default.