Can't open config file at null/configuration.yaml startup error

[Koenkk]

Description of the issue

The HA addon fails with an error on startup: can't open config file at null/configuration.yaml. This probably occurs due to a s6 bug: just-containers/s6-overlay#477

Since there are many different issues about this same problem and some are already closed I created this one.

I want to let you know I'm working on a fix so no need for "me too" responses.

Addon version

v1.27.2-1

Platform

Applies to all HA versions

Logs of the issue (if applicable)

No response

[Koenkk]

@ all; please check if this issue is fixed in the latest edge addon.

[oNSXo]

Looks good @Koenkk , thanks!

[stu1811]

@Koenkk So far so good

[mariokil]

So far so good. System works since 20 hours. No bugs

[Koenkk]

Great to hear, lets wait for some more confirms/days and then this can be closed.

[leenemo]

@ all; please check if this issue is fixed in the latest edge addon.

I stoped the mqtt sever and zigbee2mqtt sever,when the ha start. I fixed it.
But I don’t think it’s a good method. You mention the last add on. I can’t find it. Is it z2m?or ha?

[Koenkk]

z2m edge version, however the fix will also be included in the next z2m release on 1 October

[stu1811]

@Koenkk I haven't had any issues since using the latest edge. Uptime on container is 3 days. 🥳

[leenemo]

z2m edge version, however the fix will also be included in the next z2m release on 1 October
I find that if the yaml channel is different from the adapter channel ,the z2m can’t start up.

[Koenkk]

@leenemo that is expected behavior. Changing the channel requires repairing all devices, as a safety mechanism users have to delete the data/coordinator_backup.json file first. This is also stated in the error that can be seen in the z2m log.

[mariokil]

Hi, after few days z2m edge has stopped working.
No updates since z2m edge installation. After manually starting z2m edge situation repeat again and again

Zigbee2MQTT:info 2022-10-04 03:32:46: Zigbee: disabling joining new devices.
Zigbee2MQTT:info 2022-10-04 03:32:47: Connecting to MQTT server at mqtt://192.168.100.8:1883
Zigbee2MQTT:error 2022-10-04 03:32:47: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2022-10-04 03:32:47: MQTT failed to connect, exiting...
Zigbee2MQTT:info 2022-10-04 03:32:47: Stopping zigbee-herdsman...
Zigbee2MQTT:info 2022-10-04 03:32:47: Stopped zigbee-herdsman

[auanasgheps]

This problem is not relevant to this issue, but to your MQTT broker.

[mariokil]

This problem is not relevant to this issue, but to your MQTT broker.

Yes indeed. MQTT broker restart has been solved problem.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days