js-controller 5.0.x jetzt für alle User im STABLE!

liv-in-sky

also sayit hat sich erledigt - neu installiert und jetzt kommt kein fehler

das mit ws.5 ist etwas seltsam - habe nur ws.0 und ws.1 aktiv und ws.5 - habe jetzt ws5 abgeschaltet und in ws.2 definiert - dann startet alles ohne fehler und die vis ist wieder da

diese ganzen ws.x hatte ich mal installiert und getestet, ob meine tablets die vis stabiler anzeigen, wenn jedes tablet eigene instanzen hat

bleibt n nur noch diese warnung:

	Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead

liv-in-sky

@foxriver76

zu früh gefreut - egal, was ich in der web.x instanz einstelle (integriert, ws oder socket - alles stürzt ab) diesmal dieser fehler

also keine vis

host.iobroker59
2023-09-14 18:53:17.401	error	instance system.adapter.web.5 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker59
2023-09-14 18:53:17.401	error	Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
host.iobroker59
2023-09-14 18:53:17.401	error	Caught by controller[1]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
host.iobroker59
2023-09-14 18:53:17.401	error	Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
host.iobroker59
2023-09-14 18:53:17.401	error	Caught by controller[1]: Error: The pattern "io. scale(1.3, 1.3)" is not a valid ID pattern
host.iobroker59
2023-09-14 18:53:17.401	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

web.5
2023-09-14 18:53:16.746	error	Alias subscription error. Please check your alias definitions: sourceId=zigbee2mqtt.0.0x540f57fffef3f8cf.current_heating_setpoint, sourceObj={"type":"state","common":{"id":"current_heating_setpoint","prop":"current_heating_setpoint","name":"Temperature setpoint","role":"level.temperature","write":true,"read":true,"type":"number","min":5,"max":30,"unit":"°C","def":5},"native":{},"from":"system.adapter.zigbee2mqtt.0","user":"system.user.admin","ts":1694708659978,"_id":"zigbee2mqtt.0.0x540f57fffef3f8cf.current_heating_setpoint","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}

web.5
2023-09-14 18:53:16.746	error	Alias subscription error. Please check your alias definitions: sourceId=zigbee2mqtt.0.0x84ba20fffe2dca6b.current_heating_setpoint, sourceObj={"type":"state","common":{"id":"current_heating_setpoint","prop":"current_heating_setpoint","name":"Temperature setpoint","role":"level.temperature","write":true,"read":true,"type":"number","min":5,"max":30,"unit":"°C","def":5},"native":{},"from":"system.adapter.zigbee2mqtt.0","user":"system.user.admin","ts":1694708659054,"_id":"zigbee2mqtt.0.0x84ba20fffe2dca6b.current_heating_setpoint","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}

web.5
2023-09-14 18:53:16.746	error	Alias subscription error. Please check your alias definitions: sourceId=fritzdect.0.DECT_119610737080.tsoll, sourceObj={"type":"state","common":{"name":"Setpoint Temperature","type":"number","min":0,"max":32,"unit":"°C","read":true,"write":true,"role":"value.temperature","desc":"Setpoint Temperature"},"native":{},"from":"system.adapter.fritzdect.0","user":"system.user.admin","ts":1611662566181,"_id":"fritzdect.0.DECT_119610737080.tsoll","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}

web.5
2023-09-14 18:53:16.696	error	The pattern "io. scale(1.3, 1.3)" is not a valid ID pattern

web.5
2023-09-14 18:53:16.695	error	Error: The pattern "io. scale(1.3, 1.3)" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)

web.5
2023-09-14 18:53:16.647	error	unhandled promise rejection: The pattern "io. scale(1.3, 1.3)" is not a valid ID pattern

web.5
2023-09-14 18:53:16.647	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

web.5
2023-09-14 18:53:16.642	error	Invalid pattern on subscribe: The pattern " scale(1, 1)" is not a valid ID pattern

web.5
2023-09-14 18:53:16.641	error	Invalid pattern on subscribe: The pattern "0% { transform: scale(1, 1)" is not a valid ID pattern

iob diag:

Copy text starting here:


======================= SUMMARY =======================
                    v.2023-04-16


Operatingsystem:        Debian GNU/Linux 12 (bookworm)
Kernel:                 6.2.16-6-pve
Installation:           lxc
Timezone:               Europe/Berlin (CEST, +0200)
User-ID:                0
X-Server:               false
Boot Target:            graphical.target

Pending OS-Updates:     10
Pending iob updates:    3

Nodejs-Installation:    /usr/bin/nodejs         v18.17.1
                       /usr/bin/node           v18.17.1
                       /usr/bin/npm            9.6.7
                       /usr/bin/npx            9.6.7

Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correct

MEMORY:
              total        used        free      shared  buff/cache   available
Mem:             11G        8.0G        438M        1.8M        3.3G        3.8G
Swap:           2.1G          0B        2.1G
Total:           13G        8.0G        2.6G

Active iob-Instances:   74
Active repo(s): beta

ioBroker Core:          js-controller           5.0.12
                       admin                   6.10.1

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: redis

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : iobroker59                               -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.admin.1                  : admin                 : iobroker59                               -  enabled, port: 8088, bind: 0.0.0.0, run as: admin
 system.adapter.admin.2                  : admin                 : iobroker59                               - disabled, port: 8089, bind: 0.0.0.0, run as: admin
 system.adapter.admin.3                  : admin                 : iobroker59                               - disabled, port: 8071, bind: 0.0.0.0, run as: admin
 system.adapter.web-speedy.0             : web-speedy            : iobroker59                               - disabled
+ system.adapter.web.0                    : web                   : iobroker59                               -  enabled, port: 8082, bind: 192.168.178.59, run as: admin
+ system.adapter.web.1                    : web                   : iobroker59                               -  enabled, port: 8072, bind: 192.168.178.59, run as: admin
 system.adapter.web.2                    : web                   : iobroker59                               - disabled, port: 8098, bind: 0.0.0.0, run as: admin
 system.adapter.web.3                    : web                   : iobroker59                               - disabled, port: 8074, bind: 0.0.0.0, run as: admin
 system.adapter.web.4                    : web                   : iobroker59                               - disabled, port: 8075, bind: 0.0.0.0, run as: admin
+ system.adapter.web.5                    : web                   : iobroker59                               -  enabled, port: 8076, bind: 0.0.0.0, run as: admin
 system.adapter.web.6                    : web                   : iobroker59                               - disabled, port: 8077, bind: 0.0.0.0, run as: admin
 system.adapter.web.7                    : web                   : iobroker59                               - disabled, port: 8078, bind: 0.0.0.0, run as: admin
+ system.adapter.webcal.0                 : webcal                : iobroker59                               -  enabled
+ system.adapter.webcal.1                 : webcal                : iobroker59                               -  enabled
+ system.adapter.webcal.2                 : webcal                : iobroker59                               -  enabled

Objects:                71340
States:                 78158

Size of iob-Database:

163M    /opt/iobroker/iobroker-data/objects.jsonl
26M     /opt/iobroker/iobroker-data/states.jsonl



=================== END OF SUMMARY ====================



Active repo(s): beta

Installed ioBroker-Instances
Used repository: beta
Adapter    "admin"        : 6.10.1   , installed 6.10.1
Adapter    "alexa-timer-vis": 0.2.0  , installed 0.2.0
Adapter    "alexa2"       : 3.25.2   , installed 3.25.2
Adapter    "alias-manager": 1.2.6    , installed 1.2.6
Adapter    "backitup"     : 2.8.1    , installed 2.8.1
Adapter    "broadlink2"   : 2.1.5    , installed 2.1.5
Adapter    "calendar"     : 1.2.0    , installed 1.2.0
Adapter    "cloud"        : 4.4.1    , installed 4.4.1
Adapter    "contact"      : 1.1.3    , installed 1.1.3
Adapter    "countdown"    : 2.2.0    , installed 2.2.0
Adapter    "daswetter"    : 3.1.10   , installed 3.1.10
Adapter    "device-reminder": 2.0.1  , installed 1.2.9  [Updatable]
Adapter    "devices"      : 1.1.5    , installed 1.1.5
Adapter    "dwd"          : 2.8.5    , installed 2.8.5
Adapter    "email"        : 1.2.0    , installed 1.2.0
Adapter    "esphome"      : 0.2.4    , installed 0.2.4
Adapter    "eventlist"    : 1.2.3    , installed 1.2.3
Adapter    "feiertage"    : 1.1.4    , installed 1.1.4
Adapter    "flot"         : 1.12.0   , installed 1.12.0
Adapter    "fritzdect"    : 2.3.1    , installed 2.3.1
Adapter    "fuelpricemonitor": 0.3.6 , installed 0.3.6-alpha.0 [Updatable]
Adapter    "fullybrowser" : 2.1.2    , installed 2.1.2
Adapter    "gotify"       : 0.2.0    , installed 0.2.0
Adapter    "history"      : 2.2.6    , installed 2.2.6
Adapter    "ical"         : 1.13.3   , installed 1.13.3
Adapter    "iceroad"      : 1.2.1    , installed 1.2.1
Adapter    "icons-addictive-flavour-png": 0.1.0, installed 0.1.0
Adapter    "icons-icons8" : 0.0.1    , installed 0.0.1
Adapter    "icons-material-svg": 0.1.0, installed 0.1.0
Adapter    "icons-mfd-png": 1.1.0    , installed 1.1.0
Adapter    "icons-mfd-svg": 1.1.0    , installed 1.1.0
Adapter    "icons-open-icon-library-png": 0.1.2, installed 0.1.3
Adapter    "icons-ultimate-png": 1.0.1, installed 1.0.1
Adapter    "imap"         : 0.1.1    , installed 0.1.1
Adapter    "info"         : 2.0.0    , installed 2.0.0
Adapter    "iot"          : 2.0.11   , installed 2.0.11
Adapter    "iqontrol"     : 2.3.0    , installed 2.3.0
Adapter    "javascript"   : 7.1.4    , installed 7.1.4
Controller "js-controller": 5.0.12   , installed 5.0.12
Adapter    "lgtv"         : 1.1.12   , installed 1.1.12
Adapter    "linux-control": 1.1.5    , installed 1.1.5
Adapter    "meross"       : 1.15.1   , installed 1.15.1
Adapter    "meteoalarm"   : 2.3.7    , installed 2.3.7
Adapter    "mihome"       : 1.4.0    , installed 1.4.0
Adapter    "mpd"          : 1.1.1    , installed 1.1.1
Adapter    "mqtt"         : 4.1.1    , installed 4.1.1
Adapter    "netatmo-crawler": 0.8.1  , installed 0.8.1
Adapter    "node-red"     : 4.0.3    , installed 4.0.3
Adapter    "nut"          : 1.6.0    , installed 1.6.0
Adapter    "odl"          : 2.0.5    , installed 2.0.5
Adapter    "openweathermap": 0.4.3   , installed 0.4.3
Adapter    "parcel"       : 0.1.2    , installed 0.1.2
Adapter    "parser"       : 2.0.5    , installed 2.0.5
Adapter    "pi-hole"      : 1.3.6    , installed 1.3.6
Adapter    "ping"         : 1.6.2    , installed 1.6.2
Adapter    "pixelit"      : 1.1.1    , installed 1.1.1
Adapter    "plex"         : 1.1.0    , installed 1.1.0
Adapter    "proxmox"      : 2.0.2    , installed 2.0.2
Adapter    "puppeteer"    : 0.2.7    , installed 0.2.7
Adapter    "pushbullet"   : 1.0.1    , installed 1.0.1
Adapter    "pushover"     : 3.0.4    , installed 3.0.4
Adapter    "pushsafer"    : 1.0.3    , installed 1.0.3
Adapter    "sayit"        : 3.0.5    , installed 3.0.5
Adapter    "scenes"       : 2.3.9    , installed 2.3.9
Adapter    "scheduler"    : 1.1.9    , installed 1.1.9
Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
Adapter    "socketio"     : 6.5.3    , installed 6.5.3
Adapter    "sonoff"       : 2.5.7    , installed 2.5.7
Adapter    "sourceanalytix": 0.4.14  , installed 0.4.14
Adapter    "spotify-premium": 1.2.2  , installed 1.2.2
Adapter    "sql"          : 2.2.0    , installed 2.2.0
Adapter    "tankerkoenig" : 3.3.7    , installed 3.3.7
Adapter    "telegram"     : 1.16.0   , installed 1.16.0
Adapter    "telegram-menu": 0.6.7    , installed 0.6.7
Adapter    "time-switch"  : 2.2.2    , installed 2.2.2
Adapter    "tr-064"       : 4.2.18   , installed 4.2.18
Adapter    "traccar"      : 1.1.2    , installed 0.0.12 [Updatable]
Adapter    "trashschedule": 2.2.0    , installed 2.2.0
Adapter    "tvprogram"    : 1.1.2    , installed 1.1.2
Adapter    "unifi"        : 0.6.6    , installed 0.6.6
Adapter    "upnp"         : 1.0.21   , installed 1.0.21
Adapter    "valuetrackerovertime": 1.0.1, installed 1.0.1
Adapter    "virtualpowermeter": 1.4.6, installed 1.4.6
Adapter    "vis"          : 1.4.16   , installed 1.4.16
Adapter    "vis-bars"     : 0.1.4    , installed 0.1.4
Adapter    "vis-canvas-gauges": 1.0.1, installed 1.0.1
Adapter    "vis-colorpicker": 2.0.3  , installed 2.0.3
Adapter    "vis-fancyswitch": 1.1.0  , installed 1.1.0
Adapter    "vis-google-fonts": 1.0.4 , installed 1.0.4
Adapter    "vis-history"  : 1.0.0    , installed 1.0.0
Adapter    "vis-hqwidgets": 1.4.0    , installed 1.4.0
Adapter    "vis-icontwo"  : 0.96.0   , installed 0.96.0
Adapter    "vis-inventwo" : 3.3.3    , installed 3.3.3
Adapter    "vis-jqui-mfd" : 1.0.12   , installed 1.0.12
Adapter    "vis-justgage" : 1.0.2    , installed 1.0.2
Adapter    "vis-map"      : 1.0.4    , installed 1.0.4
Adapter    "vis-material-advanced": 1.7.4, installed 1.7.4
Adapter    "vis-materialdesign": 0.5.9, installed 0.5.9
Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
Adapter    "vis-players"  : 0.1.6    , installed 0.1.6
Adapter    "vis-plumb"    : 1.0.2    , installed 1.0.2
Adapter    "vis-rgraph"   : 0.0.2    , installed 0.0.2
Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
Adapter    "vis-weather"  : 2.5.6    , installed 2.5.6
Adapter    "web"          : 6.1.1    , installed 6.1.1
Adapter    "web-speedy"   : 0.2.0    , installed 0.2.0
Adapter    "whatsapp-cmb" : 0.2.3    , installed 0.2.3
Adapter    "windows-control": 0.1.5  , installed 0.1.5
Adapter    "wled"         : 0.7.0    , installed 0.7.0
Adapter    "ws"           : 2.5.4    , installed 2.5.4
Adapter    "zigbee"       : 1.8.24   , installed 1.8.24
Adapter    "zigbee2mqtt"  : 2.13.1   , installed 2.13.1

mcm1957

@mcm57 said in js-controller 5.0.x jetzt für alle User im STABLE!:

@foxriver76
Ok
Wenn ihr keine Zeit habt kann ich am Abend release versuchen

Ok, der botvac hat weder release script noch github tests - Museumsstand was die Infrastruktur betrifft. Ich werd dann mal anfangen, kann aber auch noch nen Tag dauern bis ne saubere Release entsteht.

Wer will, kann zwischenzeitlich die GITHUB Version versuchen (übliches Disclaimer - at own risk + Backup). Der Code sollte an js-controller 5 angepasst sein. Er enthält allerdings auch ein paar weitere Änderungen die nicht ins README gefunden haben, da muss ich erst mal schaun ob da ne Info was geändert wurde extrahieren kann.

Thomas Braun

@liv-in-sky sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

User-ID:                0
Pending OS-Updates:     10
Pending iob updates:    3

Das würde ich zunächst in Angriff nehmen. Also user anlegen und nicht als root herummachen und die Updates einspielen. Auf der Basis kann man dann weiter schauen.

JohGre

@mcm57 Danke schon mal für deine Hilfe beim Botvac Adapter.
Aber viel wichtiger wäre mir Hilfe bei der Lösung des Problems mit dem ham-modul homebridge-balboa-spa@2.2.6, das brauch ich wirklich da ich damit unsere Whirlpool steuere.

Mehr spukt das log dazu nicht aus.

2023-09-14 14:40:20.837  - [31merror[39m: ham.0 (35321) Error: Library homebridge-balboa-spa@2.2.6 not installed after 3 attempts

foxriver76

@liv-in-sky Im Endeffekt iwo ein binding in vis, welches mist macht. Aber ich denke wir sollten noch eine neue Web Adapter Version machen weil ist eigentlich gefixt in socket classes aber dafür müsste web Adapter neu installiert oder geupdated werden.

liv-in-sky

@foxriver76 du meinst ich soll den web adapter deinstallieren und neu installieren ?

mcm1957

@johgre said in js-controller 5.0.x jetzt für alle User im STABLE!:

@mcm57 Danke schon mal für deine Hilfe beim Botvac Adapter.
Aber viel wichtiger wäre mir Hilfe bei der Lösung des Problems mit dem ham-modul homebridge-balboa-spa@2.2.6, das brauch ich wirklich da ich damit unsere Whirlpool steuere.

Mehr spukt das log dazu nicht aus.
2023-09-14 14:40:20.837  - [31merror[39m: ham.0 (35321) Error: Library homebridge-balboa-spa@2.2.6 not installed after 3 attempts

Sorry, da kann ich nix beitragen.

@foxriver76
@apollon77
Könnt ihr da was dazu sagen oder jemand triggern der sich das ansehen kann?

liv-in-sky

@thomas-braun

so ist jetzt der stand:

======================= SUMMARY =======================
                    v.2023-04-16


Operatingsystem:        Debian GNU/Linux 12 (bookworm)
Kernel:                 6.2.16-6-pve
Installation:           lxc
Timezone:               Europe/Berlin (CEST, +0200)
User-ID:                1000
X-Server:               false
Boot Target:            graphical.target

Pending OS-Updates:     0
Pending iob updates:    1

Nodejs-Installation:    /usr/bin/nodejs         v18.17.1
                       /usr/bin/node           v18.17.1
                       /usr/bin/npm            9.6.7
                       /usr/bin/npx            9.6.7

Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correct

MEMORY:
              total        used        free      shared  buff/cache   available
Mem:             11G        7.6G        2.4G        1.8M        1.8G        4.2G
Swap:           2.1G          0B        2.1G
Total:           13G        7.6G        4.5G

Active iob-Instances:   72
Active repo(s): beta

ioBroker Core:          js-controller           5.0.12
                       admin                   6.10.1

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: redis

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : iobroker59                               -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.admin.1                  : admin                 : iobroker59                               -  enabled, port: 8088, bind: 0.0.0.0, run as: admin
 system.adapter.admin.2                  : admin                 : iobroker59                               - disabled, port: 8089, bind: 0.0.0.0, run as: admin
 system.adapter.admin.3                  : admin                 : iobroker59                               - disabled, port: 8071, bind: 0.0.0.0, run as: admin
 system.adapter.web-speedy.0             : web-speedy            : iobroker59                               - disabled
+ system.adapter.web.0                    : web                   : iobroker59                               -  enabled, port: 8082, bind: 192.168.178.59, run as: admin
+ system.adapter.web.1                    : web                   : iobroker59                               -  enabled, port: 8072, bind: 192.168.178.59, run as: admin
 system.adapter.web.2                    : web                   : iobroker59                               - disabled, port: 8098, bind: 0.0.0.0, run as: admin
 system.adapter.web.3                    : web                   : iobroker59                               - disabled, port: 8074, bind: 0.0.0.0, run as: admin
 system.adapter.web.4                    : web                   : iobroker59                               - disabled, port: 8075, bind: 0.0.0.0, run as: admin
+ system.adapter.web.5                    : web                   : iobroker59                               -  enabled, port: 8076, bind: 0.0.0.0, run as: admin
 system.adapter.web.6                    : web                   : iobroker59                               - disabled, port: 8077, bind: 0.0.0.0, run as: admin
 system.adapter.web.7                    : web                   : iobroker59                               - disabled, port: 8078, bind: 0.0.0.0, run as: admin
+ system.adapter.webcal.0                 : webcal                : iobroker59                               -  enabled
+ system.adapter.webcal.1                 : webcal                : iobroker59                               -  enabled
+ system.adapter.webcal.2                 : webcal                : iobroker59                               -  enabled

Objects:                71282
States:                 78322

Size of iob-Database:

84M     /opt/iobroker/iobroker-data/objects.jsonl
26M     /opt/iobroker/iobroker-data/states.jsonl



=================== END OF SUMMARY ====================

den einen adapter kann ich nicht updaten, da die neue version davon nicht geht - ist traccar - sollte hier kein thema sein

kein root user

Thomas Braun

@liv-in-sky sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

kein root user

räusper
User-ID: 0

Edit:
Okay, geändert im aktuellen Output...

liv-in-sky

@foxriver76
@Thomas-Braun

habe leider keine zeit nehr - gehe wieder auf altes system zurück - evtl kann ich am WE nochmal testen

erstmal danke

apollon77

@johgre da muss mehr im log stehen bei normalen logleveln.

JohGre

@apollon77 Hallo, hat sich erledigt.
Einmal Adapter löschen, wieder installieren, Module neu hinzufügen, konfigurieren und schon tuts wieder.
Hab das vorher in einem neuen Container probiert und da es da geklappt hat gleich am Produktivsystem.

surfer09

Bei mir hat auch alles funktioniert. Danke!

mcm1957

This post is deleted!

Thomas Braun

@mcm57

Dann kannst du ja den Eintrag dazu ändern:

enigma2 - required: none - not at stable yet

mcm1957

@foxriver76 said in js-controller 5.0.x jetzt für alle User im STABLE!:

@liv-in-sky Im Endeffekt iwo ein binding in vis, welches mist macht. Aber ich denke wir sollten noch eine neue Web Adapter Version machen weil ist eigentlich gefixt in socket classes aber dafür müsste web Adapter neu installiert oder geupdated werden.

Ab morgen sollte eine neue Release von web / ws / socketio im stable angeboten werden, die dieses Problem (invalid bindings in vis) fixed. Danke an @foxriver76 für die schnelle Release.

oFbEQnpoLKKl6mbY5e13

@foxriver76

MQTT-Client crashed wegen eines falschen Zeichens.

2023-09-14 23:26:08.910  - [32minfo[39m: host.iobroker instance system.adapter.mqtt-client.0 started with pid 3149
2023-09-14 23:26:11.236  - [32minfo[39m: mqtt-client.0 (3149) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2023-09-14 23:26:11.348  - [32minfo[39m: mqtt-client.0 (3149) starting. Version 1.6.4 in /opt/iobroker/node_modules/iobroker.mqtt-client, node: v18.16.0, js-controller: 5.0.12
2023-09-14 23:26:12.408  - [32minfo[39m: mqtt-client.0 (3149) Try to connect to mqtt://admin:*******************@192.168.0.6:1883?clientId=mqtt-client.0.iobroker
2023-09-14 23:26:12.625  - [31merror[39m: mqtt-client.0 (3149) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-09-14 23:26:12.631  - [32minfo[39m: mqtt.0 (456) Client [mqtt-client.0.iobroker] connected with secret 1694726772485_8486
2023-09-14 23:26:12.626  - [31merror[39m: mqtt-client.0 (3149) unhandled promise rejection: The pattern "io.mqtt-client.0.stat.� 0� stat.tasmota_95F" is not a valid ID pattern
2023-09-14 23:26:12.628  - [31merror[39m: mqtt-client.0 (3149) Error: The pattern "io.mqtt-client.0.stat.� 0� stat.tasmota_95F" is not a valid ID pattern
    at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2186:15)
    at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/build/lib/states/statesInRedisClient.js:865:100)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-09-14 23:26:12.628  - [31merror[39m: mqtt-client.0 (3149) The pattern "io.mqtt-client.0.stat.� 0� stat.tasmota_95F" is not a valid ID pattern
2023-09-14 23:26:12.654  - [32minfo[39m: mqtt-client.0 (3149) connected to broker
2023-09-14 23:26:12.745  - [32minfo[39m: mqtt.0 (456) Client [mqtt-client.0.iobroker] subscribes on "mqtt.0.tele.tasmota_85D39A.STATE"
2023-09-14 23:26:13.199  - [32minfo[39m: mqtt-client.0 (3149) terminating
2023-09-14 23:26:13.202  - [33mwarn[39m: mqtt-client.0 (3149) Terminated (UNCAUGHT_EXCEPTION): Without reason
.
.
.
2023-09-14 23:26:14.110  - [32minfo[39m: mqtt.0 (456) Client [mqtt-client.0.iobroker] publishOnSubscribe send all known states
2023-09-14 23:26:14.158  - [32minfo[39m: mqtt.0 (456) Client [mqtt-client.0.iobroker] connection closed: disconnected
2023-09-14 23:26:14.366  - [32minfo[39m: mqtt-client.0 (3149) terminating with timeout
2023-09-14 23:26:14.934  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_341527.LWT: DB closed
2023-09-14 23:26:14.935  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_A36501.STATUS6: DB closed
2023-09-14 23:26:14.936  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_9E62C6.STATUS: DB closed
2023-09-14 23:26:14.936  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_56D73B.INFO3: DB closed
2023-09-14 23:26:14.937  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_A36501.LWT: DB closed
2023-09-14 23:26:14.938  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_3F8AD6.LWT: DB closed
2023-09-14 23:26:14.938  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_85CD09.STATUS: DB closed
2023-09-14 23:26:14.939  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_A36501.POWER2: DB closed
2023-09-14 23:26:14.940  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_95FE9E.STATE: DB closed
2023-09-14 23:26:14.941  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_7E7404.STATUS4: DB closed
2023-09-14 23:26:14.942  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_990526.UPGRADE: DB closed
2023-09-14 23:26:14.942  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_4CC022.STATUS4: DB closed
2023-09-14 23:26:14.943  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_63E60D.RESULT: DB closed
2023-09-14 23:26:14.944  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_4E489B.STATUS11: DB closed
2023-09-14 23:26:14.944  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_53EAB0.STATUS6: DB closed
2023-09-14 23:26:14.945  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_4E4778.STATUS4: DB closed
2023-09-14 23:26:14.945  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_9E62C6.INFO2: DB closed
2023-09-14 23:26:14.946  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tasmota.discovery.840D8E5E4526.config: DB closed
2023-09-14 23:26:14.947  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_BB868C.STATUS3: DB closed
2023-09-14 23:26:14.948  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_990210.INFO3: DB closed
2023-09-14 23:26:14.948  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_BEB72E.STATUS4: DB closed
2023-09-14 23:26:14.949  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_A36501.STATE: DB closed
2023-09-14 23:26:14.949  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_FD2178.STATE: DB closed
2023-09-14 23:26:14.950  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_5E4526.STATUS4: DB closed
2023-09-14 23:26:14.951  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.tele.tasmota_3F8AD6.SENSOR: DB closed
2023-09-14 23:26:14.952  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_95FE9E.STATUS4: DB closed
2023-09-14 23:26:14.953  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_53EAB0.STATUS1: DB closed
2023-09-14 23:26:14.953  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_41CB86.POWER: DB closed
2023-09-14 23:26:14.954  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_59618E.STATUS7: DB closed
2023-09-14 23:26:14.954  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_3F8C42.RESULT: DB closed
2023-09-14 23:26:14.955  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_3F8C42.STATUS6: DB closed
2023-09-14 23:26:14.955  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_990576.STATUS4: DB closed
2023-09-14 23:26:14.956  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_3F8AD6.UPGRADE: DB closed
2023-09-14 23:26:14.956  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_95F446.STATUS4: DB closed
2023-09-14 23:26:14.957  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_41CB86.STATUS2: DB closed
2023-09-14 23:26:14.958  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_53EAB0.UPGRADE: DB closed
2023-09-14 23:26:14.963  - [33mwarn[39m: mqtt-client.0 (3149) DB closed
2023-09-14 23:26:14.964  - [33mwarn[39m: mqtt-client.0 (3149) Could not perform strict object check of state mqtt-client.0.stat.tasmota_98FD5F.STATUS10: DB closed
2023-09-14 23:26:15.262  - [31merror[39m: mqtt-client.0 (3149) Cannot check object existence of "mqtt-client.0.info.connection": Connection is closed.
2023-09-14 23:26:15.271  - [32minfo[39m: mqtt-client.0 (3149) terminating
2023-09-14 23:26:15.393  - [31merror[39m: host.iobroker Caught by controller[0]: [ioredis] Unhandled error event: Error: write EPIPE
2023-09-14 23:26:15.394  - [31merror[39m: host.iobroker Caught by controller[0]:     at afterWriteDispatched (node:internal/stream_base_commons:160:15)
2023-09-14 23:26:15.394  - [31merror[39m: host.iobroker Caught by controller[0]:     at writeGeneric (node:internal/stream_base_commons:151:3)
2023-09-14 23:26:15.394  - [31merror[39m: host.iobroker Caught by controller[0]:     at Socket._writeGeneric (node:net:930:11)
2023-09-14 23:26:15.394  - [31merror[39m: host.iobroker Caught by controller[0]:     at Socket._write (node:net:942:8)
2023-09-14 23:26:15.395  - [31merror[39m: host.iobroker Caught by controller[0]:     at writeOrBuffer (node:internal/streams/writable:392:12)
2023-09-14 23:26:15.395  - [31merror[39m: host.iobroker Caught by controller[0]:     at _write (node:internal/streams/writable:333:10)
2023-09-14 23:26:15.395  - [31merror[39m: host.iobroker Caught by controller[0]:     at Writable.write (node:internal/streams/writable:337:10)
2023-09-14 23:26:15.395  - [31merror[39m: host.iobroker Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:679:33)
2023-09-14 23:26:15.396  - [31merror[39m: host.iobroker Caught by controller[0]:     at Redis.publish (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2023-09-14 23:26:15.396  - [31merror[39m: host.iobroker Caught by controller[0]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/build/lib/states/statesInRedisClient.js:610:35)
2023-09-14 23:26:15.396  - [31merror[39m: host.iobroker instance system.adapter.mqtt-client.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-09-14 23:26:15.396  - [32minfo[39m: host.iobroker Restart adapter system.adapter.mqtt-client.0 because enabled

foxriver76

@ofbeqnpolkkl6mby5e13 müssen wir im adapter fixen

oFbEQnpoLKKl6mbY5e13

@foxriver76

Soll ich Issue erstellen?

NEWS

js-controller 5.0.x jetzt für alle User im STABLE!

Support us

940
Online

30.5k
Users

76.7k
Topics

1.2m
Posts

NEWS

js-controller 5.0.x jetzt für alle User im STABLE!

Support us

940Online

30.5kUsers

76.7kTopics

1.2mPosts

940
Online

30.5k
Users

76.7k
Topics

1.2m
Posts