With this new tool, you can check the compatibility of ZigBee devices by entering their Manufacturer Name and Product ID. It shows which app supports the device, and which driver it uses.
Really a great idea!
However, it doesn’t seem to be that easy to find compatible devices, as the manufacturer’s name must be entered exactly, including case sensitivity.
Example
-
ZigBee Manufacturer Name: sonoff
ZigBee Product ID: SNZB-02D
: No result -
ZigBee Manufacturer Name: Sonoff
ZigBee Product ID: SNZB-02D
: No result -
ZigBee Manufacturer Name: SONOFF
ZigBee Product ID: SNZB-02D
: One result out of two possible results
App suggestion: Sonoff app by StyraHem Sweden
Notice: The stable SONOFF Zigbee app by Johan Bendz, a community app, supports the same device but is not displayed. Why?
If the search function doesn’t become more user-friendly, e.g., with a drop-down menu for the manufacturer name, many useless app requests will be created in the future.
A few more questions. Are only “official” apps suggested or also community apps? Are app test versions also searched for compatible devices?
That’s not possible, I’m completely dependent on the (undocumented) API endpoint from the Athom Apps API (the same one used when adding a generic ZigBee device in Homey that checks for compatible apps).
If you choose Homey Cloud, then only official apps will be shown. On Homey Pro/SHS, also community apps will be shown.
The “This device is not compatible” page is also different for Homey Cloud vs Homey Pro/SHS. It will only show the official app requests link if you choose Homey Cloud. On Pro/SHS, it will also show the community app requests link.
No, those aren’t searched for. The Athom Apps API endpoint only checks live versions.
Of course, because Homey Cloud only works with “official” apps.
But that’s not the case, as I mentioned in my test.
The SONOFF Zigbee community app by Johan Bendz is not offered as an option, only the “official” Sonoff app by by StyraHem Sweden.
What I forgot to mention was that I made a search request for a Homey Pro (2023 - 2026).

That is also not the case, or I’m doing something wrong:

That’s because the API seems to prefer official apps over community apps. If you choose one without an official app (only community), then it will show the community app.
That’s a bug in that case, I’ll check on it later today.
I then wonder if this tool really makes any sense. When I enter the device name in the search field in the Homey App Store, both possible Homey apps are displayed:
And the request isn’t case sensitive.
It doesn’t use that endpoint.
When you add a generic ZigBee device to Homey, it checks the Manufacturer Name and the Product ID to a Homey Apps API endpoint (this is invisible) so that it can recommend an app. My checker uses that same endpoint to check which app and driver is used.
I’ve tried to reproduce this issue but couldn’t. This is what it shows for me (exactly the same manufacturer and product ID were used):
Can you try it again? What browser are you using?
I used the Safari browser on a MacBook.
I won’t be investing any more time in it, as it’s not useful for me. A search via the Homey App Store currently yields better results, the input is not case sensitive, and the search is not limited to Zigbee devices.
Sorry!
It’s not meant for checking devices by model number/manufacturer name. It’s meant to check devices’ compatibility if you have their Manufacturer Name and Model ID (e.g. from another ZigBee coordinator) and can then copy those 2 values into the tool
I was able to reproduce the issue. It seems to happen only when you first click Pro 2023-2026 and enter an unsupported device, and then switching to Homey Cloud and then entering different device information from another unsupported device. I’ll have to check what’s causing this, it’s a strange issue.
I have fixed the bug/issue now.



