Tuya working with Homey

[Jacques]

I have a new problem again. One of my Tuya devices connected to Tuya Cloud is not working properly with my Homey Pro. The device works fine with the Tuya App. It has also worked fine with the Homey App until recently. But now the device no longer responds to commands in the Homey App while there is no error message anywhere. If I switch the device on or off in the Tuya App, it works fine. The status enabled/disabled in the Homey App will also change. But it does not listen to commands directly from the Homey App. I checked the Tuya Cloud API, not expired. No error messages. Device removed and reinstalled. Homey restarted. No solution. What could be the problem?

[Peter_Kawa]

When other devices work fine with the Tuya Cloud app, I can’t think of anything
But there’s two workarounds:

@Jurgen_Heine

Scenes

This app support the use of scenes. In the mobile Tuya/Smart life app you can make ‘Tap to run’ actions( In the past they where called scenes). Those actions can be called in a flow from this app.
The scenes for the official API are not automatically updated, for now new scenes will only appear after a restart of this app.

See also howto of @Peter_Kawa: [App][Pro] Tuya Cloud - #296 by Peter_Kawa

@Jurgen_Heine

Raw commands

You can receive all messages send for devices with trigger cards. Also there are now action cards to send commands to you device. On this way you can interact with not directly supported devices are commands. Combine it with the virtual devices app and you can control most of your devices. It’s a function for advanced users, there is no validation when sending a command to your device.

To get the device id’s, commands and possible values you can create a flow with the text event received trigger card. This card is returning device id, command and value for each action. Log the returned values to log app to know the commands of your devices, deviceid’s and possible values.

See also Howto of @Peter_Kawa: [App][Pro] Tuya Cloud - #765 by Peter_Kawa

[Jacques]

Thanks for the comment. I completely removed, reset, and reinstalled the device, which solved the problem.