Configuration invalid after modifying Zoneminder in configuration.yaml

Configuration
,
1

I have recently done some changes to my zoneminder software which needed to be reflected in my HA configuration file, however this has caused HA to start into safe mode.

ERROR (MainThread) [homeassistant.bootstrap] Failed to parse configuration.yaml: in "/config/configuration.yaml", line 28, column 14: Unable to read file /config/customize.yamlyaml.. Activating safe mode

My configuration is as follows:

# Loads default set of integrations. Do not remove.
default_config: ~

wake_on_lan: ~

# Text to speech
tts:
  - platform: google_translate

http:
  server_port: 8563

zoneminder:
  - host: 192.168.1.105:8095
    path: /
    path_zms: /cgi-bin/nph-zms
    username: WoahUsername
    password: WoahPassword

camera:
  - platform: zoneminder

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
homeassistant:
  customize: !include customize.yaml

When I initally updated the configuration and restarted HA, the end of the configuration file was updated:

homeassistant:
  customize: !include customize.yamlyaml

I first tried fixing this by simply correcting this line, and then uploading the configuration back to the server. Despite this, restarting HA or running the configuration test messes up the configuration again, putting HA back into safemode.

I am running HA in a docker container.

2

So, what error message are you getting now? Given you say you’ve fixed the one you’ve posted.

What does the ~ mean after default_config, I’ve not seen that before?

3

I once fixed the file yes, but if i restart HA or run the config tester in the developer settings, the config file goes back to its broken state preventing it from starting. As for the ~, I had some issues previously with the yaml which stopped HA from starting whenever i tried to add anything to the config (at the time i was trying to change the port), after running it through a “YAML Beautifier” it added ~ and fixed it, without this HA did not start. As for its functionality in YAML, I have no idea, all i know is it works.

4

I’m a bit confused, you say you’ve fixed the yamlyaml thing but it comes back? What editor are you using, is it saving?

5

Okay, I figured out the problem, turns out it was absolutely nothing to do with Home Assistant, or my editor.

I use Portainer to manage my docker instances across two servers, for some reason using Portainer to upload files into the volume appended to the end of the file, but only this one time, which is super strange. Regardless, thanks for your time eggman :slight_smile: