Community Forum

[image: 1772715273352-2026_03_04-resized.jpg] ioBroker Monatsrückblick Januar/Februar 2026 ist online! Das Jahr startet mit vielen neuen Adaptern. Einige noch in latest (bitte testen!), andere schon stable. Außerdem wichtig für alle Z-Wave-Nutzer: zwave2 wurde entfernt, der neue Weg heißt zwavews. Neue Adapter in latest (Tester gesucht!) 🌩️ ioBroker.hagelschutz-vkf (Wetter / Gebäudeschutz) – VKF-Hagelwarnungen (Schweiz) für automatisches Einfahren von Markisen/Rollläden. ☀️ ioBroker.foxesscloud (Energie / Solar) – Echtzeitdaten aus der FoxESS-Cloud (auch Enpal): PV, Netz, Einspeisung, SOC & Batterie. 🔌 ioBroker.apsystems-ez1 (Energie / Solar) – APsystems EZ1 lokal via HTTP: Leistung/Energie, Alarme, MaxPower setzen, Ein/Aus, inkl. VIS2-Widget. 📈 ioBroker.solectrus-influxdb (Energie / Datenbank) – States nach InfluxDB 2.x + Formel-Engine & stabiler Puffer (ideal fürs Energiemonitoring). 🚰 ioBroker.grohe-smarthome (Metering / Wasser) – Grohe/Ondus: Sense, Sense Guard, Blue inkl. Leckage/Alarmen & Ventilsteuerung. Neue Adapter in stable 🌦️ ioBroker.meteoswiss (Wetter) – MeteoSchweiz ohne API-Key: Prognosen & Unwetterwarnungen. 📡 ioBroker.serial-gps (Utility) – GPS-Maus per USB/seriell: Tracking, Geofence & Standort-Automationen. 🎯 ioBroker.autodarts (Unterhaltung / Smart Home) – Autodarts lokal: Würfe/Events als Trigger für Licht, Sound, TTS & Statistiken. 🔁 ioBroker.zwavews (Protokolle / Smart Home) – moderner Nachfolger von zwave2: Z-Wave über zwave-js-ui per WebSocket, inkl. Migration. ❄️ ioBroker.mitsubishi-local-control (Klimasteuerung) – Mitsubishi Klima lokal steuern (Modus, Temp, Lüfter, Lamellen). 🏠 ioBroker.smartfriends (IoT-Systeme / Smart Home) – SmartFriends Box lokal integrieren (Rollläden, Licht & mehr). ⚠️ Wichtig: zwave2 entfernt (Februar 2026) → bitte auf zwavews migrieren. 👉 Blog lesen: https://www.iobroker.net/#de/blog/2026_03_04 💙 Unterstützung fürs Open-Source-Projekt: https://www.paypal.com/donate?campaign_id=MJBDJ9TGBQ7GN

@tombox sagte: Teste mal v0.3.0 Bei mir startet der Adapter leider nicht mehr mit v0.3.0 Instanz, Objektbaum und Adapter auch mal vorher vollständig gelöscht. Aber leider das gleiche Ergebnis 2026-04-06 08:05:46.915 - info: host.iobroker iobroker add parcel --host iobroker 2026-04-06 08:05:47.414 - info: host.iobroker iobroker host.iobroker create instance parcel 2026-04-06 08:05:47.419 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.alive created 2026-04-06 08:05:47.427 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.connected created 2026-04-06 08:05:47.430 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.compactMode created 2026-04-06 08:05:47.432 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.cpu created 2026-04-06 08:05:47.434 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.cputime created 2026-04-06 08:05:47.436 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.memHeapUsed created 2026-04-06 08:05:47.438 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.memHeapTotal created 2026-04-06 08:05:47.440 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.memRss created 2026-04-06 08:05:47.443 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.uptime created 2026-04-06 08:05:47.445 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.inputCount created 2026-04-06 08:05:47.447 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.outputCount created 2026-04-06 08:05:47.448 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.eventLoopLag created 2026-04-06 08:05:47.450 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.sigKill created 2026-04-06 08:05:47.452 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0.logLevel created 2026-04-06 08:05:47.453 - info: host.iobroker iobroker host.iobroker object parcel.0.info created 2026-04-06 08:05:47.455 - info: host.iobroker iobroker host.iobroker object parcel.0.allProviderJson created 2026-04-06 08:05:47.456 - info: host.iobroker iobroker host.iobroker object parcel.0.allProviderObjects created 2026-04-06 08:05:47.458 - info: host.iobroker iobroker host.iobroker object parcel.0.notDelivered created 2026-04-06 08:05:47.462 - info: host.iobroker iobroker host.iobroker object parcel.0.notDeliveredCount created 2026-04-06 08:05:47.464 - info: host.iobroker iobroker host.iobroker object parcel.0.inDelivery created 2026-04-06 08:05:47.469 - info: host.iobroker iobroker host.iobroker object parcel.0.inDeliveryCountJson created 2026-04-06 08:05:47.472 - info: host.iobroker iobroker host.iobroker object parcel.0.inDeliveryCount created 2026-04-06 08:05:47.474 - info: host.iobroker iobroker host.iobroker object parcel.0.auth created 2026-04-06 08:05:47.476 - info: host.iobroker iobroker host.iobroker object parcel.0.auth.cookie created 2026-04-06 08:05:47.477 - info: host.iobroker iobroker host.iobroker object parcel.0.info.connection created 2026-04-06 08:05:47.478 - info: host.iobroker iobroker host.iobroker object parcel.0.refresh created 2026-04-06 08:05:47.480 - info: host.iobroker iobroker host.iobroker Set default value of parcel.0.notDelivered: {} 2026-04-06 08:05:47.481 - info: host.iobroker iobroker host.iobroker Set default value of parcel.0.notDeliveredCount: 0 2026-04-06 08:05:47.482 - info: host.iobroker iobroker host.iobroker Set default value of parcel.0.inDeliveryCountJson: {} 2026-04-06 08:05:47.483 - info: host.iobroker iobroker host.iobroker Set default value of parcel.0.info.connection: false 2026-04-06 08:05:47.485 - info: host.iobroker iobroker host.iobroker Set default value of parcel.0.refresh: false 2026-04-06 08:05:47.488 - info: host.iobroker iobroker host.iobroker object system.adapter.parcel.0 created 2026-04-06 08:05:48.502 - info: host.iobroker iobroker exit 0 2026-04-06 08:05:50.004 - info: admin.0 (381) ==> Connected system.user.admin from ::ffff:192.168.2.130 2026-04-06 08:05:50.806 - info: host.iobroker instance system.adapter.parcel.0 in version "0.3.0" started with pid 405645 2026-04-06 08:05:51.526 - error: host.iobroker Caught by controller[0]: node:internal/modules/esm/module_job:450 2026-04-06 08:05:51.526 - error: host.iobroker Caught by controller[0]: throw new ERR_REQUIRE_ASYNC_MODULE(filename, parentFilename); 2026-04-06 08:05:51.526 - error: host.iobroker Caught by controller[0]: ^ 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: Error [ERR_REQUIRE_ASYNC_MODULE]: require() cannot be used on an ESM graph with top-level await. Use import() instead. To see where the top-level await comes from, use --experimental-print-required-tla. 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: From /opt/iobroker/node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: Requiring /opt/iobroker/node_modules/jsdom/node_modules/@asamuzakjp/dom-selector/src/index.js 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at ModuleJobSync.runSync (node:internal/modules/esm/module_job:450:13) 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:435:47) 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at loadESMFromCJS (node:internal/modules/cjs/loader:1537:24) 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1688:5) 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at Object..js (node:internal/modules/cjs/loader:1839:10) 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1441:32) 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at Function._load (node:internal/modules/cjs/loader:1263:12) 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at TracingChannel.traceSync (node:diagnostics_channel:328:14) 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1463:12) { 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: code: 'ERR_REQUIRE_ASYNC_MODULE' 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: } 2026-04-06 08:05:51.527 - error: host.iobroker Caught by controller[0]: Node.js v22.22.0 2026-04-06 08:05:51.527 - error: host.iobroker instance system.adapter.parcel.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2026-04-06 08:05:51.527 - info: host.iobroker Restart adapter system.adapter.parcel.0 because enabled

Follow here https://forum.iobroker.net/post/1332936

@hawkeye Thanks for clearification. I already assumed that goggle translation did not get the conplete context. As I cannot read rusky language, I'll write in english and hope translation is correct. For the technical facts: The maintainer of the adapter did not grant access to npm although request for a long time. So its technical impossible to move the adapter to iobroker-community-adapters. As no maintainance has been done for a long time the adapter has been removed from repositories. It ist still possible to install it directly from nom using url iobroker.megadd. BUT there is some news too. I just detected that there is an adapter iobroker.megadd2. This adapter has been archived too and is not published at repositories. But it has been written by @Bluefox which ist one ofe the active core developers. So maybe he can held - ans as far as I know he can communicate using rusky languge very well. @Bluefox Please respond if you have time to do so. Спасибо за разъяснения. Я уже предполагал, что перевод Google не передал весь контекст. Поскольку я не могу читать на русском языке, напишу на английском и надеюсь, что перевод будет верным. Технические факты: Разработчик адаптера долгое время не предоставлял доступ к npm, несмотря на запрос. Поэтому технически невозможно перенести адаптер в iobroker-community-adapters. Поскольку поддержка не производилась в течение длительного времени, адаптер был удалён из репозиториев. Его всё ещё можно установить напрямую из nom, используя URL iobroker.megadd. НО есть и новости. Я только что обнаружил, что существует адаптер iobroker.megadd2. Этот адаптер тоже заархивирован и не опубликован в репозиториях. Но его написал @Bluefox, один из активных разработчиков ядра. Так что, возможно, он сможет помочь — и, насколько мне известно, он очень хорошо умеет общаться на русском языке. @Bluefox Пожалуйста, ответьте, если у вас есть время.

@tanelkoth Ik zie dat je deze vraag hebt. Mocht je vraag nog actueel zijn, laat het even weten. Met behulp van een Blockly script kan je eenvoudig dit regelen.

@polegato Estou devolta aqui :-) ... O exemplo do lobomau é perfeito. Vc tem que instalar o ioBroker.javascript para isso e fazer um Blockly. Com esse Blockly vc pode montar automacao como um quebra cabeca. Muito legal e depois de algums, ja fica bem mais fácil.