Stefan Agner

> One of the strange things is, that while debugging I can see that sometimes `/dev/mmd_bidcos` cannot be used and sometimes `/dev/mmd_hmip` cannot be used and sometimes the other way...

Right, it needs something which calls `open()` on the device file. `head -n 0` seams to work without reading, and has a proper exit code: ``` $ docker run --rm...

Closing this issue as the main problem of the race condition is addressed by https://github.com/home-assistant/supervisor/pull/3868. There is still a problem with the hot-plug functionality. Unfortunately the new runc device permission...

What kind of Zigbee adapter are you using? Do you use other USB dongles on that system? Did you use device path with `by-id` (see https://www.home-assistant.io/integrations/zha/#configuration---gui).

This very much sounds like a broken SD card 😢

SD cards can fail in weird ways. Often some writes start to fail, while reads still succeed. > There are no errors in the logs hinting at disk failures, Well,...

Linux does not have a guaranteed order of devices, the device names get assigned whatever comes first, and it seems that in your system that ends up to be random...

This change has been on purpose, see https://github.com/home-assistant/operating-system/pull/2116. The reason this folder was writeable is for Docker to store the `key.json` file. This is now redirected to a wrietable directory....

> Perhaps it might be a good idea to build something similar to HA OS with SSH access and a few other changes. Maybe that would bring back some decent...

> It's just that it doesn't make sense to have hardcoded and read-only settings because someone will break their system. Why does that not make sense? It does a lot...