I recently recreated my HASS setup on a new pi 3b+ so I could keep the old pi up while setting it up, and utilize all of the newer stuff available, and clean out some old clutter. Everything has gone VERY smooth so far except playing local mp3’s that some of my automation’s use. If I plug the old pi back in, they still function as they should. not sure what is going on, any help would be greatly appreciated. Below is an example of one of the service data I have been using. It runs the service through one of the various google homes I have installed throughout the house. The local files are simple things like “the garage is open” etc, which does not warrant calling a TTS each time. This script gets called at 6:15am as a general wakeup call during the weekdays. All of the files are in the www folder, nothing has changed from one pi to the other. Any ideas? I should say, the previous pi was running hassio version .83, this new pi is running the most current version.
I have tried several iterations to point to the file to no avail. I have tried “/local/wakup.mp3” “IP address/wakup.mp3” “www/wakeup.mp3” etc.
At the moment I have the important ones making TTS calls again, to ensure that I get the information, but I would like them to switch back to using local files if possible. I do have one automation that plays a very viscous dog bark when the nest hello detects a person approaching the door (sudo alarm system lol) that would be nice to get back up and running.
I should add, all of my other calls for local files mainly picture files works well, and there are no issues with that when setting up my lovelace interface.
{
“entity_id”: “media_player.living_room_audio”,
“media_content_id”: “https://myaddresshere.duckdns.org/local/wakeup.mp3”,
“media_content_type”: “audio/mp3”
}