@skvarel sagte:

Die 0.3.3 ist online

Ja, schaut besser aus.

tidy.0
2026-06-18 16:02:49.758	info	Automatic scanning enabled: Every 24 hour(s)

tidy.0
2026-06-18 16:02:49.756	info	Complete scan finished: 20866 datapoints (4739 dead, 1245 stale, 0 orphaned, 0 excluded) in 10.53s

tidy.0
2026-06-18 16:02:39.224	info	Scanning entire object tree (complete scan) ...

tidy.0
2026-06-18 16:02:39.223	info	Scan completed for 0_userdata.0: 1940 datapoints (471 dead, 548 stale, 0 orphaned, 0 excluded) in 0.41s

tidy.0
2026-06-18 16:02:38.816	info	Scanning path: 0_userdata.0

tidy.0
2026-06-18 16:02:38.795	info	Starting Tidy adapter...

tidy.0
2026-06-18 16:02:38.786	info	starting. Version 0.3.3 in C:/SmartHome/node_modules/iobroker.tidy, node: v22.23.0, js-controller: 7.2.2

Der Fehler Invalid string length tritt auf, wenn der Complete Scan versucht, alle Datenpunkte mit ihren vollen Werten in einem einzigen JSON-State zu speichern – bei großen Installationen überschreitet das das Node.js-Limit.

In der nächsten Version (0.3.3) ist das behoben: Werte werden gekürzt, States werden gebündelt geladen, und bei extrem großen Instanzen gibt es einen Fallback ohne Wert-Feld.

Bis dahin: Complete Scan vorübergehend deaktivieren und stattdessen gezielte Pfad-Scans nutzen (z. B. alias, hm-rpc, 0_userdata.0).

Bitte testen und mir eine kurze Rückmeldung geben

EDIT:
Die 0.3.3 ist online

Hallo,

der Adapter arbeitet gut wenn man keinen Complet Scan macht.
Dann stürzt er ab und blockiert mein System.

tidy.0
2026-06-18 12:30:42.761	warn	Cannot parse "QUEUED"

tidy.0
2026-06-18 12:30:42.760	warn	Cannot parse "OK"

tidy.0
2026-06-18 12:30:27.763	warn	Cannot parse "QUEUED"

tidy.0
2026-06-18 12:30:27.762	warn	Cannot parse "OK"

tidy.0
2026-06-18 12:30:12.752	warn	Cannot parse "QUEUED"

tidy.0
2026-06-18 12:30:12.751	warn	Cannot parse "OK"

tidy.0
2026-06-18 12:29:57.724	warn	Cannot parse "QUEUED"

tidy.0
2026-06-18 12:29:57.723	warn	Cannot parse "OK"

tidy.0
2026-06-18 12:29:57.716	info	Automatic scanning enabled: Every 24 hour(s)

tidy.0
2026-06-18 12:29:57.715	error	Error during complete scan: Invalid string length

tidy.0
2026-06-18 12:29:40.025	info	Scanning entire object tree (complete scan) ...

tidy.0
2026-06-18 12:29:40.024	info	Scan completed for 0_userdata.0: 1940 datapoints (471 dead, 548 stale, 0 orphaned, 0 excluded) in 1.30s

tidy.0
2026-06-18 12:29:38.727	info	Scanning path: 0_userdata.0

tidy.0
2026-06-18 12:29:38.708	info	Starting Tidy adapter...

tidy.0
2026-06-18 12:29:38.699	info	starting. Version 0.3.2 in C:/SmartHome/node_modules/iobroker.tidy, node: v22.23.0, js-controller: 7.2.2

tidy.0
2026-06-18 12:29:33.607	warn	redis get 0_userdata.0.allestoerungen.Hot.disruption_desc_2, error - Connection is closed.

tidy.0
2026-06-18 12:29:33.605	warn	redis get 0_userdata.0.allestoerungen.Hot.disruption_2, error - Connection is closed.

tidy.0
2026-06-18 12:29:33.601	info	terminating

tidy.0
2026-06-18 12:29:33.601	info	terminating

tidy.0
2026-06-18 12:29:33.155	info	Scanning path: 0_userdata.0

tidy.0
2026-06-18 12:29:33.102	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

tidy.0
2026-06-18 12:29:33.100	info	terminating

tidy.0
2026-06-18 12:29:33.099	info	Got terminate signal TERMINATE_YOURSELF

tidy.0
2026-06-18 12:29:33.098	info	Configuration updated — reloading paths and rescanning

tidy.0
2026-06-18 12:28:40.956	info	Automatic scanning enabled: Every 24 hour(s)

tidy.0
2026-06-18 12:28:40.955	info	Scan completed for 0_userdata.0: 1940 datapoints (471 dead, 548 stale, 0 orphaned, 0 excluded) in 1.51s

tidy.0
2026-06-18 12:28:39.441	info	Scanning path: 0_userdata.0

Plattform: Windows
RAM: 15.9 GB
Node.js: v22.23.0
NPM: 10.9.8
Tidy: 0.3.2
JS: 7.2.2
Admin: 7.9.2

0.3.3 (2026-06-18)

(skvarel) Fixed complete scan failing with "Invalid string length" on large instances
(skvarel) Modified complete scan to load states in bulk instead of one-by-one

0.3.2 (2026-06-18)

(skvarel) Removed accidentally committed local dev-server data directory from repository (fixes #14)

0.3.1 (2026-06-16)

(skvarel) Added admin UI help text explaining "Check alias targets" on Scan Paths tab (boxed info panel)
(skvarel) Fixed alias target check for read/write split aliases (common.alias.id with read and write)

0.3.0 (2026-06-13)

(skvarel) Added wildcard patterns for exception list (* matches any suffix, ? matches one character)