GET response the same for schema and DPS ID

[lgwapnitsky]

When I try the following code injection, the response is the same as {"operation":"GET","schema":true}:

{"operation":"GET" , "dps": 1}

Output:

{"data":{"devId":"37307038a4e57cae2684","dps":{"1":true,"7":0,"101":"sense","102":"sense","103":"sense","104":"sense","105":"sense","106":"sense","107":"sense","108":"sense","110":"sense","111":"sense","112":"sense","113":"sense"}},"deviceId":"37307038a4e57cae2684","deviceName":"office controller"}

Am I missing something? I've tested on multiple devices with the same results.

[msillano]

Any Tuya device, any DP can have its own behavior. I too have encountered devices with this irregular behavior. Each GET responds as if it were a SCHEMA. e.g.

• Power strip. With this device SET(DP, null) behaves as GET(DP) should behave. You can try this on your device.

• One more example: Switch 1CH.

We need to adapt.

[yin583014830]

The above figure is for reference, and all DPS instructions for this device can be obtained

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.