Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 4.0.x jetzt für alle User im STABLE!

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    js-controller 4.0.x jetzt für alle User im STABLE!

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

      @meister-mopper was stand im log? Falls du schauen willst.

      liv-in-sky 1 Reply Last reply Reply Quote 0
      • R
        rasrol last edited by rasrol

        Läuft perfekt.
        Ich musste zwar ein Neuinstallation per Script durchführen, aber seither keine Fehler.

        Debian 11
        Node.js:v14.19.0
        NPM:6.14.16

        Danke

        1 Reply Last reply Reply Quote 1
        • liv-in-sky
          liv-in-sky @apollon77 last edited by liv-in-sky

          @apollon77

          hat das was mit controller 4 zu tun - versuch javascript update - ging vor js-c update auch nicht zum updaten - mit controller 4 kommt beim update des javasc. adapters diese meldung:

          host.iobroker59
          2022-02-26 11:11:00.509	error	iobroker (node:27388) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency(node:27388) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency(node:27388) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
          host.iobroker59
          2022-02-26 11:11:00.505	error	iobroker (node:27388) Warning: Accessing non-existent property 'count' of module exports inside circular dependency(Use `node --trace-warnings ...` to show where the warning was created)
          

          siehe auch:https://forum.iobroker.net/post/768862

          nehme an, ist anderes topic - nicht für hier?

          apollon77 1 Reply Last reply Reply Quote 0
          • apollon77
            apollon77 @liv-in-sky last edited by apollon77

            @liv-in-sky ließ mal in der faq. Du hast ne alte mongodb lib wohl von nem node-red. Liegt eher an nodejs 14+ als am Controller.

            Latzi 1 Reply Last reply Reply Quote 0
            • andiko2
              andiko2 last edited by

              Habe heute die Updates gemacht und alles läuft soweit gut.

              Plattform
              linux
              Betriebssystem
              linux
              Architektur
              x64
              CPUs
              4
              Geschwindigkeit
              1692 MHz
              Modell
              Intel(R) Celeron(R) CPU J3455 @ 1.50GHz
              RAM
              7.64 GB
              System-Betriebszeit
              7 T. 01:15:35
              Node.js
              v12.22.10 (Empfohlene Version v14.19.0)
              time
              1645873156427
              timeOffset
              -60
              Anzahl der Adapter
              399
              NPM
              6.14.16
              Datenträgergröße
              109.04 GB
              freier Festplattenspeicher
              58.43 GB
              Betriebszeit
              00:29:23
              Aktive Instanzen
              26
              location
              /opt/iobroker/
              Hostname
              ioBrokerPC
              Einzigster Fehler mein Adapter Systeminfo geht nicht mehr. im Log steht volgendes:
              host.ioBrokerPC
              2022-02-26 12:25:34.470 error instance system.adapter.systeminfo.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
              systeminfo.0
              2022-02-26 12:25:33.842 error Cannot read property 'getObjectList' of undefined
              systeminfo.0
              2022-02-26 12:25:33.841 error TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:314:20) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8223:26
              systeminfo.0
              2022-02-26 12:25:33.838 error unhandled promise rejection: Cannot read property 'getObjectList' of undefined
              systeminfo.0
              2022-02-26 12:25:33.838 error 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().

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

                @andiko2 Zu systeminfo: siehe Post #1 ... da stehts drin inkkl. wie du es fixen kannst bis es ein Update gibt

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

                  @apollon77 was ist Post '#1? Bin nicht so der Forumkenner. Wenn möglich Link.

                  apollon77 T 2 Replies Last reply Reply Quote 0
                  • apollon77
                    apollon77 @andiko2 last edited by

                    @andiko2 Der erste Post in diesem Thread? Einfach gaaaaaaaaaaaaaaaaaaaanz nach oben Scrollen. Dort im Abschnitt "VOR der Installation"

                    1 Reply Last reply Reply Quote 0
                    • T
                      tobrog @andiko2 last edited by tobrog

                      @andiko2 Einfach in der Datei /opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js in Zeile 44 von"adapter.objects.getObjectList" zu "adapter.getObjectList" ändern.

                      andiko2 1 Reply Last reply Reply Quote 1
                      • T
                        TDCroPower last edited by

                        Update des js-controllers auf dem Docker Image von buanet ist durch, lediglich der rebuild vom BLE Adapter läuft bei 3 Versuchen nicht durch und im Log sieht man jetzt folgendes...

                        host.helios64
                        2022-02-26 12:48:17.793	info	Rebuild for adapter system.adapter.ble.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually.
                        host.helios64
                        2022-02-26 12:48:17.792	info	instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                        

                        wenn ich den Befehl in der Konsole eingebe kommt folgendes...

                        root@helios64:/opt/iobroker# npm install --production
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/fsevents):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/node_modules/fsevents):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                        
                        removed 3 packages and updated 1 package in 34.934s
                        
                        137 packages are looking for funding
                          run `npm fund` for details
                        
                        root@helios64:/opt/iobroker#
                        

                        was nun !?

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

                          @tobrog said in js-controller 4.0.x jetzt für alle User im STABLE!:

                          adapter.getObjectList

                          Dankeschön. Genau diese Info hat geholfen.

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

                            @tdcropower Naja du solltest den "npm install" in einem bestimmten Verzeichnis ausführen - steht an sich in den Anweisungen im Log. Du hast es im iobroker "root" verzeichnis ausgeführt. Das hilft nicht, ja.
                            Du musst es in /opt/iobroker/node_modules/iobroker.ble ausführen

                            Und ja leider ist der BLE Adapter bze eine Library davon gerade nicht rebuild-fähig. Wir haben dort schon eine Änderung eingereicht, die ist aber noch nicht released.

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

                              @apollon77 danke habe es eben auch im Issue bei git gelesen.
                              Leider fehlt der Hinweis auf das Verzeichnis in der Log Nachricht, wobei "adapter directory" es eigentlich sagt.

                              Naja, jetzt hat es funktioniert...

                              root@helios64:/opt/iobroker# cd node_modules/iobroker.ble/
                              root@helios64:/opt/iobroker/node_modules/iobroker.ble# npm install -- production
                              npm WARN deprecated request@2.12.0: request has been deprecated, see https://github.com/request/request/issues/3142
                              
                              > deasync@0.1.24 install /opt/iobroker/node_modules/iobroker.ble/node_modules/deasync
                              > node ./build.js
                              
                              make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/build'
                                CXX(target) Release/obj.target/deasync/src/deasync.o
                                SOLINK_MODULE(target) Release/obj.target/deasync.node
                                COPY Release/deasync.node
                              make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/build'
                              Installed in `/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/bin/linux-arm64-node-14/deasync.node`
                              
                              > usb@1.9.2 install /opt/iobroker/node_modules/iobroker.ble/node_modules/usb
                              > node-gyp-build
                              
                              make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/build'
                                CC(target) Release/obj.target/libusb/libusb/libusb/core.o
                                CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
                                CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
                                CC(target) Release/obj.target/libusb/libusb/libusb/io.o
                                CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
                                CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
                                CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
                                CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
                                CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
                                CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
                                AR(target) Release/obj.target/usb.a
                                COPY Release/usb.a
                                CXX(target) Release/obj.target/usb_bindings/src/node_usb.o
                              ../src/node_usb.cc: In function ‘Napi::Value SetDebugLevel(const Napi::CallbackInfo&)’:
                              ../src/node_usb.cc:118:71: warning: ‘void libusb_set_debug(libusb_context*, int)’ is deprecated: Use libusb_set_option instead [-Wdeprecated-declarations]
                                118 |  libusb_set_debug(usb_context, info[0].As<Napi::Number>().Int32Value());
                                    |                                                                       ^
                              In file included from ../src/node_usb.h:11,
                                               from ../src/node_usb.cc:1:
                              ../libusb/libusb/libusb.h:1325:18: note: declared here
                               1325 | void LIBUSB_CALL libusb_set_debug(libusb_context *ctx, int level);
                                    |                  ^~~~~~~~~~~~~~~~
                                CXX(target) Release/obj.target/usb_bindings/src/device.o
                                CXX(target) Release/obj.target/usb_bindings/src/transfer.o
                                SOLINK_MODULE(target) Release/obj.target/usb_bindings.node
                                COPY Release/usb_bindings.node
                              make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/build'
                              
                              > @abandonware/bluetooth-hci-socket@0.5.3-8 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket
                              > node-pre-gyp install --fallback-to-build
                              
                              node-pre-gyp ERR! install response status 404 Not Found on https://github.com/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v83-linux-arm64.tar.gz 
                              node-pre-gyp WARN Pre-built binaries not installable for @abandonware/bluetooth-hci-socket@0.5.3-8 and node@14.18.2 (node-v83 ABI, glibc) (falling back to source compile with node-gyp) 
                              node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v83-linux-arm64.tar.gz 
                              make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/build'
                                CXX(target) Release/obj.target/bluetooth_hci_socket/src/BluetoothHciSocket.o
                              In file included from /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node_buffer.h:25,
                                               from ../src/BluetoothHciSocket.cpp:7:
                              /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:787:7: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                787 |       (node::addon_register_func) (regfunc),                          \
                                    |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                              /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:821:3: note: in expansion of macro ‘NODE_MODULE_X’
                                821 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                                    |   ^~~~~~~~~~~~~
                              ../src/BluetoothHciSocket.cpp:635:1: note: in expansion of macro ‘NODE_MODULE’
                                635 | NODE_MODULE(binding, BluetoothHciSocket::Init);
                                    | ^~~~~~~~~~~
                              ../src/BluetoothHciSocket.cpp: In member function ‘int BluetoothHciSocket::kernelDisconnectWorkArounds(int, char*)’:
                              ../src/BluetoothHciSocket.cpp:401:1: warning: control reaches end of non-void function [-Wreturn-type]
                                401 | }
                                    | ^
                                SOLINK_MODULE(target) Release/obj.target/bluetooth_hci_socket.node
                                COPY Release/bluetooth_hci_socket.node
                                COPY /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node
                                TOUCH Release/obj.target/action_after_build.stamp
                              make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/build'
                              
                              > @abandonware/noble@1.9.2-15 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble
                              > node-gyp rebuild
                              
                              make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build'
                                SOLINK_MODULE(target) Release/obj.target/noble.node
                                COPY Release/noble.node
                              make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build'
                              
                              > core-js@2.6.12 postinstall /opt/iobroker/node_modules/iobroker.ble/node_modules/core-js
                              > node -e "try{require('./postinstall')}catch(e){}"
                              
                              Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
                              
                              The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 
                              > https://opencollective.com/core-js 
                              > https://www.patreon.com/zloirock 
                              
                              Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
                              
                              
                              > parcel-bundler@1.12.5 postinstall /opt/iobroker/node_modules/iobroker.ble/node_modules/parcel-bundler
                              > node -e "console.log('\u001b[35m\u001b[1mLove Parcel? You can now donate to our open collective:\u001b[22m\u001b[39m\n > \u001b[34mhttps://opencollective.com/parcel/donate\u001b[0m')"
                              
                              Love Parcel? You can now donate to our open collective:
                               > https://opencollective.com/parcel/donate
                              npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/glob-watcher/node_modules/fsevents):
                              npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                              npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/@parcel/watcher/node_modules/fsevents):
                              npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                              npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
                              npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                              
                              + production@0.0.2
                              added 1489 packages from 1205 contributors in 146.424s
                              
                              109 packages are looking for funding
                                run `npm fund` for details
                              
                              root@helios64:/opt/iobroker/node_modules/iobroker.ble#
                              

                              .. danach nur noch den Adapter neustarten und er ist wieder Grün!

                              mikeal created this issue in request/request

                              open Request’s Past, Present and Future #3142

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

                                @tdcropower

                                mit root geht es mit nodejs nicht gut!

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

                                  @tdcropower Jupp. Jetzt am besten ein „iob fix“ hinterher und dann am besten nicht mehr mit root

                                  T 1 Reply Last reply Reply Quote 1
                                  • T
                                    TDCroPower @apollon77 last edited by

                                    @apollon77 ihr habt Recht, im Docker Image gibt es noch einen iobroker user auf dem iobroker installiert wurde.

                                    iobroker@helios64:~$ ls -l
                                    total 1132
                                    drwxrwxr-x+   3 iobroker iobroker    4096 Feb 26 02:30 backups
                                    -rwxrwxrwx+   1 iobroker iobroker     233 Nov 23 16:15 INSTALLER_INFO.txt
                                    lrwxrwxrwx    1 iobroker iobroker      22 Nov 23 16:15 iob -> /opt/iobroker/iobroker
                                    -rwxr-xr-x+   1 iobroker iobroker     178 Feb 26 12:56 iobroker
                                    -rwxr-xr-x+   1 iobroker iobroker     178 Feb 26 12:40 iobroker.bak
                                    drwxrwxr-x+  10 iobroker iobroker    4096 Feb 26 14:20 iobroker-data
                                    drwxrwxr-x+   2 iobroker iobroker    4096 Feb 26 13:30 log
                                    drwxrwxr-x+ 621 iobroker iobroker   20480 Feb 26 12:51 node_modules
                                    -rw-rwxr--+   1 iobroker iobroker     864 Feb 26 12:39 package.json
                                    -rw-rwxr--+   1 iobroker iobroker 1098042 Feb 26 12:51 package-lock.json
                                    -rw-rwxr--+   1 iobroker iobroker    5693 Dez 23 01:16 reinstall.js
                                    iobroker@helios64:~$
                                    

                                    Dann bleibt der default Portainer User root wieder weg.

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

                                      Ich habe gerade das Update nach Anleitung gemacht. Leider ist wohl ein Fehler aufgetreten, jetzt scheint mein ioBroker tot zu sein. Da ich Linux-mäßig leider Laie bin, fehlt mir jetzt ehrlich gesagt die Idee, wie ich am besten mit einer Reparatur anfangen kann.

                                      tlettschmidt@iobroker:~$ iob upgrade self
                                      Update js-controller from @3.3.22 to @4.0.15
                                      NPM version: 6.14.16
                                      npm install iobroker.js-controller@4.0.15 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                                      In file included from ../../nan/nan.h:58,
                                                       from ../src/unix_dgram.cc:5:
                                      /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                        793 |       (node::addon_register_func) (regfunc),                          \
                                            |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                      /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
                                        827 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                                            |   ^~~~~~~~~~~~~
                                      ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
                                        404 | NODE_MODULE(unix_dgram, Initialize)
                                            | ^~~~~~~~~~~
                                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
                                      Server States 127.0.0.1:56264 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
                                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
                                      Server States 127.0.0.1:56268 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: Unknown LUA script load
                                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: Unknown LUA script load
                                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: Unknown LUA script load
                                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                                      Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                                      

                                      Bin für jede Anregung und jeden Tipp dankbar.

                                      E 1 Reply Last reply Reply Quote 0
                                      • E
                                        Etbron @Etbron last edited by

                                        Schnappatmung hat sich ein wenig beruhigt. Ich habe ihn nochmal gestoppt, nochmal gestartet und scheinbar läuft er jetzt. Trotzdem wäre es schön, wenn sich jemand den Fehler anschauen würde und mir ein kurzes Feedback geben könnte, ob ich jetzt ein problem habe bzw. bekommen werde.

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

                                          @tdcropower ok da bin ich ehrlich. Keine Ahnung. An sich sollte man nicht mit dem iobroker User arbeiten. @andre ?! Wie ist das bei Docker am besten?!

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

                                            @etbron das ist alles ok. Ließ doch mal gaaaaanz oben im ersten post. Da steht alles drin. Diese Meldungen sind erwartet gewesen und daher voll normal. Jaaaanz ruhig

                                            E 1 Reply Last reply Reply Quote 1
                                            • First post
                                              Last post

                                            Support us

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

                                            536
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            83
                                            501
                                            107084
                                            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