Kasa node repeated error in debug log

[rakgupta]

I am seeing repeated errors in the debug log - "Polling error for 192.168.1.128: Error: TCP Socket Closed. segment:0 hadError:false". The node(s) and the device respond correctly and I can turn the plug on/off.

This is the only TP-Link device that I have and it is an HS-105 (Kasa Smart Wi-Fi Plug Mini).

To Reproduce I just installed the plug and was testing it - not sure why the error is being generated or how to replicate.

Expected behavior Debug log should be clean

Screenshots If applicable, add screenshots to help explain your problem

Desktop (please complete the following information):

• OS: [e.g. iOS] MacOS High Sierra (for node-red server), client MacOS Catalina
• Browser [e.g. chrome, safari] Safari
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[hufftheweevil]

That should only be displayed if Debug is selected in the config. In my experience, polling errors don't usually hamper control of the device. They do happen occasionally, sometimes in quick succession, but nothing to worry about. If it does become a problem affecting control, increase the poll intervals.