This proposal closely reflects the difficulty I am currently experiencing with a separate issue involving the official Homey–Alexa integration
Since August, newly added Homey devices have not been discovered by Alexa, although previously discovered devices continue to work. The failure has been reproduced across several device types—including Hue, native Zigbee, groups and virtual devices—and independently by another Homey Pro user. I have documented the testing in a separate community thread.
The ability to publish newly added and replacement Homey devices to Alexa is a core function of the official Homey–Alexa integration. Without it, existing endpoints may continue working, but the Alexa-connected environment cannot be maintained or expanded. There is currently no supported, non-destructive workaround through the official integration.
What makes this particularly concerning is that I have since found closely similar reports dating back considerably further. One Homey Pro 2019 user reported the same inability to expose new devices to Alexa in March 2025 and ultimately moved to Home Assistant after the problem remained unresolved. A separate October 2025 discussion also describes the same basic pattern: existing devices continued working while Alexa discovery failed to add new Homey devices.
I cannot establish from community reports alone that every case has precisely the same underlying cause, or that this represents one continuous incident. However, the similarity and recurrence of the reports should warrant formal correlation and review by Athom rather than each affected customer being treated as an isolated case.
In my own case, Athom Support has been helpful, engaged constructively with the testing and kept my ticket open. The resulting evidence has been recorded on Athom’s internal problem board and given a high-priority tag.
However, I have also been told that the tag is not a formally reviewed severity assessment, that the issue has not yet been picked up by development, and that Support cannot initiate a separate management or service-owner review or provide a date for engineering triage. The case therefore remains recorded but without active engineering ownership or a defined review date.
That distinction is important. The difficulty is not the willingness of the individual Support representative to help; it is the apparent absence of a visible engineering-triage and service-ownership process after Support has exhausted the actions available to it.
For me, this illustrates exactly why a curated Known Issues system would be valuable. Customers would not need access to Athom’s complete internal backlog or a guaranteed resolution date. It would already help considerably to know:
- whether a significant issue has been officially confirmed;
- which products or integrations are affected;
- whether related reports have been correlated;
- whether it is awaiting triage or under active investigation;
- whether a workaround exists; and
- when its status was last reviewed.
This is especially important where a core function of an official integration is unavailable and there is no supported workaround. The Community Forum can reveal that other users have experienced similar failures, but it cannot establish whether Athom has formally assessed, correlated or accepted them for engineering investigation.
Another affected user has already documented moving from Homey to Home Assistant after this type of Alexa discovery failure remained unresolved. I am also having to consider what alternatives may eventually be necessary if newly added devices cannot be integrated with Alexa and there remains no defined route to investigation. That is not intended as a threat; it is the practical consequence of being unable to maintain an important part of the home-automation environment.
A curated Known Issues page with optional update subscriptions would provide clarity for customers, reduce repeated support enquiries and give Athom another way of measuring how many users are affected.
