Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 5.0.x jetzt für alle User im STABLE!

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.1k
  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k
  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.1k

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

Scheduled Pinned Locked Moved ioBroker Allgemein
js-controllerstableupgrade
509 Posts 82 Posters 139.1k Views 65 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • mcm1957M mcm1957

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

    mcm1957M Offline
    mcm1957M Offline
    mcm1957
    wrote on last edited by
    #21

    @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.

    JohGreJ 2 Replies Last reply
    1
    • liv-in-skyL 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

      Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      wrote on last edited by
      #22

      @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.

      Linux-Werkzeugkasten:
      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
      NodeJS Fixer Skript:
      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

      liv-in-skyL 1 Reply Last reply
      0
      • mcm1957M 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.

        JohGreJ Offline
        JohGreJ Offline
        JohGre
        wrote on last edited by
        #23

        @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  - error: ham.0 (35321) Error: Library homebridge-balboa-spa@2.2.6 not installed after 3 attempts

        nuc i5: RaspberryMatic, ioBroker, pi-hole, SQL-Server, OMV-NAS, Influx-DB & Grafana, OpenHab, tasmoadmin

        mcm1957M apollon77A 2 Replies Last reply
        0
        • liv-in-skyL 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

          foxriver76F Offline
          foxriver76F Offline
          foxriver76
          Developer
          wrote on last edited by
          #24

          @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.

          Videotutorials & mehr

          Hier könnt ihr mich unterstützen.

          liv-in-skyL mcm1957M 3 Replies Last reply
          0
          • foxriver76F 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-skyL Offline
            liv-in-skyL Offline
            liv-in-sky
            wrote on last edited by
            #25

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

            nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

            1 Reply Last reply
            0
            • JohGreJ 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  - error: ham.0 (35321) Error: Library homebridge-balboa-spa@2.2.6 not installed after 3 attempts
              mcm1957M Offline
              mcm1957M Offline
              mcm1957
              wrote on last edited by
              #26

              @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  - error: 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?

              1 Reply Last reply
              0
              • Thomas BraunT 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.

                liv-in-skyL Offline
                liv-in-skyL Offline
                liv-in-sky
                wrote on last edited by
                #27

                @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 🙂

                nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

                Thomas BraunT 1 Reply Last reply
                0
                • liv-in-skyL 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 BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  wrote on last edited by Thomas Braun
                  #28

                  @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...

                  Linux-Werkzeugkasten:
                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                  NodeJS Fixer Skript:
                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                  1 Reply Last reply
                  0
                  • foxriver76F 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-skyL Offline
                    liv-in-skyL Offline
                    liv-in-sky
                    wrote on last edited by
                    #29

                    @foxriver76
                    @Thomas-Braun

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

                    erstmal danke

                    nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

                    1 Reply Last reply
                    0
                    • JohGreJ 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  - error: ham.0 (35321) Error: Library homebridge-balboa-spa@2.2.6 not installed after 3 attempts
                      apollon77A Online
                      apollon77A Online
                      apollon77
                      wrote on last edited by
                      #30

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

                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                      JohGreJ 1 Reply Last reply
                      0
                      • apollon77A apollon77

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

                        JohGreJ Offline
                        JohGreJ Offline
                        JohGre
                        wrote on last edited by
                        #31

                        @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.

                        nuc i5: RaspberryMatic, ioBroker, pi-hole, SQL-Server, OMV-NAS, Influx-DB & Grafana, OpenHab, tasmoadmin

                        surfer09S 1 Reply Last reply
                        0
                        • JohGreJ 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.

                          surfer09S Offline
                          surfer09S Offline
                          surfer09
                          wrote on last edited by
                          #32

                          Bei mir hat auch alles funktioniert. Danke! 😉

                          IO-Broker Master/Slave auf Windows 11 64bit, NPM 11.6.1, Node 22.21.1 js-controller 7.0.7

                          1 Reply Last reply
                          0
                          • mcm1957M mcm1957

                            This post is deleted!

                            mcm1957M Offline
                            mcm1957M Offline
                            mcm1957
                            wrote on last edited by mcm1957
                            #33
                            This post is deleted!
                            Thomas BraunT 1 Reply Last reply
                            0
                            • mcm1957M mcm1957

                              This post is deleted!

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              wrote on last edited by
                              #34

                              @mcm57

                              Dann kannst du ja den Eintrag dazu ändern:

                              ⚪ enigma2 - required: none - not at stable yet

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              1 Reply Last reply
                              0
                              • foxriver76F 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.

                                mcm1957M Offline
                                mcm1957M Offline
                                mcm1957
                                wrote on last edited by
                                #35

                                @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.

                                KrisiunK 1 Reply Last reply
                                1
                                • foxriver76F foxriver76

                                  Hallo ioBroker-Community,

                                  Heute möchten wir Euch den js-controller 5.0 endlich auch im STABLE Repository zur Verfügung stellen. Dieser Post enthält alle wichtigen Infos. Bitte unbedingt lesen!!
                                  Wir bedanken uns bei allen Usern die bisher die neue Version bereits als Alpha oder Beta getestet und Feedback gegeben haben.

                                  Node.js Versions-Anforderungen
                                  In diesem Release entfällt Node.js 12.x welches seit April letztem Jahr nicht mehr gepflegt wird und Node.js 14.x welches seit April diesem Jahres EOL ist. Node.js 18.x ist dazugekommen. Die unterstützten Node.js Versionen sind: 16.4.0+ und 18.x und nach aktuellem Stand Node.js 20.x, wobei hier noch erfahrungen fehlen. Die empfohlene Node.js Version für ioBroker haben wir vor kurzem auf 18.x angehoben.
                                  Bitte beachtet weiterhin bei Node.js Updates die Anleitung im Forum unter https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-14-16-und-18 !

                                  Informationen zur Version
                                  Es gibt EINIGE Adapter die aktualisiert werden müssen!! Bitte weiter unten lesen!

                                  In dieser Version wurde die Umstellung des Quellcodes auf TypeScript sehr stark vorangetrieben (inzwischen bei 88%), wodurch am Ende die Stabilität weiter steigt weil viele Code-Fehler nicht mehr auftreten können. Natürlich sind neben Optimierungen und Fehlerbehebungen auch ein paar neue Features hinzugekommen. Auch wenn mit dieser Version keine neuen Prüfungen hinzukommen, die zu Log-Ausgaben bei Adaptern führen, meldet aktuelle Logausgaben bitte weiterhin bei den Adaptern.

                                  Detailliertere Informationen zu allen Änderungen und Features findet Ihr weiter unten und im Changelog.

                                  Für die aktive Mitarbeit an dieser Version des js-controller bedanke mich diesmal wieder besonders bei Apollon77, AlCalzone und natürlich Bluefox und auch ein paar weiteren Entwicklern!

                                  ACHTUNG backups inkompatibel bei Downgrades!!

                                  Neben der Node.js Version gibt es eine wichtige Inkompatibilität: Backups die mit der 5.0 des js-controller erstellt wurden lassen sich nicht mit einem js-controller 4 oder kleiner wieder restoren!

                                  Darüber hinaus ist der js-controller 5.0 generell kompatibel mit allen bestehenden ioBroker-Systemen. Ein Update von der 2.0/2.1/2.2/3.x ist problemlos möglich. Wir empfehlen allerings vor dem Update auf die 5.0 idealerweise ein Update auf die 4.0 und vorher auf 3.3.x durchzuführen, da ein Downgrade nach einem erfolgten Update nur auf eine 3.3.x möglich ist (siehe FAQ)! Nur die Node.js Version muss weiterhin mindestens 16.x sein, wie oben bereits ausgeführt. Wer überlegt die Node.js Version anzuheben bitte weiter unten im Abschnitt "Was ist zu testen" lesen 🙂

                                  Aufgrund einiger internen Umstellungen brauchen wieder einige Adapter Updates. Diese sollten am besten VOR dem Update installiert werden!
                                  Bitte dazu die Informationen weiter unten beachten!

                                  Installation

                                  VOR der Installation

                                  Wie bei jedem Upgrade dieser Art: Bitte macht ein Backup! iobroker backup bzw kopieren des iobroker-data Verzeichnisses reichen an sich aus. Bitte nicht das node_modules Verzeichnis einfach kopieren, da sonst symbolische Links kaputt gehen können, was zu größeren Problemen danach führt. Eine alte 4.0.x-Version des js-controller kann im Notfall einfach wieder per npm install iobroker.js-controller@version ("version" durch die gewünschte Versionsnummer ersetzen) installiert werden und sollte alles wieder herstellen (Vorheriger Stable Stand ist die 4.0.24)

                                  Nötige Adapter-Aktualisierungen

                                  Am besten dennoch VOR dem js-controller Update alle verfügbaren Adapter-Updates prüfen und alle Updates installieren, die im Changelog auf Optimierungen oder Anpassungen für den js-controller 4.0 oder höher hinweisen.

                                  Diesmal sind doch einige Adapter auf der Liste die man updaten muss -falls installiert! Siehe Spoiler!

                                  • ✅ acme - required: none / 0.1.0 - released
                                  • ✅ admin - required: 6.8.0 - released
                                  • ✅ anelhut - required: 1.0.15 - released
                                  • ✅b-control-em - required: 0.3.1 - released
                                  • ⚪ bosch-ebike - required: none
                                  • ✅ cul - required: 2.2.0 - released (no change)
                                  • ✅ daikin-cloud - required: 0.3.0 - released
                                  • ✅ doorbird - required: 0.1.7 - newer released
                                  • ✅ ds18b20 - required: 2.0.4 - released
                                  • ✅ energymanager - required: 1.4.2 - released
                                  • ⚪ enigma2 - required: none - not at stable yet
                                  • ✅ fakeroku - required: 0.2.2+ - released
                                  • ✅ fhem - required: 2.0.5 - released
                                  • ✅ history - required: 2.2.6 - released
                                  • ✅ iqontrol - required: 2.3.0 - released
                                  • ⚪ javascript - required: none
                                  • 🚫 km200 - deprecated - Ersatz: ems-esp
                                  • ✅ lgtv - required: 1.1.12 - released
                                  • ❗linux-control - required: ???
                                  • ✅ maxcul - required: 1.3.1 (no change)
                                  • ⚪ miio - required: none - not at stable
                                  • ✅ mydlink - required: 1.3.4 - released
                                  • ✅ nanoleaf-lightpanales - required: 1.4.0 - released
                                  • ✅ node-red - required: 4.03+ (no change)
                                  • ✅ notification.manager - required: 0.1.1 - released
                                  • ✅ pi-hole - required: 1.3.6+ - released
                                  • ✅ ping - required: 1.6.2 - released
                                  • ✅ pushbullet - required: 1.0.1 - released
                                  • 🚫 samsung_tyzen - stale repo - deprecated with js-controller 5
                                  • ✅ socketio - required: 6.5.2 - released
                                  • ✅ stiebel-isg - required: 1.7.6+ - newer released
                                  • ✅ systeminfo - required: 1.0.0 - released
                                  • ✅ viessmann - required: 1.4.4+ - released
                                  • ✅ web - required: 6.1.0 - released
                                  • ✅ ws - required: 2.5.3 - released
                                  • ✅yahka - required: 1.0.1 - newer version released
                                  • ✅ zigbee - required: 1.8.23 - released
                                  Achtung: MASTER-Systeme Reihenfolgen beachten!

                                  Bei einem Multi-Host-System, welches auf js-controller 2.2, 3.x oder 4.0.x läuft, ist es beim Update auf Version 5.0 empfohlen, zuerst das Master-System zu aktualisieren. Der Master muss dann wieder gestartet werden. Die Slaves werden danach aktualisiert!

                                  Bei Updates von Master/Slave-Systemen mit js-controller 1.5 oder früher Bitte die jeweiligen Update Threads der empfohlenen Zwischenversionen prüfen.

                                  Windows
                                  Generell muss das Update manuell via npm installiert werden.

                                  Hierzu im ioBroker-Verzeichnis nach stoppen des ioBroker den Befehl iob upgrade self ausführen.

                                  Linux

                                  • ioBroker stoppen (iobroker stop)
                                  • Prüfen das keine Prozesse (Adapter, Backups) mehr laufen (ps auxww|grep io und auch ps auxww|grep backup ). Es passiert manchmal das trotz dem Stoppen noch Zombies zurückbleiben
                                  • cd /opt/iobroker
                                  • Das Update erfolgt via iob upgrade self
                                  • ioBroker starten (iobroker start)

                                  Bei Fehlern:
                                  Wenn bei der Installation Fehler wegen fehlender Zugriffsrechte auftreten, am besten den Installation-Fixer (iobroker fix wer schon einen js-controller 2.x oder höher hat, alternativ weiterhin manuell via curl -sL https://iobroker.net/fix.sh | bash -) nutzen und die Installation wiederholen.
                                  Falls es auch danach noch Fehler gibt, bitte die Installation erneut mittels sudo -H -u iobroker npm install iobroker.js-controller versuchen. Bitte berichtet solche Fälle hier im Thread.

                                  NACH der Installation

                                  Wenn alles klappt merkt Ihr ausser der höheren Versionsnummer in der Host-Ansicht im Admin keinen Unterschied. Alles funktioniert weiterhin wie vorher. Alle Adapterinstanzen starten und funktionieren. Wenn das so ist hat alles geklappt.

                                  Falls im Log Warn-Meldungen auftauchen mit dem Hinweis diese an den Entwickler zu senden, dann bitte schauen welcher Adapter es ist und entsprechend dort Issues bitte anlegen!

                                  Was hat sich geändert, was besonders ansehen/beachten?

                                  Neben einiger weiterer Bugfixes gibt es folgende Änderungen und Fixes zu erwähnen:

                                  • generell siehe Changelog, speziell auch für die Features
                                  • generell bitte im CLI und auch sonst überall drüber schauen. Die Typescript Umstellungen haben sehr viel Code angefasst.
                                  • Falls jemand sporadisch Alias Fehler im Log hatte bitte versuchen diese mit der neuen version wieder zu provoziere und rückmelden

                                  Speziell die Entwickler sollten bitte die genannten Deprecations und neuen Features anschauen und beachten.

                                  Wie bereits gesagt, viele Änderungen fanden hinter den Kulissen statt. Hier für Interessierte als Spoiler eine Zusammenfassung:

                                  5.0. Release Jana

                                  BREAKING CHANGES

                                  • Support for Node.js 12 and 14 is dropped! Supported are Node.js 16.4.0+ and 18.x and hopefully 20.x
                                  • Backups created with the new js-controller version cannot be restored on hosts with lower js-controller version!
                                  • Update recommended npm version to 8
                                  • Deprecate binary states, Adapters will change to use Files instead!

                                  Features

                                  • (foxriver76) Show npm error message on failing adapter installations and update also without debug parameter
                                  • (foxriver76) Introduce iobroker setting (dnsResolution) to choose between verbatim and ipv4 first dns resolution order
                                  • (foxriver76) Add support for windows for iob fix
                                  • (bluefox) Added CLI option to restart/start/stop all instances of an adapter (e.g. iob stop admin now also works)
                                  • (foxriver76) Allow to use iob host oldname command when new host already exists but has no instances
                                  • (foxriver76) Added an admin notification if redis is misconfigured and info how to fix it
                                  • (foxriver76) Enable upgrade of js-controller via Admin UI (Linux only)

                                  Optimizations and Fixes

                                  • (foxriver76) Speedup "getStates" calls with many IDs often used by visualizations: JSONL 17 times faster, Redis 23 times faster
                                  • (foxriver76) significantly reduce backup size
                                  • (foxriver76) Enhance CLI help for list command to show all possible types to list
                                  • (foxriver76) Also stop instances before updating from GitHub
                                  • (foxriver76) Conversion of big parts of the js-controller codebase to typeScript and address all found issues
                                  • (Apollon77) Only log error on "enable/disable via .alive" if there is an error
                                  • (foxriver76) Optimize adapter unload and stop handling for edge cases
                                  • (AlCalzone) Carefully normalize jsonlOptions
                                  • (bluefox) Do not show warning on a requested adapter stop/termination
                                  • (bluefox) Make sure that the first log line is not missing in Admin
                                  • (foxriver76) Fix wrong formatting of cli get binary state if no encoding is passed
                                  • (foxriver76) Fix restoring backups from pre js-controller 4.x which were created without config.system
                                  • (foxriver76) Preserve tier setting on adapter upload
                                  • (foxriver76) update apt sources before installing os dependencies
                                  • (foxriver76) Only skip erase on upload if opted out explicitly to always cleanup unneeded files
                                  • (foxriver76) Try to fix strange alias errors, inform us if it happens again!
                                  • (foxriver76) Remove windows bat files completely, installer will create them when needed
                                  • (AlCalzone/Apollon77) Update jsonl db to prevent locking issues
                                  • (foxriver76) Fixes iob file sync not working for jsonl
                                  • (foxriver76) Do not crash if we cannot initialize db backup directory on start
                                  • (foxriver76) Fixed issue with certificate validity on leap years
                                  • (Apollon77/foxriver76) Make sure that all relevant files are removed when eraseOnUpload is used
                                  • (foxriver76) fix wrong hostname after backup restore
                                  • (bluefox) allow CLI vendor update without explicitly specifying vendor file (default file is used)
                                  • (Apollon77, foxriver76, bluefox, AlCalzone) Several fixes and refactorings to prevent potential crash cases reported by Sentry and other sources

                                  Developer relevant DEPRECATIONS/WARNINGS

                                  • Deprecate binary states, Migrate your adapters to use Files instead!
                                  • If you need to access special js-controller common tools please use adapter-core instead of js-controller directly - see https://github.com/ioBroker/adapter-core#commontools
                                  • Parameter that contain patterns (e.g. mqtt.*) are now checked for allowed characters and general correctness!

                                  Developer relevant new Features

                                  • (bluefox) Added options to subscribe to file changes: subscribeForeignFiles, unsubscribeForeignFiles, onAdapterFileChanged (event contains id, fileName, size and not the whole content of the file!)

                                  • (foxriver76) Introduce on("install") handler for adapter which is automatically called when adapter process is started with --install

                                  • (foxriver76) Introduce io-package flag common.nodeProcessParams to allow to pass adapter specific nodejs process parameters (disables compact mode for the adapter!)

                                  • (foxriver76) Respect dns resolution (ipv4/ipv6 first) from config internally and provide relevant methods via adapter-core

                                  • (foxriver76) Add JSON-Schema for iobroker.json

                                  • (bluefox) Allowed export of password.js (to be used with adapter-core)

                                  • (bluefox) Added _design/chart to the system designs

                                  • (foxriver76) Automatically generated Code-Docs for Adapter class https://github.com/ioBroker/ioBroker.js-controller/tree/master/packages/controller/doc

                                  • (foxriver76) Added (foreign)objectExists to adapter methods

                                  • (bluefox) Extend getSuitableLicenses to look for other licenses

                                  • (buefox/foxriver76) Added new category for notifications: blocked and respect js-controller common.blockedVersions to block versions from starting

                                  • (bluefox) Added new system view "custom-full" to return the full objects for objects with a custom part and not only the custom details

                                  • (foxriver76) Added support for getForeignObjects with an array of strings as pattern

                                  • (AlCalzone) Preparations to allow js-controller Dev version to be used with dev-server

                                  • (foxriver76) Validate max timeout value (max 32bit max number) on setTimeout/setInterval and throw on error to prevent issues

                                  • (foxriver76) new io-package flag common.supportedMessages to replace messagebox and other messagebox-related properties

                                  • (foxriver76) adapter.sendTo now accepts an optional timeout argument

                                  • Developer relevant Optimizations and Fixes

                                  • (foxriver76) Ensure setObjectNotExists returns id on success

                                  • (foxriver76) Fix Typings for sendTo/sendToHost

                                  • (Bluefox) Add User permission check to requireLog

                                  • (foxriver76) added nonEdit property of objects to types and document functionality

                                  • (foxriver76) introduced constants for state quality

                                  • (foxriver76) subscribeStates now also accepts an array of ids

                                  • general dependency updates

                                  • code style optimizations and streamline code

                                  Generell ist zu testen, ob alles noch so funktioniert wie vorher auch. Das ist das wichtigste!

                                  Wie Fehler melden?

                                  Wer sich unsicher ist, ob ein Fehler vorliegt, sollte am besten hier im Thread das Problem beschreiben. So können wir alle versuchen, das Problem nachzuvollziehen und ggf. einzugrenzen.

                                  Sobald ein Fehler auftritt der in einer Fehlermeldung oder einen Crash mit Fehlerdetails im Log oder auf Kommandozeile endet, dann dazu am besten direkt ein GitHub-Issue im js-controller Projekt öffnen und zusätzlich hier im Thread posten. Je detaillierter die Angaben im Issue sind (genaue Fehlermeldungen/Logs, Infos zur OS- und Node.js-Umgebung sowie genaue Schritte zur Reproduktion des Problems), umso schneller können wir Fehler einkreisen und beheben.

                                  Bitte postet auch die Ausgabe von iob diag mit rein.

                                  Wir wünschen allen viel Spaß mit dem neuen Controller und vielen Dank für Eure Unterstützung!

                                  fox

                                  O Away
                                  O Away
                                  oFbEQnpoLKKl6mbY5e13
                                  wrote on last edited by oFbEQnpoLKKl6mbY5e13
                                  #36

                                  @foxriver76

                                  MQTT-Client crashed wegen eines falschen Zeichens.

                                  2023-09-14 23:26:08.910  - info: host.iobroker instance system.adapter.mqtt-client.0 started with pid 3149
2023-09-14 23:26:11.236  - info: 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  - info: 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  - info: 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  - error: 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  - info: mqtt.0 (456) Client [mqtt-client.0.iobroker] connected with secret 1694726772485_8486
2023-09-14 23:26:12.626  - error: 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  - error: 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  - error: 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  - info: mqtt-client.0 (3149) connected to broker
2023-09-14 23:26:12.745  - info: mqtt.0 (456) Client [mqtt-client.0.iobroker] subscribes on "mqtt.0.tele.tasmota_85D39A.STATE"
2023-09-14 23:26:13.199  - info: mqtt-client.0 (3149) terminating
2023-09-14 23:26:13.202  - warn: mqtt-client.0 (3149) Terminated (UNCAUGHT_EXCEPTION): Without reason
.
.
.
2023-09-14 23:26:14.110  - info: mqtt.0 (456) Client [mqtt-client.0.iobroker] publishOnSubscribe send all known states
2023-09-14 23:26:14.158  - info: mqtt.0 (456) Client [mqtt-client.0.iobroker] connection closed: disconnected
2023-09-14 23:26:14.366  - info: mqtt-client.0 (3149) terminating with timeout
2023-09-14 23:26:14.934  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: mqtt-client.0 (3149) DB closed
2023-09-14 23:26:14.964  - warn: 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  - error: mqtt-client.0 (3149) Cannot check object existence of "mqtt-client.0.info.connection": Connection is closed.
2023-09-14 23:26:15.271  - info: mqtt-client.0 (3149) terminating
2023-09-14 23:26:15.393  - error: host.iobroker Caught by controller[0]: [ioredis] Unhandled error event: Error: write EPIPE
2023-09-14 23:26:15.394  - error: host.iobroker Caught by controller[0]:     at afterWriteDispatched (node:internal/stream_base_commons:160:15)
2023-09-14 23:26:15.394  - error: host.iobroker Caught by controller[0]:     at writeGeneric (node:internal/stream_base_commons:151:3)
2023-09-14 23:26:15.394  - error: host.iobroker Caught by controller[0]:     at Socket._writeGeneric (node:net:930:11)
2023-09-14 23:26:15.394  - error: host.iobroker Caught by controller[0]:     at Socket._write (node:net:942:8)
2023-09-14 23:26:15.395  - error: host.iobroker Caught by controller[0]:     at writeOrBuffer (node:internal/streams/writable:392:12)
2023-09-14 23:26:15.395  - error: host.iobroker Caught by controller[0]:     at _write (node:internal/streams/writable:333:10)
2023-09-14 23:26:15.395  - error: host.iobroker Caught by controller[0]:     at Writable.write (node:internal/streams/writable:337:10)
2023-09-14 23:26:15.395  - error: 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  - error: 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  - error: 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  - error: host.iobroker instance system.adapter.mqtt-client.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-09-14 23:26:15.396  - info: host.iobroker Restart adapter system.adapter.mqtt-client.0 because enabled

                                  mqtt2.PNG

                                  foxriver76F 1 Reply Last reply
                                  0
                                  • O oFbEQnpoLKKl6mbY5e13

                                    @foxriver76

                                    MQTT-Client crashed wegen eines falschen Zeichens.

                                    2023-09-14 23:26:08.910  - info: host.iobroker instance system.adapter.mqtt-client.0 started with pid 3149
2023-09-14 23:26:11.236  - info: 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  - info: 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  - info: 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  - error: 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  - info: mqtt.0 (456) Client [mqtt-client.0.iobroker] connected with secret 1694726772485_8486
2023-09-14 23:26:12.626  - error: 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  - error: 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  - error: 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  - info: mqtt-client.0 (3149) connected to broker
2023-09-14 23:26:12.745  - info: mqtt.0 (456) Client [mqtt-client.0.iobroker] subscribes on "mqtt.0.tele.tasmota_85D39A.STATE"
2023-09-14 23:26:13.199  - info: mqtt-client.0 (3149) terminating
2023-09-14 23:26:13.202  - warn: mqtt-client.0 (3149) Terminated (UNCAUGHT_EXCEPTION): Without reason
.
.
.
2023-09-14 23:26:14.110  - info: mqtt.0 (456) Client [mqtt-client.0.iobroker] publishOnSubscribe send all known states
2023-09-14 23:26:14.158  - info: mqtt.0 (456) Client [mqtt-client.0.iobroker] connection closed: disconnected
2023-09-14 23:26:14.366  - info: mqtt-client.0 (3149) terminating with timeout
2023-09-14 23:26:14.934  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: 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  - warn: mqtt-client.0 (3149) DB closed
2023-09-14 23:26:14.964  - warn: 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  - error: mqtt-client.0 (3149) Cannot check object existence of "mqtt-client.0.info.connection": Connection is closed.
2023-09-14 23:26:15.271  - info: mqtt-client.0 (3149) terminating
2023-09-14 23:26:15.393  - error: host.iobroker Caught by controller[0]: [ioredis] Unhandled error event: Error: write EPIPE
2023-09-14 23:26:15.394  - error: host.iobroker Caught by controller[0]:     at afterWriteDispatched (node:internal/stream_base_commons:160:15)
2023-09-14 23:26:15.394  - error: host.iobroker Caught by controller[0]:     at writeGeneric (node:internal/stream_base_commons:151:3)
2023-09-14 23:26:15.394  - error: host.iobroker Caught by controller[0]:     at Socket._writeGeneric (node:net:930:11)
2023-09-14 23:26:15.394  - error: host.iobroker Caught by controller[0]:     at Socket._write (node:net:942:8)
2023-09-14 23:26:15.395  - error: host.iobroker Caught by controller[0]:     at writeOrBuffer (node:internal/streams/writable:392:12)
2023-09-14 23:26:15.395  - error: host.iobroker Caught by controller[0]:     at _write (node:internal/streams/writable:333:10)
2023-09-14 23:26:15.395  - error: host.iobroker Caught by controller[0]:     at Writable.write (node:internal/streams/writable:337:10)
2023-09-14 23:26:15.395  - error: 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  - error: 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  - error: 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  - error: host.iobroker instance system.adapter.mqtt-client.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-09-14 23:26:15.396  - info: host.iobroker Restart adapter system.adapter.mqtt-client.0 because enabled

                                    mqtt2.PNG

                                    foxriver76F Offline
                                    foxriver76F Offline
                                    foxriver76
                                    Developer
                                    wrote on last edited by
                                    #37

                                    @ofbeqnpolkkl6mby5e13 müssen wir im adapter fixen

                                    Videotutorials & mehr

                                    Hier könnt ihr mich unterstützen.

                                    O 3 Replies Last reply
                                    0
                                    • foxriver76F foxriver76

                                      @ofbeqnpolkkl6mby5e13 müssen wir im adapter fixen

                                      O Away
                                      O Away
                                      oFbEQnpoLKKl6mbY5e13
                                      wrote on last edited by
                                      #38

                                      @foxriver76

                                      Soll ich Issue erstellen?

                                      foxriver76F KrisiunK 2 Replies Last reply
                                      0
                                      • O oFbEQnpoLKKl6mbY5e13

                                        @foxriver76

                                        Soll ich Issue erstellen?

                                        foxriver76F Offline
                                        foxriver76F Offline
                                        foxriver76
                                        Developer
                                        wrote on last edited by
                                        #39

                                        @ofbeqnpolkkl6mby5e13 ja sehr gerne

                                        Videotutorials & mehr

                                        Hier könnt ihr mich unterstützen.

                                        1 Reply Last reply
                                        0
                                        • foxriver76F foxriver76

                                          @ofbeqnpolkkl6mby5e13 müssen wir im adapter fixen

                                          O Away
                                          O Away
                                          oFbEQnpoLKKl6mbY5e13
                                          wrote on last edited by
                                          #40

                                          @foxriver76

                                          https://github.com/iobroker-community-adapters/ioBroker.mqtt-client/issues/233

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          247

                                          Online

                                          32.4k

                                          Users

                                          81.4k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe