Node red errors occur when kasa device is off

[grumpazoid]

I have a Kasa KL110B bulb and am running node red 1.2.9 on raspberry pi 3b.

Problem 1 If the Kasa bulb is powered off (at the mains) when node red starts I get an error generated in the console. Even if the bulb is then switched on, the Kasa node does not work until node red is restarted.

TCP 192.168.20.17:9999 Error: TCP Timeout after 1000ms 192.168.20.17:9999 {"system":{"get_sysinfo":{}}} at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:59:36) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7)

Problem 2 If the bulb is switched on when node red starts but is then powered off (at the mains), lots of errors are generated in the console as follows:

TCP 192.168.20.17:9999 Error: TCP Timeout after 1000ms 192.168.20.17:9999 {"smartlife.iot.common.emeter":{"get_realtime":{}},"smartlife.iot.smartbulb.lightingservice":{"get_light_state":{}},"smartlife.iot.common.schedule":{"get_next_action":{}},"system":{"get_sysinfo":{}},"smartlife.iot.common.cloud":{"get_info":{}}} at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:59:36) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7) [Kasa1] device.send() Error: TCP Timeout after 1000ms 192.168.20.17:9999 {"smartlife.iot.common.emeter":{"get_realtime":{}},"smartlife.iot.smartbulb.lightingservice":{"get_light_state":{}},"smartlife.iot.common.schedule":{"get_next_action":{}},"system":{"get_sysinfo":{}},"smartlife.iot.common.cloud":{"get_info":{}}} at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:59:36) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7)

The bulb is able to be controlled fine at all times via the Kasa app and via alexa app / echo device.