homebridge-tuya-lan: [TuyaLan] Failed to discover -NAME- (-ID-) in time but will keep looking.

Did everything just like the instructions say. Received id and key pair and added it into config file. When homebridge restarts, I’m getting:

[TuyaLan] Failed to discover Socket (10343760bcddc2232f7a) in time but will keep looking.

My config file:

{
  "platform": "TuyaLan",
  "devices": [
    {
      "name": "Deer Light",
      "type": "Outlet",
      "manufacturer": "BlitzWolf",
      "model": "BW-SHP6",
      "id": "10343760bcddc2232f7a",
      "key": "-KEY-"
    }
  ]
}

Any idea what could be wrong?

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 19 (3 by maintainers)

Most upvoted comments

I finally got my hands on one of these.

Please give the latest rc release a shot by doing npm i -g homebridge-tuya-lan@rc. It includes logic to understand this newer API.

A known issue is that the current state is not reported by some devices; they however work fine as soon as you interact with them. I have reached out to Tuya for a solution.

The Setup Instructions have changed in case you need to obtain a fresh id and key.

AMoo-Miki on Sep 6, 2019

My MCU and WIFI Modules are both at 1.0.1. When I do a firmware check my SmartLife app tells me I am on the latest version. I use the following plugs https://www.amazon.ca/TECKIN-Wireless-Compatible-Function-Required/dp/B07PZ7VVGC/ref=sr_1_2_sspa?keywords=smart+plug&qid=1560525067&s=gateway&sr=8-2-spons&psc=1

So perhaps this is an issue with the newer version of the firmware. Ideally what we need is the ability to specify the devices via IP vs having the homebrige plugin trying to automatically discover them.

iaansari on Jun 14, 2019