Die Zwangstrennung war um 03:37 - danach hat er die Verbindung auch wieder aufgebaut. Habe gerade nochmal in der Fritzbox nachgeschaut, danach war von Seiten des ISP kein Abbruch mehr.
Spoiler2019-03-02 03:37:46.543 - error: iot.0 read ECONNRESET
2019-03-02 03:37:46.545 - info: iot.0 Connection changed: disconnect
2019-03-02 03:37:46.546 - info: iot.0 Connection lost
2019-03-02 03:37:50.806 - info: alexa2.0 Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2019-03-02 03:37:51.845 - info: iot.0 Connection changed: connect
2019-03-02 03:37:56.898 - info: alexa2.0 Alexa-Push-Connection established. Disable Polling
2019-03-02 03:38:04.955 - error: telegram.0 polling_error:EFATAL, EFATAL: Error: read ECONNRESET
2019-03-02 03:38:20.822 - info: alexa2.0 Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2019-03-02 03:38:26.708 - info: alexa2.0 Alexa-Push-Connection established. Disable Polling
2019-03-02 04:00:00.175 - info: host.bananapimaster instance system.adapter.ical.0 started with pid 25111
2019-03-02 04:00:05.225 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.15.0
2019-03-02 04:00:05.994 - info: ical.0 processing URL: Müllabfuhr
https://calendar.google.com/calendar/ical/iv3htfrk6ua9t038g9u35c02uo%40group.calendar.google.com/private-dee65d06cf0190e3c162d7f916e3ed0b/basic.ics
2019-03-02 04:00:07.228 - info: ical.0 processing URL: ItaloBrothers
https://calendar.google.com/calendar/ical/0ah106cilokm7mvs5i3v7cpm64%40group.calendar.google.com/private-a8dd673b0bad076698a352d940c2d828/basic.ics
2019-03-02 04:00:13.286 - info: host.bananapimaster instance system.adapter.ical.0 terminated with code 0 (OK)
2019-03-02 04:29:56.006 - error: sonoff.0 websocket error
2019-03-02 04:29:56.019 - error: sonoff.0 Error: websocket error
at WS.Transport.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:64:13)
at WebSocket.ws.onerror (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:150:10)
at WebSocket.onError (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:109:16)
at emitOne (events.js:116:13)
at WebSocket.emit (events.js:211:7)
at WebSocket.finalize (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:182:41)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:66:8)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
2019-03-02 05:04:00.081 - info: telegram.0 Scheduled restart.
2019-03-02 05:04:01.599 - info: telegram.0 terminating with timeout