Configuration not found

Hello everyone,
I am trying to integrate the add-on MQTT Siemens S7 Connector and fail to load the configuration.
I have already tried the configuration in the following folders:

/homeassistant/addon_configs/xxxxxxxx_mqtt-s7-connector/config.yaml
/homeassistant/config.yaml
/homeassistant/config_files/config.yaml
/homeassistant/configfiles/config.yaml
/homeassistant/config/config.yaml

I always get an error that the configuration is not found.

What am I doing wrong here?

Please find attached the complete error message.


Add-on: MQTT Siemens S7 Connector

MQTT Siemens S7 connector to integrate Siemens PLC’s with Home Assistant


Add-on version: 1.0.8

You are running the latest version of this add-on.

System: Home Assistant OS 14.2 (amd64 / generic-x86-64)

Home Assistant Core: 2025.3.0

Home Assistant Supervisor: 2025.03.2


s6-rc: info: service base-addon-banner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service base-addon-log-level: starting

s6-rc: info: service fix-attrs successfully started

Log level is set to WARNING

s6-rc: info: service base-addon-log-level successfully started

s6-rc: info: service legacy-cont-init: starting

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service init: starting

s6-rc: info: service init successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

[email protected] start

node index.js --addonversion 1.0.8 --config /config/config.yaml --loglevel=4

INIT ## log level is set to: 4

2025-3-8 9:13:57 ## ERROR ## Config file ‘/config/config.yaml’ not found

/usr/src/mqtt-s7-connector/service_functions.js:57

throw new Error(msg);

^

Error: Config file ‘/config/config.yaml’ not found

at Object.error (/usr/src/mqtt-s7-connector/service_functions.js:57:9)

at Object.config (/usr/src/mqtt-s7-connector/config_handler.js:40:20)

at Object. (/usr/src/mqtt-s7-connector/index.js:12:31)

at Module._compile (node:internal/modules/cjs/loader:1550:14)

at Object…js (node:internal/modules/cjs/loader:1702:10)

at Module.load (node:internal/modules/cjs/loader:1307:32)

at Function._load (node:internal/modules/cjs/loader:1121:12)

at TracingChannel.traceSync (node:diagnostics_channel:322:14)

at wrapModuleLoad (node:internal/modules/cjs/loader:219:24)

at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)

Node.js v23.2.0

s6-rc: info: service legacy-services: stopping

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service init: stopping

s6-rc: info: service mqtt-s7-connector: stopping

s6-rc: info: service init successfully stopped

s6-rc: info: service legacy-cont-init: stopping

s6-rc: info: service mqtt-s7-connector successfully stopped

s6-rc: info: service legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service base-addon-log-level: stopping

s6-rc: info: service fix-attrs successfully stopped

s6-rc: info: service base-addon-log-level successfully stopped

s6-rc: info: service base-addon-banner: stopping

s6-rc: info: service base-addon-banner successfully stopped

s6-rc: info: service s6rc-oneshot-runner: stopping

s6-rc: info: service s6rc-oneshot-runner successfully stopped

I have no clue about this integration but if this is how you reference files in it it is wrong. The file you want is configuration.yaml, not config.yaml.

Hello MIngo,
Welcome to the HA forum!

I would contact the Add-on’s author in the place you got the software from.
Some years ago now HA did some folder structure changes concerning /config and /homeassistant. Your software’s author may not have caught up to that yet. I would check there for a work around.

This might I suspect be a file that is specific to this software that the install person needs to make? Would have to look in the repo.

Add-ons doing stuff with the configuration.yaml would be out of the norm.

1 Like

Hello,
thx for your answers.
I solved the problem.

Root cause was - my file editor.

With this setting I am able to find the right directory.

Enforce Basepath
If set to true, access is limited to files within the /config directory.