When testing out new components, or preparing an automation, I often test the service calls (actions) in the handy developer tools UI first. However, many times, the action does not work, and there is no simple way to figure out why. In fact, the UI makes it seem like it did work, by giving a green check mark icon that the call was executed (even if it immediately failed).
As an example, I have been trying to figure out how to play media via an automation on a smart speaker. My thought was to use media_extractor.play_media and pass the URL, but this hasn’t been working. There is no feedback whatsoever showing that there was a problem, other than me waiting, and not hearing anything. If I go to the logs, however, I see errors related to the failures.
It would be amazing if the relevant logs printed to a terminal in the developer tools actions UI, so I could see right away what was going on.