Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • 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

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter Linux Control v1.x.x

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.4k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    818

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.1k

Test Adapter Linux Control v1.x.x

Geplant Angeheftet Gesperrt Verschoben Tester
adaptercontrolhardwarelinuxsteuern
715 Beiträge 73 Kommentatoren 181.5k Aufrufe 66 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • D Offline
    D Offline
    deta
    Most Active
    schrieb am zuletzt editiert von
    #664

    Fehler gefunden....
    Ich hatte noch keinen openssh Server auf dem Desktop installiert :disappointed:

    Jetzt geht es.
    Danke

    D 1 Antwort Letzte Antwort
    1
    • D deta

      Fehler gefunden....
      Ich hatte noch keinen openssh Server auf dem Desktop installiert :disappointed:

      Jetzt geht es.
      Danke

      D Offline
      D Offline
      denjo
      schrieb am zuletzt editiert von
      #665

      ich habe auch probleme mit dem Adapter

      über Putty kann ich ohne probleme zugreifen

      Mein IObroker ist bei allem auf aktuellen stand

      Node.js: v20.19.4
      JS Controller 7.0.6
      Adapter. 1.1.5

      
      host.iOBroker
      2025-08-13 20:44:20.577	info	"system.adapter.linux-control.0" disabled
      
      linux-control.0
      2025-08-13 20:44:06.264	error	Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string"
      
      host.iOBroker
      2025-08-13 20:44:05.094	info	instance system.adapter.linux-control.0 in version "1.1.5" started with pid 3987
      
      host.iOBroker
      2025-08-13 20:43:34.740	info	Restart adapter system.adapter.linux-control.0 because enabled
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[14]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[14]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[14]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[14]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[14]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[13]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[13]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[13]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[13]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[13]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[12]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[12]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[12]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[12]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[12]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[11]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[11]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[11]: ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[11]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[10]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[10]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[10]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[10]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[10]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[9]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[9]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[9]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[9]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[8]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[8]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[8]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[8]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[8]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[7]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[7]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[7]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[6]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.740	error	Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[5]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[5]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[5]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[5]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[4]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[4]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[4]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[4]: 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:
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[3]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[3]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[3]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	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:
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[2]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[2]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[2]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	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:
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[1]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[1]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
      
      host.iOBroker
      2025-08-13 20:43:34.739	error	Caught by controller[1]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      host.iOBroker
      2025-08-13 20:43:34.739	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:
      
      linux-control.0
      2025-08-13 20:43:34.634	error	[needrestart] hyperion (192.168.178.67:22): error: Cannot find view "system", stack: Error: Cannot find view "system" at ObjectsInRedisClient._getObjectView (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4272:19) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4346:33)
      
      linux-control.0
      2025-08-13 20:43:34.595	error	Cannot find view "system" for search "state" : Connection is closed.
      
      linux-control.0
      2025-08-13 20:43:34.593	error	[servicesInfo] hyperion (192.168.178.67:22): error: DB closed, stack: Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:639:26) at Socket.emit (node:events:524:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:343:12)
      
      linux-control.0
      2025-08-13 20:43:34.554	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.554	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.554	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.553	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().
      
      linux-control.0
      2025-08-13 20:43:34.515	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.515	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.515	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.514	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().
      
      linux-control.0
      2025-08-13 20:43:34.480	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.480	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.479	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.479	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().
      
      linux-control.0
      2025-08-13 20:43:34.464	error	Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.463	error	ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
      
      linux-control.0
      2025-08-13 20:43:34.463	error	unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.463	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().
      
      host.iOBroker-Server
      2025-08-13 20:43:34.462	warn	States 127.0.0.1:45704 Error from InMemDB: Error: The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:242:14) at RedisHandler.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:380:26) at RedisHandler.emit (node:events:524:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:483:21)
      
      linux-control.0
      2025-08-13 20:43:34.436	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.436	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.435	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.435	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().
      
      linux-control.0
      2025-08-13 20:43:34.366	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.366	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.365	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.365	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().
      
      linux-control.0
      2025-08-13 20:43:34.351	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.351	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.351	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.350	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().
      
      linux-control.0
      2025-08-13 20:43:34.288	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.288	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.287	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.287	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().
      
      linux-control.0
      2025-08-13 20:43:34.256	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.256	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.255	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.255	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().
      
      linux-control.0
      2025-08-13 20:43:34.215	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.215	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.215	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.215	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().
      
      linux-control.0
      2025-08-13 20:43:34.194	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.194	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      linux-control.0
      2025-08-13 20:43:34.145	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.145	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().
      
      linux-control.0
      2025-08-13 20:43:34.138	error	ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
      
      linux-control.0
      2025-08-13 20:43:34.138	error	unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.138	error	Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
      
      linux-control.0
      2025-08-13 20:43:34.137	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().
      
      crunchipC 1 Antwort Letzte Antwort
      0
      • D denjo

        ich habe auch probleme mit dem Adapter

        über Putty kann ich ohne probleme zugreifen

        Mein IObroker ist bei allem auf aktuellen stand

        Node.js: v20.19.4
        JS Controller 7.0.6
        Adapter. 1.1.5

        
        host.iOBroker
        2025-08-13 20:44:20.577	info	"system.adapter.linux-control.0" disabled
        
        linux-control.0
        2025-08-13 20:44:06.264	error	Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string"
        
        host.iOBroker
        2025-08-13 20:44:05.094	info	instance system.adapter.linux-control.0 in version "1.1.5" started with pid 3987
        
        host.iOBroker
        2025-08-13 20:43:34.740	info	Restart adapter system.adapter.linux-control.0 because enabled
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[14]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[14]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[14]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[14]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[14]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[13]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[13]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[13]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[13]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[13]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[12]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[12]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[12]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[12]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[12]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[11]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[11]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[11]: ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[11]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[10]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[10]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[10]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[10]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[10]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[9]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[9]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[9]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[9]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[8]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[8]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[8]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[8]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[8]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[7]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[7]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[7]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[6]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.740	error	Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[5]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[5]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[5]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[5]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[4]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[4]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[4]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[4]: 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:
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[3]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[3]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[3]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	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:
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[2]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[2]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[2]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	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:
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[1]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[1]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
        
        host.iOBroker
        2025-08-13 20:43:34.739	error	Caught by controller[1]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        host.iOBroker
        2025-08-13 20:43:34.739	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:
        
        linux-control.0
        2025-08-13 20:43:34.634	error	[needrestart] hyperion (192.168.178.67:22): error: Cannot find view "system", stack: Error: Cannot find view "system" at ObjectsInRedisClient._getObjectView (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4272:19) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4346:33)
        
        linux-control.0
        2025-08-13 20:43:34.595	error	Cannot find view "system" for search "state" : Connection is closed.
        
        linux-control.0
        2025-08-13 20:43:34.593	error	[servicesInfo] hyperion (192.168.178.67:22): error: DB closed, stack: Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:639:26) at Socket.emit (node:events:524:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:343:12)
        
        linux-control.0
        2025-08-13 20:43:34.554	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.554	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.554	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.553	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().
        
        linux-control.0
        2025-08-13 20:43:34.515	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.515	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.515	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.514	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().
        
        linux-control.0
        2025-08-13 20:43:34.480	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.480	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.479	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.479	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().
        
        linux-control.0
        2025-08-13 20:43:34.464	error	Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.463	error	ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
        
        linux-control.0
        2025-08-13 20:43:34.463	error	unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.463	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().
        
        host.iOBroker-Server
        2025-08-13 20:43:34.462	warn	States 127.0.0.1:45704 Error from InMemDB: Error: The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:242:14) at RedisHandler.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:380:26) at RedisHandler.emit (node:events:524:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:483:21)
        
        linux-control.0
        2025-08-13 20:43:34.436	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.436	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.435	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.435	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().
        
        linux-control.0
        2025-08-13 20:43:34.366	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.366	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.365	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.365	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().
        
        linux-control.0
        2025-08-13 20:43:34.351	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.351	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.351	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.350	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().
        
        linux-control.0
        2025-08-13 20:43:34.288	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.288	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.287	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.287	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().
        
        linux-control.0
        2025-08-13 20:43:34.256	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.256	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.255	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.255	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().
        
        linux-control.0
        2025-08-13 20:43:34.215	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.215	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.215	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.215	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().
        
        linux-control.0
        2025-08-13 20:43:34.194	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.194	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        linux-control.0
        2025-08-13 20:43:34.145	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.145	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().
        
        linux-control.0
        2025-08-13 20:43:34.138	error	ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
        
        linux-control.0
        2025-08-13 20:43:34.138	error	unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.138	error	Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
        
        linux-control.0
        2025-08-13 20:43:34.137	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().
        
        crunchipC Abwesend
        crunchipC Abwesend
        crunchip
        Forum Testing Most Active
        schrieb am zuletzt editiert von
        #666

        @denjo sagte in Test Adapter Linux Control v1.x.x:

        linux-control.0.hyperion.services.●.restart

        Ist das Problem

        umgestiegen von Proxmox auf Unraid

        1 Antwort Letzte Antwort
        0
        • F Offline
          F Offline
          flispy
          schrieb am zuletzt editiert von
          #667

          Moin,
          leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
          Ich habe den Adapter in Version 1.1.6 installiert.

          Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

          iputils-ping habe ich neu installiert.

          Hat jemand eine Idee woran es liegen könnte?

          F 1 Antwort Letzte Antwort
          1
          • F flispy

            Moin,
            leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
            Ich habe den Adapter in Version 1.1.6 installiert.

            Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

            iputils-ping habe ich neu installiert.

            Hat jemand eine Idee woran es liegen könnte?

            F Offline
            F Offline
            flispy
            schrieb am zuletzt editiert von
            #668

            @flispy sagte in Test Adapter Linux Control v1.x.x:

            Moin,
            leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
            Ich habe den Adapter in Version 1.1.6 installiert.

            Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

            iputils-ping habe ich neu installiert.

            Hat jemand eine Idee woran es liegen könnte?

            hab es lösen können. Ich musste folgendes ausführen
            sudo setcap cap_net_raw+p /usr/bin/ping

            M 1 Antwort Letzte Antwort
            1
            • F flispy

              @flispy sagte in Test Adapter Linux Control v1.x.x:

              Moin,
              leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
              Ich habe den Adapter in Version 1.1.6 installiert.

              Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

              iputils-ping habe ich neu installiert.

              Hat jemand eine Idee woran es liegen könnte?

              hab es lösen können. Ich musste folgendes ausführen
              sudo setcap cap_net_raw+p /usr/bin/ping

              M Offline
              M Offline
              mading
              schrieb am zuletzt editiert von
              #669

              @flispy sagte in Test Adapter Linux Control v1.x.x:

              @flispy sagte in Test Adapter Linux Control v1.x.x:

              Moin,
              leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
              Ich habe den Adapter in Version 1.1.6 installiert.

              Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

              iputils-ping habe ich neu installiert.

              Hat jemand eine Idee woran es liegen könnte?

              hab es lösen können. Ich musste folgendes ausführen
              sudo setcap cap_net_raw+p /usr/bin/ping

              Geht wieder, habe den Befehl auf dem iobroker ausgeführt. Danke!

              1 Antwort Letzte Antwort
              0
              • F Offline
                F Offline
                Fichte
                schrieb am zuletzt editiert von Fichte
                #670

                Hallo zusammen

                Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                [getConnection] Host 'Name' (IP:Port) seems not to be online
                

                "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                Quelle hier

                Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                Abhilfe steht im Link und ist relativ einfach:

                1. Anmelden
                2. sudo nano /usr/lib/sysctl.d/50-default.conf
                3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                4. Speichern und Neustarten

                Liebe Grüße

                NashraN wendy2702W M 3 Antworten Letzte Antwort
                1
                • F Fichte

                  Hallo zusammen

                  Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                  [getConnection] Host 'Name' (IP:Port) seems not to be online
                  

                  "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                  Quelle hier

                  Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                  Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                  Abhilfe steht im Link und ist relativ einfach:

                  1. Anmelden
                  2. sudo nano /usr/lib/sysctl.d/50-default.conf
                  3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                  4. Speichern und Neustarten

                  Liebe Grüße

                  NashraN Offline
                  NashraN Offline
                  Nashra
                  Most Active Forum Testing
                  schrieb am zuletzt editiert von
                  #671

                  @fichte
                  danke für den Hinweis, Ping arbeitet wieder

                  Gruß Ralf
                  Mir egal, wer Dein Vater ist! Wenn ich hier angel, wird nicht übers Wasser gelaufen!!

                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                  1 Antwort Letzte Antwort
                  0
                  • F Fichte

                    Hallo zusammen

                    Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                    [getConnection] Host 'Name' (IP:Port) seems not to be online
                    

                    "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                    Quelle hier

                    Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                    Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                    Abhilfe steht im Link und ist relativ einfach:

                    1. Anmelden
                    2. sudo nano /usr/lib/sysctl.d/50-default.conf
                    3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                    4. Speichern und Neustarten

                    Liebe Grüße

                    wendy2702W Offline
                    wendy2702W Offline
                    wendy2702
                    schrieb am zuletzt editiert von
                    #672

                    @fichte auch nach einem Restart ?

                    Bitte keine Fragen per PN, die gehören ins Forum!

                    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                    F 1 Antwort Letzte Antwort
                    0
                    • wendy2702W wendy2702

                      @fichte auch nach einem Restart ?

                      F Offline
                      F Offline
                      Fichte
                      schrieb am zuletzt editiert von
                      #673

                      @wendy2702 Ja Punkt 4

                      1 Antwort Letzte Antwort
                      0
                      • F Fichte

                        Hallo zusammen

                        Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                        [getConnection] Host 'Name' (IP:Port) seems not to be online
                        

                        "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                        Quelle hier

                        Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                        Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                        Abhilfe steht im Link und ist relativ einfach:

                        1. Anmelden
                        2. sudo nano /usr/lib/sysctl.d/50-default.conf
                        3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                        4. Speichern und Neustarten

                        Liebe Grüße

                        M Offline
                        M Offline
                        mading
                        schrieb am zuletzt editiert von
                        #674

                        @fichte sagte in Test Adapter Linux Control v1.x.x:

                        Hallo zusammen

                        Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                        [getConnection] Host 'Name' (IP:Port) seems not to be online
                        

                        "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                        Quelle hier

                        Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                        Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                        Abhilfe steht im Link und ist relativ einfach:

                        1. Anmelden
                        2. sudo nano /usr/lib/sysctl.d/50-default.conf
                        3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                        4. Speichern und Neustarten

                        Liebe Grüße

                        Muss das auf jedem server durchgeführt werden oder nur auf dem iob?

                        wendy2702W 1 Antwort Letzte Antwort
                        0
                        • M mading

                          @fichte sagte in Test Adapter Linux Control v1.x.x:

                          Hallo zusammen

                          Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                          [getConnection] Host 'Name' (IP:Port) seems not to be online
                          

                          "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                          Quelle hier

                          Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                          Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                          Abhilfe steht im Link und ist relativ einfach:

                          1. Anmelden
                          2. sudo nano /usr/lib/sysctl.d/50-default.conf
                          3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                          4. Speichern und Neustarten

                          Liebe Grüße

                          Muss das auf jedem server durchgeführt werden oder nur auf dem iob?

                          wendy2702W Offline
                          wendy2702W Offline
                          wendy2702
                          schrieb am zuletzt editiert von
                          #675

                          @mading nur auf dem wo der Linux Control Adapter läuft.

                          Bitte keine Fragen per PN, die gehören ins Forum!

                          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                          1 Antwort Letzte Antwort
                          0
                          • 1Topf1 Offline
                            1Topf1 Offline
                            1Topf
                            schrieb am zuletzt editiert von
                            #676

                            Ich hab da auch mal ne Frage. Ich hab jetzt einen Raspi3 eingebunden, auf welchem 2 Kameras (Garten u. Hof) auf einem USB-Stick Bilder ablegen. Beide Ordner enthalten aktuell jeweils >20GB Daten. Wieso wird das nicht korrekt dargestellt? Hat da jemand eine Idee? Die Anzahl der Dateien hingegen stimmt.

                            ordner01.jpg

                            1 Antwort Letzte Antwort
                            0
                            • D3ltoroxpD Offline
                              D3ltoroxpD Offline
                              D3ltoroxp
                              schrieb am zuletzt editiert von D3ltoroxp
                              #677

                              Ich wollte mir das auch mal anschauen. Habe ein paar Befehle eingetragen und mal einen Server. In der Log bekomme ich massig so etwas. An dem Pattern kann ich ja gar nichts ändern.

                              linux-control.0
                              2026-01-10 09:37:46.274	warn	Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
                              
                              linux-control.0
                              2026-01-10 09:37:46.182	error	adapter disabled
                              
                              linux-control.0
                              2026-01-10 09:37:14.374	warn	State "linux-control.0.Proxmox_Homeserver.services.●.load" has no existing object, this might lead to an error in future versions
                              
                              linux-control.0
                              2026-01-10 09:37:14.373	warn	Used invalid characters: linux-control.0.Proxmox_Homeserver.services.●.load changed to linux-control.0.Proxmox_Homeserver.services._.load
                              
                              linux-control.0
                              2026-01-10 09:37:14.310	warn	Used invalid characters: linux-control.0.Proxmox_Homeserver.services.●.stop changed to linux-control.0.Proxmox_Homeserver.services._.stop
                              
                              linux-control.0
                              2026-01-10 09:37:14.308	error	The pattern "io.linux-control.0.Proxmox_Homeserver.services.●.start" is not a valid ID pattern
                              
                              linux-control.0
                              2026-01-10 09:37:14.308	error	Error: The pattern "io.linux-control.0.Proxmox_Homeserver.services.●.start" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) at processTicksAndRejections (node:internal/process/task_queues:105:5)
                              
                              linux-control.0
                              2026-01-10 09:37:14.307	error	unhandled promise rejection: The pattern "io.linux-control.0.Proxmox_Homeserver.services.●.start" is not a valid ID pattern
                              
                              linux-control.0
                              2026-01-10 09:37:14.307	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().
                              
                              linux-control.0
                              2026-01-10 09:37:14.305	warn	Used invalid characters: linux-control.0.Proxmox_Homeserver.services.●.start changed to linux-control.0.Proxmox_Homeserver.services._.start
                              
                              linux-control.0
                              2026-01-10 09:37:14.304	error	Error The pattern "linux-control.0.Proxmox_Homeserver.services.●.restart" is not a valid ID pattern
                              
                              linux-control.0
                              2026-01-10 09:37:14.304	error	ReplyError: Error The pattern "linux-control.0.Proxmox_Homeserver.services.●.restart" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                              
                              linux-control.0
                              2026-01-10 09:37:14.303	error	unhandled promise rejection: Error The pattern "linux-control.0.Proxmox_Homeserver.services.●.restart" is not a valid ID pattern
                              
                              linux-control.0
                              2026-01-10 09:37:14.303	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().
                              
                              linux-control.0
                              2026-01-10 09:37:14.302	warn	Used invalid characters: linux-control.0.Proxmox_Homeserver.services.●.restart changed to linux-control.0.Proxmox_Homeserver.services._.restart
                              
                              linux-control.0
                              2026-01-10 09:37:14.259	warn	State "linux-control.0.Proxmox_Homeserver.services.●.description" has no existing object, this might lead to an error in future versions
                              
                              linux-control.0
                              2026-01-10 09:37:14.258	warn	Used invalid characters: linux-control.0.Proxmox_Homeserver.services.●.description changed to linux-control.0.Proxmox_Homeserver.services._.description
                              
                              linux-control.0
                              2026-01-10 09:37:14.209	warn	State "linux-control.0.Proxmox_Homeserver.services.●.running" has no existing object, this might lead to an error in future versions
                              
                              linux-control.0
                              2026-01-10 09:37:14.207	warn	Used invalid characters: linux-control.0.Proxmox_Homeserver.services.●.running changed to linux-control.0.Proxmox_Homeserver.services._.running
                              
                              linux-control.0
                              2026-01-10 09:37:14.159	warn	State "linux-control.0.Proxmox_Homeserver.services.●.active" has no existing object, this might lead to an error in future versions
                              
                              linux-control.0
                              2026-01-10 09:37:14.158	warn	Used invalid characters: linux-control.0.Proxmox_Homeserver.services.●.active changed to linux-control.0.Proxmox_Homeserver.services._.active
                              
                              linux-control.0
                              2026-01-10 09:37:14.114	warn	State "linux-control.0.Proxmox_Homeserver.services.●.load" has no existing object, this might lead to an error in future versions
                              
                              linux-control.0
                              2026-01-10 09:37:14.113	warn	Used invalid characters: linux-control.0.Proxmox_Homeserver.services.●.load changed to linux-control.0.Proxmox_Homeserver.services._.load
                              
                              linux-control.0
                              2026-01-10 09:37:14.010	error	Error The pattern "linux-control.0.Proxmox_Homeserver.services.●.stop" is not a valid ID pattern
                              

                              Was kann ich tun, oder wo liegt mein Fehler. So sehen die Befehle aus.
                              d5d8a605-1e8b-4ccd-9ba5-9d480ed4042e-image.png

                              1 Antwort Letzte Antwort
                              0
                              • M Offline
                                M Offline
                                mading
                                schrieb am zuletzt editiert von mading
                                #678

                                Interessant, irgendwie interpretiert er was falsch bzgl. des Datenpunkts services.●.load und der anderen

                                Gibt es den Datenpunkt? Wie ist er benannt?

                                1 Antwort Letzte Antwort
                                0
                                • Ro75R Offline
                                  Ro75R Offline
                                  Ro75
                                  schrieb am zuletzt editiert von
                                  #679

                                  Ggfs. mit Alias arbeiten.

                                  Ro75.

                                  SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

                                  1 Antwort Letzte Antwort
                                  0
                                  • D3ltoroxpD Offline
                                    D3ltoroxpD Offline
                                    D3ltoroxp
                                    schrieb am zuletzt editiert von
                                    #680

                                    Hm der Adapter hat ja die DP's erstellt, sollte das dann nicht passen ? Heißt das ich müsst die jetzt von Hand abändern, wenn ich so komische Schreibweise finde ?

                                    crunchipC 1 Antwort Letzte Antwort
                                    0
                                    • D3ltoroxpD D3ltoroxp

                                      Hm der Adapter hat ja die DP's erstellt, sollte das dann nicht passen ? Heißt das ich müsst die jetzt von Hand abändern, wenn ich so komische Schreibweise finde ?

                                      crunchipC Abwesend
                                      crunchipC Abwesend
                                      crunchip
                                      Forum Testing Most Active
                                      schrieb am zuletzt editiert von
                                      #681

                                      @D3ltoroxp die Frage ist eher, was da genau läuft auf deinen Systemen. Hat ja nichts mit den Befehlen zu tun.

                                      umgestiegen von Proxmox auf Unraid

                                      D3ltoroxpD 1 Antwort Letzte Antwort
                                      0
                                      • RoddiEFR Offline
                                        RoddiEFR Offline
                                        RoddiEF
                                        schrieb am zuletzt editiert von
                                        #682

                                        Ich war mal so frei und habe mir diesen Adapter mal installiert aber bekomme sofort nach dem ersten Start eine Fehlermeldung:

                                        linux-control.0
                                        2026-01-12 18:02:09.233	error	Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                                        

                                        Kann jemand was damit anfangen und mir Sagen wo der Adapter sein Problem hat?

                                        Edit:
                                        Eingetragen sind nur 2 Raspberry sonst sind keine weiteren Einstellungen gemacht worden.

                                        Ich bin wie ich bin, was anderes bekommt man nicht !!

                                        Meister MopperM 1 Antwort Letzte Antwort
                                        0
                                        • RoddiEFR RoddiEF

                                          Ich war mal so frei und habe mir diesen Adapter mal installiert aber bekomme sofort nach dem ersten Start eine Fehlermeldung:

                                          linux-control.0
                                          2026-01-12 18:02:09.233	error	Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                                          

                                          Kann jemand was damit anfangen und mir Sagen wo der Adapter sein Problem hat?

                                          Edit:
                                          Eingetragen sind nur 2 Raspberry sonst sind keine weiteren Einstellungen gemacht worden.

                                          Meister MopperM Offline
                                          Meister MopperM Offline
                                          Meister Mopper
                                          schrieb am zuletzt editiert von Meister Mopper
                                          #683

                                          @RoddiEF

                                          Guckst du hier

                                          Is aber nicht schlimm, der Adapter läuft sonst super gut!

                                          Proxmox und HA

                                          1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          363

                                          Online

                                          32.6k

                                          Benutzer

                                          82.0k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe