Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Adapter: ioBroker.unifi

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Adapter: ioBroker.unifi

    This topic has been deleted. Only users with topic management privileges can see it.
    • wendy2702
      wendy2702 @Elektroniker86 last edited by 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”.

      Elektroniker86 1 Reply Last reply Reply Quote 0
      • Elektroniker86
        Elektroniker86 @wendy2702 last edited by

        @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.....

        wendy2702 1 Reply Last reply Reply Quote 0
        • lobomau
          lobomau @Hant0r last edited by

          @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

          Hant0r 1 Reply Last reply Reply Quote 1
          • wendy2702
            wendy2702 @Elektroniker86 last edited by

            @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.

            Elektroniker86 1 Reply Last reply Reply Quote 1
            • Elektroniker86
              Elektroniker86 @wendy2702 last edited by

              @wendy2702

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

              lobomau 1 Reply Last reply Reply Quote 0
              • lobomau
                lobomau @Elektroniker86 last edited by

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

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

                SebastianSchultz created this issue in ioBroker/ioBroker.example

                closed No suitable Lua script, fallback to keys #71

                Elektroniker86 1 Reply Last reply Reply Quote 0
                • Elektroniker86
                  Elektroniker86 @lobomau last edited by

                  @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.

                  wendy2702 1 Reply Last reply Reply Quote 0
                  • wendy2702
                    wendy2702 @Elektroniker86 last edited by 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

                    pietro4711 created this issue in iobroker-community-adapters/ioBroker.unifi

                    closed Implement support UniFi OS based controllers (e.g. UniFi Dream Machine) #28

                    Elektroniker86 1 Reply Last reply Reply Quote 1
                    • Elektroniker86
                      Elektroniker86 @wendy2702 last edited by

                      @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.....

                      wendy2702 1 Reply Last reply Reply Quote 0
                      • wendy2702
                        wendy2702 @Elektroniker86 last edited by

                        @elektroniker86 Gab es vielleicht ein Update der Dream Machine?

                        Elektroniker86 1 Reply Last reply Reply Quote 0
                        • Elektroniker86
                          Elektroniker86 @wendy2702 last edited by

                          @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..... 🤔

                          Hiltex 1 Reply Last reply Reply Quote 0
                          • Hiltex
                            Hiltex @Elektroniker86 last edited by

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

                            wendy2702 Elektroniker86 2 Replies Last reply Reply Quote 0
                            • wendy2702
                              wendy2702 @Hiltex last edited by

                              @hiltex @Elektroniker86

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

                              1 Reply Last reply Reply Quote 0
                              • Elektroniker86
                                Elektroniker86 @Hiltex last edited by

                                @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?

                                Hiltex 1 Reply Last reply Reply Quote 0
                                • Hiltex
                                  Hiltex @Elektroniker86 last edited by

                                  @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

                                  1 Reply Last reply Reply Quote 0
                                  • Hant0r
                                    Hant0r @lobomau last edited by

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

                                    lobomau 1 Reply Last reply Reply Quote 0
                                    • lobomau
                                      lobomau @Hant0r last edited by

                                      @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

                                      Hant0r 1 Reply Last reply Reply Quote 0
                                      • Hant0r
                                        Hant0r @lobomau last edited by

                                        @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. 🤦‍♂️

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

                                        lobomau 1 Reply Last reply Reply Quote 0
                                        • lobomau
                                          lobomau @Hant0r last edited by

                                          @hant0r Ahh... ist mir auch schon passiert 😉

                                          Meister Mopper 1 Reply Last reply Reply Quote 1
                                          • Meister Mopper
                                            Meister Mopper @lobomau last edited by

                                            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?

                                            Meister Mopper 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

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

                                            591
                                            Online

                                            31.6k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            unifi
                                            170
                                            997
                                            284816
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo