NEWS
Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update
Error/Bug
169
Beiträge
15
Kommentatoren
24.1k
Aufrufe
12
Watching
-
@thomas-braun
Die Verzeichnisse sind umbenannt. Jetzt lautet die Fehlermeldung:iobroker upgrade info --debug Installation broken or unknown objects type: jsonl configured.Was meinst du genau mit:
Und das node16-Repository nochmal anlegen oder die nodesource.list bearbeiten.
Was muss ich hier genau machen? Entschuldige bitte, ich bin nicht der Linux Profi. ;-)
-
-
iobroker update -i Installation broken or unknown objects type: jsonl configured.Mehr nicht? Bitte besser die kompletten Ein- und Ausgabezeilen zeigen, dann kann man das besser einordnen.
iobroker status iobroker list instances iobroker list adapters -
Mehr nicht? Bitte besser die kompletten Ein- und Ausgabezeilen zeigen, dann kann man das besser einordnen.
iobroker status iobroker list instances iobroker list adapters@thomas-braun mehr wird nicht in der Console angezeigt:
xx@iobroker-prod:~$ iobroker update -i Installation broken or unknown objects type: jsonl configured. xx@iobroker-prod:~$ iobroker list instances Installation broken or unknown objects type: jsonl configured. xx@iobroker-prod:~$ iobroker list adapters Installation broken or unknown objects type: jsonl configured. xx@iobroker-prod:~$ -
@thomas-braun mehr wird nicht in der Console angezeigt:
xx@iobroker-prod:~$ iobroker update -i Installation broken or unknown objects type: jsonl configured. xx@iobroker-prod:~$ iobroker list instances Installation broken or unknown objects type: jsonl configured. xx@iobroker-prod:~$ iobroker list adapters Installation broken or unknown objects type: jsonl configured. xx@iobroker-prod:~$Installier den js-controller nochmal drüber
-
@thomas-braun mehr wird nicht in der Console angezeigt:
xx@iobroker-prod:~$ iobroker update -i Installation broken or unknown objects type: jsonl configured. xx@iobroker-prod:~$ iobroker list instances Installation broken or unknown objects type: jsonl configured. xx@iobroker-prod:~$ iobroker list adapters Installation broken or unknown objects type: jsonl configured. xx@iobroker-prod:~$@taba_luga xx ist auch ein einfallsreicher Username :joy:
-
Installier den js-controller nochmal drüber
xx@iobroker-prod:~$ npm install iobroker.js-controller npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 added 309 packages, and audited 310 packages in 1m 18 packages are looking for funding run `npm fund` for details 4 vulnerabilities (3 moderate, 1 high) To address all issues, run: npm audit fix Run `npm audit` for details. xx@iobroker-prod:~$und hier npm audit und npm audit --force
xx@iobroker-prod:~$ npm audit # npm audit report node-forge <=1.2.1 Severity: high Open Redirect in node-forge - https://github.com/advisories/GHSA-8fr3-hfg3-gpgp Prototype Pollution in node-forge debug API. - https://github.com/advisories/GHSA-5rrq-pxf6-6jx5 Prototype Pollution in node-forge util.setPath API - https://github.com/advisories/GHSA-wxgw-qj99-44c2 URL parsing in node-forge could lead to undesired behavior. - https://github.com/advisories/GHSA-gf8q-jrpm-jvxq Prototype Pollution in node-forge - https://github.com/advisories/GHSA-92xj-mqp7-vmcj Improper Verification of Cryptographic Signature in `node-forge` - https://github.com/advisories/GHSA-2r2c-g63r-vccr Improper Verification of Cryptographic Signature in node-forge - https://github.com/advisories/GHSA-x4jg-mjrx-434g Improper Verification of Cryptographic Signature in node-forge - https://github.com/advisories/GHSA-cfm4-qjh2-4765 fix available via `npm audit fix --force` Will install iobroker.js-controller@1.5.3, which is a breaking change node_modules/rsa-compat/node_modules/node-forge rsa-compat <=1.9.4 Depends on vulnerable versions of node-forge node_modules/rsa-compat le-acme-core * Depends on vulnerable versions of rsa-compat node_modules/le-acme-core iobroker.js-controller >=1.5.4 Depends on vulnerable versions of le-acme-core node_modules/iobroker.js-controller 4 vulnerabilities (3 moderate, 1 high) To address all issues (including breaking changes), run: npm audit fix --force xx@iobroker-prod:~$ npm audit fix --force npm WARN using --force Recommended protections disabled. npm WARN audit Updating iobroker.js-controller to 1.5.3,which is a SemVer major change. npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) added 173 packages, removed 145 packages, changed 48 packages, and audited 334 packages in 51s 13 packages are looking for funding run `npm fund` for details # npm audit report debug <2.6.9 Regular Expression Denial of Service in debug - https://github.com/advisories/GHSA-gxpj-cx7g-858c fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/engine.io-client/node_modules/debug node_modules/engine.io/node_modules/debug node_modules/socket.io-adapter/node_modules/debug node_modules/socket.io-client/node_modules/debug node_modules/socket.io-parser/node_modules/debug node_modules/socket.io/node_modules/debug engine.io <=4.0.0-alpha.1 Depends on vulnerable versions of debug Depends on vulnerable versions of ws node_modules/engine.io socket.io <=2.4.1 Depends on vulnerable versions of debug Depends on vulnerable versions of engine.io Depends on vulnerable versions of socket.io-adapter Depends on vulnerable versions of socket.io-client Depends on vulnerable versions of socket.io-parser node_modules/socket.io iobroker.js-controller <=2.1.1 Depends on vulnerable versions of redis Depends on vulnerable versions of socket.io Depends on vulnerable versions of socket.io-client Depends on vulnerable versions of winston-daily-rotate-file Depends on vulnerable versions of yargs node_modules/iobroker.js-controller engine.io-client <=3.3.2 || 3.4.0 - 3.5.1 || 4.0.0-alpha.0 - 4.1.3 Depends on vulnerable versions of debug Depends on vulnerable versions of parsejson Depends on vulnerable versions of ws Depends on vulnerable versions of xmlhttprequest-ssl node_modules/engine.io-client socket.io-client 1.0.0-pre - 2.1.1 || 2.3.0 - 2.3.1 || 3.0.0-rc1 - 3.0.5 Depends on vulnerable versions of debug Depends on vulnerable versions of engine.io-client Depends on vulnerable versions of socket.io-parser node_modules/socket.io-client socket.io-adapter <=1.1.0 Depends on vulnerable versions of debug Depends on vulnerable versions of socket.io-parser node_modules/socket.io-adapter socket.io-parser <=3.3.1 Depends on vulnerable versions of debug node_modules/socket.io-parser minimist <=1.2.5 Severity: critical Prototype Pollution in minimist - https://github.com/advisories/GHSA-xvch-5gv4-984h Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/winston-daily-rotate-file/node_modules/minimist mkdirp 0.4.1 - 0.5.1 Depends on vulnerable versions of minimist node_modules/winston-daily-rotate-file/node_modules/mkdirp winston-daily-rotate-file 1.7.0 - 1.7.2 Depends on vulnerable versions of mkdirp node_modules/winston-daily-rotate-file parsejson * Severity: high Regular Expression Denial of Service in parsejson - https://github.com/advisories/GHSA-q75g-2496-mxpp fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/parsejson redis 2.6.0 - 3.1.0 Severity: high Potential exponential regex in monitor mode - https://github.com/advisories/GHSA-35q2-47q7-3pc3 fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/redis ws <=1.1.4 Severity: high Denial of Service in ws - https://github.com/advisories/GHSA-5v72-xg48-5rpm fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/engine.io-client/node_modules/ws node_modules/engine.io/node_modules/ws xmlhttprequest-ssl <=1.6.1 Severity: critical Improper Certificate Validation in xmlhttprequest-ssl - https://github.com/advisories/GHSA-72mh-269x-7mh5 Arbitrary Code Injection - https://github.com/advisories/GHSA-h4j5-c7cj-74xg fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/xmlhttprequest-ssl yargs-parser 6.0.0 - 13.1.1 Severity: moderate Prototype Pollution in yargs-parser - https://github.com/advisories/GHSA-p9pc-299p-vxgp fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/yargs-parser yargs 8.0.0-candidate.0 - 12.0.5 Depends on vulnerable versions of yargs-parser node_modules/yargs 17 vulnerabilities (1 low, 4 moderate, 8 high, 4 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force xx@iobroker-prod:~$Das hat leider zu keiner Verbesserung geführt
-
xx@iobroker-prod:~$ npm install iobroker.js-controller npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 added 309 packages, and audited 310 packages in 1m 18 packages are looking for funding run `npm fund` for details 4 vulnerabilities (3 moderate, 1 high) To address all issues, run: npm audit fix Run `npm audit` for details. xx@iobroker-prod:~$und hier npm audit und npm audit --force
xx@iobroker-prod:~$ npm audit # npm audit report node-forge <=1.2.1 Severity: high Open Redirect in node-forge - https://github.com/advisories/GHSA-8fr3-hfg3-gpgp Prototype Pollution in node-forge debug API. - https://github.com/advisories/GHSA-5rrq-pxf6-6jx5 Prototype Pollution in node-forge util.setPath API - https://github.com/advisories/GHSA-wxgw-qj99-44c2 URL parsing in node-forge could lead to undesired behavior. - https://github.com/advisories/GHSA-gf8q-jrpm-jvxq Prototype Pollution in node-forge - https://github.com/advisories/GHSA-92xj-mqp7-vmcj Improper Verification of Cryptographic Signature in `node-forge` - https://github.com/advisories/GHSA-2r2c-g63r-vccr Improper Verification of Cryptographic Signature in node-forge - https://github.com/advisories/GHSA-x4jg-mjrx-434g Improper Verification of Cryptographic Signature in node-forge - https://github.com/advisories/GHSA-cfm4-qjh2-4765 fix available via `npm audit fix --force` Will install iobroker.js-controller@1.5.3, which is a breaking change node_modules/rsa-compat/node_modules/node-forge rsa-compat <=1.9.4 Depends on vulnerable versions of node-forge node_modules/rsa-compat le-acme-core * Depends on vulnerable versions of rsa-compat node_modules/le-acme-core iobroker.js-controller >=1.5.4 Depends on vulnerable versions of le-acme-core node_modules/iobroker.js-controller 4 vulnerabilities (3 moderate, 1 high) To address all issues (including breaking changes), run: npm audit fix --force xx@iobroker-prod:~$ npm audit fix --force npm WARN using --force Recommended protections disabled. npm WARN audit Updating iobroker.js-controller to 1.5.3,which is a SemVer major change. npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) added 173 packages, removed 145 packages, changed 48 packages, and audited 334 packages in 51s 13 packages are looking for funding run `npm fund` for details # npm audit report debug <2.6.9 Regular Expression Denial of Service in debug - https://github.com/advisories/GHSA-gxpj-cx7g-858c fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/engine.io-client/node_modules/debug node_modules/engine.io/node_modules/debug node_modules/socket.io-adapter/node_modules/debug node_modules/socket.io-client/node_modules/debug node_modules/socket.io-parser/node_modules/debug node_modules/socket.io/node_modules/debug engine.io <=4.0.0-alpha.1 Depends on vulnerable versions of debug Depends on vulnerable versions of ws node_modules/engine.io socket.io <=2.4.1 Depends on vulnerable versions of debug Depends on vulnerable versions of engine.io Depends on vulnerable versions of socket.io-adapter Depends on vulnerable versions of socket.io-client Depends on vulnerable versions of socket.io-parser node_modules/socket.io iobroker.js-controller <=2.1.1 Depends on vulnerable versions of redis Depends on vulnerable versions of socket.io Depends on vulnerable versions of socket.io-client Depends on vulnerable versions of winston-daily-rotate-file Depends on vulnerable versions of yargs node_modules/iobroker.js-controller engine.io-client <=3.3.2 || 3.4.0 - 3.5.1 || 4.0.0-alpha.0 - 4.1.3 Depends on vulnerable versions of debug Depends on vulnerable versions of parsejson Depends on vulnerable versions of ws Depends on vulnerable versions of xmlhttprequest-ssl node_modules/engine.io-client socket.io-client 1.0.0-pre - 2.1.1 || 2.3.0 - 2.3.1 || 3.0.0-rc1 - 3.0.5 Depends on vulnerable versions of debug Depends on vulnerable versions of engine.io-client Depends on vulnerable versions of socket.io-parser node_modules/socket.io-client socket.io-adapter <=1.1.0 Depends on vulnerable versions of debug Depends on vulnerable versions of socket.io-parser node_modules/socket.io-adapter socket.io-parser <=3.3.1 Depends on vulnerable versions of debug node_modules/socket.io-parser minimist <=1.2.5 Severity: critical Prototype Pollution in minimist - https://github.com/advisories/GHSA-xvch-5gv4-984h Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/winston-daily-rotate-file/node_modules/minimist mkdirp 0.4.1 - 0.5.1 Depends on vulnerable versions of minimist node_modules/winston-daily-rotate-file/node_modules/mkdirp winston-daily-rotate-file 1.7.0 - 1.7.2 Depends on vulnerable versions of mkdirp node_modules/winston-daily-rotate-file parsejson * Severity: high Regular Expression Denial of Service in parsejson - https://github.com/advisories/GHSA-q75g-2496-mxpp fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/parsejson redis 2.6.0 - 3.1.0 Severity: high Potential exponential regex in monitor mode - https://github.com/advisories/GHSA-35q2-47q7-3pc3 fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/redis ws <=1.1.4 Severity: high Denial of Service in ws - https://github.com/advisories/GHSA-5v72-xg48-5rpm fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/engine.io-client/node_modules/ws node_modules/engine.io/node_modules/ws xmlhttprequest-ssl <=1.6.1 Severity: critical Improper Certificate Validation in xmlhttprequest-ssl - https://github.com/advisories/GHSA-72mh-269x-7mh5 Arbitrary Code Injection - https://github.com/advisories/GHSA-h4j5-c7cj-74xg fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/xmlhttprequest-ssl yargs-parser 6.0.0 - 13.1.1 Severity: moderate Prototype Pollution in yargs-parser - https://github.com/advisories/GHSA-p9pc-299p-vxgp fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/yargs-parser yargs 8.0.0-candidate.0 - 12.0.5 Depends on vulnerable versions of yargs-parser node_modules/yargs 17 vulnerabilities (1 low, 4 moderate, 8 high, 4 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force xx@iobroker-prod:~$Das hat leider zu keiner Verbesserung geführt
@taba_luga sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:
und hier npm audit und npm audit --force
wieso machst du so etwas?
-
@taba_luga sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:
und hier npm audit und npm audit --force
wieso machst du so etwas?
-
xx@iobroker-prod:~$ npm install iobroker.js-controller npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 added 309 packages, and audited 310 packages in 1m 18 packages are looking for funding run `npm fund` for details 4 vulnerabilities (3 moderate, 1 high) To address all issues, run: npm audit fix Run `npm audit` for details. xx@iobroker-prod:~$und hier npm audit und npm audit --force
xx@iobroker-prod:~$ npm audit # npm audit report node-forge <=1.2.1 Severity: high Open Redirect in node-forge - https://github.com/advisories/GHSA-8fr3-hfg3-gpgp Prototype Pollution in node-forge debug API. - https://github.com/advisories/GHSA-5rrq-pxf6-6jx5 Prototype Pollution in node-forge util.setPath API - https://github.com/advisories/GHSA-wxgw-qj99-44c2 URL parsing in node-forge could lead to undesired behavior. - https://github.com/advisories/GHSA-gf8q-jrpm-jvxq Prototype Pollution in node-forge - https://github.com/advisories/GHSA-92xj-mqp7-vmcj Improper Verification of Cryptographic Signature in `node-forge` - https://github.com/advisories/GHSA-2r2c-g63r-vccr Improper Verification of Cryptographic Signature in node-forge - https://github.com/advisories/GHSA-x4jg-mjrx-434g Improper Verification of Cryptographic Signature in node-forge - https://github.com/advisories/GHSA-cfm4-qjh2-4765 fix available via `npm audit fix --force` Will install iobroker.js-controller@1.5.3, which is a breaking change node_modules/rsa-compat/node_modules/node-forge rsa-compat <=1.9.4 Depends on vulnerable versions of node-forge node_modules/rsa-compat le-acme-core * Depends on vulnerable versions of rsa-compat node_modules/le-acme-core iobroker.js-controller >=1.5.4 Depends on vulnerable versions of le-acme-core node_modules/iobroker.js-controller 4 vulnerabilities (3 moderate, 1 high) To address all issues (including breaking changes), run: npm audit fix --force xx@iobroker-prod:~$ npm audit fix --force npm WARN using --force Recommended protections disabled. npm WARN audit Updating iobroker.js-controller to 1.5.3,which is a SemVer major change. npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) added 173 packages, removed 145 packages, changed 48 packages, and audited 334 packages in 51s 13 packages are looking for funding run `npm fund` for details # npm audit report debug <2.6.9 Regular Expression Denial of Service in debug - https://github.com/advisories/GHSA-gxpj-cx7g-858c fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/engine.io-client/node_modules/debug node_modules/engine.io/node_modules/debug node_modules/socket.io-adapter/node_modules/debug node_modules/socket.io-client/node_modules/debug node_modules/socket.io-parser/node_modules/debug node_modules/socket.io/node_modules/debug engine.io <=4.0.0-alpha.1 Depends on vulnerable versions of debug Depends on vulnerable versions of ws node_modules/engine.io socket.io <=2.4.1 Depends on vulnerable versions of debug Depends on vulnerable versions of engine.io Depends on vulnerable versions of socket.io-adapter Depends on vulnerable versions of socket.io-client Depends on vulnerable versions of socket.io-parser node_modules/socket.io iobroker.js-controller <=2.1.1 Depends on vulnerable versions of redis Depends on vulnerable versions of socket.io Depends on vulnerable versions of socket.io-client Depends on vulnerable versions of winston-daily-rotate-file Depends on vulnerable versions of yargs node_modules/iobroker.js-controller engine.io-client <=3.3.2 || 3.4.0 - 3.5.1 || 4.0.0-alpha.0 - 4.1.3 Depends on vulnerable versions of debug Depends on vulnerable versions of parsejson Depends on vulnerable versions of ws Depends on vulnerable versions of xmlhttprequest-ssl node_modules/engine.io-client socket.io-client 1.0.0-pre - 2.1.1 || 2.3.0 - 2.3.1 || 3.0.0-rc1 - 3.0.5 Depends on vulnerable versions of debug Depends on vulnerable versions of engine.io-client Depends on vulnerable versions of socket.io-parser node_modules/socket.io-client socket.io-adapter <=1.1.0 Depends on vulnerable versions of debug Depends on vulnerable versions of socket.io-parser node_modules/socket.io-adapter socket.io-parser <=3.3.1 Depends on vulnerable versions of debug node_modules/socket.io-parser minimist <=1.2.5 Severity: critical Prototype Pollution in minimist - https://github.com/advisories/GHSA-xvch-5gv4-984h Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/winston-daily-rotate-file/node_modules/minimist mkdirp 0.4.1 - 0.5.1 Depends on vulnerable versions of minimist node_modules/winston-daily-rotate-file/node_modules/mkdirp winston-daily-rotate-file 1.7.0 - 1.7.2 Depends on vulnerable versions of mkdirp node_modules/winston-daily-rotate-file parsejson * Severity: high Regular Expression Denial of Service in parsejson - https://github.com/advisories/GHSA-q75g-2496-mxpp fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/parsejson redis 2.6.0 - 3.1.0 Severity: high Potential exponential regex in monitor mode - https://github.com/advisories/GHSA-35q2-47q7-3pc3 fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/redis ws <=1.1.4 Severity: high Denial of Service in ws - https://github.com/advisories/GHSA-5v72-xg48-5rpm fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/engine.io-client/node_modules/ws node_modules/engine.io/node_modules/ws xmlhttprequest-ssl <=1.6.1 Severity: critical Improper Certificate Validation in xmlhttprequest-ssl - https://github.com/advisories/GHSA-72mh-269x-7mh5 Arbitrary Code Injection - https://github.com/advisories/GHSA-h4j5-c7cj-74xg fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/xmlhttprequest-ssl yargs-parser 6.0.0 - 13.1.1 Severity: moderate Prototype Pollution in yargs-parser - https://github.com/advisories/GHSA-p9pc-299p-vxgp fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/yargs-parser yargs 8.0.0-candidate.0 - 12.0.5 Depends on vulnerable versions of yargs-parser node_modules/yargs 17 vulnerabilities (1 low, 4 moderate, 8 high, 4 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force xx@iobroker-prod:~$Das hat leider zu keiner Verbesserung geführt
@taba_luga hoffe das npm install war im richtigen ordner (/opt/iobroker) und ja audit fix lassen
-
xx@iobroker-prod:~$ npm install iobroker.js-controller npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 added 309 packages, and audited 310 packages in 1m 18 packages are looking for funding run `npm fund` for details 4 vulnerabilities (3 moderate, 1 high) To address all issues, run: npm audit fix Run `npm audit` for details. xx@iobroker-prod:~$und hier npm audit und npm audit --force
xx@iobroker-prod:~$ npm audit # npm audit report node-forge <=1.2.1 Severity: high Open Redirect in node-forge - https://github.com/advisories/GHSA-8fr3-hfg3-gpgp Prototype Pollution in node-forge debug API. - https://github.com/advisories/GHSA-5rrq-pxf6-6jx5 Prototype Pollution in node-forge util.setPath API - https://github.com/advisories/GHSA-wxgw-qj99-44c2 URL parsing in node-forge could lead to undesired behavior. - https://github.com/advisories/GHSA-gf8q-jrpm-jvxq Prototype Pollution in node-forge - https://github.com/advisories/GHSA-92xj-mqp7-vmcj Improper Verification of Cryptographic Signature in `node-forge` - https://github.com/advisories/GHSA-2r2c-g63r-vccr Improper Verification of Cryptographic Signature in node-forge - https://github.com/advisories/GHSA-x4jg-mjrx-434g Improper Verification of Cryptographic Signature in node-forge - https://github.com/advisories/GHSA-cfm4-qjh2-4765 fix available via `npm audit fix --force` Will install iobroker.js-controller@1.5.3, which is a breaking change node_modules/rsa-compat/node_modules/node-forge rsa-compat <=1.9.4 Depends on vulnerable versions of node-forge node_modules/rsa-compat le-acme-core * Depends on vulnerable versions of rsa-compat node_modules/le-acme-core iobroker.js-controller >=1.5.4 Depends on vulnerable versions of le-acme-core node_modules/iobroker.js-controller 4 vulnerabilities (3 moderate, 1 high) To address all issues (including breaking changes), run: npm audit fix --force xx@iobroker-prod:~$ npm audit fix --force npm WARN using --force Recommended protections disabled. npm WARN audit Updating iobroker.js-controller to 1.5.3,which is a SemVer major change. npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) added 173 packages, removed 145 packages, changed 48 packages, and audited 334 packages in 51s 13 packages are looking for funding run `npm fund` for details # npm audit report debug <2.6.9 Regular Expression Denial of Service in debug - https://github.com/advisories/GHSA-gxpj-cx7g-858c fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/engine.io-client/node_modules/debug node_modules/engine.io/node_modules/debug node_modules/socket.io-adapter/node_modules/debug node_modules/socket.io-client/node_modules/debug node_modules/socket.io-parser/node_modules/debug node_modules/socket.io/node_modules/debug engine.io <=4.0.0-alpha.1 Depends on vulnerable versions of debug Depends on vulnerable versions of ws node_modules/engine.io socket.io <=2.4.1 Depends on vulnerable versions of debug Depends on vulnerable versions of engine.io Depends on vulnerable versions of socket.io-adapter Depends on vulnerable versions of socket.io-client Depends on vulnerable versions of socket.io-parser node_modules/socket.io iobroker.js-controller <=2.1.1 Depends on vulnerable versions of redis Depends on vulnerable versions of socket.io Depends on vulnerable versions of socket.io-client Depends on vulnerable versions of winston-daily-rotate-file Depends on vulnerable versions of yargs node_modules/iobroker.js-controller engine.io-client <=3.3.2 || 3.4.0 - 3.5.1 || 4.0.0-alpha.0 - 4.1.3 Depends on vulnerable versions of debug Depends on vulnerable versions of parsejson Depends on vulnerable versions of ws Depends on vulnerable versions of xmlhttprequest-ssl node_modules/engine.io-client socket.io-client 1.0.0-pre - 2.1.1 || 2.3.0 - 2.3.1 || 3.0.0-rc1 - 3.0.5 Depends on vulnerable versions of debug Depends on vulnerable versions of engine.io-client Depends on vulnerable versions of socket.io-parser node_modules/socket.io-client socket.io-adapter <=1.1.0 Depends on vulnerable versions of debug Depends on vulnerable versions of socket.io-parser node_modules/socket.io-adapter socket.io-parser <=3.3.1 Depends on vulnerable versions of debug node_modules/socket.io-parser minimist <=1.2.5 Severity: critical Prototype Pollution in minimist - https://github.com/advisories/GHSA-xvch-5gv4-984h Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/winston-daily-rotate-file/node_modules/minimist mkdirp 0.4.1 - 0.5.1 Depends on vulnerable versions of minimist node_modules/winston-daily-rotate-file/node_modules/mkdirp winston-daily-rotate-file 1.7.0 - 1.7.2 Depends on vulnerable versions of mkdirp node_modules/winston-daily-rotate-file parsejson * Severity: high Regular Expression Denial of Service in parsejson - https://github.com/advisories/GHSA-q75g-2496-mxpp fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/parsejson redis 2.6.0 - 3.1.0 Severity: high Potential exponential regex in monitor mode - https://github.com/advisories/GHSA-35q2-47q7-3pc3 fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/redis ws <=1.1.4 Severity: high Denial of Service in ws - https://github.com/advisories/GHSA-5v72-xg48-5rpm fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/engine.io-client/node_modules/ws node_modules/engine.io/node_modules/ws xmlhttprequest-ssl <=1.6.1 Severity: critical Improper Certificate Validation in xmlhttprequest-ssl - https://github.com/advisories/GHSA-72mh-269x-7mh5 Arbitrary Code Injection - https://github.com/advisories/GHSA-h4j5-c7cj-74xg fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/xmlhttprequest-ssl yargs-parser 6.0.0 - 13.1.1 Severity: moderate Prototype Pollution in yargs-parser - https://github.com/advisories/GHSA-p9pc-299p-vxgp fix available via `npm audit fix --force` Will install iobroker.js-controller@4.0.23, which is a breaking change node_modules/yargs-parser yargs 8.0.0-candidate.0 - 12.0.5 Depends on vulnerable versions of yargs-parser node_modules/yargs 17 vulnerabilities (1 low, 4 moderate, 8 high, 4 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force xx@iobroker-prod:~$Das hat leider zu keiner Verbesserung geführt
@taba_luga sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:
Falsches Verzeichnis:
xx@iobroker-prod:~$ npm install iobroker.js-controllerDas hat leider zu keiner Verbesserung geführt
Naja, jetzt hast du es doppelt 'installiert'...
Mach es so:
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller -
@taba_luga hoffe das npm install war im richtigen ordner (/opt/iobroker) und ja audit fix lassen
@apollon77 ich befürchte nicht... Ich hatte vorher nicht das Verzeichnis gewechselt. Habe ich mir jetzt restlos alles zerschossen? Dann würde ich meinen Snapshot wieder hervor holen und bis zu diesem Punkt erst mal alles wiederholen.
[edit] der Post von @Thomas-Braun hat sich mit meiner Antwort hier überschnitten.
-
@apollon77 ich befürchte nicht... Ich hatte vorher nicht das Verzeichnis gewechselt. Habe ich mir jetzt restlos alles zerschossen? Dann würde ich meinen Snapshot wieder hervor holen und bis zu diesem Punkt erst mal alles wiederholen.
[edit] der Post von @Thomas-Braun hat sich mit meiner Antwort hier überschnitten.
@taba_luga In welchem verzeichnis haste es denn ausgeführt? WEnn in deinem User verzeichnis dann liegt da jetzt nur ein node_modules mit Zeug drin ... löschen und ende
-
@apollon77 ich befürchte nicht... Ich hatte vorher nicht das Verzeichnis gewechselt. Habe ich mir jetzt restlos alles zerschossen? Dann würde ich meinen Snapshot wieder hervor holen und bis zu diesem Punkt erst mal alles wiederholen.
[edit] der Post von @Thomas-Braun hat sich mit meiner Antwort hier überschnitten.
@taba_luga sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:
Habe ich mir jetzt restlos alles zerschossen?
Nein, du hast nur den js-controller im /home-Verzeichnis des users xx versenkt.
Aber da den den ja auch dort auditiert und gefixt hast...
...lösch das dort.Die Hauptinstallation immer noch defekt.
-
@taba_luga sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:
Falsches Verzeichnis:
xx@iobroker-prod:~$ npm install iobroker.js-controllerDas hat leider zu keiner Verbesserung geführt
Naja, jetzt hast du es doppelt 'installiert'...
Mach es so:
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller@thomas-braun
jetzt geht der Spaß mit den Ordnern wieder los...xx@iobroker-prod:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/alexa-cookie2 npm ERR! dest /opt/iobroker/node_modules/.alexa-cookie2-yH4YGJkw npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/alexa-cookie2' -> '/opt/iobroker/node_modules/.alexa-cookie2-yH4YGJkw' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-06-24T11_45_06_568Z-debug-0.log xx@iobroker-prod:/opt/iobroker$Die benenne ich dann erst mal wieder um und melde mich dann wieder bei euch. Vielen DANK schon mal zwischendurch für euren super Support!!!
-
Moin !
Leider habe auch ich ein kleines Problem. Update nach
https://forum.iobroker.net/topic/44566/how-to-node-js-iobroker-richtig-updaten-2021-22-edition
Danach den berühmten Error 25 bei der Installation von Adaptern. Es geht weder ein Update noch eine Neuinstallation eines Adapters. Nun also hier die Meldung im Forum, da ich nun auch nicht mehr ohne Hilfe weiter komme.
Nach dem Durchlesen hier habe ich mal einige Snapshots gemacht und diese stelle ich hier mit ein. Da der Fehler in der Regel beim User sitzt .............. Es ist ja leider meist so.
Wer mir da helfen kann ......... VG Mathias
-
Moin !
Leider habe auch ich ein kleines Problem. Update nach
https://forum.iobroker.net/topic/44566/how-to-node-js-iobroker-richtig-updaten-2021-22-edition
Danach den berühmten Error 25 bei der Installation von Adaptern. Es geht weder ein Update noch eine Neuinstallation eines Adapters. Nun also hier die Meldung im Forum, da ich nun auch nicht mehr ohne Hilfe weiter komme.
Nach dem Durchlesen hier habe ich mal einige Snapshots gemacht und diese stelle ich hier mit ein. Da der Fehler in der Regel beim User sitzt .............. Es ist ja leider meist so.Wer mir da helfen kann ......... VG Mathias
@nhbischo sagte in Error 25 bei Adapterupdates nach Node.JS 16.15.1 Update:
Wer mir da helfen kann .
keine Screenshots von Text!
Diesen als Text in code-tags posten -
Moin !
Leider habe auch ich ein kleines Problem. Update nach
https://forum.iobroker.net/topic/44566/how-to-node-js-iobroker-richtig-updaten-2021-22-edition
Danach den berühmten Error 25 bei der Installation von Adaptern. Es geht weder ein Update noch eine Neuinstallation eines Adapters. Nun also hier die Meldung im Forum, da ich nun auch nicht mehr ohne Hilfe weiter komme.
Nach dem Durchlesen hier habe ich mal einige Snapshots gemacht und diese stelle ich hier mit ein. Da der Fehler in der Regel beim User sitzt .............. Es ist ja leider meist so.Wer mir da helfen kann ......... VG Mathias
Keine krümeligen Screenshots aus der Konsole.
Als Text in CodeTags eingebettet hier rein. -
pi@raspberrypi:/opt/iobroker $ iobroker upgrade smartgarden --debug This upgrade of "smartgarden" will introduce the following changes: ========================================================================== -> 2.0.0: support for new login procedure to Gardena webservice; admin5 is necessary ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING C HANGES! Would you like to upgrade smartgarden from @1.0.6 to @2.0.0 now? [(y)es, (n)o]: y Update smartgarden from @1.0.6 to @2.0.0 NPM version: 8.11.0 Installing iobroker.smartgarden@2.0.0... (System call) npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry . npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm WARN tarball tarball data for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master (sha512-qGFFRFfv/uSaVT +z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master (sha512-qGFFRFfv/uSaVT +z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==) seems to be corrupted. Trying again. npm WARN old lockfile Error: sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== integrity checksum failed when using sha512: wan ted sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== but got sha512-ZH4lj95sM6IpZEL2H1HR0hXTo6GMqbUBPbQyylgdRd6TDEdU+fgohUVGW4 gPI0UnrAzqM/kx5+mozLqCVh2DCg==. (64751136 bytes) npm WARN old lockfile at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19) npm WARN old lockfile at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:434:29) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:90:18) npm WARN old lockfile at IntegrityStream.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:265:12) npm WARN old lockfile at IntegrityStream.resume (/usr/lib/node_modules/npm/node_modules/minipass/index.js:269:24) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/minipass-pipeline/index.js:105:19) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/make-fetch-happen/lib/pipeline.js:37:18) npm WARN old lockfile at CachingMinipassPipeline.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:259:10) npm WARN old lockfile Could not fetch metadata for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master Erro r: sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== integrity checksum failed when using sha512: wanted sha512-qGFFRFfv/uSaVT+ z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== but got sha512-ZH4lj95sM6IpZEL2H1HR0hXTo6GMqbUBPbQyylgdRd6TDEdU+fgohUVGW4gPI0UnrAzqM/kx5+mozLqCVh2D Cg==. (64751136 bytes) npm WARN old lockfile at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19) npm WARN old lockfile at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:370:12) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:434:29) npm WARN old lockfile at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:90:18) npm WARN old lockfile at IntegrityStream.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:265:12) npm WARN old lockfile at IntegrityStream.resume (/usr/lib/node_modules/npm/node_modules/minipass/index.js:269:24) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/minipass-pipeline/index.js:105:19) npm WARN old lockfile at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/make-fetch-happen/lib/pipeline.js:37:18) npm WARN old lockfile at CachingMinipassPipeline.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:259:10) { npm WARN old lockfile code: 'EINTEGRITY', npm WARN old lockfile found: Integrity { sha512: [ [Hash] ] }, npm WARN old lockfile expected: [ npm WARN old lockfile Hash { npm WARN old lockfile source: 'sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==', npm WARN old lockfile digest: 'qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==', npm WARN old lockfile algorithm: 'sha512', npm WARN old lockfile options: [] npm WARN old lockfile } npm WARN old lockfile ], npm WARN old lockfile algorithm: 'sha512', npm WARN old lockfile sri: Integrity { sha512: [ [Hash] ] } npm WARN old lockfile } npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/iobroker.icons-open-icon-library-png npm ERR! dest /opt/iobroker/node_modules/.iobroker.icons-open-icon-library-png-dWPxt8qG npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/iobroker.icons-open-icon-library-png' -> '/opt/iobroker/node_modules/.iobroker.icons-open-icon-li brary-png-dWPxt8qG' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-06-26T15_08_41_333Z-debug-0.log host.raspberrypi Cannot install iobroker.smartgarden@2.0.0: 217pi@raspberrypi:/opt/iobroker $ npm ls canvas iobroker.inst@2.0.3 /opt/iobroker ├─┬ iobroker.echarts@1.0.10 extraneous │ ├── canvas@2.9.1 │ └─┬ jsdom@19.0.0 │ └── canvas@2.9.1 deduped ├─┬ iobroker.iot@1.11.7 │ └── canvas@2.9.1 deduped └─┬ iobroker.mihome-vacuum@3.4.1 └── canvas@2.9.1 dedupedpi@raspberrypi:/opt/iobroker $ uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.15.1 v16.15.1 8.11.0 pi /opt/iobroker OK:1 http://archive.raspberrypi.org/debian buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 http://phoscon.de/apt/deconz buster InRelease OK:4 https://deb.nodesource.com/node_16.x buster InRelease OK:5 https://www.pivccu.de/piVCCU stable InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Alle Pakete sind aktuell. nodejs: Installiert: 16.15.1-deb-1nodesource1 Installationskandidat: 16.15.1-deb-1nodesource1 Versionstabelle: *** 16.15.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packagespi@raspberrypi:/opt/iobroker $ iobroker status iobroker is running on this host. Objects type: jsonl States type: jsonlpi@raspberrypi:/opt/iobroker $ iobroker list instances + system.adapter.accuweather.0 : accuweather : raspberrypi - enabled + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.birthdays.0 : birthdays : raspberrypi - enabled system.adapter.ble.0 : ble : raspberrypi - disabled system.adapter.calendar.0 : calendar : raspberrypi - disabled, port: 8095 + system.adapter.cloud.0 : cloud : raspberrypi - enabled + system.adapter.contact.0 : contact : raspberrypi - enabled, port: 8096 system.adapter.daswetter.0 : daswetter : raspberrypi - enabled system.adapter.devices.0 : devices : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.dwd.0 : dwd : raspberrypi - enabled + system.adapter.echarts.0 : echarts : raspberrypi - enabled + system.adapter.fahrplan.0 : fahrplan : raspberrypi - enabled + system.adapter.fb-checkpresence.0 : fb-checkpresence : raspberrypi - enabled system.adapter.feiertage.0 : feiertage : raspberrypi - enabled system.adapter.flot.0 : flot : raspberrypi - disabled + system.adapter.fritzbox.0 : fritzbox : raspberrypi - enabled system.adapter.gardena.0 : gardena : raspberrypi - disabled system.adapter.habpanel.0 : habpanel : raspberrypi - disabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.hm-rega.0 : hm-rega : raspberrypi - enabled + system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - enabled, port: 0 + system.adapter.hm-rpc.4 : hm-rpc : raspberrypi - enabled, port: 0 system.adapter.ical.1 : ical : raspberrypi - enabled system.adapter.ical.2 : ical : raspberrypi - enabled system.adapter.ical.3 : ical : raspberrypi - enabled system.adapter.ical.4 : ical : raspberrypi - enabled system.adapter.ical.5 : ical : raspberrypi - enabled system.adapter.ical.6 : ical : raspberrypi - enabled system.adapter.ical.7 : ical : raspberrypi - enabled system.adapter.ical.8 : ical : raspberrypi - enabled system.adapter.icons-fatcow-hosting.0 : icons-fatcow-hosting : raspberrypi - disabled system.adapter.icons-icons8.0 : icons-icons8 : raspberrypi - disabled system.adapter.icons-material-svg.0 : icons-material-svg : raspberrypi - disabled system.adapter.icons-mfd-png.0 : icons-mfd-png : raspberrypi - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : raspberrypi - disabled system.adapter.icons-open-icon-library-png.0: icons-open-icon-library-png: raspberrypi - disabled + system.adapter.info.0 : info : raspberrypi - enabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.iqontrol.0 : iqontrol : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled system.adapter.lovelace.0 : lovelace : raspberrypi - disabled, port: 8091, bind: 192.168.178.147, run as: admin system.adapter.luftdaten.0 : luftdaten : raspberrypi - enabled system.adapter.meteoalarm.0 : meteoalarm : raspberrypi - disabled + system.adapter.mihome-vacuum.0 : mihome-vacuum : raspberrypi - enabled, port: 54321 system.adapter.mihome.0 : mihome : raspberrypi - disabled, port: 9898, bind: 192.168.178.145 + system.adapter.milight.0 : milight : raspberrypi - enabled, port: 8899 system.adapter.mqtt.0 : mqtt : raspberrypi - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.musiccast.0 : musiccast : raspberrypi - enabled + system.adapter.nina.0 : nina : raspberrypi - enabled system.adapter.openweathermap.0 : openweathermap : raspberrypi - enabled system.adapter.parser.0 : parser : raspberrypi - disabled + system.adapter.ping.0 : ping : raspberrypi - enabled + system.adapter.pollenflug.0 : pollenflug : raspberrypi - enabled system.adapter.radar2.0 : radar2 : raspberrypi - disabled + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled system.adapter.samsung.0 : samsung : raspberrypi - disabled system.adapter.samsung_tizen.0 : samsung_tizen : raspberrypi - disabled, port: 8002 system.adapter.samsung_tizen.1 : samsung_tizen : raspberrypi - disabled, port: 8002 + system.adapter.sayit.0 : sayit : raspberrypi - enabled, port: 0 system.adapter.scenes.0 : scenes : raspberrypi - disabled system.adapter.shelly.0 : shelly : raspberrypi - disabled, port: 1882, bind: 0.0.0.0 system.adapter.smartcontrol.0 : smartcontrol : raspberrypi - disabled + system.adapter.smartgarden.0 : smartgarden : raspberrypi - enabled + system.adapter.snmp.0 : snmp : raspberrypi - enabled system.adapter.sonoff.0 : sonoff : raspberrypi - disabled, port: 1883, bind: 192.168.178.147 + system.adapter.sonos.0 : sonos : raspberrypi - enabled system.adapter.synology.0 : synology : raspberrypi - disabled, port: 5000 + system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - enabled + system.adapter.tr-064.0 : tr-064 : raspberrypi - enabled + system.adapter.trashschedule.0 : trashschedule : raspberrypi - enabled system.adapter.tuya.0 : tuya : raspberrypi - disabled + system.adapter.tvprogram.0 : tvprogram : raspberrypi - enabled system.adapter.tvspielfilm.0 : tvspielfilm : raspberrypi - enabled + system.adapter.upnp.0 : upnp : raspberrypi - enabled system.adapter.uv-protect.0 : uv-protect : raspberrypi - enabled system.adapter.vis-bars.0 : vis-bars : raspberrypi - enabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : raspberrypi - disabled system.adapter.vis-colorpicker.0 : vis-colorpicker : raspberrypi - disabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : raspberrypi - disabled system.adapter.vis-history.0 : vis-history : raspberrypi - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : raspberrypi - disabled system.adapter.vis-map.0 : vis-map : raspberrypi - disabled system.adapter.vis-material-advanced.0 : vis-material-advanced : raspberrypi - disabled system.adapter.vis-material-webfont.0 : vis-material-webfont : raspberrypi - disabled system.adapter.vis-material.0 : vis-material : raspberrypi - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : raspberrypi - disabled system.adapter.vis-players.0 : vis-players : raspberrypi - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - disabled system.adapter.vis.0 : vis : raspberrypi - enabled system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.withings.0 : withings : raspberrypi - enabled + system.adapter.yamaha.0 : yamaha : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyACM0
Support us
387
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge