-
Notifications
You must be signed in to change notification settings - Fork 96
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
[GET] Device Offline #161
Comments
I have not yet seen this happen before, the device offline error indicates that the Tuya Cloud cannot reach this device, this plugin simply forwards that message. |
The device definitely isn't powered off, or out of WiFi range. The Tuya app shows it is online and I can control the device - meanwhile Homebridge and Homekit say it's offline. Is it possible to have a communication issue between the Tuya app and Tuya web? |
Yeah a communication issue between the Tuya Cloud and the Plugin is possible (the plugin does nothing with the Tuya App, it talks directly to Tuya's servers). Please post the result of the steps under "How to check whether the api this library uses can control your device". |
Here you go! Getting credentials |
And is at the moment one of your devices mis-behaving (in this case stating that it is offline?) cause then we have a problem 😛 Thanks for your help 😄 |
All good at the moment but I'll repeat it when it happens again! |
I'm having this same issue. I can control inside Smart life app but Homekit says No Response…
|
The same here, started today at noon |
Yes, also having this issue. |
Same for me App works fine for all devices but HomeBridge says offline |
Same error happening for me here as well. 3 Devices offline in HomeBridge but visible on the Tuya app. [07/01/2021, 10:37:00] [TuyaWebPlatform] [Kitchen Downlight East] - Renewing cache due to RateLimitError |
Does not seem to be doing it anymore. |
Intriguing! Seems to have fixed itself for me too! |
I’m using the Smart Life app not. Tuya and had the same issue seem to be working now though |
Given the context of this issue and the information I got from other sources (amongst others multiple Reddit threads); it seems like there was a problem at Tuya. Please keep me updated if this happens more often. |
Ok, so I had it happen again this evening. Tuya app showed all devices online and working. Home app showed my 'Tyre' as 'No Response'. Homebridge showed '[Tyre] - [GET] Device Offline' again. I've pulled the log as you requested - it shows the tyre as online, so I guess Tuya Web is pulling the information correctly after all. That presumably means there's an issue between Tuya Web/Plugin/Homebridge/Home. Here's the log:
|
Further to my post above: I restarted Homebridge and initially all devices showed as 'No Response' in Home, while Homebridge just continued to show the Tyre as offline. Then, it changed to a different device that was offline (the fan). I checked the log again and noticed the yellow line of text. I decided to remove this line of code that was left over in my config:
After I did that, and restarted again, the issue has completely resolved itself. Unsure whether that was causing an issue or not. What do you think? |
The last warning you posted is of no influence (that is also the subtle difference between a warning and an error) in this case the plugin will just ignore that specific part of your configuration. Regarding the issue - I'll keep an eye on it cause I really don't understand what is going on here... |
So this happened to me again just now.
Screenshots and log below. And thank you for looking over this for me (and the others!). Log
|
Thanks for the report! I'll try to validate this in the next few days. |
I really can't find any glaring issues in the code and it hasn't happened for me. |
i have a same problem.. the problem seem happened when device is turning off manually and back turn on manually (loosing electricity). In tuya app, its reconect again but in homebridge it get device Offine and in home hit get No response.. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Just a follow up for those who still experiencing this and coming from searches: BLE devices can be connected to directly from your phone, in such case they seem offline, even though they're online and functional. If at iot.tuya.com you see devices as online (and can control them via Tuya app) but Homebridge/Homekit shows them offline the solution is simple: revoke bluetooth access from Tuya app. You need Bluetooth only for initial setup, but once a device is configured and accessible via web API and this plugin, Bluetooth is not necessary and even harmful as it hijacks device and makes it seem offline. So either turn off your phone's bluetooth or just revoke Bluetooth permission from Tuya / Smartlife and it should work. @milo526, maybe we can modify error message to let users understand what's happening? |
Describe the bug
Recently I've been getting a lot of 'No response' messages for devices in the Home app. All my devices are controlled by switches (so just on or off).
My log shows:
[GET] Device Offline
However, the device is definitely online - I can see it is when I check the Tuya app, and can turn it on and off without an issue. Yet the Homebridge log and Home app still show it as offline/No response.
This isn't happening on one device, but randomly across my sockets. My internet connection and WiFi reach are solid.
Restarting Homebridge fixes the issue but I'm having to do daily restarts because things keep going offline.
I've seen this happen with all sockets before and a restart fixed it, but never with one or two sockets individually - and never when they're online in the Tuya app.
Steps To Reproduce
Nothing has changed in terms of setup. WiFi is the same, Homebridge settings are the same, socket locations haven't changed.
Plugin Version
0.7.1
Homebridge Config
Device Config
Unfortunately cannot do this step. The Teckin plugs work with Tuya which works with this plugin. All devices have worked but this is an issue I've had recently.
Additional Context
Only thing not set in my config is the polling interval. I believe this was removed as a default setting not too long ago. Would this make a difference?
The text was updated successfully, but these errors were encountered: