Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum
donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. MiHome/Alexa Log-Error AddMembership/Alexa-Push-Connection

NEWS

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    695
  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    10
    1
    534
  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    1.1k

MiHome/Alexa Log-Error AddMembership/Alexa-Push-Connection

Geplant Angeheftet Gesperrt Verschoben Ungelöst Error/Bug
mihomealexa 2.0log meldung
3 Beiträge 3 Kommentatoren 350 Aufrufe 2 Beobachtet
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • T Offline
    T Offline
    Tottbeck
    schrieb am zuletzt editiert von Tottbeck
    #1
    Systemdata
    Hardwaresystem: Pi3
    Arbeitsspeicher: 1GB
    Festplattenart: SD-Karte
    Betriebssystem: Ubuntu
    Node-Version: 10.20.1
    Nodejs-Version: 10.20.1x
    NPM-Version: 6.14.5
    Installationsart: Skript
    Image genutzt: Nein

    Hallo, ich bekommen folgende Fehler in meinem iobroker-log (teilweise auch im syslog).
    Das fängt plötzlich an, das System ist dann kaum noch ansprechbar. Nach einem reboot ist (erstmal) alles wieder OK. Gibt es da ein komisches Abhängigkeit von Alexa und MiHome ??

    2020-05-27 20:12:26.331  - info: host.raspberrypi instance system.adapter.mihome.0 started with pid 22224
2020-05-27 20:12:28.699  - info: mihome.0 (22224) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.mihome, node: v10.20.1
2020-05-27 20:12:28.892  - info: mihome.0 (22224) Change connection status: false
2020-05-27 20:12:28.940  - error: mihome.0 (22224) uncaught exception: addMembership ENODEV
2020-05-27 20:12:28.941  - error: mihome.0 (22224) Error: addMembership ENODEV
    at Socket.addMembership (dgram.js:581:11)
    at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/Hub.js:117:25)
    at Socket.emit (events.js:198:13)
    at startListening (dgram.js:128:10)
    at state.handle.lookup (dgram.js:249:7)
    at process._tickCallback (internal/process/next_tick.js:63:19)
2020-05-27 20:12:28.961  - info: mihome.0 (22224) terminating
2020-05-27 20:12:28.963  - info: mihome.0 (22224) Terminated (NO_ERROR): Without reason
2020-05-27 20:12:29.491  - error: host.raspberrypi Caught by controller[0]: { Error: addMembership ENODEV
2020-05-27 20:12:29.491  - error: host.raspberrypi Caught by controller[0]:     at Socket.addMembership (dgram.js:581:11)
2020-05-27 20:12:29.492  - error: host.raspberrypi Caught by controller[0]:     at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/Hub.js:117:25)
2020-05-27 20:12:29.492  - error: host.raspberrypi Caught by controller[0]:     at Socket.emit (events.js:198:13)
2020-05-27 20:12:29.492  - error: host.raspberrypi Caught by controller[0]:     at startListening (dgram.js:128:10)
2020-05-27 20:12:29.492  - error: host.raspberrypi Caught by controller[0]:     at state.handle.lookup (dgram.js:249:7)
2020-05-27 20:12:29.493  - error: host.raspberrypi Caught by controller[0]:     at process._tickCallback (internal/process/next_tick.js:63:19) errno: 'ENODEV', code: 'ENODEV', syscall: 'addMembership' }
2020-05-27 20:12:29.493  - info: host.raspberrypi instance system.adapter.mihome.0 terminated with code 0 (NO_ERROR)
2020-05-27 20:12:29.493  - info: host.raspberrypi Restart adapter system.adapter.mihome.0 because enabled
2020-05-27 20:12:31.185  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:31.186  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:36.195  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:36.195  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:41.204  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:41.204  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:46.215  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:46.216  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:51.228  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:51.229  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:56.239  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:56.239  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:59.522  - info: host.raspberrypi instance system.adapter.mihome.0 started with pid 22880
2020-05-27 20:13:01.249  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:13:01.250  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:13:01.686  - info: mihome.0 (22880) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.mihome, node: v10.20.1
2020-05-27 20:13:01.852  - info: mihome.0 (22880) Change connection status: false

    Das Ganze beginnt scheinbar hier:

    2020-05-27 17:18:57.380  - error: iot.0 (670) Error by device connection: "premature close"
2020-05-27 17:18:57.382  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:18:57.383  - info: iot.0 (670) Connection lost
2020-05-27 17:19:02.460  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:02.462  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:02.463  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:19:12.474  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:12.475  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:12.476  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:19:32.534  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:32.535  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:32.536  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:20:00.049  - info: host.raspberrypi instance system.adapter.sbfspot.0 started with pid 5118
2020-05-27 17:20:05.004  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:05.498  - info: host.raspberrypi instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-05-27 17:20:10.059  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.158.171:443 - Local (0.0.0.0:0)
2020-05-27 17:20:10.061  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:12.546  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:20:12.547  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:20:12.548  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:20:15.072  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.158.171:443 - Local (0.0.0.0:0)
2020-05-27 17:20:15.072  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:20.088  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.158.171:443 - Local (0.0.0.0:0)
2020-05-27 17:20:20.089  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:25.102  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.158.171:443 - Local (0.0.0.0:0)
2020-05-27 17:20:25.103  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:30.158  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.148.49:443 - Local (0.0.0.0:0)
    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • apollon77A Offline
      apollon77A Offline
      apollon77
      schrieb am zuletzt editiert von
      #2

      Hey,

      ein Github Issue wäre besser und sichtbarer gewesen.

      Kommende Version wird das beheben bze den Crash abfangen. Abert wenn ein UDP Listen membership nicht gesetzt werden kann ist was auf Netzwerkebene komisch

      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
      1 Antwort Letzte Antwort
      0
      • T Tottbeck
        Systemdata
        Hardwaresystem: Pi3
        Arbeitsspeicher: 1GB
        Festplattenart: SD-Karte
        Betriebssystem: Ubuntu
        Node-Version: 10.20.1
        Nodejs-Version: 10.20.1x
        NPM-Version: 6.14.5
        Installationsart: Skript
        Image genutzt: Nein

        Hallo, ich bekommen folgende Fehler in meinem iobroker-log (teilweise auch im syslog).
        Das fängt plötzlich an, das System ist dann kaum noch ansprechbar. Nach einem reboot ist (erstmal) alles wieder OK. Gibt es da ein komisches Abhängigkeit von Alexa und MiHome ??

        2020-05-27 20:12:26.331  - info: host.raspberrypi instance system.adapter.mihome.0 started with pid 22224
2020-05-27 20:12:28.699  - info: mihome.0 (22224) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.mihome, node: v10.20.1
2020-05-27 20:12:28.892  - info: mihome.0 (22224) Change connection status: false
2020-05-27 20:12:28.940  - error: mihome.0 (22224) uncaught exception: addMembership ENODEV
2020-05-27 20:12:28.941  - error: mihome.0 (22224) Error: addMembership ENODEV
    at Socket.addMembership (dgram.js:581:11)
    at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/Hub.js:117:25)
    at Socket.emit (events.js:198:13)
    at startListening (dgram.js:128:10)
    at state.handle.lookup (dgram.js:249:7)
    at process._tickCallback (internal/process/next_tick.js:63:19)
2020-05-27 20:12:28.961  - info: mihome.0 (22224) terminating
2020-05-27 20:12:28.963  - info: mihome.0 (22224) Terminated (NO_ERROR): Without reason
2020-05-27 20:12:29.491  - error: host.raspberrypi Caught by controller[0]: { Error: addMembership ENODEV
2020-05-27 20:12:29.491  - error: host.raspberrypi Caught by controller[0]:     at Socket.addMembership (dgram.js:581:11)
2020-05-27 20:12:29.492  - error: host.raspberrypi Caught by controller[0]:     at Hub.onListening (/opt/iobroker/node_modules/iobroker.mihome/lib/Hub.js:117:25)
2020-05-27 20:12:29.492  - error: host.raspberrypi Caught by controller[0]:     at Socket.emit (events.js:198:13)
2020-05-27 20:12:29.492  - error: host.raspberrypi Caught by controller[0]:     at startListening (dgram.js:128:10)
2020-05-27 20:12:29.492  - error: host.raspberrypi Caught by controller[0]:     at state.handle.lookup (dgram.js:249:7)
2020-05-27 20:12:29.493  - error: host.raspberrypi Caught by controller[0]:     at process._tickCallback (internal/process/next_tick.js:63:19) errno: 'ENODEV', code: 'ENODEV', syscall: 'addMembership' }
2020-05-27 20:12:29.493  - info: host.raspberrypi instance system.adapter.mihome.0 terminated with code 0 (NO_ERROR)
2020-05-27 20:12:29.493  - info: host.raspberrypi Restart adapter system.adapter.mihome.0 because enabled
2020-05-27 20:12:31.185  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:31.186  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:36.195  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:36.195  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:41.204  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:41.204  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:46.215  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:46.216  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:51.228  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:51.229  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:56.239  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:12:56.239  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:12:59.522  - info: host.raspberrypi instance system.adapter.mihome.0 started with pid 22880
2020-05-27 20:13:01.249  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 72.21.207.190:443 - Local (0.0.0.0:0)
2020-05-27 20:13:01.250  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 20:13:01.686  - info: mihome.0 (22880) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.mihome, node: v10.20.1
2020-05-27 20:13:01.852  - info: mihome.0 (22880) Change connection status: false

        Das Ganze beginnt scheinbar hier:

        2020-05-27 17:18:57.380  - error: iot.0 (670) Error by device connection: "premature close"
2020-05-27 17:18:57.382  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:18:57.383  - info: iot.0 (670) Connection lost
2020-05-27 17:19:02.460  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:02.462  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:02.463  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:19:12.474  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:12.475  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:12.476  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:19:32.534  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:32.535  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:19:32.536  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:20:00.049  - info: host.raspberrypi instance system.adapter.sbfspot.0 started with pid 5118
2020-05-27 17:20:05.004  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:05.498  - info: host.raspberrypi instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-05-27 17:20:10.059  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.158.171:443 - Local (0.0.0.0:0)
2020-05-27 17:20:10.061  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:12.546  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:20:12.547  - error: iot.0 (670) Error by device connection: "connect ENETUNREACH 34.243.105.177:8883 - Local (0.0.0.0:0)"
2020-05-27 17:20:12.548  - info: iot.0 (670) Connection changed: disconnect
2020-05-27 17:20:15.072  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.158.171:443 - Local (0.0.0.0:0)
2020-05-27 17:20:15.072  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:20.088  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.158.171:443 - Local (0.0.0.0:0)
2020-05-27 17:20:20.089  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:25.102  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.158.171:443 - Local (0.0.0.0:0)
2020-05-27 17:20:25.103  - info: alexa2.0 (622) Alexa-Push-Connection disconnected - retry: Retry Connection in 5s
2020-05-27 17:20:30.158  - info: alexa2.0 (622) Alexa-Push-Connection Error: Error: connect ENETUNREACH 52.46.148.49:443 - Local (0.0.0.0:0)
        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #3

        @Tottbeck Losgelöst vom Problem würde ich node12 installieren.

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        1 Antwort Letzte Antwort
        0

        Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

        Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

        Mit deinem Input könnte dieser Beitrag noch besser werden 💗

        Registrieren Anmelden
        Antworten
        • In einem neuen Thema antworten
        Anmelden zum Antworten
        • Älteste zuerst
        • Neuste zuerst
        • Meiste Stimmen

        Support us

        ioBroker
        Community Adapters
        Donate

        579

        Online

        32.8k

        Benutzer

        82.9k

        Themen

        1.3m

        Beiträge
        Community
        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
        ioBroker Community 2014-2025
        logo
        • Anmelden
        • Du hast noch kein Konto? Registrieren
        • Anmelden oder registrieren, um zu suchen
        • Erster Beitrag
          Letzter Beitrag
        0
        • Home
        • Aktuell
        • Tags
        • Ungelesen 0
        • Kategorien
        • Unreplied
        • Beliebt
        • GitHub
        • Docu
        • Hilfe