NEWS
ioBroker.js-controller 1.5.6
-
Es scheint alles zu laufen.
Scheinbar habe ich noch irgendwo einen undefinierten State, der vorher aber nicht bemerkt wurde.
Jetzt bekomme ich eine minütliche Fehlermeldungjavascript.0 2019-02-13 07:48:00.596 error Error in callback: TypeError: Cannot read property 'common' of undefinedIch habe schon alle Scripts durchgesucht, ob ich irgendwo einen Minuten Timer habe. Aber ich habe leider nach 30 Minuten Suche nichts gefunden.
-
Ich konnte es jetzt einkreisen.
javascript.0 2019-02-13 07:56:00.209 error Error in callback: TypeError: Cannot read property 'common' of undefined javascript.0 2019-02-13 07:55:38.422 error Error in callback: TypeError: Cannot read property 'common' of undefined javascript.0 2019-02-13 07:55:38.248 error TypeError: Cannot read property 'common' of undefined javascript.0 2019-02-13 07:55:38.248 error ^ javascript.0 2019-02-13 07:55:38.247 error if (!language || !dayOfWeeksFull[language]) language = objects['system.config'].common.language; javascript.0 2019-02-13 07:55:38.247 error script.js.common.Tagescharacteristik: /opt/iobroker/node_modules/iobroker.javascript/javascript.js:2712Es ist das Kommando formatDate(new Date(), "W hh:mm").
Liegt nicht an meinen Scripts sondern wohl an der neuen js-controller Version
Was funktioniert ist: formatDate(new Date(), "hh:mm")
update:- WW, НН(cyrillic) - full week day as text
- W, Н(cyrillic) - short week day as text
funktionieren alle nicht mehr
HW:NUC (16 GB Ram)
OS: Debian Bullseye, Promox V7, node v16.x npm 8.19.3 -
Ich konnte es jetzt einkreisen.
javascript.0 2019-02-13 07:56:00.209 error Error in callback: TypeError: Cannot read property 'common' of undefined javascript.0 2019-02-13 07:55:38.422 error Error in callback: TypeError: Cannot read property 'common' of undefined javascript.0 2019-02-13 07:55:38.248 error TypeError: Cannot read property 'common' of undefined javascript.0 2019-02-13 07:55:38.248 error ^ javascript.0 2019-02-13 07:55:38.247 error if (!language || !dayOfWeeksFull[language]) language = objects['system.config'].common.language; javascript.0 2019-02-13 07:55:38.247 error script.js.common.Tagescharacteristik: /opt/iobroker/node_modules/iobroker.javascript/javascript.js:2712Es ist das Kommando formatDate(new Date(), "W hh:mm").
Liegt nicht an meinen Scripts sondern wohl an der neuen js-controller Version
Was funktioniert ist: formatDate(new Date(), "hh:mm")
update:- WW, НН(cyrillic) - full week day as text
- W, Н(cyrillic) - short week day as text
funktionieren alle nicht mehr
-
Hab es mal versucht, sieht nicht so gut aus.
root@ioBroker-OPi2E:~# iobroker stop Stopping iobroker controller daemon... iobroker controller daemon stopped. Exit code for "killall.sh": 0 root@ioBroker-OPi2E:~# cd .. root@ioBroker-OPi2E:/# cd opt root@ioBroker-OPi2E:/opt# cd iobroker root@ioBroker-OPi2E:/opt/iobroker# npm i iobroker.js-controller@1.5.5 npm WARN lifecycle iobroker.js-controller@1.5.5~preinstall: cannot run in wd %s %s (wd=%s) iobroker.js-controller@1.5.5 node lib/preinstallCheck.js /opt/iobroker/node_modules/.staging/iobroker.js-controller-a76002ca > authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam > node-gyp rebuild make: Entering directory '/opt/iobroker/node_modules/authenticate-pam/build' CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o ../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: No such file or directory compilation terminated. authenticate_pam.target.mk:92: recipe for target 'Release/obj.target/authenticate_pam/authenticate_pam.o' failed make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Error 1 make: Leaving directory '/opt/iobroker/node_modules/authenticate-pam/build' gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23) gyp ERR! stack at emitTwo (events.js:106:13) gyp ERR! stack at ChildProcess.emit (events.js:191:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12) gyp ERR! System Linux 4.14.70-sunxi gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam gyp ERR! node -v v6.14.4 gyp ERR! node-gyp -v v3.4.0 gyp ERR! not ok > ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional > node rebuild.js > diskusage@0.2.6 install /opt/iobroker/node_modules/diskusage > node-gyp rebuild make: Entering directory '/opt/iobroker/node_modules/diskusage/build' CXX(target) Release/obj.target/diskusage/src/main.o CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o SOLINK_MODULE(target) Release/obj.target/diskusage.node COPY Release/diskusage.node make: Leaving directory '/opt/iobroker/node_modules/diskusage/build' > iobroker.js-controller@1.5.5 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first > rsa-compat@1.9.2 postinstall /opt/iobroker/node_modules/acme-v2/node_modules/rsa-compat > node lib/telemetry.js event:install > rsa-compat@1.9.2 postinstall /opt/iobroker/node_modules/greenlock/node_modules/rsa-compat > node lib/telemetry.js event:install - asn1js@1.2.12 node_modules/asn1js - buffer-v6-polyfill@1.0.5 node_modules/buffer-v6-polyfill - node.extend@1.1.6 node_modules/certpem/node_modules/node.extend cliui@4.1.0 node_modules/iobroker.js-controller/node_modules/cliui -> node_modules/cliui - node.extend@1.1.6 node_modules/greenlock/node_modules/node.extend - arraybuffer.slice@0.0.7 node_modules/iobroker.js-controller/node_modules/arraybuffer.slice - camelcase@4.1.0 node_modules/iobroker.js-controller/node_modules/camelcase - component-emitter@1.2.1 node_modules/iobroker.js-controller/node_modules/component-emitter - debug@3.1.0 node_modules/iobroker.js-controller/node_modules/debug - engine.io-parser@2.1.2 node_modules/iobroker.js-controller/node_modules/engine.io-parser - isarray@2.0.1 node_modules/iobroker.js-controller/node_modules/isarray - socket.io-adapter@1.1.1 node_modules/iobroker.js-controller/node_modules/socket.io-adapter - socket.io-parser@3.2.0 node_modules/iobroker.js-controller/node_modules/socket.io-parser - ultron@1.1.1 node_modules/iobroker.js-controller/node_modules/ultron - ws@3.3.3 node_modules/iobroker.js-controller/node_modules/ws - engine.io@3.2.0 node_modules/iobroker.js-controller/node_modules/engine.io - xmlhttprequest-ssl@1.5.5 node_modules/iobroker.js-controller/node_modules/xmlhttprequest-ssl - engine.io-client@3.2.1 node_modules/iobroker.js-controller/node_modules/engine.io-client - socket.io-client@2.1.1 node_modules/iobroker.js-controller/node_modules/socket.io-client - socket.io@2.1.1 node_modules/iobroker.js-controller/node_modules/socket.io - yargs-parser@9.0.2 node_modules/iobroker.js-controller/node_modules/yargs/node_modules/yargs-parser - pkijs@1.3.33 node_modules/pkijs - certpem@1.0.1 node_modules/certpem - glob@7.1.2 node_modules/rimraf/node_modules/glob - bindings@1.1.1 node_modules/unix-dgram/node_modules/bindings - yargs-parser@4.2.1 node_modules/iobroker.js-controller/node_modules/yargs-parser yargs@11.1.0 node_modules/iobroker.js-controller/node_modules/yargs -> node_modules/yargs iobroker@1.0.0 /opt/iobroker └─┬ iobroker.js-controller@1.5.5 ├─┬ diskusage@0.2.6 │ └── nan@2.12.1 ├─┬ greenlock@2.6.7 │ ├── acme@1.2.0 │ ├─┬ acme-v2@1.5.2 │ │ └─┬ rsa-compat@1.9.2 │ │ └── node-forge@0.7.6 │ ├── cert-info@1.5.0 │ ├── le-store-certbot@2.2.1 │ └─┬ rsa-compat@1.9.2 │ ├── node-forge@0.7.6 │ └─┬ ursa-optional@0.9.10 │ ├─┬ bindings@1.4.0 │ │ └── file-uri-to-path@1.0.0 │ └── nan@2.12.1 ├─┬ jsonwebtoken@8.4.0 │ └─┬ jws@3.2.1 │ └── jwa@1.2.0 ├─┬ jszip@3.1.5 │ └── pako@1.0.8 ├── le-acme-core@2.1.4 ├── le-sni-auto@2.1.6 ├─┬ loadavg-windows@1.0.2 │ └── weak-daemon@1.0.3 ├─┬ node-schedule@1.3.1 │ └─┬ cron-parser@2.7.3 │ └── moment-timezone@0.5.23 ├─┬ node.extend@2.0.2 │ ├── has@1.0.3 │ └── is@3.3.0 ├─┬ pidusage@2.0.17 │ └── safe-buffer@5.1.2 ├─┬ prompt@1.0.0 │ └─┬ utile@0.3.0 │ └─┬ rimraf@2.6.3 │ └── glob@7.1.3 ├── pyconf@1.1.6 ├─┬ redis@2.8.0 │ └── redis-commands@1.4.0 ├── safe-replace@1.1.0 ├─┬ tar@4.4.8 │ ├── chownr@1.1.1 │ ├── minipass@2.3.5 │ ├── minizlib@1.2.1 │ └── yallist@3.0.3 └── winston@2.4.4 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.javascript/node_modules/mymodule/package.json' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install: `node-gyp rebuild` npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1 -
Ich konnte es jetzt einkreisen.
javascript.0 2019-02-13 07:56:00.209 error Error in callback: TypeError: Cannot read property 'common' of undefined javascript.0 2019-02-13 07:55:38.422 error Error in callback: TypeError: Cannot read property 'common' of undefined javascript.0 2019-02-13 07:55:38.248 error TypeError: Cannot read property 'common' of undefined javascript.0 2019-02-13 07:55:38.248 error ^ javascript.0 2019-02-13 07:55:38.247 error if (!language || !dayOfWeeksFull[language]) language = objects['system.config'].common.language; javascript.0 2019-02-13 07:55:38.247 error script.js.common.Tagescharacteristik: /opt/iobroker/node_modules/iobroker.javascript/javascript.js:2712Es ist das Kommando formatDate(new Date(), "W hh:mm").
Liegt nicht an meinen Scripts sondern wohl an der neuen js-controller Version
Was funktioniert ist: formatDate(new Date(), "hh:mm")
update:- WW, НН(cyrillic) - full week day as text
- W, Н(cyrillic) - short week day as text
funktionieren alle nicht mehr
@Marty56 said in ioBroker.js-controller 1.5.4/1.5.5:
formatDate(new Date(), "hh:mm")
Ich kann diesen Fehler nicht erklären. Reproduzieren kann ich auch nicht, aber ich habe js-controller@1.5.6 und javascript@3.6.5 gemacht.
Kannst du ausprobieren? Erst javascript updaten und dann js-controller.cd /optOderHomeVerzeichnis/iobroker iobroker stop npm i iobroker.javascript@3.6.5 --production npm i iobroker.js-controller@1.5.6 --production iobroker u javascript iobroker start -
Bei einer Iobroker Installation mit neuen Installer ist auf die korrekte Rechtevergabe zu achten.
Der Befehlnpm i iobroker.js-controller@1.5.6kann nicht einfach als anderer User ausgeführt werden, da sonst der User iobroker nicht alle Recht hat.
-
js-controller 1.5.5 läuft hier einwandfrei.
iobroker.admin - aktuell aus git
iobroker.web - aktuell aus git
iobroker.iot - aktuell aus git
iobroker.javascript - aktuell aus gitNode 8.15, NPM 6.7, Linux mint 18.3. in ner VM unter proxmox.
( Hauptsystem, 170 Netzwerkdevices und 88 MiHome - es wird genug traffic erzeugt.. ;-))
Auf den Raspi's mit gleichen Versionen unter ARM auch keine Probleme.
js-controller 1.5.5 wirkt im admin schneller. ( er aktualisiert die Seite sehr schnell )Testsystem frisch aufgesetzt und auf latest gestellt, auch Node 8.15, NPM6.7, Linux Mint 19.1, keine Fehler.
( hier sind nur ein paar Skripts am laufen)Ansonsten klasse, weiter so! Das neue Forum ist auch viel besser.
Frage: auf 1.5.6 kann ich nicht updaten, npm findet die Version nicht?
npm ERR! notarget No matching version found for iobroker.js-controller@1.5.6
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist. -
@Bluefox sagte in ioBroker.js-controller 1.5.6:
npm i iobroker.js-controller@1.5.6 --production
Hab's versucht aber
npm i iobroker.js-controller@1.5.6 --production iobroker u javascript npm ERR! code ETARGET npm ERR! notarget No matching version found for iobroker.js-controller@1.5.6 npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2019-02-13T15_37_04_235Z-debug.logerhalten!
p.s.: ich mach solche Sachen unter der neuen iobroker-Installation immer mit vorher:sudo -u iobroker sh -
@Marty56 said in ioBroker.js-controller 1.5.4/1.5.5:
formatDate(new Date(), "hh:mm")
Ich kann diesen Fehler nicht erklären. Reproduzieren kann ich auch nicht, aber ich habe js-controller@1.5.6 und javascript@3.6.5 gemacht.
Kannst du ausprobieren? Erst javascript updaten und dann js-controller.cd /optOderHomeVerzeichnis/iobroker iobroker stop npm i iobroker.javascript@3.6.5 --production npm i iobroker.js-controller@1.5.6 --production iobroker u javascript iobroker start -
@Bluefox Danke, funktioniert !
-
Moin,
hier fliegt der iobroker mit der Version alle 30sec. auseinander. Habe die 1.5.5 probiert und auch die 1.5.6.admin.0 2019-02-13 18:19:16.539 info terminating http server on port 8081 cloud.0 2019-02-13 18:19:10.594 info Connection changed: connect cloud.0 2019-02-13 18:19:10.437 info Trying to connect as system.user.admin host.raspberry 2019-02-13 18:19:05.979 info instance system.adapter.upnp.0 terminated with code 0 (OK) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Receiver.ontext (/opt/iobroker/node_modules/ws/lib/WebSocket.js:841:10) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WebSocket.emit (events.js:214:7) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at emitTwo (events.js:126:13) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WebSocket.onMessage (/opt/iobroker/node_modules/ws/lib/WebSocket.js:442:14) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:146:10) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WS.Transport.onData (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:137:8) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WS.Transport.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:145:8) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WS.<anonymous> (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:237:14) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at decodeString (/opt/iobroker/node_modules/socket.io-parser/index.js:325:9) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at tryParse (/opt/iobroker/node_modules/socket.io-parser/index.js:336:12) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: RangeError: Maximum call stack size exceeded host.raspberry 2019-02-13 18:19:05.660 info iobroker exit 0 host.raspberry 2019-02-13 18:19:05.659 info iobroker Starting node restart.js host.raspberry 2019-02-13 18:19:05.539 info iobroker _restart host.raspberry 2019-02-13 18:19:05.539 error RangeError: Maximum call stack size exceeded at Buffer.write (buffer.js:855:34) at fromString (buffer.js:319:20) at Function.Buffer.from (buffer.js:177:12) at new Buffer (buffer.js:158 host.raspberry 2019-02-13 18:19:05.538 error uncaught exception: Maximum call stack size exceeded iot.0 2019-02-13 18:19:04.819 info Connection changed: connectMatze
-
Moin,
hier fliegt der iobroker mit der Version alle 30sec. auseinander. Habe die 1.5.5 probiert und auch die 1.5.6.admin.0 2019-02-13 18:19:16.539 info terminating http server on port 8081 cloud.0 2019-02-13 18:19:10.594 info Connection changed: connect cloud.0 2019-02-13 18:19:10.437 info Trying to connect as system.user.admin host.raspberry 2019-02-13 18:19:05.979 info instance system.adapter.upnp.0 terminated with code 0 (OK) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Receiver.ontext (/opt/iobroker/node_modules/ws/lib/WebSocket.js:841:10) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WebSocket.emit (events.js:214:7) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at emitTwo (events.js:126:13) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WebSocket.onMessage (/opt/iobroker/node_modules/ws/lib/WebSocket.js:442:14) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:146:10) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WS.Transport.onData (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:137:8) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WS.Transport.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:145:8) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at WS.<anonymous> (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:237:14) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at decodeString (/opt/iobroker/node_modules/socket.io-parser/index.js:325:9) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: at tryParse (/opt/iobroker/node_modules/socket.io-parser/index.js:336:12) host.raspberry 2019-02-13 18:19:05.979 error Caught by controller[0]: RangeError: Maximum call stack size exceeded host.raspberry 2019-02-13 18:19:05.660 info iobroker exit 0 host.raspberry 2019-02-13 18:19:05.659 info iobroker Starting node restart.js host.raspberry 2019-02-13 18:19:05.539 info iobroker _restart host.raspberry 2019-02-13 18:19:05.539 error RangeError: Maximum call stack size exceeded at Buffer.write (buffer.js:855:34) at fromString (buffer.js:319:20) at Function.Buffer.from (buffer.js:177:12) at new Buffer (buffer.js:158 host.raspberry 2019-02-13 18:19:05.538 error uncaught exception: Maximum call stack size exceeded iot.0 2019-02-13 18:19:04.819 info Connection changed: connectMatze
-
@Bluefox : ich bin schon wieder auf 1.4.2 zurück. Kannst du dann damit noch was anfangen?
Und noch als Hinweis, Usern mit neuerer Version ( neuer Installer ) haut es beim Update die Berechtigungen auseinander. Da hast du dann Ordner mit Besitzer "root" dazwischen.Gruß
Matze -
Bei einer Iobroker Installation mit neuen Installer ist auf die korrekte Rechtevergabe zu achten.
Der Befehlnpm i iobroker.js-controller@1.5.6kann nicht einfach als anderer User ausgeführt werden, da sonst der User iobroker nicht alle Recht hat.
@simatec sagte in ioBroker.js-controller 1.5.6:
Bei einer Iobroker Installation mit neuen Installer ist auf die korrekte Rechtevergabe zu achten.
Der Befehlnpm i iobroker.js-controller@1.5.6kann nicht einfach als anderer User ausgeführt werden, da sonst der User iobroker nicht alle Recht hat.
Hier steht schon ein Hinweis darauf, das sollte natürlich auch im ioBroker-Admin angezeigt werden, als deutlichen Hinweis darauf, dass es zwei unterschiedliche Installationsvarianten gibt. Nicht dass es da noch große Diskussionen gibt!
Enrico
Support us
845
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge