My point is more that I don’t think Home Assistant controls these files, so there’s not a lot they can do to fix this. I’ve looked a bit more into this, and Docker indeed blocks off access to these files.

Home Assistant Core (the one doing basically no installation other than a virtual environment) certainly won’t affect the kernel like this. If you’re using a python virtualenv, your problem lies with the OS you’re running. That said, what they call “core” and what users call “core” seem to be two very different things.

If the Docker based Home Assistant installs have been providing access to these files, they’ve overridden the explicit choices of the Docker people themselves, which seems rather risky. There’s an issue upstream with a suggestion (“just turn off all protection Docker offers” basically) but the Docker team hasn’t allowed access to these files for almost two years now.

Perhaps it’s only happening now because you updated Docker recently?

If you’re not using Docker, you should check with the upstream Linux distro to see why you can’t access the devicetree information.

If you are using Docker, you could consider asking the home assistant people to put back whatever hack they used to expose this information, or perhaps they could instruct you with how to apply this hack yourself. Currently, Docker explicitly hides these files, though, so to get this information you’ll have to fight the underlying software.