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

Im Debug sieht man das die erste Meldung direkt nach dem Login kommt und danach alle 60s ohne das Daten abgefragt werden, es werden Fahrzeugdaten gelesen und auch neu Werte ausgelesen. 2026-04-04 09:47:26.501 - info: vw-connect.0 (64061) Login successful 2026-04-04 09:47:26.796 - debug: vw-connect.0 (64061) get user data {xxxx... 2026-04-04 09:47:27.384 - debug: vw-connect.0 (64061) {"vehicles":[{xxxx... 2026-04-04 09:47:27.385 - info: vw-connect.0 (64061) Found 1 vehicles 2026-04-04 09:47:27.443 - debug: vw-connect.0 (64061) Connecting to MQTT 2026-04-04 09:47:27.684 - error: vw-connect.0 (64061) MQTT Error: ErrorWithReasonCode: Connection refused: Not authorized 2026-04-04 09:47:27.685 - error: vw-connect.0 (64061) MQTT Offline 2026-04-04 09:47:27.685 - info: vw-connect.0 (64061) MQTT Connection closed 2026-04-04 09:47:27.695 - debug: vw-connect.0 (64061) {"overall": xxxx 2026-04-04 09:47:27.695 - debug: vw-connect.0 (64061) xxxxxxx.status.vehicle-status 2026-04-04 09:47:27.695 - debug: vw-connect.0 (64061) 200 ..... Das sind die Meldungen die einen Fehlercode erzeugen, sonst ist der status 200 2026-04-04 09:47:35.509 - debug: vw-connect.0 (64061) air-conditioning /settings 2026-04-04 09:47:35.509 - debug: vw-connect.0 (64061) AxiosError: Request failed with status code 403 2026-04-04 09:47:35.509 - debug: vw-connect.0 (64061) "" 2026-04-04 09:47:35.509 - debug: vw-connect.0 (64061) "" 2026-04-04 09:47:35.579 - debug: vw-connect.0 (64061) charging /settings 2026-04-04 09:47:35.579 - debug: vw-connect.0 (64061) AxiosError: Request failed with status code 404 2026-04-04 09:47:35.579 - debug: vw-connect.0 (64061) {"timestamp":"2026-04-04T07:47:35.626+00:00","path":"/api/v1/charging/xxxxxxx/settings","status":404,"error":"Not Found","requestId":"313418a3-30342369"} 2026-04-04 09:47:35.579 - debug: vw-connect.0 (64061) Vehicle is not supporting charging /settings ..... 2026-04-04 09:47:36.761 - debug: vw-connect.0 (64061) fueling/sessions 2026-04-04 09:47:36.761 - debug: vw-connect.0 (64061) AxiosError: Request failed with status code 404 2026-04-04 09:47:36.761 - debug: vw-connect.0 (64061) "Resource not found" 2026-04-04 09:47:36.761 - debug: vw-connect.0 (64061) Vehicle is not supporting fueling/sessions 2026-04-04 09:47:36.862 - debug: vw-connect.0 (64061) fueling/sessions /state 2026-04-04 09:47:36.862 - debug: vw-connect.0 (64061) AxiosError: Request failed with status code 404 2026-04-04 09:47:36.862 - debug: vw-connect.0 (64061) "Resource not found" 2026-04-04 09:47:36.862 - debug: vw-connect.0 (64061) Vehicle is not supporting fueling/sessions /state 2026-04-04 09:47:36.972 - debug: vw-connect.0 (64061) fueling/locations 2026-04-04 09:47:36.972 - debug: vw-connect.0 (64061) AxiosError: Request failed with status code 500 2026-04-04 09:47:36.972 - debug: vw-connect.0 (64061) "Internal server error" 2026-04-04 09:47:36.972 - info: vw-connect.0 (64061) Server not available. For endpoint fueling/locations Please try again later:"Internal server error" 2026-04-04 09:47:37.051 - debug: vw-connect.0 (64061) fueling/sessions /latest 2026-04-04 09:47:37.051 - debug: vw-connect.0 (64061) AxiosError: Request failed with status code 404 2026-04-04 09:47:37.051 - debug: vw-connect.0 (64061) {"timestamp":"2026-04-04T07:47:37.097+00:00","path":"/api/v2/fueling/sessions/xxxxxxxxx/latest","status":404,"error":"Not Found","requestId":"e33165f1-30110497"} 2026-04-04 09:47:37.051 - debug: vw-connect.0 (64061) Vehicle is not supporting fueling/sessions /latest 2026-04-04 09:47:39.662 - debug: vw-connect.0 (64061) trip-statistics 2026-04-04 09:47:39.662 - debug: vw-connect.0 (64061) AxiosError: Request failed with status code 403 2026-04-04 09:47:39.662 - debug: vw-connect.0 (64061) "Not authorized" 2026-04-04 09:47:39.662 - debug: vw-connect.0 (64061) "Not authorized" 2026-04-04 09:47:39.899 - debug: vw-connect.0 (64061) trip-statistics 2026-04-04 09:47:39.899 - debug: vw-connect.0 (64061) AxiosError: Request failed with status code 403 2026-04-04 09:47:39.899 - debug: vw-connect.0 (64061) "Not authorized" 2026-04-04 09:47:39.900 - debug: vw-connect.0 (64061) "Not authorized" .... 2026-04-04 09:48:27.686 - info: vw-connect.0 (64061) MQTT Reconnecting with refreshed token 2026-04-04 09:48:27.910 - error: vw-connect.0 (64061) MQTT Error: ErrorWithReasonCode: Connection refused: Not authorized 2026-04-04 09:48:27.911 - info: vw-connect.0 (64061) MQTT Connection closed

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.