I created a link to my NAS box via the storage function. This worked great. All my directories show up under “My Media”. When I click on a media file, nothing, the name of the track shows with a spinning circle.
To make things more confusing, I am able to go into terminal and cp these same files to /media. The same files play fine from /media.
Any ideas/suggestions?
Which NAS and which storage share type are you using?
The NAS box is a TruNAS I do believe. I am using a Samba share.
As mentioned I can see the files, and in terminal I can copy the files. I just can not play them in Media. Is there a length limit to the absolute file name? With tree structure mine are rather long. Which still would not explain why the name shows up in Media with the revolving circle.
If you would like me to perform any test I would be more than happy to do that!!!
Greg
Some more testing and results.
When I copy the MP3 files to the root of the NAS share “/media/Music” I can play them.
When I copy them into the directory below that “/media/Music/#Dance” I can NOT play them.
When I copy them into the directory below that “/media/Music/Test” I CAN play them.
The only difference is the length of the subdirectory, 6 vs 4 char, and a # at the beginning of the one I can not play.
The MP3 files are the same in all cases.
Greg
That # is probably messing something up with SMB, or HA. I wouldn’t recommend using special characters with HA/SMB at all.
With that said: I personally would try NFS before renaming anything, it is way better for stuff like this.
in TrueNAS, go to Shares, click Add on the UNIX share box. In the popup TrueNAS menu, pick your music path, then add the Home Assistant IP address to the “Hosts” picker (single IP, e.g 192.168.20.5). Then click Advanced Options, and set both Mapall User and Mapall Group to a user with permissions to at least read the music share. Then just hit save.
Note the exact path TrueNAS is advertising (this will be the exact path on the TrueNAS host. e.g /mnt/tank/Music) and in HA Network Storage, add an NFS server with the exact path you just noted. No authentication needed because NFS goes by client IP.
Test and see if that works. If that’s not it, it may be Home Assistant doing something weird with the folder name.
OK will try using an NSF share out. I am using the special Char for a particular reason so not that easy to change it…
Looks like that was the issue. Even with an NSF share if the folder start with a # Media wont play. Oddly enough starting with a ^ appears to work just fine.
Thanks for the help!! Now just to fix 100,000 MP3 files 
OH Joy.
Greg
You’re welcome! Sad that it does not work…
But before you go through all of the renaming/tagging saga, you could try reporting a bug at Issues · home-assistant/core · GitHub.
You could in the meantime create a symlink or something, if HA will traverse it.
I’ll also test my setup to see if we have the same behavior.
@GregoryWest It is a bug in Home Assistant. I did some testing on my install, same failure.
#s in URLS are usually instructions for the browser which are never sent to HTTP servers, so your browser sees the request for #<whatever> and discards it.
I sent in the bug report. If nothing else MM can tell people the # is an issue. In the mean time I am updating my files. Mostly just batch jobs, but does take time. I am chopping at the bit to work on the voice control of my media 
Greg
Great, thanks! I subscribed to the issue on GitHub.