search

arteck / ioBroker.hs100

iobroker tp-link hs100 intergration
MIT License
16 stars 14 forks source link

crashes with uncaught exception: TCP Timeout #59

Closed Garfonso closed 4 years ago

Garfonso commented 4 years ago 
2020-04-20 23:24:24.177  - error: host.Server Caught by controller[4]: [HasenLampe] device.send() Error: TCP Timeout
2020-04-20 23:24:24.177  - error: host.Server Caught by controller[4]:     at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/client.js:226:20)
2020-04-20 23:24:24.177  - error: host.Server Caught by controller[4]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:24:24.177  - error: host.Server Caught by controller[4]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:24:24.177  - error: host.Server Caught by controller[5]: TCP Timeout
2020-04-20 23:24:24.177  - error: host.Server Caught by controller[5]: TCP Timeout

Probably related to js-controller 3 being more restrictive with uncaught errors / rejections.

I'm not 100% sure if that is not an issue with tplink-smarthome-api. I tried updating the depencency to 2.0.0, which did not cause additional trouble but also did not solve the issue. Error log then changed to this one:

2020-04-20 23:54:38.029  - error: hs100.0 (11031) uncaught exception: TCP Timeout
2020-04-20 23:54:38.030  - error: hs100.0 (11031) Error: TCP Timeout
    at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.031  - info: hs100.0 (11031) terminating
2020-04-20 23:54:38.031  - info: hs100.0 (11031) Terminated (NO_ERROR): Without reason
2020-04-20 23:54:38.662  - error: host.Server Caught by controller[0]: TCP HS110-Deko3:9999 Error: connect EHOSTUNREACH 192.168.0.184:9999
2020-04-20 23:54:38.662  - error: host.Server Caught by controller[0]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
2020-04-20 23:54:38.662  - error: host.Server Caught by controller[0]:   errno: 'EHOSTUNREACH',
2020-04-20 23:54:38.662  - error: host.Server Caught by controller[0]:   code: 'EHOSTUNREACH',
2020-04-20 23:54:38.662  - error: host.Server Caught by controller[0]:   syscall: 'connect',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[0]:   address: '192.168.0.184',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[0]:   port: 9999
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[0]: }
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[1]: TCP HS110-Deko2:9999 Error: connect EHOSTUNREACH 192.168.0.183:9999
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[1]:   errno: 'EHOSTUNREACH',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[1]:   code: 'EHOSTUNREACH',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[1]:   syscall: 'connect',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[1]:   address: '192.168.0.183',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[1]:   port: 9999
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[1]: }
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[2]: TCP HS110-Deko1:9999 Error: connect EHOSTUNREACH 192.168.0.182:9999
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[2]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[2]:   errno: 'EHOSTUNREACH',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[2]:   code: 'EHOSTUNREACH',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[2]:   syscall: 'connect',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[2]:   address: '192.168.0.182',
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[2]:   port: 9999
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[2]: }
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[3]: TCP WohnzimmerCouchLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[3]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[3]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[3]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[4]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[4]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[4]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[4]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[5]: TCP WohnzimmerCouchLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[5]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[5]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[5]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[6]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[6]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[6]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[6]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[7]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[7]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[7]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[7]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[8]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[8]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[8]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[8]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[9]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[9]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[9]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[9]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[10]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[10]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[10]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[10]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[11]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663  - error: host.Server Caught by controller[11]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.664  - error: host.Server Caught by controller[11]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.664  - error: host.Server Caught by controller[11]:     at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.664  - info: host.Server instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
arteck commented 4 years ago

check new version

Black-Thunder commented 4 years ago

Installed v1.1.2, but I'm still experiencing the same exceptions and adapter crashes: 

2020-04-28 17:33:06.754 - error: hs100.0 (32328) uncaught exception: TCP Timeout
2020-04-28 17:33:06.755 - error: hs100.0 (32328) Error: TCP Timeout
at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/client.js:226:20)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
2020-04-28 17:33:06.758 - error: hs100.0 (32328) uncaught exception: TCP Timeout
2020-04-28 17:33:06.758 - error: hs100.0 (32328) Error: TCP Timeout
at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/client.js:226:20)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
2020-04-28 17:33:06.771 - info: hs100.0 (32328) terminating
2020-04-28 17:33:06.772 - info: hs100.0 (32328) Terminated (NO_ERROR): Without reason
2020-04-28 17:33:07.342 - error: host.raspberrypi Caught by controller[1]: TCP Timeout
2020-04-28 17:33:07.343 - error: host.raspberrypi Caught by controller[2]: [Terrarium Nepenthes] device.send() Error: TCP Timeout
2020-04-28 17:33:07.343 - error: host.raspberrypi Caught by controller[2]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/client.js:226:20)
2020-04-28 17:33:07.344 - error: host.raspberrypi Caught by controller[2]: at listOnTimeout (internal/timers.js:549:17)
2020-04-28 17:33:07.344 - error: host.raspberrypi Caught by controller[2]: at processTimers (internal/timers.js:492:7)
2020-04-28 17:33:07.344 - error: host.raspberrypi Caught by controller[3]: TCP Timeout
2020-04-28 17:33:07.345 - error: host.raspberrypi Caught by controller[4]: [Terrarium Nepenthes] device.send() Error: TCP Timeout
2020-04-28 17:33:07.345 - error: host.raspberrypi Caught by controller[4]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/client.js:226:20)
2020-04-28 17:33:07.345 - error: host.raspberrypi Caught by controller[4]: at listOnTimeout (internal/timers.js:549:17)
2020-04-28 17:33:07.345 - error: host.raspberrypi Caught by controller[4]: at processTimers (internal/timers.js:492:7)
2020-04-28 17:33:07.346 - info: host.raspberrypi instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
2020-04-28 17:33:07.346 - info: host.raspberrypi Restart adapter system.adapter.hs100.0 because enabled
2020-04-28 17:33:37.477 - info: host.raspberrypi instance system.adapter.hs100.0 started with pid 5389
2020-04-28 17:33:38.771 - info: hs100.0 (5389) starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.hs100, node: v12.16.2, js-controller: 3.0.20

2020-04-28 19:28:27.193 - error: hs100.0 (32315) uncaught exception: TCP Timeout
2020-04-28 19:28:27.195 - error: hs100.0 (32315) Error: TCP Timeout
at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/client.js:226:20)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
2020-04-28 19:28:27.224 - info: hs100.0 (32315) terminating
2020-04-28 19:28:27.226 - info: hs100.0 (32315) Terminated (NO_ERROR): Without reason
2020-04-28 19:28:27.753 - error: host.raspberrypi Caught by controller[1]: TCP Timeout
2020-04-28 19:28:27.753 - error: host.raspberrypi Caught by controller[2]: [Aquarium Gang CO2] device.send() Error: TCP Timeout
2020-04-28 19:28:27.753 - error: host.raspberrypi Caught by controller[2]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/client.js:226:20)
2020-04-28 19:28:27.754 - error: host.raspberrypi Caught by controller[2]: at listOnTimeout (internal/timers.js:549:17)
2020-04-28 19:28:27.754 - error: host.raspberrypi Caught by controller[2]: at processTimers (internal/timers.js:492:7)
2020-04-28 19:28:27.754 - error: host.raspberrypi Caught by controller[3]: TCP Timeout
2020-04-28 19:28:27.754 - error: host.raspberrypi Caught by controller[3]: TCP Timeout
2020-04-28 19:28:27.754 - error: host.raspberrypi Caught by controller[3]: TCP Timeout
2020-04-28 19:28:27.754 - info: host.raspberrypi instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
Black-Thunder commented 4 years ago

Seems to be a bug in the tplink-smarthome-api which hasn't been fixed yet: https://github.com/plasticrake/tplink-smarthome-api/issues/71

I've applied the mentioned workaround there on my local system. So far I haven't had any adapter crashes anymore.

Update: Unfortunately, a few hours later I still got some uncaught exceptions...

Garfonso commented 4 years ago

Seems to be a bug in the tplink-smarthome-api which hasn't been fixed yet: plasticrake/tplink-smarthome-api#71

I've applied the mentioned workaround there on my local system. So far I haven't had any adapter crashes anymore.

Update: Unfortunately, a few hours later I still got some uncaught exceptions...

Can you post a log of them?

Also, are you sure you edited the right file? I (as so often) have tplink-smarthome-api installed in iobroker/node_modules and also in iobroker/node_modules/iobroker.hs100/node_modules and I first changed the first one and then saw it used the second one (which I did not see at first)... I now also edited the second one and will see..

But you might be right. The fix is in startPolling, but I see a crash in getDevice:

2020-04-29 10:42:15.605  - error: hs100.0 (25794) uncaught exception: TCP Timeout
2020-04-29 10:42:15.606  - error: hs100.0 (25794) Error: TCP Timeout
    at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/client.js:226:20)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)
2020-04-29 10:42:15.609  - info: hs100.0 (25794) terminating
2020-04-29 10:42:15.610  - info: hs100.0 (25794) Terminated (NO_ERROR): Without reason
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[0]: TCP Timeout
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[1]: [HWRWaschmaschine] device.send() Error: TCP Timeout
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[1]:     at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/client.js:226:20)
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[1]:     at listOnTimeout (internal/timers.js:549:17)
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[1]:     at processTimers (internal/timers.js:492:7)
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[2]: TCP Timeout
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[3]: TCP Timeout
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[3]: TCP Timeout
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[3]: TCP Timeout
2020-04-29 10:42:16.256  - error: host.Server Caught by controller[3]: TCP Timeout
Black-Thunder commented 4 years ago

On my system tp-link-smarthome-api is only located at "/opt/iobroker/node_modules". There is no second installation in "/opt/iobroker/node_modules/iobroker.hs100/node_modules" (doesn't exist).

I've directly edited the file "/opt/iobroker/node_modules/tplink-smarthome-api/lib/device/index.js" and didn't notice any change. Do I need to do anything else apart from editing the file for the change to take effect?

Garfonso commented 4 years ago

You probably need to restart the adapter (or iobroker, if you are using compact mode).

I did not see the crash yet, after 2 1/2 hours with the fix in the right place. I even added my not connected plugs back into the config and they do not cause trouble anymore. I'll keep an eye out.

But can you post a log from your crash?

Black-Thunder commented 4 years ago

As already posted above, the log looks like this:

2020-04-29 13:09:06.562 - error: hs100.0 (29621) uncaught exception: TCP Timeout
2020-04-29 13:09:06.568 - error: hs100.0 (29621) Error: TCP Timeout
at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/client.js:226:20)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
2020-04-29 13:09:06.730 - info: hs100.0 (29621) terminating
2020-04-29 13:09:06.732 - info: hs100.0 (29621) Terminated (NO_ERROR): Without reason
2020-04-29 13:09:07.295 - error: host.raspberrypi Caught by controller[1]: TCP Timeout
2020-04-29 13:09:07.296 - error: host.raspberrypi Caught by controller[1]: TCP Timeout
2020-04-29 13:09:07.296 - error: host.raspberrypi Caught by controller[2]: TCP Timeout
2020-04-29 13:09:07.297 - error: host.raspberrypi Caught by controller[3]: TCP Timeout
2020-04-29 13:09:07.297 - error: host.raspberrypi Caught by controller[3]: TCP Timeout
2020-04-29 13:09:07.298 - error: host.raspberrypi Caught by controller[4]: TCP Timeout
2020-04-29 13:09:07.298 - error: host.raspberrypi Caught by controller[5]: TCP Timeout
2020-04-29 13:09:07.298 - error: host.raspberrypi Caught by controller[6]: TCP Timeout
2020-04-29 13:09:07.298 - error: host.raspberrypi Caught by controller[7]: TCP Timeout
2020-04-29 13:09:07.299 - error: host.raspberrypi Caught by controller[8]: TCP Timeout
2020-04-29 13:09:07.299 - error: host.raspberrypi Caught by controller[9]: TCP Timeout
2020-04-29 13:09:07.299 - error: host.raspberrypi Caught by controller[9]: TCP Timeout
2020-04-29 13:09:07.300 - error: host.raspberrypi Caught by controller[10]: TCP Timeout
2020-04-29 13:09:07.300 - error: host.raspberrypi Caught by controller[10]: TCP Timeout
2020-04-29 13:09:07.300 - error: host.raspberrypi Caught by controller[10]: TCP Timeout
2020-04-29 13:09:07.301 - error: host.raspberrypi Caught by controller[11]: TCP Timeout
2020-04-29 13:09:07.301 - error: host.raspberrypi Caught by controller[11]: TCP Timeout
2020-04-29 13:09:07.301 - error: host.raspberrypi Caught by controller[11]: [Terrarium Nepenthes] device.send() Error: TCP Timeout
2020-04-29 13:09:07.302 - error: host.raspberrypi Caught by controller[11]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/client.js:226:20)
2020-04-29 13:09:07.302 - error: host.raspberrypi Caught by controller[11]: at listOnTimeout (internal/timers.js:549:17)
2020-04-29 13:09:07.302 - error: host.raspberrypi Caught by controller[11]: at processTimers (internal/timers.js:492:7)
2020-04-29 13:09:07.302 - error: host.raspberrypi Caught by controller[11]: TCP Timeout
2020-04-29 13:09:07.303 - error: host.raspberrypi Caught by controller[11]: TCP Timeout
2020-04-29 13:09:07.303 - info: host.raspberrypi instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
2020-04-29 13:09:07.303 - info: host.raspberrypi Restart adapter system.adapter.hs100.0 because enabled
2020-04-29 13:09:37.363 - info: host.raspberrypi instance system.adapter.hs100.0 started with pid 6171
2020-04-29 13:09:38.434 - info: hs100.0 (6171) starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.hs100, node: v12.16.2, js-controller: 3.0.20
Garfonso commented 4 years ago

Ok, so you still get the same errors.. hm. Strange.

I really can not see where there is an error there that is not caught... :-(

Black-Thunder commented 4 years ago

Yep, seems strange.

As a quick and dirty approach, I've commented out the line which triggers the Promise.reject() (tplink-smarthome-api/lib/client.js:226): 

.....
        if (timeout > 0) {
          timer = setTimeout(() => {
            this.log.debug(`[${socketId}] client.sendTcp(): timeout(${timeout})`);
            this.log.error('TCP Timeout');
            socket.destroy();
            //reject(new Error('TCP Timeout')); // THIS LINE
          }, timeout);
        }
.....

So far I haven't had any crashes or exceptions during the last 3 hours. Of course that's not a real fix, but for now the adapter seems to be reliable and stable again.

Garfonso commented 4 years ago

Hi,

I tried the same modification but I get a different error, now:

2020-04-30 19:24:50.509  - error: hs100.0 (4160) uncaught exception: TCP Socket Closed. segment:0 hadError:false
2020-04-30 19:24:50.510  - error: hs100.0 (4160) Error: TCP Socket Closed. segment:0 hadError:false
    at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
    at Object.onceWrapper (events.js:417:26)
    at Socket.emit (events.js:310:20)
    at TCP.<anonymous> (net.js:672:12)
2020-04-30 19:24:50.511  - info: hs100.0 (4160) terminating
2020-04-30 19:24:50.512  - info: hs100.0 (4160) Terminated (NO_ERROR): Without reason

I still do not really get why those errors are not caught by the .catch statement. As far as I can see all methods return promises and all throws are inside of these promises (so a throw should be converted into promise.reject which will be handeld by promise.catch)...

arteck commented 4 years ago

@Garfonso also with 1.1.5 version ??

Black-Thunder commented 4 years ago

Still getting frequent crashes and exceptions in the log with v1.1.5:

hs100.0 2020-05-11 08:37:05.498 info (2030) Terminated (NO_ERROR): Without reason
hs100.0 2020-05-11 08:37:05.496 info (2030) terminating
hs100.0 2020-05-11 08:37:05.396 error at processTimers (internal/timers.js:492:7)
hs100.0 2020-05-11 08:37:05.396 error at listOnTimeout (internal/timers.js:549:17)
hs100.0 2020-05-11 08:37:05.396 error at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
hs100.0 2020-05-11 08:37:05.396 error (2030) Error: TCP Timeout
hs100.0 2020-05-11 08:37:05.395 error (2030) unhandled promise rejection: TCP Timeout
hs100.0 2020-05-11 08:34:24.386 info (2030) starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.hs100, node: v12.16.3, js-controller: 3.1.4
hs100.0 2020-05-11 08:48:55.606 info (26259) Terminated (NO_ERROR): Without reason
hs100.0 2020-05-11 08:48:55.603 info (26259) terminating
hs100.0 2020-05-11 08:48:55.579 error (26259) Error: TCP Timeout at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22) at listOnTimeout (internal/timers.js:549:17) at processTi
hs100.0 2020-05-11 08:48:55.577 error (26259) unhandled promise rejection: TCP Timeout
hs100.0 2020-05-11 08:48:55.575 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
hs100.0 2020-05-11 08:48:03.807 info (26259) starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.hs100, node: v12.16.3, js-controller: 3.1.4

2020-05-11 08:50:24.449 - info: hs100.0 (28814) terminating 2020-05-11 08:50:24.451 - info: hs100.0 (28814) Terminated (NO_ERROR): Without reason 2020-05-11 08:50:24.970 - error: host.raspberrypi Caught by controller[1]: TCP 192.168.150.56:9999 Error: connect EHOSTUNREACH 192.168.150.56:9999 2020-05-11 08:50:24.971 - error: host.raspberrypi Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) { 2020-05-11 08:50:24.971 - error: host.raspberrypi Caught by controller[1]: errno: 'EHOSTUNREACH', 2020-05-11 08:50:24.971 - error: host.raspberrypi Caught by controller[1]: code: 'EHOSTUNREACH', 2020-05-11 08:50:24.972 - error: host.raspberrypi Caught by controller[1]: syscall: 'connect', 2020-05-11 08:50:24.972 - error: host.raspberrypi Caught by controller[1]: address: '192.168.150.56', 2020-05-11 08:50:24.972 - error: host.raspberrypi Caught by controller[1]: port: 9999 2020-05-11 08:50:24.972 - error: host.raspberrypi Caught by controller[1]: } 2020-05-11 08:50:24.972 - error: host.raspberrypi Caught by controller[2]: TCP 123.456.78.99:9999 Error: getaddrinfo ENOTFOUND 123.456.78.99 2020-05-11 08:50:24.972 - error: host.raspberrypi Caught by controller[2]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:64:26) { 2020-05-11 08:50:24.972 - error: host.raspberrypi Caught by controller[2]: errno: 'ENOTFOUND', 2020-05-11 08:50:24.972 - error: host.raspberrypi Caught by controller[2]: code: 'ENOTFOUND', 2020-05-11 08:50:24.973 - error: host.raspberrypi Caught by controller[2]: syscall: 'getaddrinfo', 2020-05-11 08:50:24.973 - error: host.raspberrypi Caught by controller[2]: hostname: '123.456.78.99' 2020-05-11 08:50:24.973 - error: host.raspberrypi Caught by controller[2]: } 2020-05-11 08:50:24.973 - error: host.raspberrypi Caught by controller[3]: TCP 192.168.150.56:9999 Error: connect EHOSTUNREACH 192.168.150.56:9999 2020-05-11 08:50:24.973 - error: host.raspberrypi Caught by controller[3]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) { 2020-05-11 08:50:24.973 - error: host.raspberrypi Caught by controller[3]: errno: 'EHOSTUNREACH', 2020-05-11 08:50:24.973 - error: host.raspberrypi Caught by controller[3]: code: 'EHOSTUNREACH', 2020-05-11 08:50:24.973 - error: host.raspberrypi Caught by controller[3]: syscall: 'connect', 2020-05-11 08:50:24.974 - error: host.raspberrypi Caught by controller[3]: address: '192.168.150.56', 2020-05-11 08:50:24.974 - error: host.raspberrypi Caught by controller[3]: port: 9999 2020-05-11 08:50:24.974 - error: host.raspberrypi Caught by controller[3]: } 2020-05-11 08:50:24.974 - error: host.raspberrypi Caught by controller[4]: TCP 123.456.78.99:9999 Error: getaddrinfo ENOTFOUND 123.456.78.99 2020-05-11 08:50:24.974 - error: host.raspberrypi Caught by controller[4]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:64:26) { 2020-05-11 08:50:24.974 - error: host.raspberrypi Caught by controller[4]: errno: 'ENOTFOUND', 2020-05-11 08:50:24.974 - error: host.raspberrypi Caught by controller[4]: code: 'ENOTFOUND', 2020-05-11 08:50:24.974 - error: host.raspberrypi Caught by controller[4]: syscall: 'getaddrinfo', 2020-05-11 08:50:24.975 - error: host.raspberrypi Caught by controller[4]: hostname: '123.456.78.99' 2020-05-11 08:50:24.975 - error: host.raspberrypi Caught by controller[4]: } 2020-05-11 08:50:24.975 - error: host.raspberrypi Caught by controller[5]: TCP 192.168.150.56:9999 Error: connect EHOSTUNREACH 192.168.150.56:9999 2020-05-11 08:50:24.975 - error: host.raspberrypi Caught by controller[5]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) { 2020-05-11 08:50:24.975 - error: host.raspberrypi Caught by controller[5]: errno: 'EHOSTUNREACH', 2020-05-11 08:50:24.975 - error: host.raspberrypi Caught by controller[5]: code: 'EHOSTUNREACH', 2020-05-11 08:50:24.975 - error: host.raspberrypi Caught by controller[5]: syscall: 'connect', 2020-05-11 08:50:24.976 - error: host.raspberrypi Caught by controller[5]: address: '192.168.150.56', 2020-05-11 08:50:24.976 - error: host.raspberrypi Caught by controller[5]: port: 9999 2020-05-11 08:50:24.976 - error: host.raspberrypi Caught by controller[5]: } 2020-05-11 08:50:24.976 - error: host.raspberrypi Caught by controller[6]: TCP 123.456.78.99:9999 Error: getaddrinfo ENOTFOUND 123.456.78.99 2020-05-11 08:50:24.976 - error: host.raspberrypi Caught by controller[6]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:64:26) { 2020-05-11 08:50:24.976 - error: host.raspberrypi Caught by controller[6]: errno: 'ENOTFOUND', 2020-05-11 08:50:24.976 - error: host.raspberrypi Caught by controller[6]: code: 'ENOTFOUND', 2020-05-11 08:50:24.976 - error: host.raspberrypi Caught by controller[6]: syscall: 'getaddrinfo', 2020-05-11 08:50:24.977 - error: host.raspberrypi Caught by controller[6]: hostname: '123.456.78.99' 2020-05-11 08:50:24.977 - error: host.raspberrypi Caught by controller[6]: } 2020-05-11 08:50:24.977 - error: host.raspberrypi Caught by controller[7]: TCP 192.168.150.56:9999 Error: connect EHOSTUNREACH 192.168.150.56:9999 2020-05-11 08:50:24.977 - error: host.raspberrypi Caught by controller[7]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) { 2020-05-11 08:50:24.977 - error: host.raspberrypi Caught by controller[7]: errno: 'EHOSTUNREACH', 2020-05-11 08:50:24.977 - error: host.raspberrypi Caught by controller[7]: code: 'EHOSTUNREACH', 2020-05-11 08:50:24.977 - error: host.raspberrypi Caught by controller[7]: syscall: 'connect', 2020-05-11 08:50:24.977 - error: host.raspberrypi Caught by controller[7]: address: '192.168.150.56', 2020-05-11 08:50:24.978 - error: host.raspberrypi Caught by controller[7]: port: 9999 2020-05-11 08:50:24.978 - error: host.raspberrypi Caught by controller[7]: } 2020-05-11 08:50:24.978 - error: host.raspberrypi Caught by controller[8]: TCP 123.456.78.99:9999 Error: getaddrinfo ENOTFOUND 123.456.78.99 2020-05-11 08:50:24.978 - error: host.raspberrypi Caught by controller[8]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:64:26) { 2020-05-11 08:50:24.978 - error: host.raspberrypi Caught by controller[8]: errno: 'ENOTFOUND', 2020-05-11 08:50:24.978 - error: host.raspberrypi Caught by controller[8]: code: 'ENOTFOUND', 2020-05-11 08:50:24.978 - error: host.raspberrypi Caught by controller[8]: syscall: 'getaddrinfo', 2020-05-11 08:50:24.978 - error: host.raspberrypi Caught by controller[8]: hostname: '123.456.78.99' 2020-05-11 08:50:24.979 - error: host.raspberrypi Caught by controller[8]: } 2020-05-11 08:50:24.979 - error: host.raspberrypi Caught by controller[9]: TCP 192.168.150.56:9999 Error: connect EHOSTUNREACH 192.168.150.56:9999 2020-05-11 08:50:24.979 - error: host.raspberrypi Caught by controller[9]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) { 2020-05-11 08:50:24.979 - error: host.raspberrypi Caught by controller[9]: errno: 'EHOSTUNREACH', 2020-05-11 08:50:24.979 - error: host.raspberrypi Caught by controller[9]: code: 'EHOSTUNREACH', 2020-05-11 08:50:24.979 - error: host.raspberrypi Caught by controller[9]: syscall: 'connect', 2020-05-11 08:50:24.979 - error: host.raspberrypi Caught by controller[9]: address: '192.168.150.56', 2020-05-11 08:50:24.979 - error: host.raspberrypi Caught by controller[9]: port: 9999 2020-05-11 08:50:24.980 - error: host.raspberrypi Caught by controller[9]: } 2020-05-11 08:50:24.980 - error: host.raspberrypi Caught by controller[10]: TCP 123.456.78.99:9999 Error: getaddrinfo ENOTFOUND 123.456.78.99 2020-05-11 08:50:24.980 - error: host.raspberrypi Caught by controller[10]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:64:26) { 2020-05-11 08:50:24.980 - error: host.raspberrypi Caught by controller[10]: errno: 'ENOTFOUND', 2020-05-11 08:50:24.980 - error: host.raspberrypi Caught by controller[10]: code: 'ENOTFOUND', 2020-05-11 08:50:24.980 - error: host.raspberrypi Caught by controller[10]: syscall: 'getaddrinfo', 2020-05-11 08:50:24.980 - error: host.raspberrypi Caught by controller[10]: hostname: '123.456.78.99' 2020-05-11 08:50:24.980 - error: host.raspberrypi Caught by controller[10]: } 2020-05-11 08:50:24.981 - error: host.raspberrypi Caught by controller[11]: TCP 192.168.150.56:9999 Error: connect EHOSTUNREACH 192.168.150.56:9999 2020-05-11 08:50:24.981 - error: host.raspberrypi Caught by controller[11]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) { 2020-05-11 08:50:24.981 - error: host.raspberrypi Caught by controller[11]: errno: 'EHOSTUNREACH', 2020-05-11 08:50:24.981 - error: host.raspberrypi Caught by controller[11]: code: 'EHOSTUNREACH', 2020-05-11 08:50:24.981 - error: host.raspberrypi Caught by controller[11]: syscall: 'connect', 2020-05-11 08:50:24.981 - error: host.raspberrypi Caught by controller[11]: address: '192.168.150.56', 2020-05-11 08:50:24.981 - error: host.raspberrypi Caught by controller[11]: port: 9999 2020-05-11 08:50:24.981 - error: host.raspberrypi Caught by controller[11]: } 2020-05-11 08:50:24.982 - error: host.raspberrypi Caught by controller[12]: TCP 123.456.78.99:9999 Error: getaddrinfo ENOTFOUND 123.456.78.99 2020-05-11 08:50:24.982 - error: host.raspberrypi Caught by controller[12]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:64:26) { 2020-05-11 08:50:24.982 - error: host.raspberrypi Caught by controller[12]: errno: 'ENOTFOUND', 2020-05-11 08:50:24.982 - error: host.raspberrypi Caught by controller[12]: code: 'ENOTFOUND', 2020-05-11 08:50:24.982 - error: host.raspberrypi Caught by controller[12]: syscall: 'getaddrinfo', 2020-05-11 08:50:24.982 - error: host.raspberrypi Caught by controller[12]: hostname: '123.456.78.99' 2020-05-11 08:50:24.982 - error: host.raspberrypi Caught by controller[12]: } 2020-05-11 08:50:24.982 - error: host.raspberrypi Caught by controller[13]: TCP 192.168.150.48:9999 Error: TCP Timeout 2020-05-11 08:50:24.983 - error: host.raspberrypi Caught by controller[13]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22) 2020-05-11 08:50:24.983 - error: host.raspberrypi Caught by controller[13]: at listOnTimeout (internal/timers.js:549:17) 2020-05-11 08:50:24.983 - error: host.raspberrypi Caught by controller[13]: at processTimers (internal/timers.js:492:7) 2020-05-11 08:50:24.983 - info: host.raspberrypi instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR) 2020-05-11 08:50:24.983 - info: host.raspberrypi Restart adapter system.adapter.hs100.0 because enabled

Garfonso commented 4 years ago

Ja, das hab ich mit 1.1.5 auch immer noch, leider... 🙁

dmw02 commented 4 years ago

Version 1.1.6 Fehler ist noch da.

hs100.0 2020-05-31 22:04:05.142 info (2344) starting. Version 1.1.6 in /opt/iobroker/node_modules/iobroker.hs100, node: v10.20.1, js-controller: 3.1.4
host.raspberrypi 2020-05-31 22:03:51.660 info instance system.adapter.hs100.0 started with pid 2344
host.raspberrypi 2020-05-31 22:03:20.238 info Restart adapter system.adapter.hs100.0 because enabled
host.raspberrypi 2020-05-31 22:03:20.238 info instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
host.raspberrypi 2020-05-31 22:03:20.238 error Caught by controller[26]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.238 error Caught by controller[25]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.238 error Caught by controller[24]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.237 error Caught by controller[23]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.237 error Caught by controller[22]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.237 error Caught by controller[22]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.237 error Caught by controller[22]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.237 error Caught by controller[21]: TCP 192.168.1.141:9999 Error: connect EHOSTUNREACH 192.168.1.141:9999
host.raspberrypi 2020-05-31 22:03:20.237 error Caught by controller[20]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.237 error Caught by controller[19]: TCP 192.168.1.141:9999 Error: connect EHOSTUNREACH 192.168.1.141:9999
host.raspberrypi 2020-05-31 22:03:20.236 error Caught by controller[18]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.236 error Caught by controller[18]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.236 error Caught by controller[18]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.236 error Caught by controller[17]: TCP 192.168.1.141:9999 Error: connect EHOSTUNREACH 192.168.1.141:9999
host.raspberrypi 2020-05-31 22:03:20.236 error Caught by controller[16]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.236 error Caught by controller[15]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.236 error Caught by controller[14]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.236 error Caught by controller[13]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.235 error Caught by controller[12]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.235 error Caught by controller[11]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.235 error Caught by controller[10]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.235 error Caught by controller[10]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.234 error Caught by controller[9]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.234 error Caught by controller[9]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.234 error Caught by controller[8]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.234 error Caught by controller[7]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.234 error Caught by controller[6]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.234 error Caught by controller[5]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.234 error Caught by controller[4]: TCP 192.168.1.141:9999 Error: connect EHOSTUNREACH 192.168.1.141:9999
host.raspberrypi 2020-05-31 22:03:20.233 error Caught by controller[3]: TCP 192.168.1.141:9999 Error: connect EHOSTUNREACH 192.168.1.141:9999
host.raspberrypi 2020-05-31 22:03:20.233 error Caught by controller[2]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.233 error Caught by controller[1]: TCP 192.168.1.141:9999 Error: connect EHOSTUNREACH 192.168.1.141:9999
host.raspberrypi 2020-05-31 22:03:20.233 error Caught by controller[1]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.232 error Caught by controller[1]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.232 error Caught by controller[1]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.232 error Caught by controller[1]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.232 error Caught by controller[1]: TCP 192.168.1.141:9999 Error: connect EHOSTUNREACH 192.168.1.141:9999
host.raspberrypi 2020-05-31 22:03:20.232 error Caught by controller[1]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.232 error Caught by controller[1]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.231 error Caught by controller[1]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.231 error Caught by controller[1]: TCP 192.168.1.139:9999 Error: TCP Timeout
host.raspberrypi 2020-05-31 22:03:20.230 error Caught by controller[1]: TCP 192.168.1.139:9999 Error: TCP Timeout
hs100.0 2020-05-31 22:03:19.692 info (26907) Terminated (NO_ERROR): Without reason
hs100.0 2020-05-31 22:03:19.691 info (26907) terminating
hs100.0 2020-05-31 22:03:19.684 error at Timer.processTimers (timers.js:223:10)
hs100.0 2020-05-31 22:03:19.684 error at listOnTimeout (timers.js:263:5)
hs100.0 2020-05-31 22:03:19.684 error at tryOnTimeout (timers.js:300:5)
hs100.0 2020-05-31 22:03:19.684 error at ontimeout (timers.js:436:11)
hs100.0 2020-05-31 22:03:19.684 error at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
hs100.0 2020-05-31 22:03:19.684 error (26907) Error: TCP Timeout
hs100.0 2020-05-31 22:03:19.683 error (26907) unhandled promise rejection: TCP Timeout
Unhandled 2020-05-31 22:03:19.682 error promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
arteck commented 4 years ago

neue version 2.0.0

Garfonso commented 4 years ago

Jup scheint damit zu gehen.

Garfonso commented 4 years ago

Ich war ein bisschen zu optimistisch. Heute passiert es wieder:

2020-06-15 16:21:24.698  - warn: hs100.0 (8665) getDevice Socket connection Timeout : WohnzimmerHasenLampe
2020-06-15 16:21:26.024  - error: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2020-06-15 16:21:26.025  - error: hs100.0 (8665) unhandled promise rejection: TCP Timeout
2020-06-15 16:21:26.025  - error: hs100.0 (8665) Error: TCP Timeout
    at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)
2020-06-15 16:21:26.025  - info: hs100.0 (8665) cleaned everything up...
2020-06-15 16:21:26.027  - info: hs100.0 (8665) terminating
2020-06-15 16:21:26.027  - info: hs100.0 (8665) Terminated (NO_ERROR): Without reason
2020-06-15 16:21:26.665  - error: host.Server Caught by controller[1]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-06-15 16:21:26.665  - error: host.Server Caught by controller[1]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-06-15 16:21:26.665  - error: host.Server Caught by controller[1]:     at listOnTimeout (internal/timers.js:549:17)
2020-06-15 16:21:26.665  - error: host.Server Caught by controller[1]:     at processTimers (internal/timers.js:492:7)
2020-06-15 16:21:26.665  - error: host.Server Caught by controller[2]: TCP WohnzimmerBaerenkette:9999 Error: TCP Timeout
2020-06-15 16:21:26.665  - error: host.Server Caught by controller[2]:     at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-06-15 16:21:26.665  - error: host.Server Caught by controller[2]:     at listOnTimeout (internal/timers.js:549:17)
2020-06-15 16:21:26.665  - error: host.Server Caught by controller[2]:     at processTimers (internal/timers.js:492:7)
2020-06-15 16:21:26.665  - info: host.Server instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
2020-06-15 16:21:26.665  - info: host.Server Restart adapter system.adapter.hs100.0 because enabled