js-controller 3.2 jetzt im Latest!
-
@crunchip ahhh meinst das Admin es komisch angezeigt hat. Am Ende gewinnt immer das logfile auf Platte
-
@apollon77 said in js-controller 3.2 jetzt im Latest!:
@ofbeqnpolkkl6mby5e13 es gibt manchmal seltene caching Fälle. Versuch „iobroker update“ nochmal
War ich wirklich gemeint?
-
@ilovegym said in js-controller 3.2 jetzt im Latest!:
@apollon77 3.2.7 - nothing to report.
dito...läuft
-
@apollon77 said in js-controller 3.2 jetzt im Latest!:
@crunchip ahhh meinst das Admin es komisch angezeigt hat. Am Ende gewinnt immer das logfile auf Platte
Diesen Effekt hatte ich vor 1 bis 2 Tagen auch einmal. Da ich kurz vorher was gefiltert hatte dachte ich es käme vom Filter. Nach einem F5 war alles wieder gut.
-
Ich habe lediglich drei Adapter mit Warnungen:
fullybrowser
hs100
proxmoxBei allen drei existiert ein Issue.
-
@apollon77 Bei mir war nach dem Update plötzlich der Terminaladapter auf aktiv geschaltet:
host.ioBroker 2021-01-17 10:51:18.887 info Restart adapter system.adapter.terminal.0 because enabled host.ioBroker 2021-01-17 10:51:18.886 error instance system.adapter.terminal.0 terminated with code 1 (JS_CONTROLLER_STOPPED) terminal.0 2021-01-17 10:51:18.712 error (23869) port 8081 already in use terminal.0 2021-01-17 10:51:18.392 info (23869) starting. Version 0.1.2 in /opt/iobroker/node_modules/iobroker.terminal, node: v12.20.1, js-controller: 3.2.7 host.ioBroker 2021-01-17 10:51:16.590 info instance system.adapter.terminal.0 started with pid 23869Nicht wichtig, da der nur mal vor langer Zeit für einen Sonderfall drauf war. Ich habe den jetzt deinstalliert.
-
Hallo,
upgrade hat funktioniert. Bin nun auf 3.2.7.
Für folgende Adapter habe ich Issues erstellt:- zwave
- husq-automower
- octoprint
Waren aber nur Warungen:
State "xxxxx" has no existing object, this might lead to an error in future versions -
@ilovegym said in js-controller 3.2 jetzt im Latest!:
@apollon77 3.2.7 - nothing to report.
bei mir genauso.
-
zwave2.0 Adapter läuft nicht mit dieser Version. Folgende Fehlermeldung wird ausgegeen wenn der Adapter gestartet wird. "Failed to load the configuration: config_1.loadDeviceClasses is not a function"
-
@noell Bitte vollständige Exception als issue im zwave adapter bitte melden!
-
@apollon77 Heute um 17.00 Uhr hat der DWD Adapter folgendes gemeldet:
2021-01-17 17:00:31.794 - info: dwd.0 (15026) starting. Version 2.6.1 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.18.3, js-controller: 3.2.7 2021-01-17 17:00:32.375 - info: dwd.0 (15026) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2021-01-17 17:00:32.974 - warn: dwd.0 (15026) get state Error: Connection is closed. 2021-01-17 17:00:32.979 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:32.980 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:32.981 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:32.982 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:32.986 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:32.991 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:32.993 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:32.994 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:32.997 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:32.998 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.001 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.002 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.004 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.005 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.007 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.008 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.009 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.015 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.016 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.017 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.018 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.018 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.019 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.020 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.027 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.028 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.028 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.029 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.029 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.030 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.031 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.032 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.032 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.033 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.039 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.039 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.040 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.041 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.042 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.042 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.047 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.048 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.049 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.049 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.050 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.050 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.056 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.056 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.057 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.058 - warn: dwd.0 (15026) get state Error: DB closed 2021-01-17 17:00:33.162 - info: host.beebox(iobrokerMaster) instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)Davor und danach war alles ruhig im Log.
-
@noell Also bei anderen tut es. Bitte am besten mal schauen und die aktuelle version von zwave2 neu installieren bzw updaten
-
@feuersturm ich schaue nochmal was da ist in dwd
-
@apollon77 Ja da scheint bei mir was anderes defekt zu sein, es liegt nicht an der 3.2.7. Der Adapter läuft jetzt nach der neu Installation.
-
Hi all
Bei mir läuft soweit auch alles "fast" nur der Vaillant Adapter hat was aus zu setzten seit dem, kann das mit dem Update zusammen hängen?host.Surface-3 2021-01-17 19:36:37.283 info instance system.adapter.vaillant.0 started with pid 59903 host.Surface-3 2021-01-17 19:36:07.226 info Restart adapter system.adapter.vaillant.0 because enabled host.Surface-3 2021-01-17 19:36:07.225 error instance system.adapter.vaillant.0 terminated with code 6 (UNCAUGHT_EXCEPTION) vaillant.0 2021-01-17 19:36:06.540 error (59709) The state contains no properties! At least one property is expected! vaillant.0 2021-01-17 19:36:06.540 error (59709) Error: The state contains no properties! At least one property is expected! at validateSetStateObjectArgument (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5783:23) vaillant.0 2021-01-17 19:36:06.536 error (59709) unhandled promise rejection: The state contains no properties! At least one property is expected! vaillant.0 2021-01-17 19:36:06.534 error (59709) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). -
@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 Du hast doch in dem anderen Threads schon gesagt bekommen, was zu tun ist bzw. was du ggf. falsch machst.
-
@tom-son Bitte beim Adapter ein Issue anlegen
-
@amg_666 Bitte beim Adapter ein Issue anlegen
-
@apollon77 3.2.7. läuft bei mir den ganzen Tag ohne Probleme. Ohne krumme Version klappt auch wieder das Adapter-Update
ioBroker als Container unter Proxmox kann ich nur empfehlen
