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

[apollon77]

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

[JohGre]

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

[surfer09]

Bei mir hat auch alles funktioniert. Danke!

[mcm1957]

This post is deleted!

[Thomas Braun]

@mcm57

Dann kannst du ja den Eintrag dazu ändern:

enigma2 - required: none - not at stable yet

[mcm1957]

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

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

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

[oFbEQnpoLKKl6mbY5e13]

@foxriver76

MQTT-Client crashed wegen eines falschen Zeichens.

2023-09-14 23:26:08.910  - 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

[foxriver76]

@ofbeqnpolkkl6mby5e13 müssen wir im adapter fixen

[oFbEQnpoLKKl6mbY5e13]

@foxriver76

Soll ich Issue erstellen?

[foxriver76]

@ofbeqnpolkkl6mby5e13 ja sehr gerne

[oFbEQnpoLKKl6mbY5e13]

@foxriver76

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

RP70DP created this issue in iobroker-community-adapters/ioBroker.mqtt-client

closed JS-Controller 5.0.12: Adapter is crashing because of a wrong pattern #233

[Krisiun]

@ofbeqnpolkkl6mby5e13
Ja bitte wobei ich weiß nicht was ich damit anfangen soll. Irgend wie will mir niemand das ganze hier erklären obwohl ich möchte das alles verstehen. Vielen Dank.

[Thomas Braun]

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

Irgend wie will mir niemand das ganze hier erklären obwohl ich möchte das alles verstehen.

In diesem Thread geht es um Auffälligkeiten/Probleme/Beobachtungen im Rahmen der Veröffentlichung des js-controller 5 als Stabile Version.
@oFbEQnpoLKKl6mbY5e13 hat offenbar da was mit dem Adaper mqtt-client gefunden und das hier vermerkt.

Hat mit deiner veralteten Beta-Version, die nicht auf js-controller angepasst war, nichts zu tun.

[Krisiun]

@thomas-braun
Das klingt jetzt bestimmt komisch weil viele das selber immer schreiben aber da bin ich der nächste der einfach nur sagt : VIELEN DANK

[oFbEQnpoLKKl6mbY5e13]

@foxriver76

Scheint im MQTT-Adapter selbst auch nicht komplett abgefangen zu werden:

2023-09-15 00:37:44.321  - error: mqtt.0 (456) Client [DVES_990210] Cannot parse "stat/tasmota_990210/STATUS11": {"StatusSTS":{"Time":"2023-09-14T23:37:34","Uptime":"100T16:49:22","UptimeSec":8700562,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":24,"POWER":"OFF","Wifi":{"AP":1,"SSId":"***","BSSId":"***","Channel":1,"Mode":"11n","RSSI":62,"Signal":-69,"LinkCount":8,"Downtime":"0T00� stat/t

[Krisiun]

@ofbeqnpolkkl6mby5e13
hmm? keine ahnung aber bis jetzt geht alles. Vielen vielen Dank.

[Fabio]

@foxriver76 ich habe seit heute morgen das Problem das ich keine Skripte exportieren kann.

host.nuc
2023-09-15 07:46:19.842	warn	Saving in binary state "system.host.nuc.zip.2023-09-15-scripts.zip" is deprecated. Please add the "fileStorageNamespace" attribute to request (with e.g. "admin.0" value) to save ZIP in file as "zip/2023-09-15-scripts.zip"

System ist auf dem neusten Stand.
Grüße
Fabio

[Walter White]

@fa-bio Same, hier geht es auch nicht mehr, anscheinend seit dem Update:

host.DietPi
2023-09-15 08:14:23.184	warn	Saving in binary state "system.host.DietPi.zip.2023-09-15-scripts.zip" is deprecated. Please add the "fileStorageNamespace" attribute to request (with e.g. "admin.0" value) to save ZIP in file as "zip/2023-09-15-scripts.zip"

[wendy2702]

Gerade mal probiert.

JS Controller 5.0.12
Javascript 7.1.4
Firefox

Export hat problemlos funktioniert. Export Datei trägt folgenden Namen: 2023-09-15-scripts.zip

[oFbEQnpoLKKl6mbY5e13]

@fa-bio

7.1.1 (2023-06-20)  (bluefox) corrected the script export

Vermute ich dann mal, denn mit 7.0.3 geht es bei mir auch nicht.