Stefan Agner

What you can do instead is creating a local add-on, and have the long running tasks be part of the Dockerfile. The build does not have a timeout, and a...

> In my opinion this is something that should be fixed on the add-on side anyway. Even though the MAC was more stable in older Docker versions, it was never...

@fish12345 you need to have the json file in place when the Matter Server starts (the json files are only parsed on startup). You may need to use `--ota-provider-dir` to...

@3oris (and others) when the device go unavailable, does reloading the integration helps? Settings -> Devices & services -> Matter -> Three dot menu -> Reload. What Home Assistant OS...

> Resetting my HomeAssistant VM to a previous state fixed the problem for me. > Know I see the nodes again. Running version `6.4.1` now. If you do a regular...

> @agners -- So, it happened again, I restarted the _integration_ , devices came back very very slowly. And only a few minutes after they were all back, they all...

Hm, afaik this model should be supported by #3628. @darkxst thoughts?

> @agners: what are your thoughts on this? should match the new strings with the caveat it will also match ZBDongle-P? Hm, definitly not ideal UX I guess :cry: Ideally...

The reason for this behavior is that the add-on stores the certificate in its internal config directory (in `/data`). You could uninstall and reinstall the add-on to clear this data...

Hm, this confirms what I suspected in https://github.com/home-assistant/core/issues/123086#issuecomment-2268656315: There is an underlying problem in your setup which prevents updates. Since this time it's really another vendor (Eve) gives an important...