Over the last decade there has been some really great software products that have been shut down with little to no warning. This is getting so common that someone created a website called Killed by Google. After Google shutdown Reader in 2013, I spent months trying to find a replacement. During this research I determined I should try to find solutions to services I use everyday that wouldn’t be shut down in some board room over profit margins.

This post is going to cover normalizing all media_player volume levels with Home Assistant and Node-RED. If you haven’t already, I’d recommend reading my previous blog post on sending Text-to-Speech notifications which dives a bit deeper on the optional accessibility Subflow this Flow consumes.

Have you ever wanted to send Text-to-Speech (TTS) notifications with Home Assistant and Node-RED? In the sections below I’m going to be using Amazon Alexa Media Player Integration to send TTS notifications. Please note you can easily switch out the TTS integration to the one of your choosing and still use this Subflow (with a few tweaks).

I define accessibility as a critical necessity to be inclusive to everyone. No matter how big or small the task, anyone should be able complete the task at hand regardless of the disability (e.g., vision, hearing, mobility, device access, language, etc).