-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TuyaLan] Failed to discover -NAME- (-ID-) in time but will keep looking. #54
Comments
The same thing is happening with my setup. Any guidance would be appreciated. The device I am trying to connect to is a door/window sensor and I set it up as a SimpleLight as asked for unknown devices. It is possible my problem has something to do with the fact that it is a sensor and not a device like a switch or outlet. |
It is very possible that I could be to do with the device type that you are telling homebridge which is causing it to look for different codes along with the if and key so what I recommend doing is opening another issue and put it as a device support request and then reference this issue. I don’t know how long it will take as no one has been able to get in contact with AMoo-Miki via GitHub recently.
… On 5 Jun 2019, at 9:52 pm, scsammyk ***@***.***> wrote:
The same thing is happening with my setup. Any guidance would be appreciated.
The device I am trying to connect to is a door/window sensor and I set it up as a SimpleLight as asked for unknown devices. It is possible my problem has something to do with the fact that it is a sensor and not a device like a switch or outlet.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I was having the exact same issue with the same error messages for my Smart Plugs (Type Outlet). However they resolved on their own once I upgraded the firmware on my plugs. So I suspect this is more of an API / firmeware issue on the TuyaLan side than a homebrige plugin problem. Perhaps TuyaLan is limiting API access to only the latest firmware release? |
What version of the firmware are your devices on? Mine says it is on the latest |
I have the error on 1.0.3 which it says is the latest firmware. The one which is on an earlier version still works.
… On 14 Jun 2019, at 11:25 am, scsammyk ***@***.***> wrote:
What version of the firmware are your devices on? Mine says it is on the latest
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#54?email_source=notifications&email_token=AMGUEY3M3VEC4565KHYJNULP2LXPPA5CNFSM4HSGD4XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXVOP7Q#issuecomment-501934078>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMGUEYZMV7UR2QWZUFN4DLTP2LXPPANCNFSM4HSGD4XA>.
|
Is that the MCU version or the Wi-if version? Mine are 1.0.0 and 1.0.6 respectively |
On the Outlet which has this error, both the MCU Module and Wifi Module are on 1.0.3, which it says is the latest version. This is the outlet I'm using: https://www.bunnings.com.au/brilliant-smart-wifi-plug-and-usb-charger_p0091644 |
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. |
Same problem here, I have the Koogeek one that uses the tuya protocol ( https://www.amazon.it/gp/product/B07QNT8X61/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1 ) and I have 1.1.1 in both MCU and Wifi modules. Failed to discover in time but will keep looking |
Same here |
Same, My Air-conditioner worked worked well 6 months ago when he first got it going for me now I'm getting this error. He must be taking a break from the project for a while. I hope he comes back soon. He did a superb job setting the air conditioner up for me. It still works, this error just fills the log -
|
Dear iaansari - very interestingly I think I have the same adapter as you from Amazon but called Woox. Picture is identical. Mine are running the same MCU and WiFi Modules 1.0.1 - which the app tells me is the latest version. However, I still get the failed to discover error message. Wondered if anyone else had had any success? Kind regards - Michael |
+1, MCU & WIFI 1.0.2 |
I finally got my hands on one of these. Please give the latest 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 |
I've purchased three of these https://www.amazon.de/gp/product/B07PS5LRPQ/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1. I'm also getting the "Failed to discover" message, also with the rc-version of TuyaLAN. I've added the ip-addresses in the device block and can see a constant connecting/disconnecting and ERR_PING_TIMED_OUT. I hope you can fix this in some of your next releases and will of course help where I can. |
@fraho67, do you know which version of the If that is not the case with yours, could you please create a new issue and we can dig deep into it there together (thanks for the offer to help debug). |
Closed for inactivity. Please reopen if you continue to need help. |
I'm fighting with new LIDL smart devices, which are just a rebranded Tuya manufactured by Silvercrest.
Weirdly enough, if I don't set up these accessories, the plugins discover them:
|
hello I just try @AMoo-Miki solution but now here is the problem TuyaDiscovery] Discovery started on port 6666. any ideas ?? thanks |
Did everything just like the instructions say.
Received id and key pair and added it into config file.
When homebridge restarts, I'm getting:
My config file:
Any idea what could be wrong?
The text was updated successfully, but these errors were encountered: