Mqtt Broker complains it can find a file and folder that are there according to file explorer

[15:58:42] INFO: Starting mosquitto MQTT broker…
1749337122: Error: Unable to open include_dir ‘/share/mosquitto’.
1749337122: Error found at /etc/mosquitto/mosquitto.conf:43.
[22:58:42] WARNING: Halt add-on

But I swear it’s there. What next?

What type of Home Assistant are you running?

Installation Methods
&

/etc is not a place that HAOS can usually find, so unless we know the answer to my question, we have no idea…

HOAS on RPi 4.

It appears I am having a similar problem with another addon. ZHA is giving me a ‘can’t find that’ error in config folder. Is there a folder permissions setting area somewhere that needs turned on?

Any feedback here? Do I need to post more details?

I am new to HA and coming over from Hubitat with 5+ years of home automation experience.

I am seeing very strange things in the File Editor add-on. It doesn’t seem to save a file rename (although it give you the indication it has). Also as mentioned I am getting errors that files I know are there are not accessible. It seems I may have missed some permissions step in setup?

Again I am install on HAOS on a Raspberry Pi.

This issues have me stopped in my tracks for my setup, and are starting to get very frustrating. Any help out there?

Should I be using a different file editor? What am I missing?

Seems something went wrong with the initial flash. Ha should have access to /share

Maybe make a backup and flash again ?

The /etc is the /etc of the mosquitto container, which is normally mapped to /share. But /share seems inaccessible.

Flash again. Does that mean reinstall HOAS? I’m not intimidated by that, just want to confirm that is what is intended. I’ve had several weird problems - perhaps that would help other areas too?

Yes, make a backup, and flash HA OS again, then restore your backup.

As an update I haven’t had a chance for a reboot yet, but will get back to this project soon. I also plan a similar install on my other HA install to see if it’s an issue with my approach. Thanks for the comments thus far.