To make log reading easier, highlight them in the message and click the </> button above the comment edit box. It will format the logs better.
BigTalker makes a SmartThings API call to the textToSpeech() function when using a mediaPlayer device. This function causes SmartThings platform to do work in the background and convert a desired text phrase to an mp3 file and then hosts it on their servers. BigTalker gets a URL back from the API call that points to the MP3. BigTalker then sends a request to your device handler using it’s API calls playText(url), playTextAndResume(url), etc telling the devicehandler to communicate with your device and request that it play the mp3 at the given URL. If you’ve configured volumes, these get thrown into the function calls to your device handler as well. The Device Handler is what does the actual communication/control of your device.
(unrelated to your configuration but for the sake of completeness), In the case of speechSynthesis devices, no MP3 is produced and a simple API call to the function speak() is made to the Device Handler with the desired text. The device handler handles sending that text to the device to be converted to spoken audio.
I see in your logs that SmartThings returned the URL https://s3.amazonaws.com/smartapp-media/polly-tts/salli/motion_sensor_is_now_inactive.mp3 . I’ve checked this URL with VLC and it does indeed play.
Are these the complete logs?
I’m not seeing anything happen after getting the “Current Status”, Sound URL, “currentVolume” and “currentTrack” information. I’m not seeing the API call to playText, playTextandResume, or playTextandRestore. It appears to just stop processing.
Have you tried the BigTalker 2.0 development version to see if it will play them? That is where my development and troubleshooting focus is at now. It can run alongside BigTalker 1.1.12, just install it as a different smartapp (don’t overwrite your 1.1.12 code with it).