Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 2.0 ab sofort im Latest Repo

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    js-controller 2.0 ab sofort im Latest Repo

    This topic has been deleted. Only users with topic management privileges can see it.
    • apollon77
      apollon77 @Chaot last edited by

      @Chaot iobroker update?! 😉

      Chaot 1 Reply Last reply Reply Quote 0
      • Chaot
        Chaot @apollon77 last edited by

        @apollon77
        Bereits drei mal versucht.

        iobroker stop
        iobroker update
        iobroker upgrade self

        "Host "iobroker" is up to date"

        1 Reply Last reply Reply Quote 0
        • crunchip
          crunchip Forum Testing Most Active @apollon77 last edited by

          @apollon77 sagte in js-controller 2.0 ab sofort im Latest Repo:

          jetzt wirklich die letzte

          Abwarten😂

          sigi234 Chaot 2 Replies Last reply Reply Quote 0
          • sigi234
            sigi234 Forum Testing Most Active @crunchip last edited by sigi234

            @crunchip sagte in js-controller 2.0 ab sofort im Latest Repo:

            @apollon77 sagte in js-controller 2.0 ab sofort im Latest Repo:

            jetzt wirklich die letzte

            Abwarten😂

            Quote: 50:50

            😀
            Muss ja mal auch ein bisschen Spaß sein.

            1 Reply Last reply Reply Quote 0
            • Chaot
              Chaot @crunchip last edited by

              @crunchip Na warte mal.
              Nur um dich zu ärgern schiebt er dann die 3.x.x 😀

              apollon77 1 Reply Last reply Reply Quote 0
              • apollon77
                apollon77 @Chaot last edited by

                @Chaot 😛

                1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 last edited by

                  Ps: ihr dürft einfach nur nix neues mehr finden ;-))

                  crunchip 1 Reply Last reply Reply Quote 0
                  • crunchip
                    crunchip Forum Testing Most Active @apollon77 last edited by

                    @apollon77 bin noch nicht zu hause und heute mag ich auch nicht mehr suchen.
                    Aber morgen ist ja auch noch ein Tag😉

                    1 Reply Last reply Reply Quote 0
                    • MathiasJ
                      MathiasJ last edited by

                      So,
                      dieses Update ist durch.
                      Mein System bringt mir immer

                      loglevel error --prefix "/opt/iobroker" (System call)

                      egal, ob ich den JS-Controller oder einen Adapter update.
                      In diesem Fall ist es der rpc-Adapter.

                      Gruß,
                      Mathias

                      apollon77 AlCalzone 2 Replies Last reply Reply Quote 0
                      • apollon77
                        apollon77 @MathiasJ last edited by

                        @MathiasJ jetzt brauch ich aber mehr Kontext .... Was genau ist dein "Problem" damit? Oder ist es der Teil "loglevel error" weil das früher nicht da war?

                        BBTown 1 Reply Last reply Reply Quote 0
                        • AlCalzone
                          AlCalzone Developer @MathiasJ last edited by

                          @MathiasJ Das ist ein Teil des Befehls, der zum Installieren aufgerufen wird. loglevel error heißt lediglich dass nur Fehler ausgegeben werden, keine Warnungen oder Hinweise. Letztendlich vermeidet das, dass unbedarfte Anwender sich über seitenweise "Fehler" beschweren.

                          1 Reply Last reply Reply Quote 0
                          • Neuschwansteini
                            Neuschwansteini @apollon77 last edited by Neuschwansteini

                            @apollon77 Hi,
                            soeben von der 42 auf die 43 geupdatet, erst die Clienthosts, dann den Master, lief alles ohne fehler durch, "nur" hatte ich den Effekt, dass nach dem update des masters die clients sich alle! ( 5 Raspis, vom Zero bis 3+ alles dabei..) sich nicht mehr automatisch verbunden haben..
                            musste mich auf allen per ssh einloggen (also das Netzwerk war es nicht, sind auch welche mit Kabel verbunden) und ein 'iobroker restart' machen, dann war alles gut. (System file, kein redis)

                            Wo die Errors anfangen, hab ich den Master gestoppt, geupdated, und dann wieder gestartet... aber die haben sich alle nicht mehr gefangen..

                            Schau mal hier das log von einem( hab ein paar Hundert sich wiederholende Meldungen rausgelöscht):

                            2019-11-13 11:19:27.295  - info: host.meterberry received SIGTERM
2019-11-13 11:19:27.301  - info: host.meterberry stopInstance system.adapter.ble.1 (process=true)
2019-11-13 11:19:27.369  - info: host.meterberry stopInstance system.adapter.ble.1 send kill signal
2019-11-13 11:19:28.122  - info: host.meterberry instance system.adapter.ble.1 terminated with code 156 (156)
2019-11-13 11:19:28.123  - info: host.meterberry All instances are stopped.
2019-11-13 11:19:28.141  - info: host.meterberry terminated
2019-11-13 11:23:08.024  - info: host.meterberry iobroker.js-controller version 2.0.43 js-controller starting
2019-11-13 11:23:08.035  - info: host.meterberry Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
2019-11-13 11:23:08.036  - info: host.meterberry hostname: meterberry, node: v10.17.0
2019-11-13 11:23:08.039  - info: host.meterberry ip addresses: 192.168.0.59 2001:16b8:20a3:f500:bfe:b89e:b17a:d67f fe80::fc1f:86d5:4984:5043
2019-11-13 11:23:08.265  - info: host.meterberry connected to Objects and States
2019-11-13 11:23:08.674  - info: host.meterberry 71 instances found
2019-11-13 11:23:08.731  - info: host.meterberry starting 1 instance
2019-11-13 11:23:08.781  - info: host.meterberry instance system.adapter.ble.1 started with pid 557
2019-11-13 11:35:35.201  - error: host.meterberry connect ECONNREFUSED 192.168.178.41:9001
2019-11-13 11:35:35.226  - error: ble.1 (557) connect ECONNREFUSED 192.168.178.41:9001
2019-11-13 11:35:35.929  - error: host.meterberry connect ECONNREFUSED 192.168.178.41:9000
2019-11-13 11:35:35.929  - error: ble.1 (557) connect ECONNREFUSED 192.168.178.41:9000
2019-11-13 11:35:40.224  - error: host.meterberry connect ECONNREFUSED 192.168.178.41:9001
2019-11-13 11:35:40.245  - error: ble.1 (557) connect ECONNREFUSED 192.168.178.41:9001
2019-11-13 11:35:40.939  - error: ble.1 (557) connect ECONNREFUSED 192.168.178.41:9000
2019-11-13 11:35:40.940  - error: host.meterberry connect ECONNREFUSED 192.168.178.41:9000
2019-11-13 11:35:45.230  - error: host.meterberry connect ECONNREFUSED 192.168.178.41:9001
2019-11-13 11:38:07.750  - error: host.meterberry connect ECONNREFUSED 192.168.178.41:9000
2019-11-13 11:38:07.756  - warn: ble.1 (557) redis get ble.1.c4:7c:8d:66:1b:36.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.757  - warn: ble.1 (557) redis get ble.1.54:d2:72:b0:6c:c1.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.758  - warn: ble.1 (557) redis get ble.1.c4:7c:8d:66:1b:36.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.759  - warn: ble.1 (557) redis get ble.1.c4:7c:8d:66:1b:36.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.776  - warn: ble.1 (557) redis get ble.1.54:d2:72:b0:6c:c1.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.777  - warn: ble.1 (557) redis get ble.1.54:d2:72:b0:6c:c1.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.778  - warn: ble.1 (557) get state Error: Connection is closed.
2019-11-13 11:38:07.779  - warn: ble.1 (557) get state Error: Connection is closed.
2019-11-13 11:38:07.784  - warn: ble.1 (557) get state Error: Connection is closed.
2019-11-13 11:38:07.785  - warn: ble.1 (557) get state Error: Connection is closed.
2019-11-13 11:38:07.786  - warn: ble.1 (557) redis get ble.1.54:d2:72:b0:6c:c1.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.787  - warn: ble.1 (557) redis get ble.1.c4:7c:8d:66:1b:36.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.788  - warn: ble.1 (557) redis get ble.1.54:d2:72:b0:6c:c1.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.788  - warn: ble.1 (557) redis get ble.1.74:a3:4a:b6:12:26.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.789  - warn: ble.1 (557) redis get ble.1.74:a3:4a:b6:12:26.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.790  - warn: ble.1 (557) redis get ble.1.54:d2:72:b0:6c:c1.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.791  - warn: ble.1 (557) redis get ble.1.74:a3:4a:b6:12:26.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.791  - warn: ble.1 (557) redis get ble.1.74:a3:4a:b6:12:26.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.792  - warn: ble.1 (557) redis get ble.1.74:a3:4a:b6:12:26.rssi, error - Error: Connection is closed.
2019-11-13 11:38:07.793  - warn: ble.1 (557) get state Error: Connection is closed.
2019-11-13 11:38:07.832  - warn: ble.1 (557) get state Error: Connection is closed.
2019-11-13 11:38:07.838  - error: ble.1 (557) unhandled promise rejection: Error: Connection is closed.
2019-11-13 11:38:07.839  - error: ble.1 (557) unhandled promise rejection: Error: Connection is closed.
2019-11-13 11:38:07.858  - error: ble.1 (557) unhandled promise rejection: Error: Connection is closed.
2019-11-13 11:38:07.859  - error: ble.1 (557) unhandled promise rejection: Error: Connection is closed.
2019-11-13 11:38:07.869  - error: ble.1 (557) connect ECONNREFUSED 192.168.178.41:9001
2019-11-13 11:38:07.754  - warn: Unable to subscribe to expiry Keyspace events from Redis Server: Error: Connection is closed.
2019-11-13 11:38:07.756  - warn: Unable to subscribe to evicted Keyspace events from Redis Server: Error: Connection is closed.
2019-11-13 11:38:07.763  - warn: host.meterberry get state Error: Connection is closed.
2019-11-13 11:38:07.869  - warn: host.meterberry get state Error: Connection is closed.
2019-11-13 11:38:07.872  - warn: Unable to subscribe to expiry Keyspace events from Redis Server: Error: Connection is closed.
2019-11-13 11:38:07.873  - warn: Unable to subscribe to evicted Keyspace events from Redis Server: Error: Connection is closed.
2019-11-13 11:38:07.873  - error: ble.1 (557) unhandled promise rejection: Error: Connection is closed.
2019-11-13 11:38:07.886  - error: ble.1 (557) unhandled promise rejection: Error: Connection is closed.
2019-11-13 11:38:10.098  - error: ble.1 (557) unhandled promise rejection: Error: Connection is closed.
2019-11-13 11:38:10.238  - warn: host.meterberry Slave controller detected disconnection. Stop all instances.
2019-11-13 11:38:10.246  - info: host.meterberry stopInstance system.adapter.ble.1 (process=true)
2019-11-13 11:38:10.247  - info: host.meterberry stopInstance forced system.adapter.ble.1 killing pid 557
2019-11-13 11:38:10.256  - warn: ble.1 (557) get state Error: Connection is closed.
2019-11-13 11:38:10.257  - warn: ble.1 (557) get state Error: Connection is closed.
2019-11-13 11:38:10.800  - warn: host.meterberry get state Error: Connection is closed.
2019-11-13 11:38:10.801  - warn: host.meterberry get state Error: Connection is closed.
2019-11-13 11:38:10.802  - error: host.meterberry Cannot find view "system" for search "instance" : Error: Connection is closed.
2019-11-13 11:38:10.808  - info: host.meterberry instance system.adapter.ble.1 terminated with code 156 (156)
2019-11-13 11:38:10.810  - info: host.meterberry All instances are stopped.
2019-11-13 11:38:18.278  - warn: host.meterberry get state Error: Connection is closed.
2019-11-13 11:55:48.326  - warn: host.meterberry get state Error: Connection is closed.
2019-11-13 11:55:48.327  - warn: host.meterberry get state Error: Connection is closed.
2019-11-13 11:55:53.662  - info: host.meterberry received SIGTERM
2019-11-13 11:55:53.668  - info: host.meterberry stopInstance system.adapter.ble.1 (process=false)
2019-11-13 11:55:53.669  - warn: host.meterberry get state Error: Connection is closed.
2019-11-13 11:55:53.670  - info: host.meterberry force terminating
2019-11-13 11:55:56.090  - info: host.meterberry iobroker.js-controller version 2.0.43 js-controller starting
2019-11-13 11:55:56.101  - info: host.meterberry Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
2019-11-13 11:55:56.102  - info: host.meterberry hostname: meterberry, node: v10.17.0
2019-11-13 11:55:56.105  - info: host.meterberry ip addresses: 192.168.0.59 2001:16b8:20a3:f500:bfe:b89e:b17a:d67f fe80::fc1f:86d5:4984:5043
2019-11-13 11:55:56.363  - info: host.meterberry connected to Objects and States
2019-11-13 11:55:56.774  - info: host.meterberry 71 instances found
2019-11-13 11:55:56.821  - info: host.meterberry starting 1 instance
2019-11-13 11:55:56.861  - info: host.meterberry instance system.adapter.ble.1 started with pid 949
                            apollon77 1 Reply Last reply Reply Quote 0
                            • BBTown
                              BBTown @apollon77 last edited by

                              @apollon77
                              bei mir lief die Aktualisierung problemlos duch, alles macht was es soll

                              • kein Slave
                              • file/file
                              1 Reply Last reply Reply Quote 0
                              • apollon77
                                apollon77 @Neuschwansteini last edited by

                                @ilovegym sagte in js-controller 2.0 ab sofort im Latest Repo:
                                ok ich checke bei mir nochmal, aber daran hab ich an sich nix gedreht ... mal schauen ...

                                Wann war denn der Master wieder da genau?

                                Neuschwansteini 1 Reply Last reply Reply Quote 0
                                • SBorg
                                  SBorg Forum Testing Most Active @apollon77 last edited by

                                  @apollon77 sagte in js-controller 2.0 ab sofort im Latest Repo:

                                  • (Apollon77) increase object init timeout for adapter starts before complaining/stopping

                                  Hi,
                                  betraf/betrifft das auch den "no connection to objekts db"-Fehler (oder gerade eben diesen)?
                                  Nach Update und Start:

                                  2019-11-13 11:38:50.229 - warn: tr-064-community.0 (14931) no connection to objects DB
2019-11-13 11:38:50.243 - warn: tankerkoenig.0 (14634) no connection to objects DB
2019-11-13 11:38:53.070 - warn: terminal.0 (14825) no connection to objects DB
2019-11-13 11:38:53.912 - warn: tuya.0 (15103) no connection to objects DB
2019-11-13 11:38:54.282 - warn: tr-064-community.0 (14931) no connection to states DB
2019-11-13 11:38:54.838 - warn: vis-google-fonts.0 (15350) no connection to objects DB
2019-11-13 11:38:56.750 - warn: tankerkoenig.0 (14634) no connection to states DB
2019-11-13 11:38:56.864 - warn: terminal.0 (14825) no connection to states DB
2019-11-13 11:38:57.161 - info: host.Ubuntu instance scheduled system.adapter.yr.0 33 * * * *
2019-11-13 11:38:57.201 - info: host.Ubuntu instance system.adapter.yr.0 started with pid 15851
2019-11-13 11:38:57.437 - warn: vis.0 (15525) no connection to objects DB
2019-11-13 11:38:57.577 - info: radar2.0 (14026) radar2 initialization started...
2019-11-13 11:38:57.580 - info: radar2.0 (14026) radar2 starting main...
2019-11-13 11:38:59.619 - info: host.Ubuntu instance system.adapter.fb-checkpresence.0 started with pid 16025
2019-11-13 11:39:01.789 - warn: tuya.0 (15103) no connection to states DB
2019-11-13 11:39:01.792 - warn: vis.0 (15525) no connection to states DB
2019-11-13 11:39:21.444 - info: radar2.0 (14026) Connected with '0.0.0.0' for DHCP Scan
2019-11-13 11:39:21.940 - info: radar2.0 (14026) Will try to scan BT devices: true
2019-11-13 11:39:23.830 - info: statistics.0 (14498) starting. Version 0.2.2 in /opt/iobroker/node_modules/iobroker.statistics, node: v8.16.2
2019-11-13 11:39:30.503 - info: statistics.0 (14498) [INFO] statistics observes 1 values after startup
2019-11-13 11:39:30.503 - info: statistics.0 (14498) [INFO] monitor "MyOwnData.0.Wetter.Ozon.Ozonwert" as avg
2019-11-13 11:39:30.505 - info: statistics.0 (14498) [INFO] monitor "MyOwnData.0.Wetter.Ozon.Ozonwert" as minmax
2019-11-13 11:39:33.364 - info: sonoff.0 (14322) Starting MQTT authenticated server on port 1885
2019-11-13 11:39:33.665 - warn: upnp.0 (15260) no connection to objects DB
2019-11-13 11:39:33.875 - warn: web.0 (15839) no connection to objects DB
2019-11-13 11:39:33.885 - warn: yr.0 (15851) no connection to objects DB
...und weitere Connect-Fehler

                                  Daraufhin habe ich nochmal in den Einstellungen geschaut, der Connection-Timeout stand da (noch) auf 2000ms.
                                  Dann habe ich den ioB gestoppt, den Timeout händisch mal auf 3 Sek. gestellt und seit ~ 2 h ist absolute Ruhe, kein einziger Fehler mehr. Muss ich aber noch mal über einen ganzen Tag beobachten 🙂

                                  apollon77 1 Reply Last reply Reply Quote 0
                                  • Neuschwansteini
                                    Neuschwansteini @apollon77 last edited by

                                    @apollon77 ab 11:42...
                                    hmm hab jetzt mal iobroker stop, und wieder gestartet, läuft.. hmm.. vielleicht hab ich nicht lange genug gewartet..

                                    2019-11-13 11:35:30.912  - warn: host.iobroker Multihost discovery server: service started on 0.0.0.0:50005
2019-11-13 11:41:29.432  - info: host.iobroker iobroker.js-controller version 2.0.43 js-controller starting
2019-11-13 11:41:29.435  - info: host.iobroker Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
2019-11-13 11:41:29.436  - info: host.iobroker hostname: iobroker, node: v10.17.0
2019-11-13 11:41:29.436  - info: host.iobroker ip addresses: 192.168.178.41 2001:16b8:20a3:f500:b01e:c80:4af8:2b16 fe80::9e97:b87d:9152:5695
2019-11-13 11:41:30.270  - info: host.iobroker connected to Objects and States
2019-11-13 11:41:30.513  - info: host.iobroker 71 instances found
2019-11-13 11:41:30.593  - info: host.iobroker starting 64 instances
2019-11-13 11:41:30.601  - warn: host.iobroker Multihost discovery server: service started on 0.0.0.0:50005
2019-11-13 11:41:30.619  - info: host.iobroker instance system.adapter.admin.0 started with pid 833
2019-11-13 11:41:34.609  - info: host.iobroker instance system.adapter.mihome.0 started with pid 855
2019-11-13 11:41:38.609  - info: host.iobroker instance system.adapter.wifilight.0 started with pid 871
2019-11-13 11:41:42.606  - info: host.iobroker instance system.adapter.amazon-dash.0 started with pid 887
2019-11-13 11:41:46.607  - info: host.iobroker instance system.adapter.cloud.0 started with pid 913
2019-11-13 11:41:50.610  - info: host.iobroker instance system.adapter.email.0 started with pid 928
2019-11-13 11:41:54.611  - info: host.iobroker instance system.adapter.email.1 started with pid 943
2019-11-13 11:41:58.603  - info: host.iobroker instance scheduled system.adapter.feiertage.0 0 0 * * *
2019-11-13 11:41:58.618  - info: host.iobroker instance system.adapter.feiertage.0 started with pid 959
2019-11-13 11:42:02.291  - info: host.iobroker instance system.adapter.feiertage.0 terminated with code 0 (NO_ERROR)
2019-11-13 11:42:02.613  - info: host.iobroker instance system.adapter.firetv.0 started with pid 974
2019-11-13 11:42:04.105  - error: firetv.0 (974) ID: 192.168.178.83 Error=Failure: 'device unauthorized. Please check the confirmation dialog on your device.'
2019-11-13 11:42:04.107  - error: firetv.0 (974) ID: 192.168.178.85 Error=Failure: 'device unauthorized. Please check the confirmation dialog on your device.'
2019-11-13 11:42:04.110  - error: firetv.0 (974) ID: 192.168.178.83 Error=Failure: 'device unauthorized. Please check the confirmation dialog on your device.'
2019-11-13 11:42:04.111  - error: firetv.0 (974) ID: 192.168.178.85 Error=Failure: 'device unauthorized. Please check the confirmation dialog on your device.'
2019-11-13 11:42:04.114  - error: firetv.0 (974) ID: 192.168.178.83 Error=Failure: 'device unauthorized. Please check the confirmation dialog on your device.'
2019-11-13 11:42:04.117  - error: firetv.0 (974) ID: 192.168.178.85 Error=Failure: 'device unauthorized. Please check the confirmation dialog on your device.'
2019-11-13 11:42:06.609  - info: host.iobroker instance system.adapter.history.0 started with pid 1004
2019-11-13 11:42:09.594  - warn: history.0 (1004) Alias * has no target 12
2019-11-13 11:42:10.196  - warn: host.iobroker "system.host.zweiberry" is offline
2019-11-13 11:42:10.196  - warn: host.iobroker "system.host.zeroberry" is offline
2019-11-13 11:42:10.196  - warn: host.iobroker "system.host.berrymotion" is offline
2019-11-13 11:42:10.197  - warn: host.iobroker "system.host.meterberry" is offline
2019-11-13 11:42:10.197  - warn: host.iobroker "system.host.gymberry" is offline
2019-11-13 11:42:10.611  - info: host.iobroker instance system.adapter.info.0 started with pid 1019
2019-11-13 11:42:14.608  - info: host.iobroker instance system.adapter.javascript.0 started with pid 1039
2019-11-13 11:42:18.799  - info: host.iobroker instance system.adapter.mihome-vacuum.0 started with pid 1545
2019-11-13 11:42:20.717  - info: host.iobroker Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
2019-11-13 11:42:20.720  - warn: host.iobroker "system.host.zweiberry" is offline
                                    apollon77 1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 @SBorg last edited by

                                      @SBorg Das betrifft genau diesen. Kannst es auf 2000 in den Settings lassen. Im Code wird der verdoppelt 🙂 Htte also auch schon vorher ruhig gewesen sein sollen. SOnst ist dein system echt komisch und braucht lange zum "hochfahren" eines Adapter-prozesses

                                      SBorg 1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @Neuschwansteini last edited by

                                        @ilovegym Strange ... müssen wir beobachten

                                        Neuschwansteini 1 Reply Last reply Reply Quote 1
                                        • Neuschwansteini
                                          Neuschwansteini @apollon77 last edited by

                                          @apollon77 ich hab das unter "kann mal vorkommen" eingestuft.. solange das nicht öfters ist.. bis jetzt sonst keine Fehler im Log und auch keine Auffälligkeiten.. von daher..

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            schmid_no1 last edited by

                                            Nabend Jungs
                                            Habe die Version 2.0.24 noch installiert und wollte auch auf die 2.0.43 gehen und bekomme es nicht installiert bei
                                            "iobroker upgrade self"
                                            Kommt nur
                                            "host is up to date"

                                            Iobroker update habe ich gemacht

                                            Kann mir jemand sagen was ich falsch mache

                                            Glasfaser 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

                                            736
                                            Online

                                            31.6k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller
                                            89
                                            1052
                                            265252
                                            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