this post was submitted on 13 Jun 2025
15 points (100.0% liked)
homeassistant
14807 readers
28 users here now
Home Assistant is open source home automation that puts local control and privacy first.
Powered by a worldwide community of tinkerers and DIY enthusiasts.
Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation
Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @GreatAlbatross@feddit.uk
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
HA has a "www" folder that by default that is accessible to the network. Anything in /config/www appears at http://yourhassaddress:8123/local, so your images will be at http://homeassistant.local:8123/local/image.jpg
Aha, that was what I was after, big thanks!
So, after a bit of meddling:
The location I was placing things in was media>my media (from the HA UI).
Assets there are stored in /media, and served in 8123/media/local, but require an autoSig.
Changing permissions doesn't affect the availability, no sig is a 401 error.
However, if the file is copied from /media to /config/www/ , it's then served (as you said) under 8123/local.
Brill, not too painful a process for a few static images (or indeed if I'm feeling brave, I could just symlink the folders).
Maybe one day there will be a way to upload background images for picture elements cards from the UI :)
If you're using HAOS (ie not running in docker), there is an official add-on called "File Editor" that allows you to edit the config.yaml and upload files from the UI. It's not perfect but gets the job done.
That's a very good shout, as it'll save me mucking about in bash.