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 jetzt im BETA/LATEST!

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    js-controller 4.0 jetzt im BETA/LATEST!

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

      @apollon77 Der wird mir abr noch nicht im admin angezeigt, muss/soll ich den über die Katze installieren?

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

        @amg_666

        ist auf dem Weg ins Beta/Latest Repo.

        ... Naja der weg ist manchmal lang ... 🙂

        1.) Hast Du repo aktualisiert?
        2.) Hast Du Beta/Latest Repo?
        3.) Falls 1+2 ja ... versuch später nochmal ... CDN Updates brauchen auch zeit

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

          @apollon77 beta Repro, ich sehe aber jetzt in der Konsole, dass bei "iob update" die 4.0.18 angezeigt wird. Alles gut...

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

            @amg_666 Und nochwas: js-controller NIE über GitHub installieren!!

            arteck amg_666 2 Replies Last reply Reply Quote 0
            • arteck
              arteck Developer Most Active @apollon77 last edited by arteck

              @apollon77 das jeht doch nicht mehr 😊 aber echt ehhhh

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

                @apollon77 Das war ein Denkfehler von mir. ist ja kein Adapter...
                So ist bei mir installiert (iob auf nuc mit Debian 10 im Container und einmal Slave auf Raspi 3b), lief soweit alles fehlerfrei durch.
                backitup habe ich noch getestet: Das Backup lief durch, danach "hängt" aber das Fenster im Adminadapter (schließt sich nicht)
                cb43fb0e-0fe3-4c44-ac8a-c56311779dd1-grafik.png

                Laut log ist er aber durch:

                backitup.0
	2022-03-04 11:32:38.524	debug	slave backups are completed
backitup.0
	2022-03-04 11:32:38.524	debug	Slave Backup from backitup.1 is finish with result: [EXIT] 0
backitup.0
	2022-03-04 11:32:33.019	debug	Slave backup from Backitup-Master is started ...
                apollon77 1 Reply Last reply Reply Quote 0
                • Diginix
                  Diginix @apollon77 last edited by

                  @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                  @Diginix Happy testing "erase on Upload" (ein iob upload adaptername/all hat den gleichen effekt und räumt auch vor dem Upload auf)

                  Danke für Euer Feedback

                  Ingo

                  iob upload all hat noch mal 20 MB bereinigt. Ich hatte ja schon mehrere 100 MB zuvor händisch bereinigt.
                  Dürfte also bei nicht wenigen Usern zu deutlich freiwerdenden Plattenplatz führen.

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

                    @apollon77 👍 sauber durchgeflutscht!

                    woody@ioBroker:~$ iob status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl
woody@ioBroker:~$

                    db2c24a8-0913-433a-bd3d-ec03c452529c-grafik.png

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

                      @amg_666 Naja melde das am besten mal im backitup thread

                      coyote 1 Reply Last reply Reply Quote 0
                      • coyote
                        coyote Most Active @apollon77 last edited by coyote

                        @apollon77
                        ich weiß nicht, ob es was mit dem js-controller zu tun hat, ich bekomme beim hochlaufen sowas hier:

                        
javascript.0
2022-03-04 15:35:19.513	error	In file included from ../src/binding.cc:6: /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793: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] 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/binding.cc:2003:1: note: in expansion of macro 'NODE_MODULE' 2003 | NODE_MODULE(sshcrypto, init) | ^~~~~~~~~~~

javascript.0
2022-03-04 15:35:17.326	error	In file included from ../src/binding.cc:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793: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] 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/binding.cc:153:1: note: in expansion of macro 'NODE_MODULE' 153 | NODE_MODULE(cpufeatures, init) | ^~~~~~~~~~~

                        Etwas mehr log:

                        
javascript.0
2022-03-04 15:35:19.513	error	In file included from ../src/binding.cc:6: /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793: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] 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/binding.cc:2003:1: note: in expansion of macro 'NODE_MODULE' 2003 | NODE_MODULE(sshcrypto, init) | ^~~~~~~~~~~

javascript.0
2022-03-04 15:35:18.461	info	CXX(target) Release/obj.target/sshcrypto/src/binding.o

javascript.0
2022-03-04 15:35:18.459	info	make: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/ssh2/lib/protocol/crypto/build'
host.ioBroker
2022-03-04 15:35:18.323	info	instance system.adapter.ical.1 started with pid 142315
host.ioBroker
2022-03-04 15:35:18.312	info	instance scheduled system.adapter.ical.1 0,30 * * * *

javascript.0
2022-03-04 15:35:17.745	info	> ssh2@1.6.0 install /opt/iobroker/node_modules/iobroker.javascript/node_modules/ssh2 > node install.js

javascript.0
2022-03-04 15:35:17.717	info	make: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/build'

javascript.0
2022-03-04 15:35:17.711	info	COPY Release/cpufeatures.node

javascript.0
2022-03-04 15:35:17.619	info	SOLINK_MODULE(target) Release/obj.target/cpufeatures.node

javascript.0
2022-03-04 15:35:17.326	error	In file included from ../src/binding.cc:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793: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] 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/binding.cc:153:1: note: in expansion of macro 'NODE_MODULE' 153 | NODE_MODULE(cpufeatures, init) | ^~~~~~~~~~~

hm-rpc.2
2022-03-04 15:35:16.698	info	new HMIP devices/channels after filter: 0

javascript.0
2022-03-04 15:35:16.572	info	CXX(target) Release/obj.target/cpufeatures/src/binding.o

javascript.0
2022-03-04 15:35:16.566	info	TOUCH Release/obj.target/build_deps.stamp

javascript.0
2022-03-04 15:35:16.561	info	gmake[1]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:16.545	info	gmake[2]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:16.543	info	[100%] Built target unix_based_hardware_detection

javascript.0
2022-03-04 15:35:16.527	info	gmake[3]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

hm-rpc.2
2022-03-04 15:35:16.481	info	xmlrpc <- newDevices 60

javascript.0
2022-03-04 15:35:16.470	info	[100%] Building C object CMakeFiles/unix_based_hardware_detection.dir/src/unix_features_aggregator.c.o

javascript.0
2022-03-04 15:35:16.375	info	[ 88%] Building C object CMakeFiles/unix_based_hardware_detection.dir/src/hwcaps.c.o

javascript.0
2022-03-04 15:35:16.354	info	gmake[3]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:16.351	info	gmake[3]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:16.349	info	Scanning dependencies of target unix_based_hardware_detection

javascript.0
2022-03-04 15:35:16.332	info	gmake[3]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:16.329	info	[ 77%] Built target list_cpu_features

javascript.0
2022-03-04 15:35:16.314	info	gmake[3]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

hm-rpc.2
2022-03-04 15:35:16.289	info	xmlrpc -> 0 devices

javascript.0
2022-03-04 15:35:16.263	info	[ 77%] Linking C executable list_cpu_features

hm-rpc.2
2022-03-04 15:35:16.069	info	xmlrpc <- listDevices ["ioBroker:hm-rpc.2:b33106cb96ac33f808729bdd7f5821c9"]

javascript.0
2022-03-04 15:35:16.002	info	[ 66%] Building C object CMakeFiles/list_cpu_features.dir/src/utils/list_cpu_features.c.o

hm-rpc.2
2022-03-04 15:35:15.988	info	Connected

javascript.0
2022-03-04 15:35:15.987	info	gmake[3]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.985	info	gmake[3]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.984	info	Scanning dependencies of target list_cpu_features

javascript.0
2022-03-04 15:35:15.968	info	gmake[3]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.965	info	[ 55%] Built target cpu_features

hm-rpc.2
2022-03-04 15:35:15.942	info	xmlrpc client is trying to connect to 192.168.66.36:2010/ with ["http://192.168.66.68:2000","ioBroker:hm-rpc.2:b33106cb96ac33f808729bdd7f5821c9"]

hm-rpc.2
2022-03-04 15:35:15.941	info	xmlrpc server is trying to listen on 192.168.66.68:2000

javascript.0
2022-03-04 15:35:15.949	info	gmake[3]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.901	info	[ 55%] Linking C static library libcpu_features.a

hm-rpc.2
2022-03-04 15:35:15.479	info	starting. Version 1.15.8 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v14.19.0, js-controller: 4.0.18

javascript.0
2022-03-04 15:35:15.514	info	[ 44%] Building C object CMakeFiles/cpu_features.dir/src/cpuinfo_x86.c.o

javascript.0
2022-03-04 15:35:15.500	info	gmake[3]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.497	info	gmake[3]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.496	info	Scanning dependencies of target cpu_features

javascript.0
2022-03-04 15:35:15.474	info	gmake[3]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.469	info	[ 33%] Built target utils

javascript.0
2022-03-04 15:35:15.452	info	gmake[3]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

hm-rpc.2
2022-03-04 15:35:15.406	info	Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system

javascript.0
2022-03-04 15:35:15.312	info	[ 33%] Building C object CMakeFiles/utils.dir/src/string_view.c.o

javascript.0
2022-03-04 15:35:15.240	info	[ 22%] Building C object CMakeFiles/utils.dir/src/stack_line_reader.c.o

javascript.0
2022-03-04 15:35:15.162	info	[ 11%] Building C object CMakeFiles/utils.dir/src/filesystem.c.o

javascript.0
2022-03-04 15:35:15.148	info	gmake[3]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.145	info	gmake[3]: Leaving directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.143	info	Scanning dependencies of target utils

javascript.0
2022-03-04 15:35:15.122	info	gmake[3]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.119	info	gmake[2]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.080	info	gmake[1]: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build'

javascript.0
2022-03-04 15:35:15.050	info	ACTION Building dependencies /opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build/libcpu_features.a

javascript.0
2022-03-04 15:35:15.045	info	TOUCH Release/obj.target/config_deps.stamp

javascript.0
2022-03-04 15:35:15.040	info	-- Build files have been written to: /opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build

javascript.0
2022-03-04 15:35:15.038	info	-- Generating done

javascript.0
2022-03-04 15:35:15.024	info	-- Configuring done

javascript.0
2022-03-04 15:35:15.014	info	-- Looking for getauxval - found

javascript.0
2022-03-04 15:35:14.858	info	-- Looking for getauxval

javascript.0
2022-03-04 15:35:14.857	info	-- Looking for dlfcn.h - found

javascript.0
2022-03-04 15:35:14.718	info	-- Looking for dlfcn.h

javascript.0
2022-03-04 15:35:14.708	info	-- Detecting C compile features - done

javascript.0
2022-03-04 15:35:14.705	info	-- Detecting C compile features

javascript.0
2022-03-04 15:35:14.704	info	-- Check for working C compiler: /usr/bin/cc - skipped

javascript.0
2022-03-04 15:35:14.665	info	-- Detecting C compiler ABI info - done

javascript.0
2022-03-04 15:35:14.528	info	-- Detecting C compiler ABI info

javascript.0
2022-03-04 15:35:14.502	info	-- The C compiler identification is GNU 10.2.1

javascript.0
2022-03-04 15:35:14.328	info	ACTION Configuring dependencies /opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/deps/cpu_features/build/Makefile
host.ioBroker
2022-03-04 15:35:14.325	info	instance system.adapter.hm-rpc.2 started with pid 142091

javascript.0
2022-03-04 15:35:14.321	info	make: Entering directory '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features/build'


javascript.0
2022-03-04 15:35:13.582	info	> cpu-features@0.0.2 install /opt/iobroker/node_modules/iobroker.javascript/node_modules/cpu-features > node-gyp rebuild

                        Ansonsten sieht alles gut aus. Alle Adapter laufen bisher ohne Fehler 👍

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

                          @coyote Alles gut da wurde das eine native Modul neu gebaut. Sind die üblichen Ausgaben halt

                          1 Reply Last reply Reply Quote 1
                          • B
                            blackeagle998 last edited by

                            @apollon77
                            Ist das jetzt hier der richtige BETA Thread?
                            Um deine Frage zu beantworten, hier die Auszüge aus dem SYSLOG:

                            Mar  4 16:34:18 RasPImaster bash[1219]: /opt/iobroker/node_modules/@iobroker/db-base/lib/inMemFileDB.js:187
Mar  4 16:34:18 RasPImaster bash[1219]:             this.log.warn(
Mar  4 16:34:18 RasPImaster bash[1219]:                      ^
Mar  4 16:34:18 RasPImaster bash[1219]: TypeError: Cannot read property 'warn' of undefined
Mar  4 16:34:18 RasPImaster bash[1219]:     at ObjectsInMemoryServer.initBackupDir (/opt/iobroker/node_modules/@iobroker/db-base/lib/inMemFileDB.js:187:22)
Mar  4 16:34:18 RasPImaster bash[1219]:     at new InMemoryFileDB (/opt/iobroker/node_modules/@iobroker/db-base/lib/inMemFileDB.js:83:18)
Mar  4 16:34:18 RasPImaster bash[1219]:     at new ObjectsInMemoryFileDB (/opt/iobroker/node_modules/@iobroker/db-objects-file/lib/objects/objectsInMemFileDB.js:34:9)
Mar  4 16:34:18 RasPImaster bash[1219]:     at new ObjectsInMemoryJsonlDB (/opt/iobroker/node_modules/@iobroker/db-objects-jsonl/lib/objects/objectsInMemJsonlDB.js:58:9)
Mar  4 16:34:18 RasPImaster bash[1219]:     at new ObjectsInMemoryServer (/opt/iobroker/node_modules/@iobroker/db-objects-jsonl/lib/objects/objectsInMemServerRedis.js:57:9)
Mar  4 16:34:18 RasPImaster bash[1219]:     at new ObjectsInMemoryServerClass (/opt/iobroker/node_modules/@iobroker/db-objects-jsonl/lib/objects/objectsInMemServerClass.js:34:30)
Mar  4 16:34:18 RasPImaster bash[1219]:     at createObjects (/opt/iobroker/node_modules/iobroker.js-controller/main.js:581:15)
Mar  4 16:34:18 RasPImaster bash[1219]:     at Object.init (/opt/iobroker/node_modules/iobroker.js-controller/main.js:5554:5)
Mar  4 16:34:18 RasPImaster bash[1219]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:8:19)
Mar  4 16:34:18 RasPImaster bash[1219]:     at Module._compile (internal/modules/cjs/loader.js:1085:14)
Mar  4 16:34:18 RasPImaster systemd[1]: iobroker.service: Main process exited, code=exited, status=1/FAILURE
Mar  4 16:34:18 RasPImaster systemd[1]: iobroker.service: Failed with result 'exit-code'.
Mar  4 16:34:21 RasPImaster systemd[1]: iobroker.service: Service RestartSec=3s expired, scheduling restart.
Mar  4 16:34:21 RasPImaster systemd[1]: iobroker.service: Scheduled restart job, restart counter is at 2.
Mar  4 16:34:21 RasPImaster systemd[1]: Stopped ioBroker Server.
                            apollon77 1 Reply Last reply Reply Quote 1
                            • apollon77
                              apollon77 @blackeagle998 last edited by

                              @blackeagle998 Ja, und ....... ja mist ... Der Fix ging das wohl am Problem vorbei. Ok, bitte einfach richtige Werte in der Konfig haben dann ists weg. Ich überlege mal ob wir noch einen Fix extra deswegen machen, denke aber eher nicht

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

                                @apollon77
                                Ich weiß ja nicht mal wo die 7200000 herkommen...
                                In beiden Controller Konfigurationen steht bei Objects und States jeweils 120 als Wert drin.
                                Scheint fast so, als wenn irgendwo noch eine Umrechnung in Millisekunden aktiv ist 120 * 60 * 1000 = 7200000.

                                Mir ist jedenfalls nicht bewusst, dass ich irgendwo diesen Wert drin stehen habe oder gibt es noch andere Stellen als /opt/iobroker/iobroker-data/iobroker.json?
                                Interessant ist ja auch, dass ich dieses File mittlerweile 5 mal editiert habe und es offensichtlich von irgendwo immer wieder mit den "falschen" Werten überschrieben wird.

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

                                  @blackeagle998 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                  Scheint fast so, als wenn irgendwo noch eine Umrechnung in Millisekunden aktiv ist 120 * 60 * 60 = 7200000.

                                  Nutzt du vllt Admin um das zu tun? Kann es sein das Admin das falsch schreibt?

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

                                    @apollon77
                                    Btw. die Rechnung habe ich oben korrigiert, muss natürlich 120 * 60 * 1000 heißen, aber egal.
                                    Das Editieren der JSON Datei habe ich auf der Konsole gemacht, per nano Befehl.

                                    In den Konfigurationen steht schon immer 120, ich habe da nie was angefasst, aber ja, es kann sein, dass beim Speichern der Konfig die Werte überschrieben werden. Ich habe eben mal eine Einstellung im Multi-Host Reiter geändert und gespeichert, aktuell sind die 120 als Wert geblieben.
                                    Such die Nadel im Heuhaufen 🤔

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

                                      @blackeagle998 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                      120 * 60 * 1000

                                      Wenn Du es findest sag bescheid 🙂

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        darkiop Most Active @apollon77 last edited by

                                        @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                        4.0.18 (2022-03-04)

                                        läuft .... Und die Augen sind offen 😉

                                        D 1 Reply Last reply Reply Quote 1
                                        • L
                                          lonsimbt @apollon77 last edited by

                                          @apollon77
                                          Das Update auf 4.0.18 ist ohne Probleme oder Fehlermeldungen durchgelaufen. System läuft!

                                          Gruß Marco

                                          1 Reply Last reply Reply Quote 1
                                          • AlCalzone
                                            AlCalzone Developer @blackeagle998 last edited by

                                            @blackeagle998 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                            7200000

                                            Stand auch bei demjenigen User, bei dem ich die fehlerhafte Konfiguration überhaupt erst gefunden hab. Oder warst du das?

                                            B apollon77 2 Replies 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

                                            425
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            70
                                            747
                                            172337
                                            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