On this [1] thread a discussion came up about running Home Assistant on Linux. I think that discussion is off topic there, so I copied and pasted the parts of the discussion about Arch Linux below, so we can discuss it further in this thread.
_dev_null:
I suggest you learn Arch, learn about Linux users and groups, post this issue on the arch support forum surely someone will help… I’ve heard their community is not completely full of egotistic ****s someone may help you
Sir_Goodenough (SG) WhatAreWeFixing.TodayGuidance Counsellor:
Also arch isn’t really a supported OS for anything HA I don’t think. So we can’t be of much help to you anyways, you appear to be in
territory.
_dev_null/dev /null:
Out of curiosity, why did you choose Arch ?
Of all the linux distros I’ve used since the 90s it’s the most bas*****d version ever. Being built on Linux imho is an insult to us and the linux name. It’s unnecessarily more difficult and easier to break.
Yes it’s a delight for power users but not exactly newbie friendly … It’s like the Arch creator wanted something to keep him on the edge like a red hot poker stick up his anus 
nickroutSolution Institution:
IMHO arch is great. Pretty much the best documentation out there. I have lost count of the time I have googled how to do something in Linux, and ended on the arch docs.
Yes the documentation has to be good as one wrong turn on Arch and you’ll screw it all up 
Also the docs are good but what happens is that Joe Bloggs ends up copying and pasting it all in without learning or understanding exactly what their doing.
Sorry, thread derailed.
In typical Arch fashion let’s throw out some commands for one to follow
sudo useradd -G uucp hass
sudo systemctl restart home-assistant
Not sure what it does but may help 
The discussion seems to derail into something entirely non HA related. The original thread was TLDR, but I did get that Home Assistant was installed on an unsupported platform. It is specifically stated that by doing so you are on your own to fix problem. Yet sound advices are given.
But there are two things wrong with the question in the previous thread:
- It expects HA to build code to help people fix problems on unsupported sysytems. It won’t happen: that is what unsupported means. The cause of the trouble was not even in HA but in the unsupported OS.
- The question expects HA to understand why things fail. If you cannot connect to something, how on earth would one get the cause? HA tries, nothing happens. HA would have to build a OS troubleshooter, that would need way more permissions (than the permission that was apparently missing) to do an analysis that would be able to figure out permissions were missing. And then a troubleshooter-troubleshooter to explain troubleshooting permissions are missing.
TLDR: can’t and won’t. So since HA is not spending time on making things work on Arch, the Arch forums are indeed your best bet. But expect things to fail more often in the future.
“Out of curiosity, why did you choose Arch?”
I first tried to run Home Automation on my raspberry pi 3B using this [1 ]tutorial, but my PI kept resetting when the CPU load went above a certain point. I suspect my USB power supply was not strong enough. So I ordered a better solution for that.
Next I saw there’s also an image and a tutorial for Generic x86-64 [2], but I didn’t want to overwrite the existing Arch linux installation on that PC, and I found it a bit too much work to put a spare HD in that machine. So I gave up on that plan.
Next I saw there’s a Home Assistant entry in the Arch linux Wiki, and followed those steps. After some problems [3] this resulted in a functional Home automation installation.
[1] Raspberry Pi - Home Assistant
[2] Generic x86-64 - Home Assistant
[3] SOLVED home-assistant restarting: /var/lib/hass/.venv/bin/hass': / System Administration / Arch Linux Forums
“HA tries, nothing happens.” → That’s not what happens. HA tries, and then gets the message from the kernel “Hey, you are not allowed to read/write there”.
Then HA hides that error message from the user. The feature request is to no longer hide that error message.