# \[APP\]\[Pro\] Amazon Echo - Looking for testers and contributors

**URL:** <https://community.homey.app/t/app-pro-amazon-echo-looking-for-testers-and-contributors/120365>\
**Category:** Apps\
**Created:** [November 12, 2024, 12:33pm UTC](https://community.homey.app/t/app-pro-amazon-echo-looking-for-testers-and-contributors/120365 "2024-11-12T12:33:05Z")\
**Posts on this page:** 1\
**Showing post:** 222

<div class="post-metadata">

**Author:** ![copiis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/copiis/32/171978_2.png) [@copiis](https://community.homey.app/u/copiis)\
**Post date:** [June 22, 2026, 6:03am UTC](https://community.homey.app/t/app-pro-amazon-echo-looking-for-testers-and-contributors/120365/222 "2026-06-22T06:03:09Z")

</div>

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 bug.

Thanks for calling that out.

---

_[View the full topic](https://community.homey.app/t/app-pro-amazon-echo-looking-for-testers-and-contributors/120365)._