Would a Homey Known Issues / Bug Tracker be useful?

Questions & Help
,
1

I recently had an issue with multiple IKEA Matter devices that stopped working after a Homey update. Support confirmed that this is a known issue and that it is currently under investigation.

It made me wonder: would a dedicated, official Homey Known Issues / Bug Tracker be useful for the community?

What could such a tracker provide?

For example:

  • Confirmed issues officially acknowledged by Homey

  • Affected Homey versions and products

  • Affected integrations, such as Matter

  • Current status: Investigating → Identified → Fix in development → Fixed

  • Available workarounds

  • The Homey version containing the fix

  • Date of the latest update

  • Optionally, an indication of how many users are affected

It wouldn’t need to expose internal development information or promise an ETA. Even a simple status such as “Confirmed and being investigated by the development team” would already be valuable.

Why would this be useful?

It would give users one official source of truth when something stops working.

It could also reduce duplicate support requests. If a customer encounters a problem that is already known, Support could simply point them to the relevant issue.

It would also clearly distinguish between:

“Users are reporting this on the Community Forum”

and

“Homey has officially confirmed this issue and is investigating it.”

What about the Community Forum?

The Community Forum is great for sharing experiences, troubleshooting and discovering that other users are experiencing the same problem.

However, I don’t think a community forum should be the primary place for customers to determine whether a bug in an official Homey product has actually been acknowledged by Homey or to track its progress.

Does Homey already have something like this?

Homey has a public status page, but that mainly covers the availability of Homey services. There has also been a Beta Status page in the past that listed known issues being worked on by the development team.

So I’m wondering whether something similar for all major Homey issues and bugs would make sense.

Would you use an official Homey Known Issues / Bug Tracker?

And what information would you personally want to see on it?

2

Beside that before Homey version v2.0 there have been a Github issue tracker. But beside the 1% techi users here it didn’t work for the 99% target users for Athom that expect plug and play and don’t search.
(Before 1.0 it probably was 80% technically users from the Kickstarter. I guess now it is less than 2% of all Homey users)

When Homey Community grows It was soon filled with issues and reactions like

  • it doesn’t work
  • me too…
  • when will it be fixed?
  • this should have the highest prio, it is a showstopper for me …

And even more and worse useless reactions.

Even here on the community I sometimes see good bug reports described. Unfortunately sooner or later someone reacts with "I have exactly the same " then stating they have a complete different Homey model or different app.

Although I as a techie would like it, I understand they don’t publish all known bugs.
I think it is extremely difficult to write the good exact bug that the normal Homey users understand and don’t misinterpreted think they have the same.

3

I understand your point, especially regarding an open GitHub-style issue tracker where everyone can create and comment on issues. I agree that this could quickly become noisy and difficult to maintain, especially with different Homey models, firmware versions and apps involved.

However, that isn’t quite what I have in mind.

I’m not suggesting that Athom should publish every internal bug or open a public developer issue tracker again. I’m thinking more about an official, curated Known Issues page, maintained by Homey’s own support/development team.

For example, if Support confirms that a particular issue is known and being investigated, Homey could decide whether it is significant enough to appear on the page. Users wouldn’t create or edit the entries themselves.

Something as simple as:

IKEA Matter devices cannot be paired
Affected: Homey Pro / Matter
Status: Investigating
First reported: September 2026
Workaround: None
Last update: September 20, 2026

No discussion, voting, prioritisation or hundreds of “me too” comments. Just an official status maintained by Homey.

I actually think this would solve some of the problems you mention rather than create them.

The Community Forum can remain the place for users to discuss problems and help each other troubleshoot. The Known Issues page would be the place to answer a different question:

“Has Homey officially acknowledged this problem, and what is its current status?”

Especially when Support tells a customer “this is a known issue and our development team is investigating it” and then closes the ticket, I think having an official place to follow that issue would be very useful.

And it doesn’t necessarily have to expose every bug. It could be limited to significant issues affecting multiple users or causing major functionality to stop working.

That’s more the kind of system I had in mind than bringing back a completely open GitHub issue tracker.

Ultimately, I see this less as a bug-reporting tool and more as a transparency and trust tool: if Homey officially acknowledges a significant issue, wouldn’t giving customers a clear and reliable way to see that status help build more trust in the platform?

4

That would imply a minimum of openness and honesty from Athom. - Considering past experience, I unfortunately do not see this coming at any time in the future. :frowning:

5

I think a page with all the issues wouldn’t be good marketing for Homey :wink:

They do already have an issue tracker for app developers, but the few issues I reported were never fixed. They do seem to follow it more actively than before though.

There is also the server status page at https://status.homey.app/, on that page the issues with the Homey servers are reported.

6

I would really love to have a User Voice page to show demand for specific features from the community and to also see if someone already raised something already so you don’t need to bother their support. But this has been brought to their attention multiple times and they do not give a shit about this. It’s their right as a private company but it’s still frustrating.

7

I understand your point, especially given past experiences with Athom.

But they are already telling customers by email when an issue is a known problem. My suggestion is simply to make that information publicly accessible instead of keeping it limited to individual support tickets.

If Athom is already willing to acknowledge known issues privately, wouldn’t publishing the same information in a curated Known Issues page actually improve transparency and customer trust?

8

I agree that a page full of bugs probably wouldn’t make for great marketing. :grinning_face_with_smiling_eyes:

But I don’t think it needs to be a list of every minor issue. I’m thinking specifically about significant, confirmed issues that are already acknowledged by Support.

We already have the server status page, and developers have their own issue tracker. What seems to be missing is a simple official place for Homey users to check: “Is this a known problem, and is Homey working on it?”

In my case, Support has already confirmed by email that the IKEA Matter issue is known and under investigation. Why shouldn’t that information also be available publicly to other affected users?

9

I agree that this is frustrating. But I think my suggestion is much more limited: not a UserVoice-style platform, but simply a curated page where Athom lists significant issues they have already confirmed and are working on.

No voting, no user-created issues, no prioritisation — just a clear answer to: “Is this a known problem, and what is its current status?”

That would already make a big difference.

10

Athom currently has quite a backlog of issues. Many of them are based on design decisions made many years ago which are practically not solveable for the current devices. Others would be solveable with some effort in software refactoring.

Both are not good for marketing and cost money to resolve. And unfortunately as long as they can get enough revenue from selling new stuff to new customers they will not do anything. - You as an existing customer are commercially completely uninteresting.
This can be clearly seen as they invested in developing a bloated remote control with a ridiculous cord danglig from it a.s instead of putting that money into fixing stuff.
That is all absolutely understandable and legitimate for a commercial entity.

If you want openness and people who care about making stuff better for existing users, you have to go for open source solutions. There is no commercial interest in the first place but folks having fun at improving things.

11

Rhet then don’t get insights about how much people are affected and say they use that for prioritizing the bugs and issue’s to resolve.

13

I agree that Athom needs a way to measure how many users are actually affected, especially if that information is used to prioritize issues.

But I don’t think the Community Forum is the right place to collect that data either.

We’re both IT guys, so I think we also understand that this is ultimately a process problem. There are well-established ways to handle this: collect reports through Support, correlate them internally, publish confirmed issues, and give affected users a way to subscribe to updates.

A possible solution would be to add a simple “Subscribe to updates” button to each Known Issue. Users who are experiencing the problem could subscribe with their email address. That would give Athom a much better indication of how many users are affected, while also giving those users a direct way to receive updates when the status changes or a fix is released.

You could even set a threshold for publishing an issue. For example, an issue only becomes a public Known Issue once it has been confirmed by Support/Development and there are at least X affected users or a significant enough impact.

That would give Athom three separate things:

  • Support reports → detailed information and troubleshooting

  • Known Issues page → officially confirmed issues and their current status

  • Subscriptions → a measurable indication of how many users are affected and a direct communication channel with those users

And this is actually where I think Athom is currently failing its users.

In my case, Support has confirmed that the IKEA Matter issue is known and that Development is investigating it. But my support ticket has simply been closed. I have no way of knowing when there is an update, whether the investigation has progressed, or when a fix is expected. I would have to open another ticket or keep searching the Community Forum myself.

From a process perspective, that’s the part I don’t understand. If Athom already knows about an issue and has confirmed it to a customer, why shouldn’t there be a process that keeps that customer informed until the issue is resolved?

The Community Forum can remain what it is good at: discussion, experiences and helping each other. It shouldn’t have to function as Athom’s unofficial bug-tracking and status system.

So I think we know that this can be solved quite elegantly without creating an open GitHub-style bug tracker or exposing every internal bug. A curated Known Issues system with thresholds, subscriptions and proper status updates would actually give Athom better data while providing better communication to its users.

Right now, in my case, Athom has acknowledged the problem, closed the ticket, and left me with no mechanism to know what happens next. That’s where I think the current process is failing the customer.

14

I don’t think any company does this and it would be pretty bad business to do so

15

Companies like Apple, Microsoft, Samsung, Synology, QNAP, Ubiquiti and Sonos all publicly communicate product, firmware or compatibility issues and fixes.

I’m not suggesting Athom publishes every bug or its internal backlog. I’m suggesting a curated Known Product Issues page for significant, confirmed issues.

Support can still collect individual reports to measure impact. Once confirmed, the issue can be published with:

  • current status
  • affected products/versions
  • workaround
  • latest update
  • “I’m affected / Subscribe to updates”

That would actually give Athom an additional way to measure impact while keeping affected users informed.

16

They all have thousands of employees and their products are used by a factor of 10 more than Homey I’d assume (apart from Sonos). Athom is still a small team and the amount of admin required to accomplish something of this scale is more than you’d think