# Sprachausgabe über Alexa (TTS)

**URL:** <https://community.homey.app/t/sprachausgabe-uber-alexa-tts/156252>\
**Category:** Fragen & Hilfe\
**Created:** [June 16, 2026, 3:33pm UTC](https://community.homey.app/t/sprachausgabe-uber-alexa-tts/156252 "2026-06-16T15:33:25Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![PeHe](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pehe/32/120855_2.png) [@PeHe](https://community.homey.app/u/PeHe)\
**Post date:** [June 22, 2026, 2:32pm UTC](https://community.homey.app/t/sprachausgabe-uber-alexa-tts/156252/27 "2026-06-22T14:32:21Z")

</div>

Ah… ok, also mehr oder weniger “pragmatische” Gründe 👎

Ok, für dich jetzt nicht (mehr) interessant. Aber das “nicht verbunden” Problem ist behoben

> [@\[APP\]\[Pro\] Amazon Echo - Looking for testers and contributors](https://community.homey.app/t/app-pro-amazon-echo-looking-for-testers-and-contributors/120365/222):
>
> The ~24h connection drops I mentioned were from the old JS version, not v2.0. I only installed 2.0 yesterday, so I haven’t been able to reproduce anything on the new stack yet. The changes in my fork are preventive — based on that old behaviour and how session/cookie refresh works in the Python rebuild. I’m running a 24h soak test on my Homey now and will post the results here either way. If 2.0 stays stable as-is, that’s great — then it’s just an extra safety net, not a fix for a confirmed bu…

---

_[View the full topic](https://community.homey.app/t/sprachausgabe-uber-alexa-tts/156252)._