API error message connecting to mqtt when starting

[PauloGoncalves86]

I am using the mqtt distributed with home assistant, I see the following error in the debug log:
[16:25:43] ERROR: Got unexpected response from the API: Service not enabled

`/package/admin/s6-overlay/libexec/preinit: info: container permissions: uid=0 (root), euid=0, gid=0 (root), egid=0
/package/admin/s6-overlay/libexec/preinit: info: /run permissions: uid=0 (root), gid=0 (root), perms=oxorgxgruxuwur
/run/s6/basedir/scripts/rc.init: info: hook /etc/s6-overlay/scripts/enable-check.sh exited 0
/run/s6/basedir/scripts/rc.init: warning: defining user bundles in /etc/s6-overlay/s6-rc.d is deprecated, please define them in /etc/s6-overlay/user-bundles.d instead
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service base-addon-banner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started

App: Advanced SSH & Web Terminal
A supercharged SSH & Web Terminal access to your Home Assistant instance

App version: 24.1.3
You are running the latest version of this app.
System: Home Assistant OS 18.2 (amd64 / generic-x86-64)
Home Assistant Core: 2026.9.1
Home Assistant Supervisor: 2026.08.0

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs successfully started
Log level is set to DEBUG
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service init-ssh: starting
s6-rc: info: service init-mysql: starting
s6-rc: info: service init-mosquitto: starting
s6-rc: info: service init-docker: starting
s6-rc: info: service legacy-cont-init successfully started
[16:25:42] DEBUG: Requested API resource: http://supervisor/services/mqtt
[16:25:42] DEBUG: Request method: GET
[16:25:42] DEBUG: API HTTP Response code: 200
[16:25:42] DEBUG: API Response: {"result":"ok","data":{"host":"core-mosquitto","port":1883,"ssl":false,"protocol":"3.1.1","username":"addons","password":"sha0aeLei...","addon":"core_mosquitto"}}
[16:25:42] DEBUG: Requested API resource: http://supervisor/services/mysql
[16:25:42] DEBUG: Request method: GET
[16:25:42] DEBUG: API HTTP Response code: 400
[16:25:42] DEBUG: API Response: {"result":"error","message":"Service not enabled"}
[16:25:43] DEBUG: Requested API resource: http://supervisor/services/mqtt
[16:25:43] DEBUG: Request method: GET
[16:25:43] DEBUG: API HTTP Response code: 200
[16:25:43] ERROR: Got unexpected response from the API: Service not enabled
[16:25:43] DEBUG: API Response: {"result":"ok","data":{"host":"core-mosquitto","port":1883,"ssl":false,"protocol":"3.1.1","username":"addons","password":"sha0aeLei..,"addon":"core_mosquitto"}}
s6-rc: info: service init-mysql successfully started

`

[frenck]

Thanks for the report. The good news: this is cosmetic, nothing is broken.

The line is not about MQTT. Your debug log shows the MQTT lookup returns 200 with the broker details, and the mosquitto_* clients are configured from that. The Service not enabled error comes from the MySQL lookup right next to it (/services/mysql returns 400), because you have no MariaDB app installed. The app checks whether a MySQL service is available and skips the configuration when it is not, which is exactly what happens here.

The noise comes from bashio (the helper library used by the app): bashio::services.available is supposed to do that check quietly, but its error logging bypasses the redirect it uses to stay silent, so the "not enabled" answer ends up in the log as an error. The fix for that belongs in bashio, so this app will pick it up through the next base image update.

Until then you can safely ignore that line.

../Frenck

                       

Blogging my personal ramblings at frenck.dev