Google won't recognize "start Earplay" command
There are a few known reasons your Google Home or Google Assistant device may be having trouble recognizing the "start Earplay" command.
- Make sure to enunciate the "Ear" in "Earplay" - Google's voice training is more likely than Alexa's to misinterpret "earplay" as "airplay."
- Try different invocation words, such as "begin Earplay," "launch Earplay," or "talk to Earplay."
- Check the language settings in your Google Home or Assistant application. Google's API for third-party actions like Earplay only works in certain language regions, and switching your settings to one of them should allow Earplay to work as intended.
- US & Outlying Territories (en-US)
- United Kingdom (en-GB)z