Repository navigation
Troubleshooting
- Verify the JSON is valid, belongs to the intended service account, and the Text-to-Speech API and billing are enabled for its project.
- Save, wait for the list to reload, select a voice other than the first entry and save again. Reopen settings to check.
- Check Homey notifications and Google's API dashboard for permission, billing or quota errors. Rotate an exposed key instead of sharing it.
- Check that the Url triggered Flow is enabled and its Url token goes to the player's URL argument, or connect the token-returning action directly.
- For cloud audio, confirm the player can reach Homey's local address on port 47333 and accepts MP3 or the selected WAV encoding. Guest networks and network isolation can block it.
- Generate a fresh URL: cached audio is lost after app restart or eviction. For Non-Cloud check the player's internet access and the 200-character limit.
- Test with short plain text. Review Homey notifications and Google's API status if synthesis fails.
The finish wait uses file duration plus device delay, not actual player feedback; adjust the delay for your player. A later speech request on the same device replaces the previous timer. Test SSML and prefix/suffix settings with a short message. The current Finished trigger may not match due to its listener; use a timed Flow or actual player feedback rather than assuming it fires.
Verify the case-sensitive project ID, JSON, Translation API, billing, permissions and quotas. Wait for language suggestions after saving settings. Check the source and target languages and test with Hello. The app uses the device source setting when an action's optional source is omitted; it does not automatically detect the source.
Check the YouTube-specific API key, enabled YouTube Data API v3, key restrictions, quota and internet access. Try a broader search. An empty result fails with “Nothing found.”
Check the community topic or open an issue. Include the device type, card, symptom and sanitized error, but never include JSON keys, API keys, private URLs or personal text.
Support development - If Google Services is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!