Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • 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. ioBroker Allgemein
  4. Adapter: ioBroker.unifi

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.5k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    2.7k

Adapter: ioBroker.unifi

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
unifi
1.0k Beiträge 172 Kommentatoren 394.9k Aufrufe 93 Watching
  • Ä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.
  • Elektroniker86E Elektroniker86

    @elektroniker86

    Hallo,

    der Adapter sprang die ganze Zeit zwischen gelb und grün. Mittlerweile ist er nur noch gelb und ich habe jede menge Error logs. Ich habe zusätzlich noch ein User in der Dream Machine angelegt jedoch gibt es keine Besserung.

    Ist es ein Konfigurationsfehler oder liegt es am Adapter?
    Hat vielleicht jemand eine Idee?

    Vielen Dank vorab!

    2021-03-22 14:13:44.154  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:13:45.520  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:13:46.864  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:13:48.216  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:13:49.577  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:13:50.939  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:13:52.291  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:13:53.366  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:13:53.650  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:13:54.999  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:13:56.370  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:13:57.723  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:13:59.123  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:00.543  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:01.481  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:01.857  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:03.436  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:03.707  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:03.977  - debug: javascript.0 (1114) system.adapter.admin.0: logging false
    2021-03-22 14:14:04.638  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:05.965  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:07.406  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:07.409  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:08.789  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:09.396  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:10.140  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:11.520  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:12.821  - debug: javascript.0 (1114) system.adapter.admin.0: logging true
    2021-03-22 14:14:12.918  - info: smartmeter.0 (736) Received 13 values, 4 updated
    2021-03-22 14:14:13.003  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:13.004  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:13.004  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:13.015  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:13.023  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:13.024  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:13.027  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:14.268  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:15.557  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:15.660  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:15.821  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:15.969  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:16.492  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:16.609  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:17.058  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:18.444  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:19.845  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:20.317  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:20.961  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:21.218  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:22.647  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:23.272  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:24.004  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:25.192  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:25.410  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:26.795  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:27.488  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:28.188  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:28.276  - info: linux-control.0 (1527) getting data from Visualisierung (192.168.1.93:22)
    2021-03-22 14:14:29.588  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:30.113  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:30.687  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:30.966  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:32.288  - debug: javascript.0 (1114) system.adapter.admin.0: logging false
    2021-03-22 14:14:32.390  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:33.241  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:33.764  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:35.155  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:35.413  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:36.594  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:37.295  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:37.956  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:38.073  - info: linux-control.0 (1527) successful received data from Visualisierung (192.168.1.93:22)
    2021-03-22 14:14:39.358  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:40.006  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:40.562  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:40.760  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:42.243  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:43.577  - info: smartmeter.0 (736) Received 13 values, 4 updated
    2021-03-22 14:14:44.056  - error: unifi.0 (31611) fetchSites: Returned data is not in valid format
    2021-03-22 14:14:44.332  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:44.969  - info: smartmeter.0 (736) Received 13 values, 4 updated
    2021-03-22 14:14:46.387  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:47.801  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:48.241  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:48.539  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:49.204  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:50.656  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:51.150  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:52.036  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:53.238  - debug: javascript.0 (1114) system.adapter.admin.0: logging true
    2021-03-22 14:14:53.434  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:14:53.458  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:54.862  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:14:55.826  - info: unifi.0 (31611) Update done
    2021-03-22 14:14:56.317  - info: smartmeter.0 (736) Received 13 values, 4 updated
    2021-03-22 14:14:56.746  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:14:57.697  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:14:59.120  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:01.481  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:15:01.946  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:15:03.376  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:03.519  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:15:03.813  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:15:04.837  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:06.096  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:15:06.228  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:07.409  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:15:07.572  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:08.182  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:15:08.978  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:15:10.374  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:10.411  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:15:11.204  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:15:11.768  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:13.198  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:13.423  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:15:14.549  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:15:15.940  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:16.496  - info: unifi.0 (31611) Update done
    2021-03-22 14:15:17.134  - error: unifi.0 (31611) fetchDevices: Returned data is not in valid format
    2021-03-22 14:15:17.347  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:15:18.748  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:19.698  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:15:20.148  - info: smartmeter.0 (736) Received 13 values, 4 updated
    2021-03-22 14:15:21.275  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:15:21.590  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:23.002  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:15:23.825  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:15:24.400  - info: smartmeter.0 (736) Received 13 values, 5 updated
    2021-03-22 14:15:25.343  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:15:25.810  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:27.231  - info: smartmeter.0 (736) Received 13 values, 6 updated
    2021-03-22 14:15:27.566  - error: unifi.0 (31611) fetchWlans: Returned data is not in valid format
    2021-03-22 14:15:28.643  - info: smartmeter.0 (736) Received 13 values, 4 updated
    
    wendy2702W Online
    wendy2702W Online
    wendy2702
    schrieb am zuletzt editiert von wendy2702
    #587

    @elektroniker86 Habe keine Dreammachine und habe den Adapter nur kurz benutzt.

    Du solltest das loggen mal auf “Debug” für die Instanz stellen. Also auf der Instanzseite den Expertenmodus aktivieren und dann hinter der Instanz den Loglevel auf Debug stellen.

    Um an das Log zu kommen dann so:

    tail -f /opt/iobroker/log/iobroker.current.log | grep unifi 
    

    Instanz neu starten.

    Beenden mit “STRG+C”.

    Bitte keine Fragen per PN, die gehören ins Forum!

    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

    Elektroniker86E 1 Antwort Letzte Antwort
    0
    • wendy2702W wendy2702

      @elektroniker86 Habe keine Dreammachine und habe den Adapter nur kurz benutzt.

      Du solltest das loggen mal auf “Debug” für die Instanz stellen. Also auf der Instanzseite den Expertenmodus aktivieren und dann hinter der Instanz den Loglevel auf Debug stellen.

      Um an das Log zu kommen dann so:

      tail -f /opt/iobroker/log/iobroker.current.log | grep unifi 
      

      Instanz neu starten.

      Beenden mit “STRG+C”.

      Elektroniker86E Offline
      Elektroniker86E Offline
      Elektroniker86
      schrieb am zuletzt editiert von
      #588

      @wendy2702 sagte in Adapter: ioBroker.unifi:

      tail -f /opt/iobroker/log/iobroker.current.log | grep unifi

      Vielen Dank! Wieder etwas gelernt.

      So hier der Log:

      2021-03-23 08:19:41.028  - info: host.ioBroker-Pi4 stopInstance system.adapter.unifi.0 (force=false, process=true)
      2021-03-23 08:19:41.041  - info: unifi.0 (6983) Got terminate signal TERMINATE_YOURSELF
      2021-03-23 08:19:41.043  - info: host.ioBroker-Pi4 stopInstance system.adapter.unifi.0 send kill signal
      2021-03-23 08:19:41.042  - info: unifi.0 (6983) cleaned everything up...
      2021-03-23 08:19:41.043  - info: unifi.0 (6983) terminating
      2021-03-23 08:19:41.044  - debug: unifi.0 (6983) Plugin sentry destroyed
      2021-03-23 08:19:41.044  - info: unifi.0 (6983) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2021-03-23 08:19:41.143  - debug: unifi.0 (6983) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:41.156  - debug: unifi.0 (6983) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:41.468  - debug: unifi.0 (6983) fetchDevices: 8
      2021-03-23 08:19:41.552  - warn: unifi.0 (6983) redis get unifi.0.default.devices.b4:fb:e4:e5:5e:15.vap_table.ath1.satisfaction, error - Connection is closed.
      2021-03-23 08:19:41.560  - warn: unifi.0 (6983) get state error: Connection is closed.
      2021-03-23 08:19:41.594  - error: unifi.0 (6983) [applyJsonLogic] error: DB closed, stack: Error: DB closed
      2021-03-23 08:19:41.596  - warn: unifi.0 (6983) redis get unifi.0.default.devices.b4:fb:e4:e5:5e:15.guest-num_sta, error - Connection is closed.
      2021-03-23 08:19:41.599  - warn: unifi.0 (6983) get state error: Connection is closed.
      2021-03-23 08:19:41.602  - error: unifi.0 (6983) [applyJsonLogic] error: DB closed, stack: Error: DB closed
      2021-03-23 08:19:41.603  - warn: unifi.0 (6983) redis get unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_1.enable, error - Connection is closed.
      2021-03-23 08:19:41.607  - error: unifi.0 (6983) Cannot check object existence of "unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_1.enable": Connection is closed.
      2021-03-23 08:19:41.608  - warn: unifi.0 (6983) Could not check object existence of state unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_1.enable: Cannot check object existence of "unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_1.enable": Connection is closed.
      2021-03-23 08:19:41.609  - warn: unifi.0 (6983) get state error: Connection is closed.
      2021-03-23 08:19:41.612  - error: unifi.0 (6983) [applyJsonLogic] error: DB closed, stack: Error: DB closed
      2021-03-23 08:19:41.613  - warn: unifi.0 (6983) redis get unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_2.enable, error - Connection is closed.
      2021-03-23 08:19:41.616  - error: unifi.0 (6983) Cannot check object existence of "unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_2.enable": Connection is closed.
      2021-03-23 08:19:41.617  - warn: unifi.0 (6983) Could not check object existence of state unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_2.enable: Cannot check object existence of "unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_2.enable": Connection is closed.
      2021-03-23 08:19:41.617  - warn: unifi.0 (6983) get state error: Connection is closed.
      2021-03-23 08:19:41.620  - error: unifi.0 (6983) [applyJsonLogic] error: DB closed, stack: Error: DB closed
      2021-03-23 08:19:41.621  - warn: unifi.0 (6983) redis get unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_3.enable, error - Connection is closed.
      2021-03-23 08:19:41.713  - info: host.ioBroker-Pi4 instance system.adapter.unifi.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2021-03-23 08:19:44.151  - info: host.ioBroker-Pi4 instance system.adapter.unifi.0 started with pid 7032
      2021-03-23 08:19:45.591  - debug: unifi.0 (7032) Redis Objects: Use Redis connection: 127.0.0.1:9001
      2021-03-23 08:19:45.629  - debug: unifi.0 (7032) Objects client ready ... initialize now
      2021-03-23 08:19:45.632  - debug: unifi.0 (7032) Objects create System PubSub Client
      2021-03-23 08:19:45.634  - debug: unifi.0 (7032) Objects create User PubSub Client
      2021-03-23 08:19:45.636  - debug: unifi.0 (7032) Objects client initialize lua scripts
      2021-03-23 08:19:45.659  - debug: unifi.0 (7032) Objects connected to redis: 127.0.0.1:9001
      2021-03-23 08:19:45.669  - debug: unifi.0 (7032) objectDB connected
      2021-03-23 08:19:45.671  - debug: unifi.0 (7032) Redis States: Use Redis connection: 127.0.0.1:9000
      2021-03-23 08:19:45.681  - debug: unifi.0 (7032) States create System PubSub Client
      2021-03-23 08:19:45.682  - debug: unifi.0 (7032) States create User PubSub Client
      2021-03-23 08:19:45.712  - debug: unifi.0 (7032) States connected to redis: 127.0.0.1:9000
      2021-03-23 08:19:45.713  - debug: unifi.0 (7032) statesDB connected
      2021-03-23 08:19:45.968  - debug: unifi.0 (7032) Plugin sentry Initialize Plugin (enabled=true)
      2021-03-23 08:19:46.462  - info: unifi.0 (7032) starting. Version 0.5.8 in /opt/iobroker/node_modules/iobroker.unifi, node: v12.21.0, js-controller: 3.2.16
      2021-03-23 08:19:46.511  - info: unifi.0 (7032) UniFi adapter is ready
      2021-03-23 08:19:46.535  - debug: unifi.0 (7032) controller = 192.168.1.1:
      2021-03-23 08:19:46.536  - debug: unifi.0 (7032) updateInterval = 2
      2021-03-23 08:19:46.537  - debug: unifi.0 (7032) Update started
      2021-03-23 08:19:46.843  - debug: unifi.0 (7032) system.adapter.admin.0: logging false
      2021-03-23 08:19:47.334  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:19:47.391  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:19:47.467  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:19:48.687  - debug: unifi.0 (7032) Update started
      2021-03-23 08:19:49.258  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:19:49.438  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:19:49.496  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:19:50.692  - debug: unifi.0 (7032) Update started
      2021-03-23 08:19:50.947  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:50.967  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:51.243  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:51.256  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:51.260  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:19:51.298  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
      2021-03-23 08:19:51.376  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:19:51.439  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:19:51.661  - debug: unifi.0 (7032) fetchDevices: 8
      2021-03-23 08:19:52.696  - debug: unifi.0 (7032) Update started
      2021-03-23 08:19:53.275  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:19:53.328  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:19:53.386  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:19:53.412  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:53.427  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:53.821  - debug: unifi.0 (7032) fetchDevices: 8
      2021-03-23 08:19:54.400  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:54.435  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:54.699  - debug: unifi.0 (7032) Update started
      2021-03-23 08:19:54.923  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
      2021-03-23 08:19:55.288  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:19:55.467  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:19:55.532  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:19:56.702  - debug: unifi.0 (7032) Update started
      2021-03-23 08:19:57.254  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:19:57.272  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:57.289  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:57.310  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:19:57.388  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:19:57.755  - debug: unifi.0 (7032) fetchDevices: 8
      2021-03-23 08:19:58.505  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:58.518  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:19:58.705  - debug: unifi.0 (7032) Update started
      2021-03-23 08:19:58.755  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
      2021-03-23 08:19:59.277  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:19:59.332  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:19:59.395  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:20:00.486  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:00.508  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:00.710  - debug: unifi.0 (7032) Update started
      2021-03-23 08:20:01.013  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
      2021-03-23 08:20:01.320  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:20:01.728  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:20:01.812  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:20:02.714  - debug: unifi.0 (7032) Update started
      2021-03-23 08:20:03.338  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:20:03.418  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:20:03.481  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:20:04.387  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:04.404  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:04.540  - debug: unifi.0 (7032) fetchWlans: 3
      2021-03-23 08:20:04.547  - debug: unifi.0 (7032) fetchWlans: 3
      2021-03-23 08:20:04.563  - debug: unifi.0 (7032) fetchWlans: 3
      2021-03-23 08:20:04.717  - debug: unifi.0 (7032) Update started
      2021-03-23 08:20:04.793  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
      2021-03-23 08:20:04.909  - info: unifi.0 (7032) Update done
      2021-03-23 08:20:04.919  - info: unifi.0 (7032) Update done
      2021-03-23 08:20:04.977  - info: unifi.0 (7032) Update done
      2021-03-23 08:20:05.141  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:05.158  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:05.274  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
      2021-03-23 08:20:05.559  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:20:05.592  - error: unifi.0 (7032) fetchSites: Returned data is not in valid format
      2021-03-23 08:20:06.720  - debug: unifi.0 (7032) Update started
      2021-03-23 08:20:07.324  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:20:07.517  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:20:07.590  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:20:07.994  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:08.007  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:08.726  - debug: unifi.0 (7032) Update started
      2021-03-23 08:20:08.865  - debug: unifi.0 (7032) fetchDevices: 8
      2021-03-23 08:20:09.555  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:20:09.652  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:20:09.765  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:20:09.885  - debug: unifi.0 (7032) fetchWlans: 3
      2021-03-23 08:20:09.923  - info: unifi.0 (7032) Update done
      2021-03-23 08:20:10.193  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:10.204  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:10.320  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
      2021-03-23 08:20:10.729  - debug: unifi.0 (7032) Update started
      2021-03-23 08:20:11.373  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:20:11.462  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:20:11.520  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:20:11.896  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:11.906  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:12.253  - debug: unifi.0 (7032) fetchDevices: 8
      2021-03-23 08:20:12.732  - debug: unifi.0 (7032) Update started
      2021-03-23 08:20:13.051  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
      2021-03-23 08:20:13.698  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:20:13.753  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:20:13.809  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:20:14.114  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:14.127  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:14.400  - debug: unifi.0 (7032) fetchDevices: 8
      2021-03-23 08:20:14.737  - debug: unifi.0 (7032) Update started
      2021-03-23 08:20:15.312  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
      2021-03-23 08:20:15.522  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:20:15.578  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:20:15.629  - debug: unifi.0 (7032) fetchClients: 33
      2021-03-23 08:20:15.919  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:15.933  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      2021-03-23 08:20:16.217  - debug: unifi.0 (7032) fetchDevices: 8
      2021-03-23 08:20:16.740  - debug: unifi.0 (7032) Update started
      2021-03-23 08:20:17.012  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
      2021-03-23 08:20:17.470  - debug: unifi.0 (7032) Login successful
      2021-03-23 08:20:17.514  - debug: unifi.0 (7032) fetchSites: default
      2021-03-23 08:20:17.571  - debug: unifi.0 (7032) fetchClients: 33
      ^C
      

      Ich hoffe mir kann hier jemand helfen.....

      wendy2702W 1 Antwort Letzte Antwort
      0
      • Hant0rH Hant0r

        Moin zusammen,
        ist es über den Adapter möglich, die Anzahl der bestehenden Wifi Verbindungen rauszufinden?

        Ich möchte gerne wissen, wie viele gerade mit meinem Gäste-Wlan verbunden sind, um entsprechende Variablen zu bedienen.

        Danke und Gruß

        lobomauL Offline
        lobomauL Offline
        lobomau
        schrieb am zuletzt editiert von
        #589

        @hant0r Anzahl der Gäste wird wohl angezeigt. Hast du den Adapter nicht installiert? Probier doch aus und setze den Haken bei num_guest:
        c71c183f-60d5-4995-b15e-50b202bdda71-image.png

        Host: NUC8i3 mit Proxmox:

        • ioBroker CT Debian 13, npm 10.9.3, nodejs 22.20.0
        • Slave: Pi4
        Hant0rH 1 Antwort Letzte Antwort
        1
        • Elektroniker86E Elektroniker86

          @wendy2702 sagte in Adapter: ioBroker.unifi:

          tail -f /opt/iobroker/log/iobroker.current.log | grep unifi

          Vielen Dank! Wieder etwas gelernt.

          So hier der Log:

          2021-03-23 08:19:41.028  - info: host.ioBroker-Pi4 stopInstance system.adapter.unifi.0 (force=false, process=true)
          2021-03-23 08:19:41.041  - info: unifi.0 (6983) Got terminate signal TERMINATE_YOURSELF
          2021-03-23 08:19:41.043  - info: host.ioBroker-Pi4 stopInstance system.adapter.unifi.0 send kill signal
          2021-03-23 08:19:41.042  - info: unifi.0 (6983) cleaned everything up...
          2021-03-23 08:19:41.043  - info: unifi.0 (6983) terminating
          2021-03-23 08:19:41.044  - debug: unifi.0 (6983) Plugin sentry destroyed
          2021-03-23 08:19:41.044  - info: unifi.0 (6983) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          2021-03-23 08:19:41.143  - debug: unifi.0 (6983) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:41.156  - debug: unifi.0 (6983) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:41.468  - debug: unifi.0 (6983) fetchDevices: 8
          2021-03-23 08:19:41.552  - warn: unifi.0 (6983) redis get unifi.0.default.devices.b4:fb:e4:e5:5e:15.vap_table.ath1.satisfaction, error - Connection is closed.
          2021-03-23 08:19:41.560  - warn: unifi.0 (6983) get state error: Connection is closed.
          2021-03-23 08:19:41.594  - error: unifi.0 (6983) [applyJsonLogic] error: DB closed, stack: Error: DB closed
          2021-03-23 08:19:41.596  - warn: unifi.0 (6983) redis get unifi.0.default.devices.b4:fb:e4:e5:5e:15.guest-num_sta, error - Connection is closed.
          2021-03-23 08:19:41.599  - warn: unifi.0 (6983) get state error: Connection is closed.
          2021-03-23 08:19:41.602  - error: unifi.0 (6983) [applyJsonLogic] error: DB closed, stack: Error: DB closed
          2021-03-23 08:19:41.603  - warn: unifi.0 (6983) redis get unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_1.enable, error - Connection is closed.
          2021-03-23 08:19:41.607  - error: unifi.0 (6983) Cannot check object existence of "unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_1.enable": Connection is closed.
          2021-03-23 08:19:41.608  - warn: unifi.0 (6983) Could not check object existence of state unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_1.enable: Cannot check object existence of "unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_1.enable": Connection is closed.
          2021-03-23 08:19:41.609  - warn: unifi.0 (6983) get state error: Connection is closed.
          2021-03-23 08:19:41.612  - error: unifi.0 (6983) [applyJsonLogic] error: DB closed, stack: Error: DB closed
          2021-03-23 08:19:41.613  - warn: unifi.0 (6983) redis get unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_2.enable, error - Connection is closed.
          2021-03-23 08:19:41.616  - error: unifi.0 (6983) Cannot check object existence of "unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_2.enable": Connection is closed.
          2021-03-23 08:19:41.617  - warn: unifi.0 (6983) Could not check object existence of state unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_2.enable: Cannot check object existence of "unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_2.enable": Connection is closed.
          2021-03-23 08:19:41.617  - warn: unifi.0 (6983) get state error: Connection is closed.
          2021-03-23 08:19:41.620  - error: unifi.0 (6983) [applyJsonLogic] error: DB closed, stack: Error: DB closed
          2021-03-23 08:19:41.621  - warn: unifi.0 (6983) redis get unifi.0.default.devices.e0:63:da:e1:d5:47.port_table.port_3.enable, error - Connection is closed.
          2021-03-23 08:19:41.713  - info: host.ioBroker-Pi4 instance system.adapter.unifi.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          2021-03-23 08:19:44.151  - info: host.ioBroker-Pi4 instance system.adapter.unifi.0 started with pid 7032
          2021-03-23 08:19:45.591  - debug: unifi.0 (7032) Redis Objects: Use Redis connection: 127.0.0.1:9001
          2021-03-23 08:19:45.629  - debug: unifi.0 (7032) Objects client ready ... initialize now
          2021-03-23 08:19:45.632  - debug: unifi.0 (7032) Objects create System PubSub Client
          2021-03-23 08:19:45.634  - debug: unifi.0 (7032) Objects create User PubSub Client
          2021-03-23 08:19:45.636  - debug: unifi.0 (7032) Objects client initialize lua scripts
          2021-03-23 08:19:45.659  - debug: unifi.0 (7032) Objects connected to redis: 127.0.0.1:9001
          2021-03-23 08:19:45.669  - debug: unifi.0 (7032) objectDB connected
          2021-03-23 08:19:45.671  - debug: unifi.0 (7032) Redis States: Use Redis connection: 127.0.0.1:9000
          2021-03-23 08:19:45.681  - debug: unifi.0 (7032) States create System PubSub Client
          2021-03-23 08:19:45.682  - debug: unifi.0 (7032) States create User PubSub Client
          2021-03-23 08:19:45.712  - debug: unifi.0 (7032) States connected to redis: 127.0.0.1:9000
          2021-03-23 08:19:45.713  - debug: unifi.0 (7032) statesDB connected
          2021-03-23 08:19:45.968  - debug: unifi.0 (7032) Plugin sentry Initialize Plugin (enabled=true)
          2021-03-23 08:19:46.462  - info: unifi.0 (7032) starting. Version 0.5.8 in /opt/iobroker/node_modules/iobroker.unifi, node: v12.21.0, js-controller: 3.2.16
          2021-03-23 08:19:46.511  - info: unifi.0 (7032) UniFi adapter is ready
          2021-03-23 08:19:46.535  - debug: unifi.0 (7032) controller = 192.168.1.1:
          2021-03-23 08:19:46.536  - debug: unifi.0 (7032) updateInterval = 2
          2021-03-23 08:19:46.537  - debug: unifi.0 (7032) Update started
          2021-03-23 08:19:46.843  - debug: unifi.0 (7032) system.adapter.admin.0: logging false
          2021-03-23 08:19:47.334  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:19:47.391  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:19:47.467  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:19:48.687  - debug: unifi.0 (7032) Update started
          2021-03-23 08:19:49.258  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:19:49.438  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:19:49.496  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:19:50.692  - debug: unifi.0 (7032) Update started
          2021-03-23 08:19:50.947  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:50.967  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:51.243  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:51.256  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:51.260  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:19:51.298  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
          2021-03-23 08:19:51.376  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:19:51.439  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:19:51.661  - debug: unifi.0 (7032) fetchDevices: 8
          2021-03-23 08:19:52.696  - debug: unifi.0 (7032) Update started
          2021-03-23 08:19:53.275  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:19:53.328  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:19:53.386  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:19:53.412  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:53.427  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:53.821  - debug: unifi.0 (7032) fetchDevices: 8
          2021-03-23 08:19:54.400  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:54.435  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:54.699  - debug: unifi.0 (7032) Update started
          2021-03-23 08:19:54.923  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
          2021-03-23 08:19:55.288  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:19:55.467  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:19:55.532  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:19:56.702  - debug: unifi.0 (7032) Update started
          2021-03-23 08:19:57.254  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:19:57.272  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:57.289  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:57.310  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:19:57.388  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:19:57.755  - debug: unifi.0 (7032) fetchDevices: 8
          2021-03-23 08:19:58.505  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:58.518  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:19:58.705  - debug: unifi.0 (7032) Update started
          2021-03-23 08:19:58.755  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
          2021-03-23 08:19:59.277  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:19:59.332  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:19:59.395  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:20:00.486  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:00.508  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:00.710  - debug: unifi.0 (7032) Update started
          2021-03-23 08:20:01.013  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
          2021-03-23 08:20:01.320  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:20:01.728  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:20:01.812  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:20:02.714  - debug: unifi.0 (7032) Update started
          2021-03-23 08:20:03.338  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:20:03.418  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:20:03.481  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:20:04.387  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:04.404  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:04.540  - debug: unifi.0 (7032) fetchWlans: 3
          2021-03-23 08:20:04.547  - debug: unifi.0 (7032) fetchWlans: 3
          2021-03-23 08:20:04.563  - debug: unifi.0 (7032) fetchWlans: 3
          2021-03-23 08:20:04.717  - debug: unifi.0 (7032) Update started
          2021-03-23 08:20:04.793  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
          2021-03-23 08:20:04.909  - info: unifi.0 (7032) Update done
          2021-03-23 08:20:04.919  - info: unifi.0 (7032) Update done
          2021-03-23 08:20:04.977  - info: unifi.0 (7032) Update done
          2021-03-23 08:20:05.141  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:05.158  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:05.274  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
          2021-03-23 08:20:05.559  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:20:05.592  - error: unifi.0 (7032) fetchSites: Returned data is not in valid format
          2021-03-23 08:20:06.720  - debug: unifi.0 (7032) Update started
          2021-03-23 08:20:07.324  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:20:07.517  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:20:07.590  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:20:07.994  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:08.007  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:08.726  - debug: unifi.0 (7032) Update started
          2021-03-23 08:20:08.865  - debug: unifi.0 (7032) fetchDevices: 8
          2021-03-23 08:20:09.555  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:20:09.652  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:20:09.765  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:20:09.885  - debug: unifi.0 (7032) fetchWlans: 3
          2021-03-23 08:20:09.923  - info: unifi.0 (7032) Update done
          2021-03-23 08:20:10.193  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:10.204  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:10.320  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
          2021-03-23 08:20:10.729  - debug: unifi.0 (7032) Update started
          2021-03-23 08:20:11.373  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:20:11.462  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:20:11.520  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:20:11.896  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:11.906  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:12.253  - debug: unifi.0 (7032) fetchDevices: 8
          2021-03-23 08:20:12.732  - debug: unifi.0 (7032) Update started
          2021-03-23 08:20:13.051  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
          2021-03-23 08:20:13.698  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:20:13.753  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:20:13.809  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:20:14.114  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:14.127  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:14.400  - debug: unifi.0 (7032) fetchDevices: 8
          2021-03-23 08:20:14.737  - debug: unifi.0 (7032) Update started
          2021-03-23 08:20:15.312  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
          2021-03-23 08:20:15.522  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:20:15.578  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:20:15.629  - debug: unifi.0 (7032) fetchClients: 33
          2021-03-23 08:20:15.919  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:15.933  - debug: unifi.0 (7032) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
          2021-03-23 08:20:16.217  - debug: unifi.0 (7032) fetchDevices: 8
          2021-03-23 08:20:16.740  - debug: unifi.0 (7032) Update started
          2021-03-23 08:20:17.012  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
          2021-03-23 08:20:17.470  - debug: unifi.0 (7032) Login successful
          2021-03-23 08:20:17.514  - debug: unifi.0 (7032) fetchSites: default
          2021-03-23 08:20:17.571  - debug: unifi.0 (7032) fetchClients: 33
          ^C
          

          Ich hoffe mir kann hier jemand helfen.....

          wendy2702W Online
          wendy2702W Online
          wendy2702
          schrieb am zuletzt editiert von
          #590

          @elektroniker86 sagte in Adapter: ioBroker.unifi:

          No suitable Lua script

          Bin aktuell nur am Handy.

          Kannst mal im Forum danach suchen:

          
          No suitable Lua script
          
          

          Meine das gab es schon mal.

          Bitte keine Fragen per PN, die gehören ins Forum!

          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

          Elektroniker86E 1 Antwort Letzte Antwort
          1
          • wendy2702W wendy2702

            @elektroniker86 sagte in Adapter: ioBroker.unifi:

            No suitable Lua script

            Bin aktuell nur am Handy.

            Kannst mal im Forum danach suchen:

            
            No suitable Lua script
            
            

            Meine das gab es schon mal.

            Elektroniker86E Offline
            Elektroniker86E Offline
            Elektroniker86
            schrieb am zuletzt editiert von
            #591

            @wendy2702

            Mhh auf die schnelle finde ich da nichts außer dein Beitrag von eben.....

            lobomauL 1 Antwort Letzte Antwort
            0
            • Elektroniker86E Elektroniker86

              @wendy2702

              Mhh auf die schnelle finde ich da nichts außer dein Beitrag von eben.....

              lobomauL Offline
              lobomauL Offline
              lobomau
              schrieb am zuletzt editiert von
              #592

              @elektroniker86 google gibt mir folgenden Treffer. Vielleicht ist es das?

              https://github.com/ioBroker/ioBroker.example/issues/71

              Host: NUC8i3 mit Proxmox:

              • ioBroker CT Debian 13, npm 10.9.3, nodejs 22.20.0
              • Slave: Pi4
              Elektroniker86E 1 Antwort Letzte Antwort
              0
              • lobomauL lobomau

                @elektroniker86 google gibt mir folgenden Treffer. Vielleicht ist es das?

                https://github.com/ioBroker/ioBroker.example/issues/71

                Elektroniker86E Offline
                Elektroniker86E Offline
                Elektroniker86
                schrieb am zuletzt editiert von
                #593

                @lobomau
                Das hatte ich auch gefunden, allerdings geht es hier um ein anderen Adapter und da schreibt Apollon das es kein Fehler sei. Aber bei mir muss es ja ein Fehler sein da der Adapter ja gelb ist?

                Keine Ahnung, damit kann ich leider nichts anfangen.

                wendy2702W 1 Antwort Letzte Antwort
                0
                • Elektroniker86E Elektroniker86

                  @lobomau
                  Das hatte ich auch gefunden, allerdings geht es hier um ein anderen Adapter und da schreibt Apollon das es kein Fehler sei. Aber bei mir muss es ja ein Fehler sein da der Adapter ja gelb ist?

                  Keine Ahnung, damit kann ich leider nichts anfangen.

                  wendy2702W Online
                  wendy2702W Online
                  wendy2702
                  schrieb am zuletzt editiert von wendy2702
                  #594

                  @elektroniker86 OK.

                  Jetzt am PC. Da kann man besser suchen.

                  Denke das Problem liegt hier:

                  2021-03-23 08:19:51.298  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                  2021-03-23 08:19:54.923  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                  2021-03-23 08:19:58.755  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                  2021-03-23 08:20:01.013  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                  2021-03-23 08:20:04.793  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                  2021-03-23 08:20:05.274  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                  2021-03-23 08:20:05.592  - error: unifi.0 (7032) fetchSites: Returned data is not in valid format
                  2021-03-23 08:20:10.320  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                  2021-03-23 08:20:13.051  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
                  2021-03-23 08:20:15.312  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
                  2021-03-23 08:20:17.012  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
                  
                  

                  Denke da kann der Adapter die Antwort von der Dreammachine nicht richtig verarbeiten.

                  Du solltest dafür am besten ein Issue aufmachen falls es noch keines gibt und hier niemand ist bei dem es funktioniert.

                  EDIT: Schau mal hier: https://github.com/iobroker-community-adapters/ioBroker.unifi/issues/28

                  Bitte keine Fragen per PN, die gehören ins Forum!

                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                  Elektroniker86E 1 Antwort Letzte Antwort
                  1
                  • wendy2702W wendy2702

                    @elektroniker86 OK.

                    Jetzt am PC. Da kann man besser suchen.

                    Denke das Problem liegt hier:

                    2021-03-23 08:19:51.298  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                    2021-03-23 08:19:54.923  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                    2021-03-23 08:19:58.755  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                    2021-03-23 08:20:01.013  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                    2021-03-23 08:20:04.793  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                    2021-03-23 08:20:05.274  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                    2021-03-23 08:20:05.592  - error: unifi.0 (7032) fetchSites: Returned data is not in valid format
                    2021-03-23 08:20:10.320  - error: unifi.0 (7032) fetchDevices: Returned data is not in valid format
                    2021-03-23 08:20:13.051  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
                    2021-03-23 08:20:15.312  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
                    2021-03-23 08:20:17.012  - error: unifi.0 (7032) fetchWlans: Returned data is not in valid format
                    
                    

                    Denke da kann der Adapter die Antwort von der Dreammachine nicht richtig verarbeiten.

                    Du solltest dafür am besten ein Issue aufmachen falls es noch keines gibt und hier niemand ist bei dem es funktioniert.

                    EDIT: Schau mal hier: https://github.com/iobroker-community-adapters/ioBroker.unifi/issues/28

                    Elektroniker86E Offline
                    Elektroniker86E Offline
                    Elektroniker86
                    schrieb am zuletzt editiert von
                    #595

                    @wendy2702

                    Das verstehe ich nicht, das hat ja die ganze Zeit funktioniert das ist erst seit ein Paar Wochen....

                    Hier muss es doch mehrere geben die eine Dream Machine haben in Verbindung mit dem Adapter.....
                    Ich habe jetzt nochmal mit dem Port 443 getestet, keine Veränderung feststellbar.
                    Werde dann doch ein Issue anlegen müssen.....

                    wendy2702W 1 Antwort Letzte Antwort
                    0
                    • Elektroniker86E Elektroniker86

                      @wendy2702

                      Das verstehe ich nicht, das hat ja die ganze Zeit funktioniert das ist erst seit ein Paar Wochen....

                      Hier muss es doch mehrere geben die eine Dream Machine haben in Verbindung mit dem Adapter.....
                      Ich habe jetzt nochmal mit dem Port 443 getestet, keine Veränderung feststellbar.
                      Werde dann doch ein Issue anlegen müssen.....

                      wendy2702W Online
                      wendy2702W Online
                      wendy2702
                      schrieb am zuletzt editiert von
                      #596

                      @elektroniker86 Gab es vielleicht ein Update der Dream Machine?

                      Bitte keine Fragen per PN, die gehören ins Forum!

                      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                      Elektroniker86E 1 Antwort Letzte Antwort
                      0
                      • wendy2702W wendy2702

                        @elektroniker86 Gab es vielleicht ein Update der Dream Machine?

                        Elektroniker86E Offline
                        Elektroniker86E Offline
                        Elektroniker86
                        schrieb am zuletzt editiert von
                        #597

                        @wendy2702

                        Ja, das gab es tatsächlich vor 2 Wochen so ungefähr........ das hatte ich gar nicht mehr auf dem Schirm.

                        Aber dann sollten sich ja noch mehrere melden, aber ich hab in der Suche hier nichts gefunden..... :thinking_face:

                        HiltexH 1 Antwort Letzte Antwort
                        0
                        • Elektroniker86E Elektroniker86

                          @wendy2702

                          Ja, das gab es tatsächlich vor 2 Wochen so ungefähr........ das hatte ich gar nicht mehr auf dem Schirm.

                          Aber dann sollten sich ja noch mehrere melden, aber ich hab in der Suche hier nichts gefunden..... :thinking_face:

                          HiltexH Offline
                          HiltexH Offline
                          Hiltex
                          schrieb am zuletzt editiert von
                          #598

                          @elektroniker86
                          Bei mir läuft der Adapter fehlerfrei, zusammen mit einer Dream Machine Pro

                          Blog: indibit.de

                          wendy2702W Elektroniker86E 2 Antworten Letzte Antwort
                          0
                          • HiltexH Hiltex

                            @elektroniker86
                            Bei mir läuft der Adapter fehlerfrei, zusammen mit einer Dream Machine Pro

                            wendy2702W Online
                            wendy2702W Online
                            wendy2702
                            schrieb am zuletzt editiert von
                            #599

                            @hiltex @Elektroniker86

                            habt ihr beide die gleiche SW auf der Dream Machine laufen ?

                            Bitte keine Fragen per PN, die gehören ins Forum!

                            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                            1 Antwort Letzte Antwort
                            0
                            • HiltexH Hiltex

                              @elektroniker86
                              Bei mir läuft der Adapter fehlerfrei, zusammen mit einer Dream Machine Pro

                              Elektroniker86E Offline
                              Elektroniker86E Offline
                              Elektroniker86
                              schrieb am zuletzt editiert von
                              #600

                              @hiltex

                              Auf meiner UDM-Pro läuft die Firmware 1.9.2 und er Controller hat die 6.1.70
                              Welche FW läuft bei dir?

                              HiltexH 1 Antwort Letzte Antwort
                              0
                              • Elektroniker86E Elektroniker86

                                @hiltex

                                Auf meiner UDM-Pro läuft die Firmware 1.9.2 und er Controller hat die 6.1.70
                                Welche FW läuft bei dir?

                                HiltexH Offline
                                HiltexH Offline
                                Hiltex
                                schrieb am zuletzt editiert von
                                #601

                                @elektroniker86
                                Die Firmware lässt sich am Handy leider nicht abrufen, da die Webseite mit den Systemeinstellungen bei mir leer bleibt. Als Controller läuft bei bei mir 6.1.61

                                Blog: indibit.de

                                1 Antwort Letzte Antwort
                                0
                                • lobomauL lobomau

                                  @hant0r Anzahl der Gäste wird wohl angezeigt. Hast du den Adapter nicht installiert? Probier doch aus und setze den Haken bei num_guest:
                                  c71c183f-60d5-4995-b15e-50b202bdda71-image.png

                                  Hant0rH Offline
                                  Hant0rH Offline
                                  Hant0r
                                  schrieb am zuletzt editiert von
                                  #602

                                  @lobomau
                                  Danke, gute Idee. Habe es mal ausprobiert, bekomme aber leider keine neuen Datenpunkte wo die Info enthalten wäre.

                                  lobomauL 1 Antwort Letzte Antwort
                                  0
                                  • Hant0rH Hant0r

                                    @lobomau
                                    Danke, gute Idee. Habe es mal ausprobiert, bekomme aber leider keine neuen Datenpunkte wo die Info enthalten wäre.

                                    lobomauL Offline
                                    lobomauL Offline
                                    lobomau
                                    schrieb am zuletzt editiert von
                                    #603

                                    @hant0r komisch. Bei mir scheint es zu gehen. Ich habe kein Gäste-Netz, deswegen hier 0. Habe aber num_user dazu genommen und hier passt es. Kommt bei jedem Device ein Wert:

                                    8d6fa371-37a3-4159-8798-1f6a6cc3364f-image.png

                                    6b062f8a-5ebc-40f9-b202-a9a25a92d53a-image.png

                                    Host: NUC8i3 mit Proxmox:

                                    • ioBroker CT Debian 13, npm 10.9.3, nodejs 22.20.0
                                    • Slave: Pi4
                                    Hant0rH 1 Antwort Letzte Antwort
                                    0
                                    • lobomauL lobomau

                                      @hant0r komisch. Bei mir scheint es zu gehen. Ich habe kein Gäste-Netz, deswegen hier 0. Habe aber num_user dazu genommen und hier passt es. Kommt bei jedem Device ein Wert:

                                      8d6fa371-37a3-4159-8798-1f6a6cc3364f-image.png

                                      6b062f8a-5ebc-40f9-b202-a9a25a92d53a-image.png

                                      Hant0rH Offline
                                      Hant0rH Offline
                                      Hant0r
                                      schrieb am zuletzt editiert von
                                      #604

                                      @lobomau
                                      Mein Fehler ... Wer lesen kann ist ganz klar im Vorteil - sorry.
                                      Ich hatte die Felder im Adapter ausgewählt, aber oben nicht den allgemeinen Reiter "Devices" aktiviert. :man-facepalming:

                                      Nun klappt es auch und so bekomme ich zumindest die Anzahl raus.
                                      Das hilft mir schonmal - Danke :)

                                      lobomauL 1 Antwort Letzte Antwort
                                      0
                                      • Hant0rH Hant0r

                                        @lobomau
                                        Mein Fehler ... Wer lesen kann ist ganz klar im Vorteil - sorry.
                                        Ich hatte die Felder im Adapter ausgewählt, aber oben nicht den allgemeinen Reiter "Devices" aktiviert. :man-facepalming:

                                        Nun klappt es auch und so bekomme ich zumindest die Anzahl raus.
                                        Das hilft mir schonmal - Danke :)

                                        lobomauL Offline
                                        lobomauL Offline
                                        lobomau
                                        schrieb am zuletzt editiert von
                                        #605

                                        @hant0r Ahh... ist mir auch schon passiert ;-)

                                        Host: NUC8i3 mit Proxmox:

                                        • ioBroker CT Debian 13, npm 10.9.3, nodejs 22.20.0
                                        • Slave: Pi4
                                        Meister MopperM 1 Antwort Letzte Antwort
                                        1
                                        • lobomauL lobomau

                                          @hant0r Ahh... ist mir auch schon passiert ;-)

                                          Meister MopperM Abwesend
                                          Meister MopperM Abwesend
                                          Meister Mopper
                                          schrieb am zuletzt editiert von
                                          #606

                                          Seit ein paar Tagen startet der Adapter (Ver. 0.5.8) nach einem Stopp-Backup und Restart von ioBroker in Proxmox nicht mehr automatisch. Im log steht dies:

                                          host.iobroker	2021-03-31 02:54:21.093	warn	Do not restart adapter system.adapter.unifi.0 because restart loop detected
                                          host.iobroker	2021-03-31 02:54:21.093	info	Restart adapter system.adapter.unifi.0 because enabled
                                          host.iobroker	2021-03-31 02:54:21.093	error	instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                          host.iobroker	2021-03-31 02:54:21.092	error	Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
                                          host.iobroker	2021-03-31 02:54:21.092	error	Caught by controller[1]: Error: connect EHOSTUNREACH x.x.x.x:8443
                                          host.iobroker	2021-03-31 02:54:21.092	error	Caught by controller[0]: 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(). The promise rejecte
                                          unifi.0	2021-03-31 02:54:20.337	error	(5813) Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH x.x.x.x:8443
                                          unifi.0	2021-03-31 02:54:20.337	error	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
                                          unifi.0	2021-03-31 02:54:20.337	error	(5813) Error: connect EHOSTUNREACH x.x.x.x:8443
                                          unifi.0	2021-03-31 02:54:20.337	error	(5813) unhandled promise rejection: connect EHOSTUNREACH x.x.x.x:8443
                                          unifi.0	2021-03-31 02:54:20.336	error	(5813) 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().
                                          host.iobroker	2021-03-31 02:54:15.681	info	instance system.adapter.unifi.0 started with pid 5813
                                          host.iobroker	2021-03-31 02:53:45.657	info	Restart adapter system.adapter.unifi.0 because enabled
                                          host.iobroker	2021-03-31 02:53:45.656	error	instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                          host.iobroker	2021-03-31 02:53:45.656	error	Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
                                          host.iobroker	2021-03-31 02:53:45.656	error	Caught by controller[1]: Error: connect EHOSTUNREACH x.x.x.x:8443
                                          host.iobroker	2021-03-31 02:53:45.655	error	Caught by controller[0]: 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(). The promise rejecte
                                          unifi.0	2021-03-31 02:53:44.912	error	(5714) Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH x.x.x.x:8443
                                          unifi.0	2021-03-31 02:53:44.912	error	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
                                          unifi.0	2021-03-31 02:53:44.912	error	(5714) Error: connect EHOSTUNREACH x.x.x.x:8443
                                          unifi.0	2021-03-31 02:53:44.912	error	(5714) unhandled promise rejection: connect EHOSTUNREACH x.x.x.x:8443
                                          unifi.0	2021-03-31 02:53:44.910	error	(5714) 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().
                                          host.iobroker	2021-03-31 02:53:40.353	info	instance system.adapter.unifi.0 started with pid 5714
                                          host.iobroker	2021-03-31 02:53:10.335	info	Restart adapter system.adapter.unifi.0 because enabled
                                          host.iobroker	2021-03-31 02:53:10.329	error	instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                          host.iobroker	2021-03-31 02:53:10.328	error	Caught by controller[0]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
                                          host.iobroker	2021-03-31 02:53:10.328	error	Caught by controller[0]: Error: connect EHOSTUNREACH x.x.x.x:8443
                                          host.iobroker	2021-03-31 02:53:10.319	error	Caught by controller[0]: 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(). The promise rejecte
                                          unifi.0	2021-03-31 02:53:09.315	error	(1544) Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH x.x.x.x:8443
                                          unifi.0	2021-03-31 02:53:09.315	error	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
                                          unifi.0	2021-03-31 02:53:09.315	error	(1544) Error: connect EHOSTUNREACH x.x.x.x:8443
                                          unifi.0	2021-03-31 02:53:09.315	error	(1544) unhandled promise rejection: connect EHOSTUNREACH x.x.x.x:8443
                                          unifi.0	2021-03-31 02:53:09.281	error	(1544) 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().
                                          host.iobroker	2021-03-31 02:34:07.018	info	instance system.adapter.unifi.0 started with pid 1544
                                          

                                          Offenbar startet der Adapter nicht wegen vorangegangenen Fehlstarts. Stoße ich den Start über die Instanz manuell an, funktioniert es wieder.

                                          Kennt jemand dieses Phänomen und weiß Abhilfe?

                                          Proxmox und HA

                                          Meister MopperM 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          789

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          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