TPLink devices not responding

James Sentman james at sentman.com
Mon Apr 27 12:02:45 EDT 2020


Good morning Tom,

Are you running the most recent XTension build? I know that I did a couple of hot patches to things that got messed up during the release process and were not included but it should be 9.4.30 now. That included a fix for the TP-Link devices that fixed a problem where a discovery could start automatically and then be interrupted by a command to the device and then nothing would be found again. I can’t tell for sure from the log output you posted if thats the latest version or not. That might fix the problem.

If you just disable and re-enable the interface does that fix it even for a short time?

The app may or may not use the local connection method to talk to the device, or it may be going through the cloud but at least we know the device is actually on the wifi if that is able to talk to it. I would still unplug and replug the device to reboot it as well just for kicks.

I’ve also had trouble with some of these devices and my wifi router. This happens rarely but does happen. It will get into a state where it won’t renew their DHCP leases or they don’t renew them properly or something I’m not sure, but a reboot of the router clears that up, so you may want to try that as well. My router is approaching this state again now as I’m starting to get errors from some of the arduino based wifi device on my network, they just start dropping off and yet then can be re-connected to. A reboot of the router will fix that even without rebooting the devices I don’t know for sure why that is but it happens. 

The pinging interface line you see is not a ping to any of the devices, just XTension sending a packet to the plugin program and getting a reply back. When XTension hasn’t heard anything from an interface in a few minutes it will just throw it a ping to make sure it’s still running and hasn’t hung up. If it doesn’t respond it will assume the plugin process has hung and restart it. That does not seem to be the problem you’re having here though.

> On Apr 26, 2020, at 2:46 PM, Tom Yarmas <tom at yarmas.com> wrote:
> 
> I have only one TPLink duplex outlet.
> 
> I noticed it stopped working sometime, not sure when. What kind of troubleshooting should I be doing for it?
> 
> I can turn the outlets on/off with the Kasa App no problem.
> 
> When in debug mode, I see the following when I turn on one of the units in XTension:
> 4/26/20 2:24:25 PM  FR2: handling command from XTension:
> 4/26/20 2:24:25 PM  TPLink: addr=68:FF:7B:80:4E:0E.1
> 4/26/20 2:24:25 PM  TPLink: APfx=xt.tplink.outlet
> 4/26/20 2:24:25 PM  TPLink: mcmd=OFF
> 4/26/20 2:24:25 PM  TPLink: PkID=2089005054702
> 4/26/20 2:24:25 PM  TPLink: Discovering devices...
> 4/26/20 2:24:30 PM  TPLink: Discovering devices…
> 
> But the light plugged in to the outlet does nothing.
> 

Thanks,
 James


James Sentman                       http://www.PlanetaryGear.org		http://MacHomeAutomation.com




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20200427/1190d79a/attachment.html>


More information about the XTensionList mailing list