Open aantono opened 5 years ago
Linking #44 as it has some similar traits!
Happened to me as well. The device (HS110) is not offline and available while homebridge says that device isn't available.
Had the same issue with homebridge in docker on my qnap. Went back to a pi a couple of days ago and no issues since. Plugin doesn’t seem at fault as both this and EWeLink we’re having issue in same docket setup as you.
This happens when the device is offline or unreachable (or unreliable) on the network.
I have a HS100 and can replicate the issue by turning off the device physically.
I guess I'm not understanding what you expect for behavior. If the device is offline, the network connection is going to error. The UnhandledPromiseRejectionWarning
is concerning, but I don't see that in my testing. If you see that warning please provide your environment details/versions and exactly how to reproduce so I can research.
There used to be a way to set a device as unreachable in homebridge but it was deprecated (Some details here: nfarina/homebridge#2078).
If i unscrew the bulb, and try to query or change a setting I get the error below. As soon as I screw the bulb back in, it resumes working in homekit.
[1/23/2019, 11:07:52 AM] [TPLink.API] TCP Timeout
[1/23/2019, 11:07:52 AM] [TPLink.API] [Lamp] device.send() Error: TCP Timeout
[1/23/2019, 11:07:52 AM] [TPLink] [Lamp] getColorTemperature
[1/23/2019, 11:07:52 AM] [TPLink] Error: TCP Timeout
at Timeout.setTimeout [as _onTimeout] (/Users/plasticrake/Code/homebridge-tplink-smarthome/node_modules/tplink-smarthome-api/lib/client.js:228:20)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
Same problem here. Lightbulbs with WiFi also connected to wall switch so if I kill power to the bulbs then we should be able to specify these as devices that may lose connection and to stop filling the screen logs with this kind of information. It may be useful to devices that are meant to be on 24/7 but sometimes they aren't (wifi lightbulbs, for example). Maybe different debug levels to defeat them?
Expected Behavior
I have a couple of TP Link LB130 Smart Bulbs that are frequently being turned off using a wall switch (an expected and supported behavior by the bulb). I expect that when they are powered off using a wall switch, the Homebridge would just ignore them, and continues to function.
Current Behavior
Currently, when the bulbs are powered off, the entire Homebridge integration is glitching, causing all devices to stay in "No Response" or "Updated" status.
The logs show:
Steps to Reproduce (for bugs)
Installed Homebridge on QNAP NAS using a Docker Container:
marcoraddatz/homebridge:latest
Configured all the plugins (see config section below) Powered off LB130 bulbs Opened iOS Home app, and see all components stuck in "No Response" state. (When the light bulbs are powered, everything works as expected)Versions
node --version
homebridge --version
Configuration
Homebridge Log / Command Output