@haselchen Danke, ja, nach der ersten Einträge hatte ich das verworfen, du hast aer recht, ist der gleiche Fehler. Dann biete ich in dem anderen Tread mal an auf meinen System zu suchen wenn das hilft.

Hallo,
ich habe auch eine Consori Fritteuse gekauft, die App eingerichtet und dann den Adapter. Dis App funktioniert, der Adapter zeigt im LOG aber die gleiche Fehlermeldung wie bei FoxMulder & MacGyver.
Scheint evtl. bei allen neuen Einrichtungen zu passieren.
Liebe Grüße

@bertderkleine
Ja, stimmt, ich tast mich mal langsam ran und vielleicht hilft auch der Mittelweg. Erstmal habe ich dein Script heute zum laufen gebracht. Ich habe die Logik zwar noch nicht ganz verstande, aber ich taste mich mal ran.
Folgende Änderungen habe ich mal reingebracht:

1. Zwei weitere Datenpunkte:
   const NetzLaden = '0_userdata.0.Technik.Strom.Speicher.MSA-280024340941.NetzLadung';
   const Entladen = '0_userdata.0.Technik.Strom.Speicher.MSA-280024340941.Entladung';

Wenn der erste auf True ist, dann wird zwangsweise vom Netz geladen
Wenn der zweite auf True ist, dann wird der Akku entladen. Mit diesem kann ich in einem ersten Schritt das Entladen am Tage blockieren und die Entladung zu einem späteren Zeitpunkt starten (Wenn der Preis oben ist)

In einem anderen Script habe ich nun zB. die Idee, die Tibberpreiskurve auszuwerten und zB. 2h vor dem max Preis && nach 18:00Uhr die Entladung zu starten. In der Regel ist der Akku dann durch den Verbrauch am Abend bis 24:00 Uhr leer.

Den Code habe ich wie folgt angepasst. Wenn du magst, kannst du das natürlich übernehmen oder an eine bessere Stelle überführen.

Zusätzlich habe ich was eingebaut, dass der Ladestrom reduziert wird, wenn die obere Ladegrenze erreicht ist. Ich meine, dies beobachtet zu haben, dass Hoymiles selber reduziert wenn es an die obere Grenze geht.

Ich berichte von meinen weiteren Versuchen

@arteck
.. ja, gerne ein Beispiel... ich habe einen Datenpunkt der liefert im Sekundenbereich Telegramme von den Kollektoren, da möchte ich überhaupt nicht im Sekundenbereich Aktoren steuern sondern eher gleitend regeln. Zb. im Minutenbereich.. Bei PID Reglern wäre dies dann die einstellbare Delta-T Regelung.

Ich sehe mir im nächsten Schritt gerne das mit dem Node-JS upgrade an.. generell finde ich es aber interessant wie Diskussionen von der eigentlichen Fragestellung abdrifften ... denn dies war ja ... warum verhalten sich die Schedule Jobs beim Boot falsch.

@mcm57 Ich habe das dort als Issue auf deinen Rat hin aufgenommen, ich hoffe dies war vom Ablauf ok,

@thomas-braun Vielen Dank, ich probiere und melde mich, wird wahrscheinlich am Feiertag passieren. Danke euch allen.

@thomas-braun .. dann mache ich das morgen nochmals um den vollen Log zu kopieren. Wenn ich den Adapter löschen und neu installieren, verliere ich aber die komplette I2C config richtig? Das sind rund 40 Devices, gibt es eine einfache Möglichkeit die Config zu retten?

@hschief Nun habe ich mal getestet. Zwei einfache Fragen vorweg:

1. Muss/Kann ich den Beitrag in den deutschen Zweig verschieben oder macht dies ein Admin?
2. Wenn ich hier was gepostet habe, dann kann ich für n-Stunden keinen weiteren Beitrag schreiben. Ich erhalte dann immer Denied. Liegt dies daran, dass ich neu im Forum bin?

Nun zu dem Problem. Ich habe nochmals auf Node.JS umgestellt. Dies habe ich mit folgendem Befehl gemacht:
iob nodejs-update 22. Der Befehl: node-gyp ist weder unter node.js 20 noch unter 22 zu finden. Alle Aktivitäten führe ich als user: iobroker aus. Der i2c Adapter startet danach nicht (siehe auch log). Als Grund vermute ich, dass er die Datei: i2c.node nicht findet.
Im Log finde ich beim boot den folgenden Hinweis, der mit dem Problem evtl. in Zusammenhabg steht: "iobroker npm-rebuild: Rebuilding native modules failed". Dies ist im iob diag nicht zu finden, da der diag wohl nur die letzten 25 Zeilen aus dem Log holt.
Wenn ich mit dem Befehl iob nodejs-update 20 auf die node.js zurück gehen, dann ist i2c.node im filesystem zu finden und der Start des Adapters läuft Problemlos.

Nun meine Diag Ausgabe:

========== Start marking the full check here ===========

```bash
Script v.2025-08-09

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 12 (bookworm)
 Static hostname: node0
       Icon name: computer
          Kernel: Linux 6.12.47+rpt-rpi-v8
    Architecture: arm64
OS is similar to: 

Model		: Raspberry Pi 4 Model B Rev 1.4
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : 64 bit

Systemuptime and Load:
 11:51:02 up 3 min,  4 users,  load average: 2.79, 1.45, 0.57
CPU threads: 4


*** LIFE CYCLE STATUS ***
Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time!

*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
No throttling issues detected.

*** TIME AND TIMEZONES ***
               Local time: Tue 2025-09-30 11:51:02 CEST
           Universal time: Tue 2025-09-30 09:51:02 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c iotnodes

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

A default user should be created! This user will be enabled to temporarily switch to root via 'sudo'!
A root login is not required in most Linux Distributions.
Run 'iobroker fix' or use the system tools to create a user.
*** DISPLAY-SERVER SETUP ***
Display-Server: 	false
Unit display-manager.service could not be found.
Display-Manager: 	
Desktop: 		
Session: 		tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            8.2G        1.9G        5.5G         20M        890M        6.3G
Swap:           209M          0B        209M
Total:          8.4G        1.9G        5.7G

Active iob-Instances: 	19

         7819 M total memory
         1814 M used memory
         1957 M active memory
          425 M inactive memory
         5270 M free memory
           81 M buffer memory
          767 M swap cache
          199 M total swap
            0 M used swap
          199 M free swap

*** top - Table Of Processes  ***
top - 11:51:02 up 3 min,  4 users,  load average: 2.79, 1.45, 0.57
Tasks: 220 total,   1 running, 219 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us, 20.0 sy,  0.0 ni, 80.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem :   7819.8 total,   5269.7 free,   1815.0 used,    849.4 buff/cache     
MiB Swap:    200.0 total,    200.0 free,      0.0 used.   6004.9 avail Mem 

*** FAILED SERVICES ***

  UNIT          LOAD   ACTIVE SUB    DESCRIPTION
* snmpd.service loaded failed failed Simple Network Management Protocol (SNMP) Daemon.

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.
1 loaded units listed.


*** DMESG CRITICAL ERRORS ***
[sudo] password for iobroker: 
No critical errors detected

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  3.6G     0  3.6G   0% /dev
tmpfs          tmpfs     1.6G  916K  1.6G   1% /run
/dev/sda2      ext4      229G   11G  209G   5% /
tmpfs          tmpfs     3.9G     0  3.9G   0% /dev/shm
tmpfs          tmpfs     5.0M   12K  5.0M   1% /run/lock
/dev/sda1      vfat      253M   87M  166M  35% /boot/firmware
log2ram        tmpfs     100M   19M   82M  19% /var/log
tmpfs          tmpfs     782M     0  782M   0% /run/user/0
tmpfs          tmpfs     782M     0  782M   0% /run/user/1000
tmpfs          tmpfs     782M     0  782M   0% /run/user/1001

Messages concerning ext4 filesystem in dmesg:
[Tue Sep 30 11:47:43 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_hdmi=0  numa=fake=2 system_heap.max_order=0 smsc95xx.macaddr=E4:5F:01:75:41:3E vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000  console=ttyAMA0,115200 console=tty1 root=PARTUUID=26bf3cd6-02 rootfstype=ext4 fsck.repair=yes rootwait
[Tue Sep 30 11:47:47 2025] EXT4-fs (sda2): mounted filesystem 6a932c1f-7335-42d9-9351-1b1b2ca538d4 ro with ordered data mode. Quota mode: none.
[Tue Sep 30 11:47:48 2025] EXT4-fs (sda2): re-mounted 6a932c1f-7335-42d9-9351-1b1b2ca538d4 r/w.

Show mounted filesystems:
TARGET           SOURCE              FSTYPE OPTIONS
/                /dev/sda2           ext4   rw,noatime
|-/boot/firmware /dev/sda1           vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro
`-/var/hdd.log   /dev/sda2[/var/log] ext4   rw,noatime

Files in neuralgic directories:

/var:
1.9G	/var/
1.2G	/var/cache/apt
1.2G	/var/cache
1.1G	/var/cache/apt/archives
496M	/var/lib

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 1.2M in the file system.

/opt/iobroker/backups:
92M	/opt/iobroker/backups/

/opt/iobroker/iobroker-data:
516M	/opt/iobroker/iobroker-data/
386M	/opt/iobroker/iobroker-data/files
97M	/opt/iobroker/iobroker-data/backup-objects
67M	/opt/iobroker/iobroker-data/files/echarts.admin
61M	/opt/iobroker/iobroker-data/files/echarts

The five largest files in iobroker-data are:
28M	/opt/iobroker/iobroker-data/objects.jsonl
27M	/opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map
26M	/opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map
26M	/opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map
24M	/opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.70a15e1f.js.map

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 	v22.20.0
/usr/bin/node 		v22.20.0
/usr/bin/npm 		10.9.3
/usr/bin/npx 		10.9.3
/usr/bin/corepack 	0.34.0

nodejs:
  Installed: 22.20.0-1nodesource1
  Candidate: 22.20.0-1nodesource1
  Version table:
 *** 22.20.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
        100 /var/lib/dpkg/status
     22.19.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.17.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.4.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     18.20.4+dfsg-1~deb12u1 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
        500 http://security.debian.org/debian-security bookworm-security/main arm64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

Checking for nodejs vulnerability:


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



*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
node0               node0 (version: 7.0.7, hostname: node0         , alive, uptime: 200)

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

nodejs modules from github: 	0

Adapter State
+ system.adapter.admin.0                  : admin                 : node0                                    -  enabled, port: 443, bind: X.X.X.X (SSL), run as: admin
+ system.adapter.backitup.0               : backitup              : node0                                    -  enabled
+ system.adapter.echarts.0                : echarts               : node0                                    -  enabled
+ system.adapter.email.0                  : email                 : node0                                    -  enabled
  system.adapter.fahrplan.0               : fahrplan              : node0                                    - disabled
  system.adapter.flot.0                   : flot                  : node0                                    -  enabled
+ system.adapter.fullybrowser.0           : fullybrowser          : node0                                    -  enabled
  system.adapter.i2c.0                    : i2c                   : node0                                    -  enabled
  system.adapter.icons-mfd-png.0          : icons-mfd-png         : node0                                    -  enabled
  system.adapter.icons-mfd-svg.0          : icons-mfd-svg         : node0                                    -  enabled
+ system.adapter.javascript.0             : javascript            : node0                                    -  enabled
  system.adapter.logparser.0              : logparser             : node0                                    - disabled
+ system.adapter.mqtt-client.1            : mqtt-client           : node0                                    -  enabled, port: 1883
+ system.adapter.nina.0                   : nina                  : node0                                    -  enabled
+ system.adapter.nut.0                    : nut                   : node0                                    -  enabled
  system.adapter.openweathermap.0         : openweathermap        : node0                                    -  enabled
  system.adapter.ring.0                   : ring                  : node0                                    - disabled
+ system.adapter.rpi2.0                   : rpi2                  : node0                                    -  enabled
+ system.adapter.simple-api.0             : simple-api            : node0                                    -  enabled, port: 8090, bind: X.X.X.X, run as: admin
+ system.adapter.sma-em.0                 : sma-em                : node0                                    -  enabled
+ system.adapter.sql.0                    : sql                   : node0                                    -  enabled
+ system.adapter.tankerkoenig.0           : tankerkoenig          : node0                                    -  enabled
+ system.adapter.tibberlink.0             : tibberlink            : node0                                    -  enabled
  system.adapter.vesync.0                 : vesync                : node0                                    - disabled
  system.adapter.vis-bars.0               : vis-bars              : node0                                    -  enabled
  system.adapter.vis-history.0            : vis-history           : node0                                    -  enabled
  system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : node0                                    -  enabled
  system.adapter.vis-icontwo.0            : vis-icontwo           : node0                                    -  enabled
+ system.adapter.vis-inventwo.0           : vis-inventwo          : node0                                    -  enabled
  system.adapter.vis-jqui-mfd.0           : vis-jqui-mfd          : node0                                    -  enabled
  system.adapter.vis-justgage.0           : vis-justgage          : node0                                    -  enabled
  system.adapter.vis-material-advanced.0  : vis-material-advanced : node0                                    -  enabled
  system.adapter.vis-materialdesign.0     : vis-materialdesign    : node0                                    -  enabled
  system.adapter.vis-players.0            : vis-players           : node0                                    -  enabled
  system.adapter.vis-timeandweather.0     : vis-timeandweather    : node0                                    -  enabled
  system.adapter.vis-weather.0            : vis-weather           : node0                                    -  enabled
  system.adapter.vis.0                    : vis                   : node0                                    -  enabled
+ system.adapter.web.0                    : web                   : node0                                    -  enabled, port: 8080, bind: X.X.X.X (SSL), run as: admin
+ system.adapter.web.1                    : web                   : node0                                    -  enabled, port: 80, bind: X.X.X.X, run as: web

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : node0                                    -  enabled, port: 443, bind: X.X.X.X (SSL), run as: admin
+ system.adapter.mqtt-client.1            : mqtt-client           : node0                                    -  enabled, port: 1883
+ system.adapter.simple-api.0             : simple-api            : node0                                    -  enabled, port: 8090, bind: X.X.X.X, run as: admin
+ system.adapter.web.0                    : web                   : node0                                    -  enabled, port: 8080, bind: X.X.X.X (SSL), run as: admin
+ system.adapter.web.1                    : web                   : node0                                    -  enabled, port: 80, bind: X.X.X.X, run as: web

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): stable
Upgrade policy: none

Installed ioBroker-Adapters
Used repository: stable
Adapter    "admin"        : 7.7.2    , installed 7.7.2
Adapter    "backitup"     : 3.3.5    , installed 3.3.5
Adapter    "echarts"      : 1.9.2    , installed 1.9.2
Adapter    "email"        : 2.0.4    , installed 2.0.4
Adapter    "fahrplan"     : 1.4.1    , installed 1.4.1
Adapter    "flot"         : 1.12.0   , installed 1.12.0
Adapter    "fullybrowser" : 3.1.2    , installed 3.1.2
Adapter    "i2c"          : 1.2.1    , installed 1.2.1
Adapter    "icons-mfd-png": 1.2.1    , installed 1.2.1
Adapter    "icons-mfd-svg": 1.2.0    , installed 1.2.0
Adapter    "javascript"   : 8.9.2    , installed 8.9.2
Controller "js-controller": 7.0.7    , installed 7.0.7
Adapter    "logparser"    : 2.4.0    , installed 2.4.0
Adapter    "mqtt-client"  : 3.0.0    , installed 3.0.0
Adapter    "nina"         : 0.0.25   , installed 0.0.25
Adapter    "nut"          : 1.6.0    , installed 1.6.0
Adapter    "openweathermap": 1.1.2   , installed 1.1.2
Adapter    "ping"         : 1.6.2    , installed 1.6.2
Adapter    "ring"         : 6.4.0    , installed 6.4.0
Adapter    "rpi2"         : 2.4.0    , installed 2.4.0
Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
Adapter    "sma-em"       : 1.3.0    , installed 1.3.0
Adapter    "socketio"     : 6.7.1    , installed 6.7.1
Adapter    "sql"          : 3.0.1    , installed 3.0.1
Adapter    "tankerkoenig" : 3.4.0    , installed 3.4.0
Adapter    "tibberlink"   : 5.0.2    , installed 5.0.2
Adapter    "upnp"         : 1.1.0    , installed 1.1.0
Adapter    "vis"          : 1.5.6    , installed 1.5.6
Adapter    "vis-bars"     : 0.1.4    , installed 0.1.4
Adapter    "vis-history"  : 1.0.0    , installed 1.0.0
Adapter    "vis-hqwidgets": 1.5.1    , installed 1.5.1
Adapter    "vis-icontwo"  : 1.18.0   , installed 1.18.0
Adapter    "vis-inventwo" : 3.3.5    , installed 3.3.5
Adapter    "vis-jqui-mfd" : 1.1.1    , installed 1.1.1
Adapter    "vis-justgage" : 2.1.7    , installed 2.1.7
Adapter    "vis-material-advanced": 1.7.4, installed 1.7.4
Adapter    "vis-materialdesign": 0.5.9, installed 0.5.9
Adapter    "vis-players"  : 0.1.6    , installed 0.1.6
Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
Adapter    "vis-weather"  : 2.5.12   , installed 2.5.12
Adapter    "web"          : 7.0.8    , installed 7.0.8
Adapter    "ws"           : 2.6.2    , installed 2.6.2

Objects and States
Please stand by - This may take a while
Objects: 	4528
States: 	3626

*** OS-Repositories and Updates ***
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://archive.raspberrypi.org/debian bookworm InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease
Reading package lists...
Pending Updates: 0

*** 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:3306          0.0.0.0:*               LISTEN      110        640        834/mariadbd        
tcp        0      0 X.X.X.X:22              0.0.0.0:*               LISTEN      0          5815       778/sshd: /usr/sbin 
tcp        0      0 X.X.X.X:8090       	0.0.0.0:*               LISTEN      1001       10726      1352/io.simple-api. 
tcp        0      0 X.X.X.X:80           0.0.0.0:*               LISTEN      1001       11364      1337/io.web.1       
tcp        0      0 X.X.X.X:443          0.0.0.0:*               LISTEN      1001       6004       944/io.admin.0      
tcp        0      0 127.0.0.1:1883          0.0.0.0:*               LISTEN      116        791        912/mosquitto       
tcp        0      0 X.X.X.X:1883         0.0.0.0:*               LISTEN      116        790        912/mosquitto       
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       1913       713/iobroker.js-con 
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       1918       713/iobroker.js-con 
tcp        0      0 0.0.0.0:3493            0.0.0.0:*               LISTEN      0          608        743/upsd            
tcp6       0      0 :::22                   :::*                    LISTEN      0          5826       778/sshd: /usr/sbin 
tcp6       0      0 :::6329                 :::*                    LISTEN      0          11828      2045/node           
tcp6       0      0 :::8080                 :::*                    LISTEN      1001       9956       1222/io.web.0       
udp        0      0 0.0.0.0:41288           0.0.0.0:*                           108        442        556/avahi-daemon: r 
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        440        556/avahi-daemon: r 
udp        0      0 0.0.0.0:9522            0.0.0.0:*                           1001       7419       1177/io.sma-em.0    
udp6       0      0 :::48065                :::*                                108        443        556/avahi-daemon: r 
udp6       0      0 :::5353                 :::*                                108        441        556/avahi-daemon: r 

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

2025-09-30 11:50:24.953  - error: host.node0 Caught by controller[0]:     at Object..js (node:internal/modules/cjs/loader:1839:10)
2025-09-30 11:50:24.953  - error: host.node0 Caught by controller[0]:     at Module.load (node:internal/modules/cjs/loader:1441:32)
2025-09-30 11:50:24.953  - error: host.node0 Caught by controller[0]:     at Function._load (node:internal/modules/cjs/loader:1263:12)
2025-09-30 11:50:24.954  - error: host.node0 Caught by controller[0]:     at TracingChannel.traceSync (node:diagnostics_channel:322:14)
2025-09-30 11:50:24.954  - error: host.node0 Caught by controller[0]:     at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
2025-09-30 11:50:24.954  - error: host.node0 Caught by controller[0]:     at Module.require (node:internal/modules/cjs/loader:1463:12)
2025-09-30 11:50:24.954  - error: host.node0 Caught by controller[0]:     at require (node:internal/modules/helpers:147:16) {
2025-09-30 11:50:24.954  - error: host.node0 Caught by controller[0]:   tries: [
2025-09-30 11:50:24.955  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/build/i2c.node',
2025-09-30 11:50:24.955  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/build/Debug/i2c.node',
2025-09-30 11:50:24.955  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/build/Release/i2c.node',
2025-09-30 11:50:24.955  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/out/Debug/i2c.node',
2025-09-30 11:50:24.956  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/Debug/i2c.node',
2025-09-30 11:50:24.956  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/out/Release/i2c.node',
2025-09-30 11:50:24.956  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/Release/i2c.node',
2025-09-30 11:50:24.956  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/build/default/i2c.node',
2025-09-30 11:50:24.957  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/compiled/22.20.0/linux/arm64/i2c.node',
2025-09-30 11:50:24.957  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/addon-build/release/install-root/i2c.node',
2025-09-30 11:50:24.958  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/addon-build/debug/install-root/i2c.node',
2025-09-30 11:50:24.958  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/addon-build/default/install-root/i2c.node',
2025-09-30 11:50:24.958  - error: host.node0 Caught by controller[0]:     '/opt/iobroker/node_modules/i2c-bus/lib/binding/node-v127-linux-arm64/i2c.node'
2025-09-30 11:50:24.959  - error: host.node0 Caught by controller[0]:   ]
2025-09-30 11:50:24.959  - error: host.node0 Caught by controller[0]: }
2025-09-30 11:50:24.959  - error: host.node0 Caught by controller[0]: Node.js v22.20.0
2025-09-30 11:50:24.960  - error: host.node0 instance system.adapter.i2c.0 terminated with code 1 (JS_CONTROLLER_STOPPED)

============ Mark until here for C&P =============

@homoran Interessante Frage, ich habe ehrlich gesagt über die Sprache/Forum nicht nachgedacht. Derzeit tendiere ich halt dazu, nur noch in den englischen Foren diese Art von Fragen zu stellen.

Ganz offen - gibt es eine Empfehlung wann Deutsch und wann Englisch?

@thomas-braun thanks, for the fast feedback. Good to know, that it will work in general. I will record an iob diag, I need a few days to do so because I have to upgrade again and I need a time window for this.
I checked already for node-gyp and this isn't available on my system. Maybe it's not installed by the iob.

Overall, I checked also the /opt/iobroker/node_modules/i2c-bus/build/Release/i2c.node file. This is available with iobroker permission. Interesting is here that adapter start shows in the log that the file is searched without success.

Dear Folk,

today I try to upgrade from Node.js 20 to Node.JS 22. After the upgrade I face some serious errors with the i2c adapter, which is a core functionality in my environment. I got the following log, maybe some face the same problem?

2025-09-29 10:00:13.087 - error: host.node0 Caught by controller[0]: /opt/iobroker/node_modules/bindings/bindings.js:135
2025-09-29 10:00:13.088 - error: host.node0 Caught by controller[0]: throw err;
2025-09-29 10:00:13.088 - error: host.node0 Caught by controller[0]: ^
2025-09-29 10:00:13.089 - error: host.node0 Caught by controller[0]: Error: Could not locate the bindings file. Tried:
2025-09-29 10:00:13.089 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/build/i2c.node
2025-09-29 10:00:13.089 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/build/Debug/i2c.node
2025-09-29 10:00:13.089 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/build/Release/i2c.node
2025-09-29 10:00:13.090 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/out/Debug/i2c.node
2025-09-29 10:00:13.090 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/Debug/i2c.node
2025-09-29 10:00:13.090 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/out/Release/i2c.node
2025-09-29 10:00:13.090 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/Release/i2c.node
2025-09-29 10:00:13.090 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/build/default/i2c.node
2025-09-29 10:00:13.091 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/compiled/22.20.0/linux/arm64/i2c.node
2025-09-29 10:00:13.091 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/addon-build/release/install-root/i2c.node
2025-09-29 10:00:13.091 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/addon-build/debug/install-root/i2c.node
2025-09-29 10:00:13.092 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/addon-build/default/install-root/i2c.node
2025-09-29 10:00:13.092 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/lib/binding/node-v127-linux-arm64/i2c.node
2025-09-29 10:00:13.092 - error: host.node0 Caught by controller[0]: at bindings (/opt/iobroker/node_modules/bindings/bindings.js:126:9)
2025-09-29 10:00:13.092 - error: host.node0 Caught by controller[0]: at Object. (/opt/iobroker/node_modules/i2c-bus/i2c-bus.js:4:32)
2025-09-29 10:00:13.092 - error: host.node0 Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1706:14)
2025-09-29 10:00:13.093 - error: host.node0 Caught by controller[0]: at Object..js (node:internal/modules/cjs/loader:1839:10)
2025-09-29 10:00:13.093 - error: host.node0 Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1441:32)
2025-09-29 10:00:13.093 - error: host.node0 Caught by controller[0]: at Function._load (node:internal/modules/cjs/loader:1263:12)
2025-09-29 10:00:13.094 - error: host.node0 Caught by controller[0]: at TracingChannel.traceSync (node:diagnostics_channel:322:14)
2025-09-29 10:00:13.094 - error: host.node0 Caught by controller[0]: at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
2025-09-29 10:00:13.094 - error: host.node0 Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1463:12)
2025-09-29 10:00:13.094 - error: host.node0 Caught by controller[0]: at require (node:internal/modules/helpers:147:16) {
2025-09-29 10:00:13.095 - error: host.node0 Caught by controller[0]: tries: [
2025-09-29 10:00:13.095 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/build/i2c.node',
2025-09-29 10:00:13.096 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/build/Debug/i2c.node',
2025-09-29 10:00:13.096 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/build/Release/i2c.node',
2025-09-29 10:00:13.097 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/out/Debug/i2c.node',
2025-09-29 10:00:13.097 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/Debug/i2c.node',
2025-09-29 10:00:13.097 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/out/Release/i2c.node',
2025-09-29 10:00:13.098 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/Release/i2c.node',
2025-09-29 10:00:13.098 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/build/default/i2c.node',
2025-09-29 10:00:13.098 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/compiled/22.20.0/linux/arm64/i2c.node',
2025-09-29 10:00:13.099 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/addon-build/release/install-root/i2c.node',
2025-09-29 10:00:13.099 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/addon-build/debug/install-root/i2c.node',
2025-09-29 10:00:13.099 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/addon-build/default/install-root/i2c.node',
2025-09-29 10:00:13.100 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/lib/binding/node-v127-linux-arm64/i2c.node'
2025-09-29 10:00:13.100 - error: host.node0 Caught by controller[0]: ]
2025-09-29 10:00:13.100 - error: host.node0 Caught by controller[0]: }
2025-09-29 10:00:13.101 - error: host.node0 Caught by controller[0]: Node.js v22.20.0
2025-09-29 10:00:13.101 - error: host.node0 instance system.adapter.i2c.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2025-09-29 10:03:55.148 - error: host.node0 Caught by controller[0]: /opt/iobroker/node_modules/bindings/bindings.js:135
2025-09-29 10:03:55.149 - error: host.node0 Caught by controller[0]: throw err;
2025-09-29 10:03:55.149 - error: host.node0 Caught by controller[0]: ^
2025-09-29 10:03:55.150 - error: host.node0 Caught by controller[0]: Error: Could not locate the bindings file. Tried:
2025-09-29 10:03:55.150 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/build/i2c.node
2025-09-29 10:03:55.150 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/build/Debug/i2c.node
2025-09-29 10:03:55.150 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/build/Release/i2c.node
2025-09-29 10:03:55.151 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/out/Debug/i2c.node
2025-09-29 10:03:55.151 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/Debug/i2c.node
2025-09-29 10:03:55.151 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/out/Release/i2c.node
2025-09-29 10:03:55.151 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/Release/i2c.node
2025-09-29 10:03:55.152 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/build/default/i2c.node
2025-09-29 10:03:55.152 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/compiled/22.20.0/linux/arm64/i2c.node
2025-09-29 10:03:55.152 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/addon-build/release/install-root/i2c.node
2025-09-29 10:03:55.152 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/addon-build/debug/install-root/i2c.node
2025-09-29 10:03:55.152 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/addon-build/default/install-root/i2c.node
2025-09-29 10:03:55.153 - error: host.node0 Caught by controller[0]: → /opt/iobroker/node_modules/i2c-bus/lib/binding/node-v127-linux-arm64/i2c.node
2025-09-29 10:03:55.153 - error: host.node0 Caught by controller[0]: at bindings (/opt/iobroker/node_modules/bindings/bindings.js:126:9)
2025-09-29 10:03:55.153 - error: host.node0 Caught by controller[0]: at Object. (/opt/iobroker/node_modules/i2c-bus/i2c-bus.js:4:32)
2025-09-29 10:03:55.153 - error: host.node0 Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1706:14)
2025-09-29 10:03:55.153 - error: host.node0 Caught by controller[0]: at Object..js (node:internal/modules/cjs/loader:1839:10)
2025-09-29 10:03:55.154 - error: host.node0 Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1441:32)
2025-09-29 10:03:55.154 - error: host.node0 Caught by controller[0]: at Function._load (node:internal/modules/cjs/loader:1263:12)
2025-09-29 10:03:55.154 - error: host.node0 Caught by controller[0]: at TracingChannel.traceSync (node:diagnostics_channel:322:14)
2025-09-29 10:03:55.154 - error: host.node0 Caught by controller[0]: at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
2025-09-29 10:03:55.155 - error: host.node0 Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1463:12)
2025-09-29 10:03:55.155 - error: host.node0 Caught by controller[0]: at require (node:internal/modules/helpers:147:16) {
2025-09-29 10:03:55.155 - error: host.node0 Caught by controller[0]: tries: [
2025-09-29 10:03:55.155 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/build/i2c.node',
2025-09-29 10:03:55.155 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/build/Debug/i2c.node',
2025-09-29 10:03:55.156 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/build/Release/i2c.node',
2025-09-29 10:03:55.156 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/out/Debug/i2c.node',
2025-09-29 10:03:55.156 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/Debug/i2c.node',
2025-09-29 10:03:55.156 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/out/Release/i2c.node',
2025-09-29 10:03:55.157 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/Release/i2c.node',
2025-09-29 10:03:55.157 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/build/default/i2c.node',
2025-09-29 10:03:55.157 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/compiled/22.20.0/linux/arm64/i2c.node',
2025-09-29 10:03:55.157 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/addon-build/release/install-root/i2c.node',
2025-09-29 10:03:55.157 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/addon-build/debug/install-root/i2c.node',
2025-09-29 10:03:55.158 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/addon-build/default/install-root/i2c.node',
2025-09-29 10:03:55.158 - error: host.node0 Caught by controller[0]: '/opt/iobroker/node_modules/i2c-bus/lib/binding/node-v127-linux-arm64/i2c.node'

Hallo,
ich habe auch eine Consori Fritteuse gekauft, die App eingerichtet und dann den Adapter. Dis App funktioniert, der Adapter zeigt im LOG aber die gleiche Fehlermeldung wie bei FoxMulder & MacGyver.
Scheint evtl. bei allen neuen Einrichtungen zu passieren.
Liebe Grüße

Hi,
Ich habe jetzt mal die Idee von Paul getestet und ebenfalls auch mal den Alias DP komplett gelöscht und mit neuem Namen neu angelegt.
Leider bleibt das merkwürdig Verhalten erhalten.
Ich hatte gestern wieder den folgenden Output beim lesen.
2025-08-12 08:02:36.996 - warn: javascript.0 (187304) script.js.Schlafzimmer_Helmut.Taster: Licht =OFF Speaker =start MqttValueTasmota =OFF
2025-08-12 22:09:15.347 - warn: javascript.0 (187304) script.js.Schlafzimmer_Helmut.Taster: Licht =OFF Speaker =stop MqttValueTasmota =OFF
2025-08-12 22:17:17.155 - warn: javascript.0 (187304) script.js.Schlafzimmer_Helmut.Taster: Licht =true Speaker =stop MqttValueTasmota =ON
Zwischen 22:09 und 22:17 habe ich den Alias Datenpunkt über die VIS auf true gesetz -> der write DP sendet dann über MQTT/CMND an Tasmota, Tasmota antwortet über STAT und der Read DP liefert OFF, was dann von dem Alias richtig umgesetzt wird.

Nach einer unbestimmten Zeit oder nach einem unbestimmten Ereignis liefert der Alias dann allerdings wie in dem Log zu sehen Licht=OFF und nicht mehr false obwohl dies entsprechend der Alias Konvertierung gar nicht passieren darf, denn dort steht: read => val=='ON', somit dürfte in diesem Fall nie ein True erscheinen.

{
  "common": {
    "name": "Licht_WC",
    "desc": "Manually created",
    "role": "state",
    "type": "boolean",
    "read": true,
    "write": true,
    "def": false,
    "alias": {
      "id": {
        "read": "0_userdata.0.Schlafzimmer_Helmut.DC4F22803CA2.stat.power1",
        "write": "0_userdata.0.Schlafzimmer_Helmut.DC4F22803CA2.cmnd.power1"
      },
      "read": "val=='ON'",
      "write": "val ? 'ON':'OFF'"
    }
  },
  "type": "state",
  "native": {},
  "_id": "alias.0.SchlafzimmerHelmut.Licht_WC",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.helmut",
    "ownerGroup": "system.group.administrator"
  },
  "from": "system.adapter.admin.0",
  "user": "system.user.helmut",
  "ts": 1754551409965
}

Gelesen wird wie folgt:

var IstStateLicht = getState(ObjIDLicht).val;
    var IstStateSpeaker = getState(ObjIDSpk).val;
    var IstMqttObject = getState(ObjIDLicht2).val;

    log('Licht =' +IstStateLicht +' Speaker =' +IstStateSpeaker + ' MqttValueTasmota =' +IstMqttObject,'warn');

@paul53 Vielen Dank für die schnelle Antwort, die Prüfung auf "ON" / "on" ist mehr der Sicherheit geschuldet. Ich hatte vorher nur "ON" & "OFF", da war der beschriebe Fehler aber auch da.
Interessant ist ja eigentlich, dass im IOBroker Admin dies richtig dargestellt wird, nur bei dem getState wohl falsch dargestellt wird
Dein Vorschlag wäre: val=='ON' || val=='on'?true : val=='OFF' || val =='off'?false : null
Richtig?

Re: Frage zu Alias
Hi, hat dazu von Euch jemand eine Idee, ich stehe ein wenig auf dem Schlauch.
Ich habe 2 DP, einen für Read, einem für write (Tasmota) beide Datatype String

1. 0_userdata.0.DC4F22803CA2.stat.power1 => MQTTClient ( subscribe stat/DC4F22803CA2/POWER1) changes only, Exactly once
2. 0_userdata.0.DC4F22803CA2.cmnd.power1=> MQTTClient ( publish cmnd/DC4F22803CA2/POWER1) Exactly once, retained

Dazu gibt es einen Alias DP. Datatype boolean

1. Read = link auf 0_userdata.0.DC4F22803CA2.stat.power1 , Read convert function: val=='ON'?true:val=='on'?true:val=='OFF'?false':val=='off'?false:null
2. Write == link auf 0_userdata.0.DC4F22803CA2.cmnd.power1, Write convert function: val?'ON':'OFF'

Nun das Problem. Die Adminoberfläche zeigt zu jedem Zeitpunkt für den Alias DP immer den richtigen Status True/False an. Wenn ich den Alias DP in einem Script auslese

var xxx = getState('aliasDP').val.

erhalte ich in einigen Fällen kein False zurück sonder auch schonmal "OFF" und nicht das Ergebnis des Convert. Hatt dazu vielleicht jemand eine Idee?

Vielen Dank
Helmut