Modbus-Adapter -> Fronius-WR Schreibfehler

diwoma

Hi,
zum zweiten Mal habe ich bei meiner Verbindung zum Fronius ein Problem gehabt, dass unangenehm ist :(.
Adapterversion: v7.0.4

Zur Erklärung: Ich lade meine Batterie zum Zeitpunkt des günstigen Preises auf. Dafür habe ich ein Skript geschrieben, dass das macht, und es funktioniert auch, ausser es kommt zu Verbindungsproblemen.
Dafür wird minütlich kontrolliert, ob eine Änderung notwendig ist.

Mein Log für ein normales Setting:

2025-10-16 02:00:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T02:00:00+02:00","endTime":"2025-10-16T03:00:00+02:00","price":9.69,"unit":"ct/kWh","isActive":true,"value":3500,"isDirty":false,"dateKey":"2025-10-16 02:00:00","day":"2025-10-16","hour":2,"preisBrutto":11.627999999999998,"preisGesamt":13.067999999999998}
2025-10-16 02:00:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 02:00:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100
2025-10-16 02:00:00.006 - info: javascript.0 (318) script.js.Batterie_Load_Control: $BLC: Actual SOC (41) less than Min-SOC (70) or calcActive == false): start Charging
2025-10-16 02:00:00.006 - info: javascript.0 (318) script.js.Batterie_Load_Control: $BLC: Activating with Value: 34.18 % / 3500 W

2025-10-16 02:01:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T02:00:00+02:00","endTime":"2025-10-16T03:00:00+02:00","price":9.69,"unit":"ct/kWh","isActive":true,"value":3500,"isDirty":false,"dateKey":"2025-10-16 02:00:00","day":"2025-10-16","hour":2,"preisBrutto":11.627999999999998,"preisGesamt":13.067999999999998}
2025-10-16 02:01:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 02:01:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 3 - Value = -34.18

Im ersten Block wird erkannt, dass eine Ladung zu erfolgen hat und die Daten werden geschrieben, erkennbar, dass die Daten im 2. Block eine Minute später gesetzt sind.

Dann kommt der Fehler (warum auch immer):
Der Wert, den ich schreiben will, ist nicht illegal, sonst würde es nie funktionieren

2025-10-16 03:00:00.008 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T03:00:00+02:00","endTime":"2025-10-16T04:00:00+02:00","price":9.97,"unit":"ct/kWh","isActive":true,"value":1000,"isDirty":false,"dateKey":"2025-10-16 03:00:00","day":"2025-10-16","hour":3,"preisBrutto":11.964,"preisGesamt":13.404}
2025-10-16 03:00:00.008 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 03:00:00.008 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 3 - Value = -34.18
2025-10-16 03:00:00.008 - info: javascript.0 (318) script.js.Batterie_Load_Control: $BLC: Changing Value to: 9.77 % / 1000 W
2025-10-16 03:00:00.053 - warn: modbus.0 (29938) Can not write value 977: Error: ILLEGAL DATA VALUE
2025-10-16 03:00:00.063 - info: modbus.0 (29938) Disconnected from slave 192.168.1.102
2025-10-16 03:00:00.085 - error: modbus.0 (29938) Socket Error Error [ERR_STREAM_WRITE_AFTER_END]: write after end
2025-10-16 03:00:00.085 - error: modbus.0 (29938) Client in error state.
2025-10-16 03:00:00.085 - warn: modbus.0 (29938) On error: {"code":"ERR_STREAM_WRITE_AFTER_END"}
2025-10-16 03:00:01.067 - info: modbus.0 (29938) Connected to slave 192.168.1.102
2025-10-16 03:00:01.085 - info: modbus.0 (29938) Disconnected from slave 192.168.1.102
2025-10-16 03:00:31.088 - info: modbus.0 (29938) Connected to slave 192.168.1.102

2025-10-16 03:01:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T03:00:00+02:00","endTime":"2025-10-16T04:00:00+02:00","price":9.97,"unit":"ct/kWh","isActive":true,"value":1000,"isDirty":false,"dateKey":"2025-10-16 03:00:00","day":"2025-10-16","hour":3,"preisBrutto":11.964,"preisGesamt":13.404}
2025-10-16 03:01:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 03:01:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 3 - Value = -34.18
2025-10-16 03:01:00.006 - info: javascript.0 (318) script.js.Batterie_Load_Control: $BLC: Changing Value to: 9.77 % / 1000 W

2025-10-16 03:02:00.006 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T03:00:00+02:00","endTime":"2025-10-16T04:00:00+02:00","price":9.97,"unit":"ct/kWh","isActive":true,"value":1000,"isDirty":false,"dateKey":"2025-10-16 03:00:00","day":"2025-10-16","hour":3,"preisBrutto":11.964,"preisGesamt":13.404}
2025-10-16 03:02:00.007 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 03:02:00.007 - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 3 - Value = -34.18

In Block 1 wird erkannt, dass die Ladeleistung geändert werden soll und beim Schreiben auf den WR kommt der Fehler. Die Daten werden auf die Datenpunkte geschrieben, das kann man nur sehen, wenn man davor sitzt, nicht im Log. Der Fehler tritt sporadisch auf, wie geschrieben, sehe ich es jetzt erst das zweite Mal.
Nach dem Verbindungs-Fehler werden die alten Daten aus dem Fronius wieder auf die Datenpunkte geschrieben, zu sehen im 2. Block. Und wieder versuche ich die Daten zu ändern, aber sie werden nicht an den Fronius übertragen und es kommt auch keine Fehlermeldung mehr.

Das funktioniert erst wieder wenn ich den Adapter neu starte.

Ob da mit diesen sproadisch auftretenden Fehler eine Analyse für den Adapter gemacht werden kann,weiss ich nicht. Aber ich hätte eine Lösung für mein Skript.

Ich prüfe, jedesmal beim Start des Cron-Jobs, ob die Daten gleich sind, wie beim letzten Write sein sollten. Passt das nicht, starte ich den Adapter einfach neu. Innerhalb der Minute wird er sich schon erfangen haben.

Dafür bräuchte ich Hilfe:
Wie kann ich abfragen, ob der Adapter gestartet und ready ist (wäre sowieso interessant)?
Wie kann ich den Adapter restarten?

mcm1957

Bitte das Template nicht löschen sondern ausfüllen:

Bitte in der nachfolgenden Übersicht die mit ... bzw x gekennzeichneten Felder ausfüllen und im Anschluss an die Tabelle auf Linux Systemen den Output des Commands iob diag einfügen.

Hinweis: Das Eröffnen eines Issues hier ersetzt NICHT das Anlegen eine Issues im Repository des Adapters. Fehlerbehebungen werden ausschließlich über Issues getrackt.

DANKE

Bitte ausfüllen:

Adaptername: ...
Link zu Adapterrepository: www.github.com...
Adapterversion: ...
js-controller Version: ...
Admin Version: ...
Hardwaresystem: NUC, Pi4 ...
Arbeitsspeicher: ...xGB
Festplattenart: SD-Karte, SSD, HDD, ...
Betriebssystem: ...
Nodejs-Version: ...
NPM-Version: ...
Installationsart: Skript oder Manuell ?
Image, Docker genutzt: Ja - Nein
Ort, Name der Imagedatei: ...

Linux User bitte hier den Output von iob diag einfügen.Bitte in der nachfolgenden Übersicht die mit ... bzw x gekennzeichneten Felder ausfüllen und im Anschluss an die Tabelle auf Linux Systemen den Output des Commands iob diag einfügen.

Hinweis: Das Eröffnen eines Issues hier ersetzt NICHT das Anlegen eine Issues im Repository des Adapters. Fehlerbehebungen werden ausschließlich über Issues getrackt.

DANKE

diwoma

@mcm1957 sagte in Modbus-Adapter -> Fronius-WR Schreibfehler:

Bitte ausfüllen:

Adaptername: ModBus
Link zu Adapterrepository: www.github.com...
Adapterversion: 7.0.4
js-controller Version: 8.9.2
Admin Version: 7.7.3
Hardwaresystem: MinisForum, Proxmox, LXC
Arbeitsspeicher: 32GB Gesamt, 4GB ioBroker
Festplattenart: SSD
Betriebssystem: Proxmox, LXC
Nodejs-Version: 20.19.1
NPM-Version: 10.8.2
Installationsart: Skript
Image, Docker genutzt: Nein
Ort, Name der Imagedatei: ...

Bezüglich Adapterrepository-Link: Keine Ahnung
Durch das Adapter-Update braucht man keinen Link zum Repository (ist ja auch verpönt und nur auf Zuruf davon zu installieren). Dadurch gibt es keine Angabe zum Repository, nicht ein mal in der Hilfe dazu.

Aber ich sehe gerade, dass ich auf eine Version 7.0.5 updaten kann, was aber mit meinem Problem laut Änderungslog nichts zu tun hat.

Script v.2025-08-09

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 11 (bullseye)
   Static hostname: ioBroker-dev
         Icon name: computer-container
           Chassis: container
    Virtualization: lxc
            Kernel: Linux 6.8.12-13-pve
      Architecture: x86-64
OS is similar to:

model name      : AMD Ryzen 9 6900HX with Radeon Graphics
Docker          : false
Virtualization  : lxc
Kernel          : x86_64
Userland        : 64 bit

Systemuptime and Load:
 10:01:02 up 41 days,  1:44,  1 user,  load average: 2.84, 2.65, 2.58
CPU threads: 2


*** LIFE CYCLE STATUS ***
Unknown release codenamed 'bullseye'. Please check yourself if the Operating System is actively maintained.

*** TIME AND TIMEZONES ***
               Local time: Thu 2025-10-16 10:01:02 CEST
           Universal time: Thu 2025-10-16 08:01:02 UTC
                 RTC time: n/a
                Time zone: Europe/Vienna (CEST, +0200)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
maier
HOME=/home/maier
GROUPS=maier sudo iobroker

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev

*** DISPLAY-SERVER SETUP ***
Display-Server:         false
Unit display-manager.service could not be found.
Display-Manager:
Desktop:
Session:                tty

System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix'

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            4.1G        974M        2.7G        0.0K        385M        3.1G
Swap:           512M        379M        132M
Total:          4.6G        1.4G        2.9G

Active iob-Instances:   11

         4096 M total memory
          974 M used memory
          702 M active memory
          576 M inactive memory
         2735 M free memory
            0 M buffer memory
          385 M swap cache
          512 M total swap
          379 M used swap
          132 M free swap

*** top - Table Of Processes  ***
top - 10:01:02 up 41 days,  1:44,  1 user,  load average: 2.84, 2.65, 2.58
Tasks:  60 total,   1 running,  59 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  3.2 sy,  0.0 ni, 96.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   4096.0 total,   2735.6 free,    974.8 used,    385.6 buff/cache
MiB Swap:    512.0 total,    132.7 free,    379.3 used.   3121.1 avail Mem

*** FAILED SERVICES ***

  UNIT                          LOAD   ACTIVE SUB    DESCRIPTION
* run-rpc_pipefs.mount          loaded failed failed RPC Pipe File System
* sys-kernel-config.mount       loaded failed failed Kernel Configuration File System
* systemd-journald-audit.socket loaded failed failed Journal Audit Socket

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
3 loaded units listed.


*** DMESG CRITICAL ERRORS ***
dmesg: read kernel buffer failed: Operation not permitted
No critical errors detected

*** FILESYSTEM ***
Filesystem                        Type      Size  Used Avail Use% Mounted on
/dev/mapper/pve-vm--1110--disk--0 ext4       12G  7.9G  3.4G  71% /
none                              tmpfs     492K  4.0K  488K   1% /dev
udev                              devtmpfs   15G     0   15G   0% /dev/tty
tmpfs                             tmpfs      15G     0   15G   0% /dev/shm
tmpfs                             tmpfs     5.9G  132K  5.9G   1% /run
tmpfs                             tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs                             tmpfs     3.0G     0  3.0G   0% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
dmesg: read kernel buffer failed: Operation not permitted

Show mounted filesystems:
TARGET SOURCE                            FSTYPE OPTIONS
/      /dev/mapper/pve-vm--1110--disk--0 ext4   rw,relatime,stripe=16

Files in neuralgic directories:

/var:
1.2G    /var/
669M    /var/log
668M    /var/log/journal
656M    /var/log/journal/9405646338474ae0a2ae2622e9e1d993
318M    /var/cache

Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal' can see all messages.
      Pass -q to turn off this notice.
Archived and active journals take up 114.4M in the file system.

/opt/iobroker/backups:
56M     /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
238M    /opt/iobroker/iobroker-data/
137M    /opt/iobroker/iobroker-data/files
77M     /opt/iobroker/iobroker-data/backup-objects
47M     /opt/iobroker/iobroker-data/files/admin.admin
46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets

The five largest files in iobroker-data are:
20M     /opt/iobroker/iobroker-data/objects.jsonl
8.1M    /opt/iobroker/iobroker-data/files/modbus.admin/assets/index-AZj-felF.js
8.1M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-DDMXSE9w.js
5.0M    /opt/iobroker/iobroker-data/states.jsonl
4.6M    /opt/iobroker/iobroker-data/files/javascript.admin/vs/language/typescript/tsWorker.js

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

No Devices found 'by-id'

Zigbee Network Settings on your coordinator/in nvbackup are:

zigbee.X
Extended Pan ID:
*** MASKED ***
Pan ID:
*** MASKED ***
Channel:
*** MASKED ***
Network Key:
*** MASKED ***

To unmask the settings run 'iob diag --unmask'


*** NodeJS-Installation ***

/usr/bin/nodejs         v20.19.1
/usr/bin/node           v20.19.1
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.31.0

nodejs:
  Installed: 20.19.1-1nodesource1
  Candidate: 20.19.5-1nodesource1
  Version table:
     20.19.5-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.19.4-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.19.3-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.19.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
 *** 20.19.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
        100 /var/lib/dpkg/status
     20.19.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.18.3-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.18.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.18.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.12.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.12.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.11.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.8.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.6.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.3.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     20.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
     12.22.12~dfsg-1~deb11u7 500
        500 http://security.debian.org bullseye-security/main amd64 Packages
     12.22.12~dfsg-1~deb11u4 500
        500 http://ftp.debian.org/debian bullseye/main amd64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

Checking for nodejs vulnerability:


██████   █████  ███    ██  ██████  ███████ ███████
██   ██ ██   ██ ████   ██ ██       ██      ██   ██
██   ██ ███████ ██ ██  ██ ██   ███ █████   ███████
██   ██ ██   ██ ██  ██ ██ ██    ██ ██      ██   ██
██████  ██   ██ ██   ████  ██████  ███████ ██   ██


The current Node.js version (v20.19.1) is vulnerable to the following CVEs:

CVE-2025-23166(high):  The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background thread, crashing the Node.js process. Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism potentially allows an adversary to remotely crash a Node.js runtime.
Patched versions: ^20.19.2 || ^22.15.1 || ^23.11.1 || ^24.0.2
=

CVE-2025-23167(medium): A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`.
This inconsistency enables request smuggling, allowing attackers to bypass proxy-based access controls and submit unauthorized requests.

The issue was resolved by upgrading `llhttp` to version 9, which enforces correct header termination.

Impact:
* This vulnerability affects only Node.js 20.x users prior to the `llhttp` v9 upgrade.

Patched versions: ^20.19.2
=

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
ioBroker-dev        ioBroker-dev (version: 7.0.7, hostname: ioBroker-dev  , alive, uptime: 3548668)

Core adapters versions
js-controller:  7.0.7
admin:          7.7.3
javascript:     8.9.2

nodejs modules from github:     0

Adapter State
+ system.adapter.admin.0                  : admin                 : ioBroker-dev                             -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.alias-manager.0          : alias-manager         : ioBroker-dev                             -  enabled
+ system.adapter.backitup.0               : backitup              : ioBroker-dev                             -  enabled
  system.adapter.bwt.0                    : bwt                   : ioBroker-dev                             - disabled
  system.adapter.discord.0                : discord               : ioBroker-dev                             - disabled
+ system.adapter.discovery.0              : discovery             : ioBroker-dev                             -  enabled
  system.adapter.fronius.0                : fronius               : ioBroker-dev                             - disabled
  system.adapter.icons-mfd-svg.0          : icons-mfd-svg         : ioBroker-dev                             -  enabled
+ system.adapter.influxdb.0               : influxdb              : ioBroker-dev                             -  enabled, port: 8086
+ system.adapter.javascript.0             : javascript            : ioBroker-dev                             -  enabled
+ system.adapter.modbus.0                 : modbus                : ioBroker-dev                             -  enabled
+ system.adapter.mqtt.0                   : mqtt                  : ioBroker-dev                             -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.puppeteer.0              : puppeteer             : ioBroker-dev                             -  enabled
+ system.adapter.shelly.0                 : shelly                : ioBroker-dev                             -  enabled, port: 1882, bind: 0.0.0.0
  system.adapter.vis-jqui-mfd.0           : vis-jqui-mfd          : ioBroker-dev                             -  enabled
  system.adapter.vis.0                    : vis                   : ioBroker-dev                             -  enabled
+ system.adapter.web.0                    : web                   : ioBroker-dev                             -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : ioBroker-dev                             -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.influxdb.0               : influxdb              : ioBroker-dev                             -  enabled, port: 8086
+ system.adapter.mqtt.0                   : mqtt                  : ioBroker-dev                             -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.shelly.0                 : shelly                : ioBroker-dev                             -  enabled, port: 1882, bind: 0.0.0.0
+ system.adapter.web.0                    : web                   : ioBroker-dev                             -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

ioBroker-Repositories
┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
│ (index) │ name     │ url                                                     │ auto upgrade │
├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
│ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
│ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
└─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘

Active repo(s): beta
Upgrade policy: none

Installed ioBroker-Adapters
Used repository: beta
Adapter    "admin"        : 7.7.3    , installed 7.7.3
Adapter    "alias-manager": 2.0.0    , installed 2.0.0
Adapter    "backitup"     : 3.3.9    , installed 3.3.9
Adapter    "bwt"          : 0.1.1    , installed 0.1.1
Adapter    "discord"      : 2.5.2    , installed 2.5.2
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Adapter    "fronius"      : 2.1.1    , installed 2.1.1
Adapter    "icons-mfd-svg": 1.2.0    , installed 1.2.0
Adapter    "influxdb"     : 4.0.2    , installed 4.0.2
Adapter    "javascript"   : 9.0.11   , installed 8.9.2  [Updatable]
Controller "js-controller": 7.0.7    , installed 7.0.7
Adapter    "modbus"       : 7.0.5    , installed 7.0.4  [Updatable]
Adapter    "mqtt"         : 6.1.4    , installed 6.1.4
Adapter    "puppeteer"    : 0.4.0    , installed 0.4.0
Adapter    "shelly"       : 10.4.0   , installed 10.3.0 [Updatable]
Adapter    "simple-api"   : 3.0.7    , installed 3.0.7
Adapter    "socketio"     : 7.0.8    , installed 7.0.8
Adapter    "vis"          : 1.5.6    , installed 1.5.6
Adapter    "vis-jqui-mfd" : 1.1.1    , installed 1.1.1
Adapter    "web"          : 7.0.9    , installed 7.0.9
Adapter    "ws"           : 3.0.19   , installed 3.0.19

Objects and States
Please stand by - This may take a while
Objects:        1566
States:         1239

*** OS-Repositories and Updates ***
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.debian.org/debian bullseye InRelease
Hit:3 http://ftp.debian.org/debian bullseye-updates InRelease
Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease
Reading package lists...
Pending Updates: 1

*** Listening Ports ***
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      0          28558      292/master
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          14298      160/sshd: /usr/sbin
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          14030      1/init
tcp        0      0 127.0.0.1:40097         0.0.0.0:*               LISTEN      1001       68617      448/chrome
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       40184      127/iobroker.js-con
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       39064      127/iobroker.js-con
tcp6       0      0 :::22                   :::*                    LISTEN      0          14300      160/sshd: /usr/sbin
tcp6       0      0 :::111                  :::*                    LISTEN      0          14032      1/init
tcp6       0      0 ::1:25                  :::*                    LISTEN      0          28559      292/master
tcp6       0      0 :::8082                 :::*                    LISTEN      1001       70076      568/io.web.0
tcp6       0      0 :::8081                 :::*                    LISTEN      1001       274021913  22581/io.admin.0
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          14131      76/dhclient
udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          14031      1/init
udp        0      0 0.0.0.0:5683            0.0.0.0:*                           1001       330442401  28210/io.shelly.0
udp6       0      0 :::111                  :::*                                0          14033      1/init

*** Log File - Last 25 Lines ***

2025-10-16 09:53:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100
2025-10-16 09:54:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T09:00:00+02:00","endTime":"2025-10-16T10:00:00+02:00","price":12.1,"unit":"ct/kWh","isActive":false,"value":0,"isDirty":false,"dateKey":"2025-10-16 09:00:00","day":"2025-10-16","hour":9,"preisBrutto":14.52,"preisGesamt":15.959999999999999}
2025-10-16 09:54:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 09:54:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100
2025-10-16 09:55:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T09:00:00+02:00","endTime":"2025-10-16T10:00:00+02:00","price":12.1,"unit":"ct/kWh","isActive":false,"value":0,"isDirty":false,"dateKey":"2025-10-16 09:00:00","day":"2025-10-16","hour":9,"preisBrutto":14.52,"preisGesamt":15.959999999999999}
2025-10-16 09:55:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 09:55:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100
2025-10-16 09:56:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T09:00:00+02:00","endTime":"2025-10-16T10:00:00+02:00","price":12.1,"unit":"ct/kWh","isActive":false,"value":0,"isDirty":false,"dateKey":"2025-10-16 09:00:00","day":"2025-10-16","hour":9,"preisBrutto":14.52,"preisGesamt":15.959999999999999}
2025-10-16 09:56:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 09:56:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100
2025-10-16 09:57:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T09:00:00+02:00","endTime":"2025-10-16T10:00:00+02:00","price":12.1,"unit":"ct/kWh","isActive":false,"value":0,"isDirty":false,"dateKey":"2025-10-16 09:00:00","day":"2025-10-16","hour":9,"preisBrutto":14.52,"preisGesamt":15.959999999999999}
2025-10-16 09:57:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 09:57:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100
2025-10-16 09:58:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T09:00:00+02:00","endTime":"2025-10-16T10:00:00+02:00","price":12.1,"unit":"ct/kWh","isActive":false,"value":0,"isDirty":false,"dateKey":"2025-10-16 09:00:00","day":"2025-10-16","hour":9,"preisBrutto":14.52,"preisGesamt":15.959999999999999}
2025-10-16 09:58:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 09:58:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100
2025-10-16 09:59:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T09:00:00+02:00","endTime":"2025-10-16T10:00:00+02:00","price":12.1,"unit":"ct/kWh","isActive":false,"value":0,"isDirty":false,"dateKey":"2025-10-16 09:00:00","day":"2025-10-16","hour":9,"preisBrutto":14.52,"preisGesamt":15.959999999999999}
2025-10-16 09:59:00.008  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 09:59:00.008  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100
2025-10-16 10:00:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T10:00:00+02:00","endTime":"2025-10-16T11:00:00+02:00","price":9.64,"unit":"ct/kWh","isActive":false,"value":0,"isDirty":false,"dateKey":"2025-10-16 10:00:00","day":"2025-10-16","hour":10,"preisBrutto":11.568,"preisGesamt":13.008}
2025-10-16 10:00:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 10:00:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100
2025-10-16 10:01:00.006  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Antwort: {"calculationConfiguration":{"calculationType":2,"socMin":70,"socMax":80,"calcActive":false,"loadStepping":true},"startTime":"2025-10-16T10:00:00+02:00","endTime":"2025-10-16T11:00:00+02:00","price":9.64,"unit":"ct/kWh","isActive":false,"value":0,"isDirty":false,"dateKey":"2025-10-16 10:00:00","day":"2025-10-16","hour":10,"preisBrutto":11.568,"preisGesamt":13.008}
2025-10-16 10:01:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Controlling!
2025-10-16 10:01:00.007  - debug: javascript.0 (318) script.js.Batterie_Load_Control: BLC: Current values: Control = 0 - Value = 100

Es ist nur mein DEV-IoBroker zum testen. Aber ich habe gesehen, dass ich mit den BS-Updates etwas zurückgeblieben bin.
Bevor ich auf mein Produktiv-System wechsle, würde ich gerne die Möglichkeit mit dem Restart ausprobieren.

Und Sorry, ich wusste nicht, dass ich so ein Template vielleicht schon zu Anfang hätte ausfüllen müssen.

NEWS

Modbus-Adapter -> Fronius-WR Schreibfehler

Support us

1.0k
Online

32.3k
Users

81.0k
Topics

1.3m
Posts

NEWS

Modbus-Adapter -> Fronius-WR Schreibfehler

Support us

1.0kOnline

32.3kUsers

81.0kTopics

1.3mPosts

1.0k
Online

32.3k
Users

81.0k
Topics

1.3m
Posts