Just noticing this error today.
IP is locked, and when I manually hit the switch in HE it responds.
It did just miss its automation and gave me this error.
dev:582019-08-11 08:30:27.486 pm infoTP plug 4.2.01 TP plug: Power: off
dev:582019-08-11 08:30:10.375 pm warnError occured with UDP message: SocketTimeoutException: Receive timed out
dev:582019-08-11 08:30:10.362 pm errorTP plug 4.2.01 CommsError: Device Offline. The device is not found at the current IP address. Caused by either the IP changed or the device not having power. Check device for power. To update IP either run the Hubitat TP-Link App or updated preferences for a manual installation
has been on a static IP - yes.
When I click the HE switch it turns off, but it dropped the connection (only started happening today) right before the automation.
Thanks for the reply
What switch? I have been having similar issues with my HS300's (delayed response) when I try to do too much at one time. If you hit the devices too fast, they appear get lost and will not respond to a command.
It actually works. I just had one of my devices not respond to an "on" command. It auto repeated the command once and recovered. The delay was perceivable very short!
Nice work on the driver, I have bought two HS110 plugs and was easily able to add them to hubitat. I was iterested in seeing an attribute showing the current power usage, knowing that it would only be updated at best every minute. I wanted to use this on my dashboard and potentially in rules down the track. Should there be an attribute for this? If not, would it be hard to add?