tuya / tuya-homebridge

Homebridge custom plugin for controlling Powered by Tuya (PBT) devices in HomeKit. This plugin is officially maintained by the Tuya Developer Team.
MIT License
348 stars 179 forks source link

Tuya IR Remote not compatible with dstv explora #397

Open Kaydee406 opened 2 weeks ago

Kaydee406 commented 2 weeks ago

Describe the bug I've been trying to configure my Tuya IR universal remote to work with my dstv explora. These are the steps I took : Step 1- added the Tuya IR remote to the app Step 2 - searched for dstv under set top box and clicked on it Step 3 - I made use of the manual learning function as I could not find my remote control on the default learning function. Some of the buttons managed to work except from the number key buttons. Each button I press, keeps bringing out the number "1" key button as output. Attached is a picture of the IR remote pack. Can someone recommend a solution for me please.

Screenshots image

Login request (please complete the following information, which can be found in log): request path = /v1.0/iot-01/associated-users/actions/authorized-login

like this:

TuyaOpenAPI request: method = post, endpoint = https://openapi.tuyacn.com, path = /v1.0/iot-01/associated-users/actions/authorized-login, params = null, body = {"country_code":86,"username":"XXXXXXXXXXXXX","password":"c44755c3379313db173e53c3e8fb6701","schema":"tuyaSmart"}, headers = {"t":"1626082406842","client_id":"XXXXXXXXXXXXX","nonce":"33341140-e2f4-11eb-abd9-491eaffd7d33","Signature-Headers":"client_id","sign":"2E250AB9256B14F6EAD94DEA9EE0EA8413E7939E7DEAB0B60D8D786B296A7AF8","sign_method":"HMAC-SHA256","access_token":"","lang":"en","dev_lang":"javascript","dev_channel":"homebridge","devVersion":"1.2.1"}

Login response (please complete the following information, which can be found in log): request path = /v1.0/devices/functions TuyaOpenAPI response: {"code":1106,"msg":"permission deny","success":false,"t":1626082407259} path = /v1.0/iot-01/associated-users/actions/authorized-login

github-actions[bot] commented 2 weeks ago

Thank you for your feedback, we will solve this issue soon