UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[arminrey]

Hallo die das lesen.

Finde leider den Fehler nicht. Ich schätze nach Update Node.js

CPU: 2,5 %
RAM: 86 %
Betriebszeit: 11h
Verfügbar: 7.0.6
Installiert: 7.0.6
Ereignisse: ⇥23 / ↦12
Plattform: Windows
Betriebssystem: win32
Architektur: x64
CPUs: 6
Geschwindigkeit: 1704 MHz
Modell: Intel(R) Core(TM) i5-8400T CPU @ 1.70GHz
RAM: 7.8 GB
System-Betriebszeit: 12:09:41
Node.js: v22.14.0
time: 1739437435275
timeOffset: -60
NPM: 10.9.2
Adapter-Anzahl: 553
Datenträgergröße: 235.5 GB
Freier Festplattenspeicher: 95.8 GB
Aktive Instanzen: 24
Pfad: C:\ioBroker\
Betriebszeit: 11:34:50

schmiert der Shelly Adapter ab.
Auffällig ist, dass sich der RAM bei dem Shelly sehr schnell auf über 1.000 MB aufschaukelt.

Hier noch ein Auszug der log:

2025-02-13 10:18:20.676  - info: shelly.0 (88316) [CoAP] Device 192.168.1.210 (shellyplug-s / shellyplug-s-8CAAB5EB716F / SHPLG-S#8CAAB5EB716F#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:21.883  - info: shelly.0 (88316) [CoAP] Device 192.168.1.148 (shellyswitch25 / shellyswitch25-C45BBE769192 / SHSW-25#C45BBE769192#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:22.908  - info: shelly.0 (88316) [CoAP] Device 192.168.1.140 (shellyplug-s / shellyplug-s-E868E76EE9D8 / SHPLG-S#E868E76EE9D8#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:24.565  - info: shelly.0 (88316) [CoAP] Device 192.168.1.147 (shellyplug-s / shellyplug-s-3C6105DDADDF / SHPLG-S#3C6105DDADDF#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:24.737  - info: shelly.0 (88316) [CoAP] Device 192.168.1.135 (shellyplug-s / shellyplug-s-8CAAB5EA6912 / SHPLG-S#8CAAB5EA6912#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:24.778  - info: shelly.0 (88316) [CoAP] Device 192.168.1.130 (shellyplug-s / shellyplug-s-4022D889B232 / SHPLG-S#4022D889B232#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:25.047  - info: shelly.0 (88316) [CoAP] Device 192.168.1.156 (shelly1pm / shelly1pm-E8DB84D24513 / SHSW-PM#E8DB84D24513#1) connected! Polltime set to 10 sec.
2025-02-13 10:20:04.419  - info: shelly.0 (88316) [CoAP] Device 192.168.1.121 (shellydw2 / shellydw2-E8DB84D4B3D4 / SHDW-2#E8DB84D4B3D4#1) connected! Polltime set to 3600 sec.
2025-02-13 10:20:38.178  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:39.843  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:39.844  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:39.845  - error: shelly.0 (88316) 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().
2025-02-13 10:20:39.845  - error: shelly.0 (88316) unhandled promise rejection: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:39.846  - error: shelly.0 (88316) ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
    at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:39.846  - error: shelly.0 (88316) Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:39.869  - info: shelly.0 (88316) terminating
2025-02-13 10:20:39.870  - warn: shelly.0 (88316) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-02-13 10:20:40.298  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:40.302  - error: shelly.0 (88316) 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().
2025-02-13 10:20:40.304  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:40.303  - error: shelly.0 (88316) unhandled promise rejection: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.303  - error: shelly.0 (88316) ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
    at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.303  - error: shelly.0 (88316) Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.309  - error: shelly.0 (88316) 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().
2025-02-13 10:20:40.309  - error: shelly.0 (88316) unhandled promise rejection: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.309  - error: shelly.0 (88316) ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
    at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.309  - error: shelly.0 (88316) Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.371  - info: shelly.0 (88316) terminating
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE 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:
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[1]: ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[1]:     at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[1]:     at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[2]: 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:
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[2]: ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[2]:     at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[2]:     at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[3]: 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:
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[3]: ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[3]:     at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[3]:     at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE instance system.adapter.shelly.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-02-13 10:20:40.561  - info: host.ADMINIS-ROKLDQE Restart adapter system.adapter.shelly.0 because enabled
2025-02-13 10:20:40.561  - warn: host.ADMINIS-ROKLDQE Do not restart adapter system.adapter.shelly.0 because restart loop detected

Kann mir da jemand einen Tipp geben. Eigentlich hatte ich noch nie Probleme mit Shelly (seit Jahren) aber jetzt ist mein Latein am Ende.

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

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

DANKE

Bitte ausfüllen:

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

Linux User bitte hier den Output von iob diag einfügen.Hallo die das lesen.

Finde leider den Fehler nicht. Ich schätze nach Update Node.js

CPU: 2,5 %
RAM: 86 %
Betriebszeit: 11h
Verfügbar: 7.0.6
Installiert: 7.0.6
Ereignisse: ⇥23 / ↦12
Plattform: Windows
Betriebssystem: win32
Architektur: x64
CPUs: 6
Geschwindigkeit: 1704 MHz
Modell: Intel(R) Core(TM) i5-8400T CPU @ 1.70GHz
RAM: 7.8 GB
System-Betriebszeit: 12:09:41
Node.js: v22.14.0
time: 1739437435275
timeOffset: -60
NPM: 10.9.2
Adapter-Anzahl: 553
Datenträgergröße: 235.5 GB
Freier Festplattenspeicher: 95.8 GB
Aktive Instanzen: 24
Pfad: C:\ioBroker\
Betriebszeit: 11:34:50

schmiert der Shelly Adapter ab.
Auffällig ist, dass sich der RAM bei dem Shelly sehr schnell auf über 1.000 MB aufschaukelt.

Hier noch ein Auszug der log:

2025-02-13 10:18:20.676  - info: shelly.0 (88316) [CoAP] Device 192.168.1.210 (shellyplug-s / shellyplug-s-8CAAB5EB716F / SHPLG-S#8CAAB5EB716F#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:21.883  - info: shelly.0 (88316) [CoAP] Device 192.168.1.148 (shellyswitch25 / shellyswitch25-C45BBE769192 / SHSW-25#C45BBE769192#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:22.908  - info: shelly.0 (88316) [CoAP] Device 192.168.1.140 (shellyplug-s / shellyplug-s-E868E76EE9D8 / SHPLG-S#E868E76EE9D8#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:24.565  - info: shelly.0 (88316) [CoAP] Device 192.168.1.147 (shellyplug-s / shellyplug-s-3C6105DDADDF / SHPLG-S#3C6105DDADDF#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:24.737  - info: shelly.0 (88316) [CoAP] Device 192.168.1.135 (shellyplug-s / shellyplug-s-8CAAB5EA6912 / SHPLG-S#8CAAB5EA6912#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:24.778  - info: shelly.0 (88316) [CoAP] Device 192.168.1.130 (shellyplug-s / shellyplug-s-4022D889B232 / SHPLG-S#4022D889B232#1) connected! Polltime set to 10 sec.
2025-02-13 10:18:25.047  - info: shelly.0 (88316) [CoAP] Device 192.168.1.156 (shelly1pm / shelly1pm-E8DB84D24513 / SHSW-PM#E8DB84D24513#1) connected! Polltime set to 10 sec.
2025-02-13 10:20:04.419  - info: shelly.0 (88316) [CoAP] Device 192.168.1.121 (shellydw2 / shellydw2-E8DB84D4B3D4 / SHDW-2#E8DB84D4B3D4#1) connected! Polltime set to 3600 sec.
2025-02-13 10:20:38.178  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:39.843  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:39.844  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:39.845  - error: shelly.0 (88316) 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().
2025-02-13 10:20:39.845  - error: shelly.0 (88316) unhandled promise rejection: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:39.846  - error: shelly.0 (88316) ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
    at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:39.846  - error: shelly.0 (88316) Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:39.869  - info: shelly.0 (88316) terminating
2025-02-13 10:20:39.870  - warn: shelly.0 (88316) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-02-13 10:20:40.298  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:40.302  - error: shelly.0 (88316) 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().
2025-02-13 10:20:40.304  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:62264 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at RedisHandler.<anonymous> (file:///C:/ioBroker/node_modules/@iobroker/db-objects-jsonl/src/lib/objects/objectsInMemServerRedis.js:597:29)
    at RedisHandler.emit (node:events:518:28)
    at RedisHandler.emit (node:domain:489:12)
    at Immediate._onImmediate (file:///C:/ioBroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37)
    at processImmediate (node:internal/timers:491:21)
2025-02-13 10:20:40.303  - error: shelly.0 (88316) unhandled promise rejection: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.303  - error: shelly.0 (88316) ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
    at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.303  - error: shelly.0 (88316) Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.309  - error: shelly.0 (88316) 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().
2025-02-13 10:20:40.309  - error: shelly.0 (88316) unhandled promise rejection: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.309  - error: shelly.0 (88316) ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
    at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
    at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.309  - error: shelly.0 (88316) Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.371  - info: shelly.0 (88316) terminating
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE 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:
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[1]: ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[1]:     at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[1]:     at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[2]: 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:
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[2]: ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[2]:     at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[2]:     at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[3]: 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:
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[3]: ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[3]:     at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE Caught by controller[3]:     at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)
2025-02-13 10:20:40.561  - error: host.ADMINIS-ROKLDQE instance system.adapter.shelly.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-02-13 10:20:40.561  - info: host.ADMINIS-ROKLDQE Restart adapter system.adapter.shelly.0 because enabled
2025-02-13 10:20:40.561  - warn: host.ADMINIS-ROKLDQE Do not restart adapter system.adapter.shelly.0 because restart loop detected

MOD-EDIT: Code in code-tags gesetzt!

Kann mir da jemand einen Tipp geben. Eigentlich hatte ich noch nie Probleme mit Shelly (seit Jahren) aber jetzt ist mein Latein am Ende.

LG Armin

[Thomas Braun]

@arminrey sagte in Shelly Instanz CoAp steigt seit inst. vom neuen Node.js aus:

Ich schätze nach Update Node.js

Nodejs@22 ist ja auch noch nicht empfohlen für den ioBroker.
Installier da nodejs@20.

[arminrey]

@thomas-braun

jetzt hatte ich auf 20.18.3 zurück, dann das Gleiche.

Jetzt auf 19.9.0 aber der RAM schauckelt sich nach wie vor auf über 1.000 mb

Leider nein, Problem nach wie vor .

[mcm1957]

@arminrey

Gelesen hast du das schon?

Bitte ausfüllen:

Adaptername: ...
Link zu Adapterrepository: www.github.com...
Adapterversion: ...
js-controller Version: ...
Admin Version: ...
Hardwaresystem: NUC, Pi4 ...
Arbeitsspeicher: ...xGB
Festplattenart: SD-Karte, SSD, HDD, ...
Betriebssystem: ...
Nodejs-Version: ...
NPM-Version: ...
Installationsart: Skript oder Manuell ?
Image, Docker genutzt: Ja - Nein
Ort, Name der Imagedatei: ...
Linux User bitte hier den Output von iob diag einfügen.

Also ich seh da keinerlei Angaben. Nicht mal die wichtigesten Infos wie die Adapter Version.
Und von einem iob diag Output seh ich auch nix.

Ergo ... wart ma mal ob da noch Infos kommen.

Und wenn du mit

Jetzt auf 19.9.0 aber

node.js 19.x.x meinst dann b itte nochmal lesen

Installier da nodejs@20.

Ungerade node.js Versionen sind development Versionen. Die solltest du NIE einsetzen.

[Thomas Braun]

@mcm1957 sagte in Shelly Instanz CoAp steigt seit inst. vom neuen Node.js aus:

Und von einem iob diag Output seh ich auch nix.

Ist eine Windows-Installation...

[mcm1957]

@thomas-braun said in Shelly Instanz CoAp steigt seit inst. vom neuen Node.js aus:

Ist eine Windows-Installation...

OK, hab ich übersehen.

Dann wird dort aber node offensichtlich manuell installiert. Der Windows Installer bietet sicher keine 19er an...

Und die Frage nach den installierten Versionen ist auch offen. Aber ja - wir erstellen ja eine Eingabemaske nur zum Spass :-(.

Und ob überhaupt Shelly Ursache oder nur Opfer ist kann man meiner Ansicht nach mit den vorhandenen Infos nicht sagen. Redis belegt ja auch Speicher - also kann da durchaus auch was anderes den Speicher mal wegfressen ...

Abe mangels readis Erfahrung und Infos bin ich dann mal weg...

[arminrey]

@mcm1957

-sorry- ich dachte die hab ich rein gestellt ...

CPU: 1,46 %
RAM: 77 %
Betriebszeit: 0h
Verfügbar: 7.0.6
Installiert: 7.0.6
Ereignisse: ⇥23 / ↦12
Plattform: Windows
Betriebssystem: win32
Architektur: x64
CPUs: 6
Geschwindigkeit: 1704 MHz
Modell: Intel(R) Core(TM) i5-8400T CPU @ 1.70GHz
RAM: 7.8 GB
System-Betriebszeit: 00:01:03
Node.js: v19.9.0
time: 1739443377999
timeOffset: -60
NPM: 9.6.3
Adapter-Anzahl: 554
Datenträgergröße: 235.5 GB
Freier Festplattenspeicher: 92.2 GB
Aktive Instanzen: 9
Pfad: C:\ioBroker
Betriebszeit: 00:00:49
aktiv: true
_nodeCurrent: 19.9.0
_nodeNewest: 19.9.0
_nodeNewestNext: 20.18.3
_npmCurrent: 9.6.3
_npmNewest: 9.6.3
_npmNewestNext: 10.8.2

[Homoran]

@arminrey sagte in Shelly Instanz CoAp steigt seit inst. vom neuen Node.js aus:

ich dachte die hab ich rein gestellt ...

die was?

@mcm1957 sagte in Shelly Instanz CoAp steigt seit inst. vom neuen Node.js aus:

die wichtigesten Infos wie die Adapter Version.

seh ich nicht

[arminrey]

@homoran
Shelly
Installierte Instanzen: 2
Verfügbare Version: 8.5.1
Installierte Version: 8.5.1

[crunchip]

@arminrey probier es mal damit

[arminrey]

@crunchip

hmm -sorry- hier gibt es keine 9.0.0

[crunchip]

@arminrey du sollst auf den Schraubenschlüssel klicken, dadurch erfolgt ein rebuild des Adapters

PS
bei Fehler bitte das Log zeigen

[Homoran]

@arminrey hast du auf beta umgestellt und danach neu geladen?

EDIT:
@crunchip wollte auf etwas anderes raus

[arminrey]

@homoran

So, musste wieder auf node20 um, da der Shelly 9 nicht akzeptiert wurde.

Leider nein

shelly.0
2025-02-13 14:05:52.131	info	terminating

shelly.0
2025-02-13 14:05:51.629	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

shelly.0
2025-02-13 14:05:51.629	info	terminating

shelly.0
2025-02-13 14:05:51.616	error	Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'

shelly.0
2025-02-13 14:05:51.616	error	ReplyError: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json' at parseError (C:\ioBroker\node_modules\redis-parser\lib\parser.js:179:12) at parseType (C:\ioBroker\node_modules\redis-parser\lib\parser.js:302:14)

shelly.0
2025-02-13 14:05:51.614	error	unhandled promise rejection: Error ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'

shelly.0
2025-02-13 14:05:51.613	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().

shelly.0
2025-02-13 14:03:39.594	info	[CoAP] Device 192.168.1.130 (shellyplug-s / shellyplug-s-4022D889B232 / SHPLG-S#4022D889B232#1) connected! Polltime set to 10 sec.

shelly.0
2025-02-13 14:03:38.209	info	[CoAP] Device 192.168.1.167 (shellyem / shellyem-485519D6C5DA / SHEM#485519D6C5DA#1) connected! Polltime set to 10 sec.

shelly.0
2025-02-13 14:03:37.922	info	[CoAP] Device 192.168.1.132 (shelly1 / shelly1-C45BBE764758 / SHSW-1#C45BBE764758#1) connected! Polltime set to 10 sec.

shelly.0
2025-02-13 14:03:37.865	info	[CoAP] Device 192.168.1.162 (shellyplug-s / shellyplug-s-4022D88943F7 / SHPLG-S#4022D88943F7#1) connected! Polltime set to 10 sec.

shelly.0
2025-02-13 14:03:37.687	info	[CoAP] Device 192.168.1.168 (shelly1pm / shelly1pm-8CAAB55FD700 / SHSW-PM#8CAAB55FD700#1) connected! Polltime set to 10 sec.

MOD-EDIT: Code in code-tags gesetzt!

[arminrey]

akutell

[crunchip]

@arminrey kein Mensch sagte etwas davon, dass du v9 installieren solltest und es fehlt auch das Installationslog dazu

lediglich auf den Schraubenschlüssel solltest du drücken und das LOG bei Fehler zeigen
und solange deine Instanz Fehler wirft ist logisch das der Ram nicht runter geht

ggf stell die Instanz auf debug und zeig den Startvorgang aus dem Log

[arminrey]

@crunchip
Falsch verstanden.... habs wieder rückgängig gemach... danke für Eure Neven zu mir, aber wenn das System lange ohne Probleme läuft, sucht man erst wieder länger...

log.txt

[haus-automatisierung]

@arminrey Ich hab den Adapter nie unter Windows getestet. Aber die Zeile hier ist schon komisch:

2025-02-13 15:00:48.318  - warn: host.ADMINIS-ROKLDQE-Server Objects 127.0.0.1:56580 Error from InMemDB: Error: ERROR writeFile-Meta id=shelly.0: UNKNOWN: unknown error, open 'C:\ioBroker\iobroker-data\files\shelly.0\_data.json'

Stimmen da eventuell Ordnerrechte nicht?

[Homoran]

@arminrey

@crunchip sagte in Shelly Instanz CoAp steigt seit inst. vom neuen Node.js aus:

zeig den Startvorgang aus dem Log

bedeutet immer als Text in code-tags!

siehe auch:
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1

[crunchip]

@haus-automatisierung sagte in Shelly Instanz CoAp steigt seit inst. vom neuen Node.js aus:

Stimmen da eventuell Ordnerrechte nicht

Wenn ichs richtig gelesen habe, hat er ja 2 Instanzen, jedoch nur bei Instanz. 0 dieses Problem

Edit
Grad das log per Handy überflogen, da stimmt ja auch etwas nicht

2025-02-13 15:04:15.400  - error: shelly.1 (16624) [MQTT] (Shelly?) device unknown, configuration for client with id "Gaszaehler" (Gaszaehler / Gaszaehler / undefined) does not exist! Maybe this device is not supported in this adapter version.
2025-02-13 15:04:15.400  - error: shelly.1 (16624) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details)
2025-02-13 15:04:15.411  - info: shelly.1 (16624) [MQTT] Client Close: (Gaszaehler / Gaszaehler / undefined) (false)