Fenecon/OpenEMS Adapter
-
wie berechnest du diesen??
-
@wolf-b
Der Adapter ist ganz frisch und ich bin noch nicht so fit im Adapterprogrammieren.
Werden ihn aber die Tage in das Beta-Repository einchecken. -
@hugo1217
Die Berechnung habe ich von openems abgeschaut.
Die benötigten Werte sind im _sum Ordner zu finden.if (consumptionActivePower <= 0) { autarchy = 100; } else { autarchy = Math.round(Math.max(0, Math.min(100, (1 - gridAcivePower / consumptionActivePower) * 100))); } -
@mrg sagte in Fenecon/OpenEMS Adapter:
@wolf-b
Der Adapter ist ganz frisch und ich bin noch nicht so fit im Adapterprogrammieren.
Werden ihn aber die Tage in das Beta-Repository einchecken.Das freut sicher nicht nur mich, wenn Du den Adapter zur Verfügung stellst - ich sage jetzt schonmal DANKE !
-
Oh ja... ich hätte auch großes Interesse daran. Ich warte schon lang auf eine einfache Lösung die Daten meines Fenecon Home in den ioBroker zu bekommen.
Wie installiert man den Adapter denn aktuell? Über GitHub gehts ja noch nicht.
Sorry für die Frage, aber ich bin leider ein bisschen raus aus dem Thema. -
@mojo1985
du kannst den Adapter vorerst manuell über Github installieren.Wie das geht ist hier zu finden: https://www.iobroker.net/?lang=de#de/documentation/admin/adapter.md unter Abschnitt 5.
Der Link zum Github lautet: https://github.com/sg-app/ioBroker.fenecon.gitGruß Georg
-
Hallo zusammen, der neue Adapter ist ja super endlich auch die Autarkie Berechnung. Hat der Adapter auch den Eigenverbrauch oder kann ich den in Prozent irgendwie mit dem Adapter berechnen lassen?
Und noch eine Frage hat jemand fürs ViS die Ansicht so hinbekommen wie im Original Fenecon Fems ?Gruß Sunnylaila
-
@sunnylaila
Danke für dein Lob.@nobroker hat die Fenecon-Seite nachgebaut hat er geschrieben. Vielleicht stellt er uns das zur Verfügung?
Die Berechnung von Eigenverbrauch kannst du selber machen.
Berechnet muss werden:(1-(_sum.GridActivePower *-1 / _sum.ProductionActivePower)) *100In meiner nächsten Version habe ich die Berechnung mit eingebaut.
Gruß Georg
-
super gerade die neueste Version installiert funktioniert klasse
Danke für deine Mühen -
habe jetzt gerade gesehen das ich im log einen haufen Warnungen vom fenecon Adapter
siehe logfenecon.0 2024-07-21 20:11:24.211 warn Got terminate signal. Checking desired PID: 0 vs own PID 4209 fenecon.0 2024-07-21 20:11:22.188 warn State "fenecon.0._sum.SelfConsumption" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.179 warn State "fenecon.0._sum.Autarchy" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.171 warn State "fenecon.0.charger1._PropertySafetyCountry" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.164 warn State "fenecon.0.charger1.Current" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.158 warn State "fenecon.0.charger1._PropertyControlMode" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.152 warn State "fenecon.0.charger1._PropertyMpptForShadowEnable" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.145 warn State "fenecon.0.charger1._PropertyMaxBatteryPower" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.139 warn State "fenecon.0.charger1.State" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.132 warn State "fenecon.0.charger1.HasNoDcPv" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.126 warn State "fenecon.0.charger1._PropertyId" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.079 warn State "fenecon.0.charger1.ActualPower" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.073 warn State "fenecon.0.charger1._PropertyRcrEnable" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.067 warn State "fenecon.0.charger1._PropertySetfeedInPowerSettings" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.061 warn State "fenecon.0.charger1._PropertyEnabled" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.055 warn State "fenecon.0.charger1._PropertyGoodWeMeterCategory" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.049 warn State "fenecon.0.charger1.ActualEnergy" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.044 warn State "fenecon.0.charger1._PropertyAlias" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.038 warn State "fenecon.0.charger1.MaxActualPower" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.032 warn State "fenecon.0.charger1.Voltage" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.026 warn State "fenecon.0.charger1._PropertyEssOrBatteryInverterId" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.020 warn State "fenecon.0.charger1._PropertyStartStop" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.014 warn State "fenecon.0.charger1._PropertyBackupEnable" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:22.006 warn State "fenecon.0.charger1._PropertyExternalMeterRatioValueB" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.951 warn State "fenecon.0.charger1._PropertyFeedPowerEnable" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.930 warn State "fenecon.0.charger1._PropertyExternalMeterRatioValueA" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.923 warn State "fenecon.0.charger1.ModbusCommunicationFailed" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.917 warn State "fenecon.0.charger1._PropertyMpptPort" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.867 warn State "fenecon.0.charger1._PropertyPvPort" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.860 warn State "fenecon.0.charger1._PropertyFeedPowerPara" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.853 warn State "fenecon.0.charger1._PropertyModbusUnitId" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.846 warn State "fenecon.0.charger1._PropertyCapacity" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.798 warn State "fenecon.0.charger1._PropertyModbusId" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.791 warn State "fenecon.0.meter2._PropertySafetyCountry" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.783 warn State "fenecon.0.meter2.Frequency" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.776 warn State "fenecon.0.meter2._PropertyMaxBatteryPower" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.768 warn State "fenecon.0.meter2._PropertyId" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.760 warn State "fenecon.0.meter2._PropertyEnabled" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.752 warn State "fenecon.0.meter2._PropertyGoodWeMeterCategory" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.745 warn State "fenecon.0.meter2.ActiveProductionEnergyL2" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.737 warn State "fenecon.0.meter2.ActiveProductionEnergyL1" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.682 warn State "fenecon.0.meter2.ReactivePower" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.668 warn State "fenecon.0.meter2.ActiveProductionEnergyL3" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.658 warn State "fenecon.0.meter2._PropertyAlias" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.608 warn State "fenecon.0.meter2.CurrentL2" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.601 warn State "fenecon.0.meter2.CurrentL1" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.538 warn State "fenecon.0.meter2.ActiveProductionEnergy" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.533 warn State "fenecon.0.meter2.Voltage" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.527 warn State "fenecon.0.meter2._PropertyBackupEnable" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.521 warn State "fenecon.0.meter2.FrequencyL2" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.515 warn State "fenecon.0.meter2._PropertyExternalMeterRatioValueB" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.510 warn State "fenecon.0.meter2.FrequencyL3" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.503 warn State "fenecon.0.meter2.ActiveConsumptionEnergy" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.497 warn State "fenecon.0.meter2._PropertyExternalMeterRatioValueA" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.449 warn State "fenecon.0.meter2.FrequencyL1" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.442 warn State "fenecon.0.meter2.ActiveConsumptionEnergyL2" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.413 warn State "fenecon.0.meter2.ActiveConsumptionEnergyL1" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.406 warn State "fenecon.0.meter2.ModbusCommunicationFailed" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.358 warn State "fenecon.0.meter2.ActiveConsumptionEnergyL3" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.352 warn State "fenecon.0.meter2._PropertyModbusId" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.347 warn State "fenecon.0.meter2.Current" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.342 warn State "fenecon.0.meter2._PropertyControlMode" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.286 warn State "fenecon.0.meter2._PropertyMpptForShadowEnable" has no existing object, this might lead to an error in future versions fenecon.0 2024-07-21 20:11:21.281 warn State "fenecon.0.meter2.State" has no existing object, this might lead to an error in future versions2024-07-21 20:11:24.236 warn Got terminate signal. Checking desired PID: 9356 vs own PID 4209habe mir angeschaut ob es Objekte mit dem Namen gibt und sie sind da und trotzdem die Warnung kannst du damit etwas anfangen?
-
@sunnylaila
Bitte Stoppe mal die Instanz, lösche alle Objekte von fenecon und starte die Instanz nochmal.
Ich musste hier einiges ändern damit der Adapter in das offizielle Repo aufgenommen wird. -
ja so hat es geklappt die Warnungen tauchen nicht mehr auf danke
-
@mrg Super! Ich danke dir!
-
Mist... funktioniert bei mir irgendwie nicht
Das spuckt er mir aus:
$ iobroker url https://github.com/sg-app/ioBroker.fenecon.git --host iobroker --debug install sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1 NPM version: 9.6.1Installing sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1... (System call) npm WARN ERESOLVE overriding peer dependency npm WARN npm WARN Could not resolve dependency:npm WARN peer @iobroker/types@"^6.0.0" from @iobroker/adapter-core@3.1.6npm WARN node_modules/iobroker.iot/node_modules/@iobroker/adapter-corenpm WARN @iobroker/adapter-core@"^3.0.4" from iobroker.iot@3.3.0npm WARN node_modules/iobroker.iotnpm WARN npm WARN Conflicting peer dependency: @iobroker/types@6.0.9 npm WARN node_modules/@iobroker/typesnpm WARN peer @iobroker/types@"^6.0.0" from @iobroker/adapter-core@3.1.6 npm WARN node_modules/iobroker.iot/node_modules/@iobroker/adapter-corenpm WARN @iobroker/adapter-core@"^3.0.4" from iobroker.iot@3.3.0npm WARN node_modules/iobroker.iot npm ERR! code EBADENGINE npm ERR! engine Unsupported engine npm ERR! engine Not compatible with your version of node/npm: iobroker.fenecon@0.4.0npm ERR! notsup Not compatible with your version of node/npm: iobroker.fenecon@0.4.0npm ERR! notsup Required: {"node":">= 18"}npm ERR! notsup Actual: {"npm":"9.6.1","node":"v16.19.1"} npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2024-07-29T07_09_19_886Z-debug-0.log host.iobroker Cannot install sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1: 1 ERROR: Process exited with code 25 -
@mojo1985 sagte in Fenecon/OpenEMS Adapter:
ERR! notsup Required: {"node":">= 18"}npm ERR! notsup Actual: {"npm":"9.6.1","node":"v16.19.1"}
-
@homoran Danke dir! Ich hab jetzt node.js nach dem How-To hier im Forum aktualisiert. Allerdings kommen jetzt wieder andere Fehler
$ iobroker url https://github.com/sg-app/ioBroker.fenecon.git --host iobroker --debug install sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1 NPM version: 10.8.1 Installing sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1... (System call) npm warn ERESOLVE overriding peer dependency npm warn While resolving: @iobroker/adapter-core@3.1.6npm warn Found: @iobroker/types@5.0.19npm warn node_modules/iobroker.iot/node_modules/@iobroker/typesnpm warn @iobroker/types@"^5.0.19" from iobroker.iot@3.3.0npm warn node_modules/iobroker.iotnpm warn iobroker.iot@"3.3.0" from the root projectnpm warnnpm warn Could not resolve dependency:npm warn peer @iobroker/types@"^6.0.0" from @iobroker/adapter-core@3.1.6npm warn node_modules/iobroker.iot/node_modules/@iobroker/adapter-corenpm warn @iobroker/adapter-core@"^3.0.4" from iobroker.iot@3.3.0npm warn node_modules/iobroker.iotnpm warnnpm warn Conflicting peer dependency: @iobroker/types@6.0.9npm warn node_modules/@iobroker/typesnpm warn peer @iobroker/types@"^6.0.0" from @iobroker/adapter-core@3.1.6npm warn node_modules/iobroker.iot/node_modules/@iobroker/adapter-corenpm warn @iobroker/adapter-core@"^3.0.4" from iobroker.iot@3.3.0npm warn node_modules/iobroker.iot npm error code EBADENGINE npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-07-29T21_11_21_852Z-debug-0.log host.iobroker Cannot install sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1: 1 ERROR: Process exited with code 25Kann jemand damit was anfangen?
-
Hier läuft es durch:
$ iobroker url https://github.com/sg-app/ioBroker.fenecon --host chet --debug install sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1 NPM version: 10.8.2 Installing sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1... (System call) npm warn skipping integrity check for git dependency ssh://git@github.com/sg-app/ioBroker.fenecon.git added 2 packages in 9s 191 packages are looking for funding run `npm fund` for details upload [13] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/fenecon.png fenecon.png image/png upload [12] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/i18n/de/translations.json i18n/de/translations.json application/json upload [11] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/i18n/en/translations.json i18n/en/translations.json application/json upload [10] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/i18n/es/translations.json i18n/es/translations.json application/json upload [9] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/i18n/fr/translations.json i18n/fr/translations.json application/json upload [7] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/i18n/nl/translations.json i18n/nl/translations.json application/json upload [6] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/i18n/pl/translations.json i18n/pl/translations.json application/json upload [5] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/i18n/pt/translations.json i18n/pt/translations.json application/json upload [4] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/i18n/ru/translations.json i18n/ru/translations.json application/json upload [3] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/i18n/uk/translations.json i18n/uk/translations.json application/json upload [1] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/jsonConfig.json jsonConfig.json application/json upload [0] fenecon.admin /opt/iobroker/node_modules/iobroker.fenecon/admin/words.js words.js application/javascript Process exited with code 0Wie sieht der Rest deines Systems aus?
iob diaganschauen.
Zusätzlich
cd /opt/iobroker npm ls @iobroker/adapter-coreprüfen.
-
@mojo1985 sagte in Fenecon/OpenEMS Adapter:
npm error code EBADENGINE
da passt was nicht zusammen. Hardware - OS - node
-
@thomas-braun Hi Thomas!
Hier der Output von "iob diag":
Static hostname: iobroker Icon name: computer Operating System: Raspbian GNU/Linux 11 (bullseye) Kernel: Linux 5.15.84-v7l+ Architecture: arm Installation: native Kernel: armv7l Userland: 32 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 21 This system needs to be REBOOTED NOW! Nodejs-Installation: /usr/bin/nodejs v20.16.0 /usr/bin/node v20.16.0 /usr/bin/npm 10.8.1 /usr/bin/npx 10.8.1 /usr/bin/corepack 0.28.2 Recommended versions are nodejs 18.20.4 and npm 10.7.0 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.8G 2.6G 469M 0.0K 750M 1.4G Swap: 99M 62M 37M Total: 3.9G 2.7G 507M Active iob-Instances: 40 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.13.16 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : iobroker - disabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.web.1 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 23561 States: 17976 Size of iob-Database: 31M /opt/iobroker/iobroker-data/objects.jsonl 81M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================pi@iobroker:~ $ cd /opt/iobroker pi@iobroker:/opt/iobroker $ npm ls @iobroker/adapter-core iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.accuweather@1.3.2 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.admin@6.13.16 │ ├── @iobroker/adapter-core@3.0.4 │ └─┬ @iobroker/socket-classes@1.5.0 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.airconwithme@0.0.4 │ └── @iobroker/adapter-core@2.6.8 ├─┬ iobroker.alexa2@3.26.5 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.backitup@2.11.0 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.bmw@2.5.7 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.chromecast@3.0.3 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.cloud@5.0.1 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.daswetter@3.1.13 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.discovery@4.5.0 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.dwd@2.8.5 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.feiertage@1.1.4 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.firetv@2.0.2 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.fritzdect@2.5.9 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.fullybrowser@2.1.2 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.history@3.0.1 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.homeconnect@1.3.0 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.ical@1.13.3 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.influxdb@4.0.2 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.info@2.0.0 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.iot@3.3.0 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.jarvis@3.1.8 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.javascript@7.1.6 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.linux-control@1.1.5 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.meross@1.17.0 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.mqtt@5.2.0 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.net-tools@0.2.0 │ └── @iobroker/adapter-core@2.6.0 ├─┬ iobroker.netatmo-crawler@0.8.1 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.nina@0.0.25 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.panasonic-viera@2.0.0 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.pi-hole@1.3.6 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.ping@1.6.2 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.pushover@3.0.6 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.ring@3.2.2 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.rpi2@1.3.2 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.samsung@0.5.11 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.scenes@3.0.4 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.shelly@6.6.1 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.simple-api@2.8.0 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.socketio@6.7.0 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.spotify-premium@1.3.1 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.tankerkoenig@2.1.1 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.telegram@3.0.1 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.tr-064@4.3.0 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.trashschedule@2.3.0 │ └── @iobroker/adapter-core@3.0.4 ├─┬ iobroker.tuya@3.15.0 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.vaillant@0.1.2 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.vis-timeandweather@1.2.2 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.vis@1.5.6 │ └── @iobroker/adapter-core@3.1.6 ├─┬ iobroker.web@6.2.5 │ ├── @iobroker/adapter-core@3.1.6 │ ├─┬ iobroker.socketio@6.6.1 │ │ └── @iobroker/adapter-core@3.1.6 deduped │ └─┬ iobroker.ws@2.5.11 │ └── @iobroker/adapter-core@3.1.6 deduped ├─┬ iobroker.windows-control@0.1.5 │ └── @iobroker/adapter-core@2.6.8 deduped ├─┬ iobroker.worx@2.3.4 │ └── @iobroker/adapter-core@3.0.4 └─┬ iobroker.ws@2.6.1 └── @iobroker/adapter-core@3.1.6Und das war der Output vom zweiten Befehl
-
@mojo1985 sagte in Fenecon/OpenEMS Adapter:
This system needs to be REBOOTED NOW!
@mojo1985 sagte in Fenecon/OpenEMS Adapter:
Hier der Output von "iob diag":
leider nicht die Langfassung!
