You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From observing Android apps, have you noticed any response that correctly maps DP ids to their names?
Some devices with the same functionality have DPs ordered in different ways, so this has to be possible for the app to understand correctly what kind of device it's connected to.
There's a chance this may be happening during the initial pairing of a device to Tuya's servers, or perhaps it's happening each time.
I've noticed there is a dpName dictionary returned from the Tuya API, but it's empty.
The text was updated successfully, but these errors were encountered:
From observing Android apps, have you noticed any response that correctly maps DP ids to their names?
Some devices with the same functionality have DPs ordered in different ways, so this has to be possible for the app to understand correctly what kind of device it's connected to.
There's a chance this may be happening during the initial pairing of a device to Tuya's servers, or perhaps it's happening each time.
I've noticed there is a
dpName
dictionary returned from the Tuya API, but it's empty.The text was updated successfully, but these errors were encountered: