Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[Negalein]

@Ro75 sagte:

hier fehlt das Abfrageintervall. Post 1 Bild 3.

leider immer noch

host.ioBroker
2026-04-28 10:38:52.105	error	instance system.adapter.linux-control.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)

linux-control.0
2026-04-28 10:38:51.480	warn	Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason

linux-control.0
2026-04-28 10:38:51.474	error	adapter disabled

javascript.0
2026-04-28 10:38:29.472	info	script.js.Wetter.Open-Meteo-Widget: Weather widget: HTML successfully generated.

javascript.0
2026-04-28 10:38:28.460	info	script.js.Wetter.Open-Meteo-Widget: Weather widget: HTML successfully generated.

host.ioBroker
2026-04-28 10:38:21.158	info	"system.adapter.linux-control.0" disabled

host.ioBroker
2026-04-28 10:38:19.014	info	Restart adapter system.adapter.linux-control.0 because enabled

host.ioBroker
2026-04-28 10:38:19.014	error	instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:103:5)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[7]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[7]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[7]: Error: The pattern "io.linux-control.0.Proxmox_3_Keller.services.●.start" is not a valid ID pattern

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[7]: 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
2026-04-28 10:38:19.014	error	Caught by controller[6]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[6]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[6]: ReplyError: Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.restart" is not a valid ID pattern

host.ioBroker
2026-04-28 10:38:19.014	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
2026-04-28 10:38:19.014	error	Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:103:5)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[5]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[5]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[5]: Error: The pattern "io.linux-control.0.Proxmox_3_Keller.services.●.start" is not a valid ID pattern

host.ioBroker
2026-04-28 10:38:19.014	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
2026-04-28 10:38:19.014	error	Caught by controller[4]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[4]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[4]: ReplyError: Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.restart" is not a valid ID pattern

host.ioBroker
2026-04-28 10:38:19.014	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
2026-04-28 10:38:19.014	error	Caught by controller[3]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[3]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[3]: ReplyError: Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.stop" is not a valid ID pattern

host.ioBroker
2026-04-28 10:38:19.014	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
2026-04-28 10:38:19.014	error	Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:103:5)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[1]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[1]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15)

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[1]: Error: The pattern "io.linux-control.0.Proxmox_3_Keller.services.●.start" is not a valid ID pattern

host.ioBroker
2026-04-28 10:38:19.014	error	Caught by controller[1]: 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
2026-04-28 10:38:19.014	error	Caught by controller[0]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

host.ioBroker
2026-04-28 10:38:19.013	error	Caught by controller[0]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)

host.ioBroker
2026-04-28 10:38:19.013	error	Caught by controller[0]: ReplyError: Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.restart" is not a valid ID pattern

host.ioBroker
2026-04-28 10:38:19.013	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
2026-04-28 10:38:18.812	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.stop changed to linux-control.0.Proxmox_3_Keller.services._.stop

linux-control.0
2026-04-28 10:38:18.808	error	Error: The pattern "io.linux-control.0.Proxmox_3_Keller.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:2507: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:103:5)

linux-control.0
2026-04-28 10:38:18.807	error	unhandled promise rejection: The pattern "io.linux-control.0.Proxmox_3_Keller.services.●.start" is not a valid ID pattern

linux-control.0
2026-04-28 10:38:18.807	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-04-28 10:38:18.804	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.start changed to linux-control.0.Proxmox_3_Keller.services._.start

linux-control.0
2026-04-28 10:38:18.797	error	ReplyError: Error The pattern "linux-control.0.Proxmox_3_Keller.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-04-28 10:38:18.797	error	unhandled promise rejection: Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.restart" is not a valid ID pattern

linux-control.0
2026-04-28 10:38:18.797	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
2026-04-28 10:38:18.796	warn	host.ioBroker-Server States 127.0.0.1:54768 Error from InMemDB: Error: The pattern "linux-control.0.Proxmox_3_Keller.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:2507:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:323:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:240: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:519:28) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:484:21) at process.callbackTrampoline (node:internal/async_hooks:130:17)

linux-control.0
2026-04-28 10:38:18.794	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.restart changed to linux-control.0.Proxmox_3_Keller.services._.restart

linux-control.0
2026-04-28 10:38:18.751	warn	State "linux-control.0.Proxmox_3_Keller.services.●.description" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.748	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.description changed to linux-control.0.Proxmox_3_Keller.services._.description

linux-control.0
2026-04-28 10:38:18.744	warn	State "linux-control.0.Proxmox_3_Keller.services.●.running" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.743	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.running changed to linux-control.0.Proxmox_3_Keller.services._.running

linux-control.0
2026-04-28 10:38:18.739	warn	State "linux-control.0.Proxmox_3_Keller.services.●.active" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.737	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.active changed to linux-control.0.Proxmox_3_Keller.services._.active

linux-control.0
2026-04-28 10:38:18.693	warn	State "linux-control.0.Proxmox_3_Keller.services.●.load" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.691	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.load changed to linux-control.0.Proxmox_3_Keller.services._.load

linux-control.0
2026-04-28 10:38:18.632	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.stop changed to linux-control.0.Proxmox_3_Keller.services._.stop

linux-control.0
2026-04-28 10:38:18.628	error	Error: The pattern "io.linux-control.0.Proxmox_3_Keller.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:2507: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:103:5)

linux-control.0
2026-04-28 10:38:18.627	error	unhandled promise rejection: The pattern "io.linux-control.0.Proxmox_3_Keller.services.●.start" is not a valid ID pattern

linux-control.0
2026-04-28 10:38:18.627	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-04-28 10:38:18.624	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.start changed to linux-control.0.Proxmox_3_Keller.services._.start

linux-control.0
2026-04-28 10:38:18.621	error	ReplyError: Error The pattern "linux-control.0.Proxmox_3_Keller.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-04-28 10:38:18.620	error	unhandled promise rejection: Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.restart" is not a valid ID pattern

linux-control.0
2026-04-28 10:38:18.619	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
2026-04-28 10:38:18.619	warn	host.ioBroker-Server States 127.0.0.1:54768 Error from InMemDB: Error: The pattern "linux-control.0.Proxmox_3_Keller.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:2507:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:323:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:240: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:519:28) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:484:21) at process.callbackTrampoline (node:internal/async_hooks:130:17)

linux-control.0
2026-04-28 10:38:18.617	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.restart changed to linux-control.0.Proxmox_3_Keller.services._.restart

linux-control.0
2026-04-28 10:38:18.614	warn	State "linux-control.0.Proxmox_3_Keller.services.●.description" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.612	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.description changed to linux-control.0.Proxmox_3_Keller.services._.description

linux-control.0
2026-04-28 10:38:18.609	warn	State "linux-control.0.Proxmox_3_Keller.services.●.running" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.608	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.running changed to linux-control.0.Proxmox_3_Keller.services._.running

linux-control.0
2026-04-28 10:38:18.604	warn	State "linux-control.0.Proxmox_3_Keller.services.●.active" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.602	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.active changed to linux-control.0.Proxmox_3_Keller.services._.active

linux-control.0
2026-04-28 10:38:18.558	warn	State "linux-control.0.Proxmox_3_Keller.services.●.load" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.557	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.load changed to linux-control.0.Proxmox_3_Keller.services._.load

linux-control.0
2026-04-28 10:38:18.489	error	ReplyError: Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.stop" 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-04-28 10:38:18.488	error	unhandled promise rejection: Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.stop" is not a valid ID pattern

linux-control.0
2026-04-28 10:38:18.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().

host.ioBroker
2026-04-28 10:38:18.478	warn	host.ioBroker-Server States 127.0.0.1:54768 Error from InMemDB: Error: The pattern "linux-control.0.Proxmox_3_Keller.services.●.stop" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:323:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:240: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:519:28) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:484:21) at process.callbackTrampoline (node:internal/async_hooks:130:17)

linux-control.0
2026-04-28 10:38:18.469	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.stop changed to linux-control.0.Proxmox_3_Keller.services._.stop

linux-control.0
2026-04-28 10:38:18.454	error	Error: The pattern "io.linux-control.0.Proxmox_3_Keller.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:2507: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:103:5)

linux-control.0
2026-04-28 10:38:18.395	error	unhandled promise rejection: The pattern "io.linux-control.0.Proxmox_3_Keller.services.●.start" is not a valid ID pattern

linux-control.0
2026-04-28 10:38:18.395	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-04-28 10:38:18.321	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.start changed to linux-control.0.Proxmox_3_Keller.services._.start

linux-control.0
2026-04-28 10:38:18.320	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

linux-control.0
2026-04-28 10:38:18.311	error	Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.restart" is not a valid ID pattern

linux-control.0
2026-04-28 10:38:18.311	error	ReplyError: Error The pattern "linux-control.0.Proxmox_3_Keller.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-04-28 10:38:18.309	error	unhandled promise rejection: Error The pattern "linux-control.0.Proxmox_3_Keller.services.●.restart" is not a valid ID pattern

linux-control.0
2026-04-28 10:38:18.309	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
2026-04-28 10:38:18.308	warn	host.ioBroker-Server States 127.0.0.1:54768 Error from InMemDB: Error: The pattern "linux-control.0.Proxmox_3_Keller.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:2507:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:323:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:240: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:519:28) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:484:21) at process.callbackTrampoline (node:internal/async_hooks:130:17)

linux-control.0
2026-04-28 10:38:18.306	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.restart changed to linux-control.0.Proxmox_3_Keller.services._.restart

linux-control.0
2026-04-28 10:38:18.261	warn	State "linux-control.0.Proxmox_3_Keller.services.●.description" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.259	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.description changed to linux-control.0.Proxmox_3_Keller.services._.description

linux-control.0
2026-04-28 10:38:18.256	warn	State "linux-control.0.Proxmox_3_Keller.services.●.running" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.255	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.running changed to linux-control.0.Proxmox_3_Keller.services._.running

linux-control.0
2026-04-28 10:38:18.252	warn	State "linux-control.0.Proxmox_3_Keller.services.●.active" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.250	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.active changed to linux-control.0.Proxmox_3_Keller.services._.active

linux-control.0
2026-04-28 10:38:18.206	warn	State "linux-control.0.Proxmox_3_Keller.services.●.load" has no existing object, this might lead to an error in future versions

linux-control.0
2026-04-28 10:38:18.202	warn	Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.load changed to linux-control.0.Proxmox_3_Keller.services._.load

host.ioBroker
2026-04-28 10:38:14.443	info	instance system.adapter.linux-control.0 in version "1.1.6" (non-npm: Scrounger/ioBroker.linux-control) started with pid 523161

host.ioBroker
2026-04-28 10:38:13.485	info	"system.adapter.linux-control.0" enabled

[Ro75]

@Negalein sagte:

Used invalid characters: linux-control.0.Proxmox_3_Keller.services.●.load

Das Problem gab es schon bei anderen. Kan dir aber leider nicht mehr die Lösung sagen. Im Log sehe ich immer nur Keller_3.

Ro75.

[crunchip]

@Negalein sagte:

Error: The pattern "io.linux-control.0.Proxmox_3_Keller.services.●.start" is not a valid ID pattern

https://github.com/Scrounger/ioBroker.linux-control/issues/55

mach den Haken mal weg bei services

[Negalein]

@crunchip sagte:

https://github.com/Scrounger/ioBroker.linux-control/issues/55

ah, da war ja mal was von mir. hab ich vergessen.

mach den Haken mal weg bei services

jetzt kommen nur noch die cpu-temp Fehler.

hab das als Befehl
vcgencmd measure_temp | awk '{print substr($1, length($0)-5,4)}'

linux-control.0
2026-04-28 11:41:26.934	error	[userCommandExecute] Proxmox_2_Keller (10.0.1.205:22, id: cpu-temp, description: die temp des servers): response error: bash: line 1: vcgencmd: command not found, stack: ResponseError: [userCommandExecute] Proxmox_2_Keller (10.0.1.205:22, id: cpu-temp, description: die temp des servers): bash: line 1: vcgencmd: command not found at LinuxControl.sendCommand (/opt/iobroker/node_modules/iobroker.linux-control/main.js:907:26) at processTicksAndRejections (node:internal/process/task_queues:103:5) at LinuxControl.userCommandExecute (/opt/iobroker/node_modules/iobroker.linux-control/main.js:249:21)

linux-control.0
2026-04-28 11:41:26.681	error	[userCommandExecute] Proxmox_1_Heizraum (10.0.1.201:22, id: cpu-temp, description: die temp des servers): response error: bash: line 1: vcgencmd: command not found, stack: ResponseError: [userCommandExecute] Proxmox_1_Heizraum (10.0.1.201:22, id: cpu-temp, description: die temp des servers): bash: line 1: vcgencmd: command not found at LinuxControl.sendCommand (/opt/iobroker/node_modules/iobroker.linux-control/main.js:907:26) at processTicksAndRejections (node:internal/process/task_queues:103:5) at LinuxControl.userCommandExecute (/opt/iobroker/node_modules/iobroker.linux-control/main.js:249:21)

linux-control.0
2026-04-28 11:41:25.087	error	[userCommandExecute] Proxmox_3_Keller (10.0.1.206:22, id: cpu-temp, description: die temp des servers): response error: bash: line 1: vcgencmd: command not found, stack: ResponseError: [userCommandExecute] Proxmox_3_Keller (10.0.1.206:22, id: cpu-temp, description: die temp des servers): bash: line 1: vcgencmd: command not found at LinuxControl.sendCommand (/opt/iobroker/node_modules/iobroker.linux-control/main.js:907:26) at processTicksAndRejections (node:internal/process/task_queues:103:5) at LinuxControl.userCommandExecute (/opt/iobroker/node_modules/iobroker.linux-control/main.js:249:21)

[Thomas Braun]

@Negalein sagte:

vcgencmd

ist ein RaspberryOS spezifisches Kommando. Auf anderen Linuxen/anderer Hardware kommst du damit nicht ans Ziel.

[Negalein]

@Thomas-Braun sagte:

ist ein RaspberryOS spezifisches Kommando. Auf anderen Linuxen/anderer Hardware kommst du damit nicht ans Ziel.

ah, danke

dann werd ich mich mal auf die Suche machen

[crunchip]

@Negalein sagte:

cpu-temp

sensors | grep Package -m 1 | awk '{print $4}' | awk '{print substr($1, length($0)-6,2)}'

[Negalein]

@crunchip sagte:

sensors | grep Package -m 1 | awk '{print $4}' | awk '{print substr($1, length($0)-6,2)}'

Danke

Sind noch da

linux-control.0
2026-04-28 12:05:02.862	error	[userCommandExecute] Proxmox_1_Heizraum (10.0.1.201:22, id: cpu-temp, description: die temp des servers): response error: bash: line 1: sensors: command not found, stack: ResponseError: [userCommandExecute] Proxmox_1_Heizraum (10.0.1.201:22, id: cpu-temp, description: die temp des servers): bash: line 1: sensors: command not found at LinuxControl.sendCommand (/opt/iobroker/node_modules/iobroker.linux-control/main.js:907:26) at processTicksAndRejections (node:internal/process/task_queues:103:5) at LinuxControl.userCommandExecute (/opt/iobroker/node_modules/iobroker.linux-control/main.js:249:21) at LinuxControl.userCommand (/opt/iobroker/node_modules/iobroker.linux-control/main.js:204:10) at LinuxControl.refreshHost (/opt/iobroker/node_modules/iobroker.linux-control/main.js:85:5) at async Promise.allSettled (index 0) at LinuxControl.onReady (/opt/iobroker/node_modules/iobroker.linux-control/main.js:53:4)

linux-control.0
2026-04-28 12:05:02.412	error	[userCommandExecute] Proxmox_2_Keller (10.0.1.205:22, id: cpu-temp, description: die temp des servers): response error: bash: line 1: sensors: command not found, stack: ResponseError: [userCommandExecute] Proxmox_2_Keller (10.0.1.205:22, id: cpu-temp, description: die temp des servers): bash: line 1: sensors: command not found at LinuxControl.sendCommand (/opt/iobroker/node_modules/iobroker.linux-control/main.js:907:26) at processTicksAndRejections (node:internal/process/task_queues:103:5) at LinuxControl.userCommandExecute (/opt/iobroker/node_modules/iobroker.linux-control/main.js:249:21) at LinuxControl.userCommand (/opt/iobroker/node_modules/iobroker.linux-control/main.js:204:10) at LinuxControl.refreshHost (/opt/iobroker/node_modules/iobroker.linux-control/main.js:85:5) at async Promise.allSettled (index 1) at LinuxControl.onReady (/opt/iobroker/node_modules/iobroker.linux-control/main.js:53:4)

linux-control.0
2026-04-28 12:05:00.840	error	[userCommandExecute] Proxmox_3_Keller (10.0.1.206:22, id: cpu-temp, description: die temp des servers): response error: bash: line 1: sensors: command not found, stack: ResponseError: [userCommandExecute] Proxmox_3_Keller (10.0.1.206:22, id: cpu-temp, description: die temp des servers): bash: line 1: sensors: command not found at LinuxControl.sendCommand (/opt/iobroker/node_modules/iobroker.linux-control/main.js:907:26) at processTicksAndRejections (node:internal/process/task_queues:103:5) at LinuxControl.userCommandExecute (/opt/iobroker/node_modules/iobroker.linux-control/main.js:249:21) at LinuxControl.userCommand (/opt/iobroker/node_modules/iobroker.linux-control/main.js:204:10) at LinuxControl.refreshHost (/opt/iobroker/node_modules/iobroker.linux-control/main.js:85:5) at async Promise.allSettled (index 2) at LinuxControl.onReady (/opt/iobroker/node_modules/iobroker.linux-control/main.js:53:4)

[Thomas Braun]

@Negalein sagte:

sensors: command not found

Also ist auch das Kommando nicht verfügbar. Kann aber ggfls. nachinstalliert werden.
Wobei solch hardwarenahes Zeuch auch auf dem Proxmox-Host besser aufgehoben wäre, denke ich.

[crunchip]

@Negalein muss auf dem proxmox host installiert sein

apt install lm-sensors

dann ausführen

sensors-detect

anschliessend

sensors

zeigt dir im teminal die Werte an

somit sollte dann auch der Adapter die Werte abholen können

[Meister Mopper]

Ich bekomme die CPU-Temp meiner NUC mit

sensors | grep 'Package id 0:' | awk '{print $4}' | cut -c2-3

[Negalein]

Danke euch