search

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
345 stars 178 forks source link

Tuya devices not showing up in Home App #219

Closed freemanuk closed 2 years ago

freemanuk commented 2 years ago

I have installed the Tuya Platform plugin, configured the IoT Dev platform and scan the QR code to Homekit, but no device is showing up in Home app.

I have double checked that all my devices were listed in the Dev Platform and I can see the bridge added in the Home app under Home settings. However, it is not showing up in Homebridge Log. Is there anything that I have missed out?

github-actions[bot] commented 2 years ago

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

jurekjure commented 2 years ago

Same issue here ... cannot get tuya platform plugin - on Hoobs (Hoobs certified plugin) to show any devices. There is no error shown.

Anzic23 commented 2 years ago

Same issue

maaper commented 2 years ago

Same issue, can not see any devices. All parameters are properly configured, but I get no accessories on homebridge. This is part of the log:

[2/13/2022, 12:20:24 AM] Homebridge v1.4.0 (HAP v0.10.0) (TuyaPlatform) is running on port 47848.
TuyaOpenAPI response: {"code":1106,"msg":"permission deny","success":false,"t":1644708025274} path = /v1.0/iot-01/associated-users/actions/authorized-login
TypeError: Cannot destructure property 'access_token' of 'res.result' as it is undefined.
    at TuyaSHOpenAPI._refreshAccessTokenIfNeed (/usr/local/lib/node_modules/homebridge-tuya-platform/lib/tuyashopenapi.js:49:11)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at TuyaSHOpenAPI.request (/usr/local/lib/node_modules/homebridge-tuya-platform/lib/tuyashopenapi.js:145:7)
    at TuyaSHOpenAPI.getDevices (/usr/local/lib/node_modules/homebridge-tuya-platform/lib/tuyashopenapi.js:63:15)
    at TuyaPlatform.initTuyaSDK (/usr/local/lib/node_modules/homebridge-tuya-platform/index.js:90:19)
Attention⚠️ ⚠️ ⚠️ ! You get an error!
Failed to get device information. Please check if the config.json is correct.

Thanks in advance!

Anzic23 commented 2 years ago

@maaper you have "permission deny" check here

GitPuffy commented 2 years ago

I have installed the Tuya Platform plugin, configured the IoT Dev platform and scan the QR code to Homekit, but no device is showing up in Home app.

I have double checked that all my devices were listed in the Dev Platform and I can see the bridge added in the Home app under Home settings. However, it is not showing up in Homebridge Log. Is there anything that I have missed out?

When I configured this plugin through Homebridge and provided "US" as my country the plugin failed. When I went back and configured my country as "1" it worked as expected. Maybe this is the same issue for you.

michelec4gno commented 2 years ago

same issue

vmoreno71 commented 2 years ago

Same issue. I tried the country code with 34 (Spain). No. problem in Hoobs, but no accessories detracted, neither in hoops or HomeKit

github-actions[bot] commented 2 years ago

Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.

Muxxx commented 2 years ago

I just attempted to set this up myself and none of my lights are showing up. It even shows in the homebridge logs that the accessories were supposedly added, but they don't appear as accessories. It just keeps saying that every time I restart my homebridge server.

onichan88 commented 2 years ago

I'm with the same problem, the logs from tuya shows the device, and the changes of the device when I turn the light on/off, but it doesn't show in the home app.

Muxxx commented 2 years ago

I’ve given up on this plug-in, as clearly the devs have too.

onichan88 commented 2 years ago

I’ve given up on this plug-in, as clearly the devs have too.

Have you tried another plugin with success?

Muxxx commented 2 years ago

I have moved away from HB specifically because of the lack of Tuya support. Both the Tuya official and Tuya LAN plugins are terrible. I switched to Home Assistant and use the native HomeKit integration (in HA) to present my devices back to my apple ecosystem. I use this plugin specifically with HA - https://github.com/make-all/tuya-local

onichan88 commented 2 years ago

The main problem is that your device category maybe is not implemented in the code, or is newer and they have to add the accessory to the code. I have a ceiling fan with light, with device category 'fsd' and I had to add it by my own. Is like a 'fs' (ceiling fan without light, already coded) but with minor changes, but if you don't make that changes, it will not show in accessories nor homekit.

ADCLBA commented 2 years ago

Hello

Same issue for me I tried to use this plugin in Homebridge, but no accessory created.

I check and every information of the device is visible in the log, I can see : Adding: Temperature Humidity Sensor (wsdcg / xxxxxxxxxxxxxx) Adding: Multi-mode Gateway (wg2 / xxxxxxxxxxxxxx)

calamarzo commented 2 years ago

@onichan88 please, can you elaborate more on this? I think this is my issue. Where did you add the category details? thanks!

The main problem is that your device category maybe is not implemented in the code, or is newer and they have to add the accessory to the code. I have a ceiling fan with light, with device category 'fsd' and I had to add it by my own. Is like a 'fs' (ceiling fan without light, already coded) but with minor changes, but if you don't make that changes, it will not show in accessories nor homekit.

onichan88 commented 2 years ago

Hi @calamarzo in the main file, I added the "fsd" type, and in the file of ceiling fan I made some minor changes. I propose some changes to this github, still waiting acceptance. If you want to try, you cam use my github fork of this github. I also forked another github to use the ceiling fan locally and it worked!

github-actions[bot] commented 2 years ago

Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.