NEWS
js-controller 3.2 jetzt im Latest!
js-controller 3.2 jetzt im Latest!
ioBroker Allgemein
575
Posts
70
Posters
144.9k
Views
57
Watching
-
@peterfido nicht sicher, aber vllt hilft es vorher mal den npm cache zu löschen.
npm cache clean --forceLeider auch nicht. Ich hänge mal die Log-Datei2021-02-28T08_33_23_642Z-debug.zip hier an.
Gruß
Peterfido
Proxmox auf Intel NUC12WSHi5
ioBroker: Debian (VM)
CCU: Debmatic (VM)
Influx: Debian (VM)
Grafana: Debian (VM)
eBus: Debian (VM)
Zigbee: Debian (VM) mit zigbee2mqtt -
Leider auch nicht. Ich hänge mal die Log-Datei2021-02-28T08_33_23_642Z-debug.zip hier an.
@peterfido kann ich nicht öffnen
-
@peterfido kann ich nicht öffnen
@crunchip
Hier nochmal 2021-02-28T08_33_23_642Z-debug.log ungezippt.eine erzwungene Installation (mit dem Parameter -f) hat jetzt den JS-Controller aktualisiert. Ob es Nebeneffekte gab, kann ich noch nicht sagen...
Ah, okay. Jetzt habe ich den 3.3 drauf. Also zurück zum Snapshot von heute Morgen...
Edit: Jetzt gleich mal mit -f installiert und läuft.
peter@proxbroker:~$ npm install -f iobroker.js-controller@3.2.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker" > iobroker.js-controller@3.2.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.11 > iobroker.js-controller@3.2.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first object _design/system updated Renamed repository "default to "stable" Renamed repository "latest to "beta" > @root/acme@3.1.0 postinstall /opt/iobroker/node_modules/@root/acme > node scripts/postinstall + iobroker.js-controller@3.2.16 added 54 packages from 25 contributors, removed 32 packages, updated 26 packages and moved 1 package in 23.176s 62 packages are looking for funding run `npm fund` for details ╭───────────────────────────────────────────────────────────────╮ │ │ │ New major version of npm available! 6.14.11 → 7.6.0 │ │ Changelog: https://github.com/npm/cli/releases/tag/v7.6.0 │ │ Run npm install -g npm to update! │ │ │ ╰───────────────────────────────────────────────────────────────╯ peter@proxbroker:~$ iobroker startGruß
Peterfido
Proxmox auf Intel NUC12WSHi5
ioBroker: Debian (VM)
CCU: Debmatic (VM)
Influx: Debian (VM)
Grafana: Debian (VM)
eBus: Debian (VM)
Zigbee: Debian (VM) mit zigbee2mqtt -
@crunchip
Hier nochmal 2021-02-28T08_33_23_642Z-debug.log ungezippt.eine erzwungene Installation (mit dem Parameter -f) hat jetzt den JS-Controller aktualisiert. Ob es Nebeneffekte gab, kann ich noch nicht sagen...
Ah, okay. Jetzt habe ich den 3.3 drauf. Also zurück zum Snapshot von heute Morgen...
Edit: Jetzt gleich mal mit -f installiert und läuft.
peter@proxbroker:~$ npm install -f iobroker.js-controller@3.2.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker" > iobroker.js-controller@3.2.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.11 > iobroker.js-controller@3.2.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first object _design/system updated Renamed repository "default to "stable" Renamed repository "latest to "beta" > @root/acme@3.1.0 postinstall /opt/iobroker/node_modules/@root/acme > node scripts/postinstall + iobroker.js-controller@3.2.16 added 54 packages from 25 contributors, removed 32 packages, updated 26 packages and moved 1 package in 23.176s 62 packages are looking for funding run `npm fund` for details ╭───────────────────────────────────────────────────────────────╮ │ │ │ New major version of npm available! 6.14.11 → 7.6.0 │ │ Changelog: https://github.com/npm/cli/releases/tag/v7.6.0 │ │ Run npm install -g npm to update! │ │ │ ╰───────────────────────────────────────────────────────────────╯ peter@proxbroker:~$ iobroker start@peterfido auch wenn optional, vllt wäre es sauber durchgelaufen, wenn du fsevent@2.3.1 installiert hättest, zumindest zeigt meine Installation diese Version
-
@peterfido auch wenn optional, vllt wäre es sauber durchgelaufen, wenn du fsevent@2.3.1 installiert hättest, zumindest zeigt meine Installation diese Version
Hat "er" ja bereits selbst versucht. Eben mal schnell nen Snapshot erstellt und manuell getestet:
peter@proxbroker:~$ npm i fsevents@2.3.1 npm ERR! code EBADPLATFORM npm ERR! notsup Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm ERR! notsup Valid OS: darwin npm ERR! notsup Valid Arch: any npm ERR! notsup Actual OS: linux npm ERR! notsup Actual Arch: x64 npm ERR! A complete log of this run can be found in: npm ERR! /home/peter/.npm/_logs/2021-02-28T09_52_02_937Z-debug.log peter@proxbroker:~$fsEvents ist für darwin gedacht. darwin könnte Apple bedeuten.
-
@crunchip
Hier nochmal 2021-02-28T08_33_23_642Z-debug.log ungezippt.eine erzwungene Installation (mit dem Parameter -f) hat jetzt den JS-Controller aktualisiert. Ob es Nebeneffekte gab, kann ich noch nicht sagen...
Ah, okay. Jetzt habe ich den 3.3 drauf. Also zurück zum Snapshot von heute Morgen...
Edit: Jetzt gleich mal mit -f installiert und läuft.
peter@proxbroker:~$ npm install -f iobroker.js-controller@3.2.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker" > iobroker.js-controller@3.2.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.11 > iobroker.js-controller@3.2.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first object _design/system updated Renamed repository "default to "stable" Renamed repository "latest to "beta" > @root/acme@3.1.0 postinstall /opt/iobroker/node_modules/@root/acme > node scripts/postinstall + iobroker.js-controller@3.2.16 added 54 packages from 25 contributors, removed 32 packages, updated 26 packages and moved 1 package in 23.176s 62 packages are looking for funding run `npm fund` for details ╭───────────────────────────────────────────────────────────────╮ │ │ │ New major version of npm available! 6.14.11 → 7.6.0 │ │ Changelog: https://github.com/npm/cli/releases/tag/v7.6.0 │ │ Run npm install -g npm to update! │ │ │ ╰───────────────────────────────────────────────────────────────╯ peter@proxbroker:~$ iobroker start@peterfido sagte in js-controller 3.2 jetzt im Latest!:
peter@proxbroker:~$ npm install -f iobroker.js-controller@3.2.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker"
bist du hier nicht im falschen Verzeichnis?
-
@peterfido sagte in js-controller 3.2 jetzt im Latest!:
peter@proxbroker:~$ npm install -f iobroker.js-controller@3.2.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker"
bist du hier nicht im falschen Verzeichnis?
@crunchip
Jo, ist mir auch aufgefallen. Macht aber keinen Unterschied.peter@proxbroker:/opt/iobroker$ npm i fsevents npm ERR! code EBADPLATFORM npm ERR! notsup Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm ERR! notsup Valid OS: darwin npm ERR! notsup Valid Arch: any npm ERR! notsup Actual OS: linux npm ERR! notsup Actual Arch: x64 npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-02-28T10_01_47_431Z-debug.log peter@proxbroker:/opt/iobroker$ -
Hat "er" ja bereits selbst versucht. Eben mal schnell nen Snapshot erstellt und manuell getestet:
peter@proxbroker:~$ npm i fsevents@2.3.1 npm ERR! code EBADPLATFORM npm ERR! notsup Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm ERR! notsup Valid OS: darwin npm ERR! notsup Valid Arch: any npm ERR! notsup Actual OS: linux npm ERR! notsup Actual Arch: x64 npm ERR! A complete log of this run can be found in: npm ERR! /home/peter/.npm/_logs/2021-02-28T09_52_02_937Z-debug.log peter@proxbroker:~$fsEvents ist für darwin gedacht. darwin könnte Apple bedeuten.
@peterfido Ja ist Apple und damit an sich optional.
Mach mal im ioBroker Verzeichnis ein "npm ls fsevents"
-
@peterfido Ja ist Apple und damit an sich optional.
Mach mal im ioBroker Verzeichnis ein "npm ls fsevents"
Hier das Ergebnis:
peter@proxbroker:/opt/iobroker$ npm ls fsevents iobroker.inst@2.0.3 /opt/iobroker ├── fsevents@2.2.1 └─┬ iobroker.js-controller@3.2.16 └─┬ chokidar@3.5.1 └── fsevents@2.3.2 peter@proxbroker:/opt/iobroker$ npm ls chokidar iobroker.inst@2.0.3 /opt/iobroker └─┬ iobroker.js-controller@3.2.16 └── chokidar@3.5.1 peter@proxbroker:/opt/iobroker$Gleich nochmal mit chokidar hinterher abgefragt.
Gruß
Peterfido
Proxmox auf Intel NUC12WSHi5
ioBroker: Debian (VM)
CCU: Debmatic (VM)
Influx: Debian (VM)
Grafana: Debian (VM)
eBus: Debian (VM)
Zigbee: Debian (VM) mit zigbee2mqtt -
Hier das Ergebnis:
peter@proxbroker:/opt/iobroker$ npm ls fsevents iobroker.inst@2.0.3 /opt/iobroker ├── fsevents@2.2.1 └─┬ iobroker.js-controller@3.2.16 └─┬ chokidar@3.5.1 └── fsevents@2.3.2 peter@proxbroker:/opt/iobroker$ npm ls chokidar iobroker.inst@2.0.3 /opt/iobroker └─┬ iobroker.js-controller@3.2.16 └── chokidar@3.5.1 peter@proxbroker:/opt/iobroker$Gleich nochmal mit chokidar hinterher abgefragt.
@peterfido sieht bei mir so aus
root@IoBroker:/opt/iobroker# npm ls fsevents iobroker.inst@2.0.3 /opt/iobroker └─┬ iobroker.js-controller@3.2.16 └─┬ chokidar@3.5.1 └── UNMET OPTIONAL DEPENDENCY fsevents@~2.3.1 -
@apollon77, @all
@apollon77 sagte in js-controller 3.2 jetzt im Latest!:@w00dy Ja, da ist der Master nicht auf controller 3.2.16 aber ein Client oder Adapter mit 3.2er code greift darauf zu. Ggf nochmal alles restarten.
Hallo, leider kann ich mich erst heute zurückmelden wegen der Fehlermeldung des Shelly-Adapters nach dem Update des js-controller. Das Netzteil vom Raspberry 4 war defekt und ich musste auf ein neues warten.
Auch nach einem Restart hagelt es alle paar Sekunden diese Fehlermeldung:
shelly.0 2021-02-28 13:09:51.386 error (1728) Cannot find search "folder" in "system"Der fritzdect-Adapter funktioniert auch nicht mehr:
fritzdect.0 2021-02-28 13:17:31.051 error (23748) Did not get session id- invalid username or password? fritzdect.0 2021-02-28 13:17:31.050 error (23748) fritzbox returned this "0000000000000000"Username und Password sind definitiv korrekt.
Keine Ahnung, ob das jetzt auch mit dem Update vom js-controller zusammenhängt, zuvor gab es allerdings keine Probs.Hast Du, habt Ihr noch ne Idee, wie ich das beheben kann?
LG,
w00dy -
@apollon77, @all
@apollon77 sagte in js-controller 3.2 jetzt im Latest!:@w00dy Ja, da ist der Master nicht auf controller 3.2.16 aber ein Client oder Adapter mit 3.2er code greift darauf zu. Ggf nochmal alles restarten.
Hallo, leider kann ich mich erst heute zurückmelden wegen der Fehlermeldung des Shelly-Adapters nach dem Update des js-controller. Das Netzteil vom Raspberry 4 war defekt und ich musste auf ein neues warten.
Auch nach einem Restart hagelt es alle paar Sekunden diese Fehlermeldung:
shelly.0 2021-02-28 13:09:51.386 error (1728) Cannot find search "folder" in "system"Der fritzdect-Adapter funktioniert auch nicht mehr:
fritzdect.0 2021-02-28 13:17:31.051 error (23748) Did not get session id- invalid username or password? fritzdect.0 2021-02-28 13:17:31.050 error (23748) fritzbox returned this "0000000000000000"Username und Password sind definitiv korrekt.
Keine Ahnung, ob das jetzt auch mit dem Update vom js-controller zusammenhängt, zuvor gab es allerdings keine Probs.Hast Du, habt Ihr noch ne Idee, wie ich das beheben kann?
@w00dy Zum Fehler mit dem "folder": kann es ein das irgendwas nioch mit nem alten Controller läuft? zb ein Master? Ansonsten versuch mal (vorher iobroker stoppen) "iobroker setup first" auf dem Master host.
Der andere Fehler kann nicht vom Controller kommen
-
@w00dy Zum Fehler mit dem "folder": kann es ein das irgendwas nioch mit nem alten Controller läuft? zb ein Master? Ansonsten versuch mal (vorher iobroker stoppen) "iobroker setup first" auf dem Master host.
Der andere Fehler kann nicht vom Controller kommen
@apollon77
Hm, ich nutze eigentlich kein Multihost-Sytem, dennoch hat das funktioniert
Hier mal die Ausgabe:rp02@ioBroker:~ $ iobroker setup first object _design/system updated Renamed repository "default to "stable" Renamed repository "latest to "beta"Hatte an den repos eigentlich nie was geändert, ...egal jetzt gibt der shelly-Adater endlich ruhe.
Den fritzdect-Adapter habe ich rausgeschmissen und neu installiert, der läuft auch wieder.
Besten Dank für die Hilfe!
LG,
w00dy -
@apollon77
Hm, ich nutze eigentlich kein Multihost-Sytem, dennoch hat das funktioniert
Hier mal die Ausgabe:rp02@ioBroker:~ $ iobroker setup first object _design/system updated Renamed repository "default to "stable" Renamed repository "latest to "beta"Hatte an den repos eigentlich nie was geändert, ...egal jetzt gibt der shelly-Adater endlich ruhe.
Den fritzdect-Adapter habe ich rausgeschmissen und neu installiert, der läuft auch wieder.
Besten Dank für die Hilfe!
-
@w00dy Sehr interessant. SIcher das das controller 3.2.16 ist? Dann hätte beim install was nicht vollständig geklappt
-
@apollon77 Ja, siehe Foto:
Und nun, ...muss ich mir Sorgen machen??
-
@w00dy wenn jetzt alles tut ist ja ok. Das install log vom install „damals“ hast du ja bestimmt nicht mehr
@apollon77 Nein, leider nicht. Ein komisches Gefühl bleibt trotzdem zurück
-
@apollon77 ICh hatte das erst als "normales" Problem unter allgemein gepostet, hoffe ich bin hier richtig
System mit 3 Raspi Pi 3b+, alle auf js-controller 3.1.6 und node.js v12.19.0). Habe einen Slave upgegradet und da Probleme mit plenticore adapter:
plenticore.0 2021-01-17 20:52:11.674 error (18379) Cannot check object existence of "plenticore.0.info.connection": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.672 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.YieldYear": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.671 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyToGridYear": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.670 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.YieldTotal": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.669 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyToGridTotal": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.668 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.YieldMonth": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.666 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyToGridMonth": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.665 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.YieldDay": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.664 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyToGridDay": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.663 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.OwnConsumptionRateYear": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.662 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.OwnConsumptionRateTotal": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.659 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.OwnConsumptionRateMonth": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.658 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.OwnConsumptionRateDay": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.657 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomePvYear": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.656 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomePvTotal": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.655 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomePvMonth": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.654 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomePvDay": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.653 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeGridYear": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.652 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeGridTotal": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.651 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeGridMonth": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.650 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeGridDay": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.649 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeBatYear": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.648 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeBatTotal": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.646 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeBatMonth": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.645 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeBatDay": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.643 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeYear": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.642 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeTotal": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.640 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeMonth": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.639 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.EnergyHomeDay": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.638 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.CO2SavingYear": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.637 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.CO2SavingTotal": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.636 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.CO2SavingMonth": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.634 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.CO2SavingDay": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.633 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.AutarkyYear": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.632 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.AutarkyTotal": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.631 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.AutarkyMonth": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.630 error (18379) Cannot check object existence of "plenticore.0.scb.statistic.EnergyFlow.AutarkyDay": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.629 error (18379) Cannot check object existence of "plenticore.0.scb.export.PortalConActive": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.628 error (18379) Cannot check object existence of "plenticore.0.devices.local.pv2.U": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.627 error (18379) Cannot check object existence of "plenticore.0.devices.local.pv2.P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.601 error (18379) Cannot check object existence of "plenticore.0.devices.local.pv2.I": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.601 error (18379) Cannot check object existence of "plenticore.0.devices.local.pv1.U": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.600 error (18379) Cannot check object existence of "plenticore.0.devices.local.pv1.P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.599 error (18379) Cannot check object existence of "plenticore.0.devices.local.pv1.I": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.598 error (18379) Cannot check object existence of "plenticore.0.devices.local.battery.U": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.597 error (18379) Cannot check object existence of "plenticore.0.devices.local.battery.SoC": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.596 error (18379) Cannot check object existence of "plenticore.0.devices.local.battery.P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.595 error (18379) Cannot check object existence of "plenticore.0.devices.local.battery.I": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.595 error (18379) Cannot check object existence of "plenticore.0.devices.local.battery.Cycles": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.594 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.S": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.593 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.Q": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.592 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.591 error (18379) Cannot check object existence of "plenticore.0.devices.local.ToGrid_P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.590 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.L3_U": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.589 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.L3_P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.589 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.L3_I": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.588 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.L2_U": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.587 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.L2_P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.586 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.L2_I": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.585 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.L1_U": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.584 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.L1_P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.584 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.L1_I": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.583 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.Frequency": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.582 error (18379) Cannot check object existence of "plenticore.0.devices.local.ac.CosPhi": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.581 error (18379) Cannot check object existence of "plenticore.0.devices.local.LimitEvuAbs": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.580 error (18379) Cannot check object existence of "plenticore.0.devices.local.inverter.State": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.579 error (18379) Cannot check object existence of "plenticore.0.devices.local.Home_P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.579 error (18379) Cannot check object existence of "plenticore.0.devices.local.HomePv_P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.578 error (18379) Cannot check object existence of "plenticore.0.devices.local.HomeOwn_P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.577 error (18379) Cannot check object existence of "plenticore.0.devices.local.HomeGrid_P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.576 error (18379) Cannot check object existence of "plenticore.0.devices.local.HomeBat_P": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.575 error (18379) Cannot check object existence of "plenticore.0.devices.local.EM_State": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.574 error (18379) Cannot check object existence of "plenticore.0.devices.local.DigitalIn": ReplyError: Error exists NOT SUPPORTED plenticore.0 2021-01-17 20:52:11.572 error (18379) Cannot check object existence of "plenticore.0.devices.local.Dc_P": ReplyError: Error exists NOT SUPPORTED@amg_666 nach dem Update zeigt bei mir der Plenticore adapter auch warnungen im log, und nicht wenig
plenticore.0 2021-03-02 16:00:38.072 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:36.563 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:36.562 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:36.561 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:34.798 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:34.797 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:34.797 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:33.176 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:33.174 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:33.174 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:31.450 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:31.449 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:31.449 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:29.783 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:29.783 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:29.781 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions -
@amg_666 nach dem Update zeigt bei mir der Plenticore adapter auch warnungen im log, und nicht wenig
plenticore.0 2021-03-02 16:00:38.072 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:36.563 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:36.562 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:36.561 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:34.798 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:34.797 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:34.797 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:33.176 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:33.174 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:33.174 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:31.450 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:31.449 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:31.449 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:29.783 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:29.783 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:29.781 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions -
@amg_666 nach dem Update zeigt bei mir der Plenticore adapter auch warnungen im log, und nicht wenig
plenticore.0 2021-03-02 16:00:38.072 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:36.563 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:36.562 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:36.561 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:34.798 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:34.797 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:34.797 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:33.176 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:33.174 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:33.174 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:31.450 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:31.449 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:31.449 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:29.783 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:29.783 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions plenticore.0 2021-03-02 16:00:29.781 warn (362561) State "plenticore.0.forecast.day1.power.9h.generated" has no existing object, this might lead to an error in future versions@man10to hmm, ich habe eben auf die 2.1.8 upgedatet, keine Probleme:
plenticore.0 2021-03-02 16:14:35.183 info (32361) Using forecast of day 2 for MinSoC calculation. plenticore.0 2021-03-02 16:14:35.182 info (32361) calcMinSoC for day 2. plenticore.0 2021-03-02 16:14:34.579 info (32361) calcMinSoC for day 1. plenticore.0 2021-03-02 16:14:32.806 info (32361) Read forecast data before calcMinSoC. plenticore.0 2021-03-02 16:14:32.796 info (32361) Using daswetter.0 in weather forcast. plenticore.0 2021-03-02 16:14:32.794 info (32361) Still 1 adapters to check. plenticore.0 2021-03-02 16:14:32.567 info (32361) Still 2 adapters to check. plenticore.0 2021-03-02 16:14:32.564 info (32361) Enabling MinSoC forecast data. plenticore.0 2021-03-02 16:14:32.539 info (32361) Enabling forecast data. plenticore.0 2021-03-02 16:14:29.178 info (32361) [INFO] Configured polling interval: 20000 plenticore.0 2021-03-02 16:14:29.175 info (32361) Configured Wp of panel(s) is 7296 plenticore.0 2021-03-02 16:14:29.171 info (32361) Got all internal forecast data and made it available to main process. plenticore.0 2021-03-02 16:14:29.075 info (32361) Requested alternative weather data from kachelmannwetter.com plenticore.0 2021-03-02 16:14:28.928 info (32361) Requested weather data from kachelmannwetter.com plenticore.0 2021-03-02 16:14:28.821 info (32361) City id for coordinates 8.771570193429486/50.28758620000001 is 2862709 plenticore.0 2021-03-02 16:14:28.098 info (32361) got weather data from met.no with 90 elements. plenticore.0 2021-03-02 16:14:27.075 info (32361) [START] Starting adapter plenticore v2.1.8r232 plenticore.0 2021-03-02 16:14:26.999 info (32361) starting. Version 2.1.8 in /opt/iobroker/node_modules/iobroker.plenticore, node: v12.20.1, js-controller: 3.2.16 host.iostrom 2021-03-02 16:14:20.178 info instance system.adapter.plenticore.0 started with pid 32361 host.iostrom 2021-03-02 16:14:15.650 info iobroker exit 0 host.iostrom 2021-03-02 16:14:15.308 info instance system.adapter.plenticore.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.iostrom 2021-03-02 16:14:14.586 info iobroker Adapter "plenticore" updated host.iostrom 2021-03-02 16:14:14.513 info iobroker upload [0] plenticore.admin /opt/iobroker/node_modules/iobroker.plenticore/admin/index_m.html index_m.html text/html host.iostrom 2021-03-02 16:14:14.445 info iobroker upload [1] plenticore.admin /opt/iobroker/node_modules/iobroker.plenticore/admin/plenticore.png plenticore.png image/png plenticore.0 2021-03-02 16:14:14.389 info (13190) Logged out from API host.iostrom 2021-03-02 16:14:14.377 info iobroker upload [2] plenticore.admin /opt/iobroker/node_modules/iobroker.plenticore/admin/style.css style.css text/css plenticore.0 2021-03-02 16:14:14.286 info (13190) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason plenticore.0 2021-03-02 16:14:14.284 info (13190) terminating plenticore.0 2021-03-02 16:14:14.282 info (13190) [END] Stopping plenticore adapter...
50
Online32.4k
Users81.3k
Topics1.3m
Posts