Just a double check: in the mobile app on the Devices tab, when you tap the + button (top righthand) and select New Device (don’t enter any keywords in the search bar), you should see a list with Suggested apps at the bottom part of the screen. That list included all your installed app. Isn’t the Universal Zigbee app included in that list?
Normally all installed apps should be listed there. You would then select the app and then select the device driver for the device that you are trying to pair. So you are not letting Homey search for an app/driver, but you are manually selecting the specific app and driver you want.
v7.4.4: Final Stability Align, Fixed “getDeviceConditionCard” crash in 114 drivers, Harmonized branding to “Unified Engine”, Added support for Insoma 2-Way Irrigation Valve, Production ready.
Covers a huge range of Tuya devices at this point.
so you say it will not work and will not have 2 separate buttons like in a physical switch? Re-adding and repairing did not help at all. You can not select any drivers or anything during adding process. I pasted the result of the interview as well. Did you check it?
On the latest version all 2 Gang Smart switches are disabled (red exclamation mark) Please check.
with V7.4.1 i wanted to give my button a new chance but must recognize that with V22.0.0 RC and V7.4.4 in the git repository my device was removed from wall_switch_4gang_1way. Can you please re-add it or was the device transferred to another driver i can’t find?
Maybe you forgot to publish it to Test from Draft? If the build is in Draft status, it isn’t shown or made available to users. It becomes available when you publish it to Test.
I installed dozens of different kind of devices, using different apps, so I think I know how to install a new device. But thanks anyway for explaining the procedure. I can imagine you think I let Homey decide what app to use, after reading the way I described it.
That’s why I asked the question. In a previous version, < 7.4.1, the Universal Zigbee app was visible. Now it isn’t anymore.
I can assure you the right app is installed. After selecting the app I think it has to be, I select the kind of device, not a specific device driver. I suppose you mean the same. That’s what confusing me in the postings of the developer. He talks about several kinds of device driver to use after showing up. In the list of devices available in the app (be careful, I mean listed in the overview of devices in the Homey app store, not when installing a device. The app isn’t available so I can’t see them of course), a lot of different devices are built in, representing the same kind of device. About 5-7 comparable plugs, f.e..
The Zigbee app I was using instead showed a lot of different devices, analog to the Universal Zigbee app (UZA). That’s why I expected that this app is the UZA.
As Homey didn’t find my device after selecting one to install in the all and after setting the device in installation mode, I decided to let Homey look for an app and device instead, expecting the fingerprint of my device will be built in the right (UZA) app. So, the UZA will show app. How big was my surprise when Homey advised a completely new app and a completely different device!
I get that. It took me a while to understand it too. My understanding is as follows:
During the process of adding a device, after selecting the app, you get an overview of ‘devices’ from which you select the corresponding one. This is a similar overview as on the app’s app store page. These ‘devices’ are actually the device drivers.
Often there is a one-on-one link between (the name of) a device and a driver. E.g. for brand specific apps. So when you select the items that has the same name/model no. of your device, you are actually selecting the driver.
For universal apps or apps that support multiple brands, one such driver supports multiple flavors/brands of the same device. This is also the case for this the universal Tuya zigbee app.
For instance, I have a 2 button scene swich/remote from the brand Marmitek, which is Tuya-based. I also have the same switch, but from the MOES brand. Both use the same 2 button scene swich driver (‘device’ in the said overview).
But…since Marmitek also has its own app, I can als choose to use that app and included drivers for both devices.
I think that the last point I mentioned above, was also what you were experiencing when trying to let Homey detect the app/driver to be used: since the universal tuya app was not available, it found another app that seems to support your device.
It’s related to invisible characters on the code ( \t \n ect ect … ) i m investigate and hopping to fix soon. The push to homey to the latest version failed related to this issue . But on my local device îm on 7.4.4
I thought something was going wrong with releasing the test versions of your app. So, I downloaded the zip file of the code at Github, unzipped it, and “homey app install” in the correct folder.
I saw a lot added:flowcards, capabilities, pictures, and DRIVERS. Those you talied about a lot in your answers and aren’t clear to the normal users. Al least, the connection between the icons of the different kind of devices (with a lot overlapped) and what you call drivers.
But unfortunately, I got some error messages:
× Command failed: npm ls --parseable --all --only=prod
npm warn config only Use --omit=dev to omit dev dependencies from the install.
npm error code ELSPROBLEMS
npm error missing: color-space@1.15.0, required by com.dlnraja.tuya.zigbee@7.4.5
npm error missing: homey-zigbeedriver@^2.2.2, required by com.dlnraja.tuya.zigbee@7.4.5
npm error missing: punycode@^2.3.1, required by com.dlnraja.tuya.zigbee@7.4.5
npm error missing: qrcode@^1.5.4, required by com.dlnraja.tuya.zigbee@7.4.5
npm error missing: tuyapi@^7.7.1, required by com.dlnraja.tuya.zigbee@7.4.5
npm error missing: zigbee-clusters@^2.6.0, required by com.dlnraja.tuya.zigbee@7.4.5
npm error A complete log of this run can be found in: C:\Users\Roger\AppData\Local\npm-cache_logs\2026-04-17T11_57_30_767Z-debug-0.log
× Error: This error may be fixed by running npm install in your app.
*** at C:\Users\Roger\AppData\Roaming\nvm\v24.14.0\node_modules\homey\lib\App.js:1126:15***
*** at process.processTicksAndRejections (node:internal/process/task_queues:104:5)***
*** at async App._copyAppProductionDependencies (C:\Users\Roger\AppData\Roaming\nvm\v24.14.0\node_modules\homey\lib\App.js:1123:26)***
*** at async App.preprocess (C:\Users\Roger\AppData\Roaming\nvm\v24.14.0\node_modules\homey\lib\App.js:890:7)***
*** at async App.install (C:\Users\Roger\AppData\Roaming\nvm\v24.14.0\node_modules\homey\lib\App.js:827:7)***
*** at async Object.handler (file:///C:/Users/Roger/AppData/Roaming/nvm/v24.14.0/node_modules/homey/bin/cmds/app/install.mjs:23:5)***
I can’t fix them, I don’t know whether they are related to my system or to something missing in the files or code at Github. Maybe you can have a look at it. But more important, Ihope you can release the correct version as the test version. I’m really looking forard to use your app so we don’t have to worry about picking the correct kind of device, but it will recognize it itself.
