Neues YouTube-Video: Visualisierung im Devices-Adapter

[searcher57]

Hallo,
kann mir jemand sagen, wie ich die lästige automatische "Actual day time" (minütlich) und die UUID alle 30 min deaktiviere?
Gruß Rainer

[Ahnungsbefreit]

@searcher57 Das ist keine automatische Meldung von Telegram. Da scheint noch irgendwas bei Dir zu laufen wie ein Script?

[searcher57]

Hallo @ahnungsbefreit ```
ich habe alle Scripte gestoppt. Trotzdem kommt jede Minute die Meldung.
hier ein Auszug von meinem LOG.

stateChange system.adapter.telegram.0.cputime 25.9 true telegram.0 2021-08-02 18:09:45.639 2021-08-02 18:09:45.639
stateChange system.adapter.telegram.0.cpu 0.47 true telegram.0 2021-08-02 18:09:45.639 2021-08-02 18:09:45.639
stateChange system.adapter.telegram.0.outputCount 11 true telegram.0 2021-08-02 18:09:45.615 2021-08-02 18:09:15.606
stateChange system.adapter.telegram.0.inputCount 0 true telegram.0 2021-08-02 18:09:45.615 2021-08-02 18:09:15.606
stateChange system.adapter.telegram.0.uptime 9302 true telegram.0 2021-08-02 18:09:45.615 2021-08-02 18:09:45.615
stateChange system.adapter.telegram.0.eventLoopLag 2 true telegram.0 2021-08-02 18:09:45.615 2021-08-02 18:09:45.615
stateChange system.adapter.telegram.0.memHeapUsed 20.02 true telegram.0 2021-08-02 18:09:45.614 2021-08-02 18:09:45.614
stateChange system.adapter.telegram.0.memHeapTotal 24.93 true telegram.0 2021-08-02 18:09:45.614 2021-08-02 17:44:15.562
stateChange system.adapter.telegram.0.memRss 69.93 true telegram.0 2021-08-02 18:09:45.613 2021-08-02 18:03:00.594
stateChange system.adapter.telegram.0.connected true true telegram.0 2021-08-02 18:09:45.609 2021-08-02 15:34:45.433
stateChange system.adapter.telegram.0.alive true true telegram.0 2021-08-02 18:09:45.608 2021-08-02 15:34:45.433
stateChange system.adapter.info.0.cputime 21.05 true info.0 2021-08-02 18:09:45.183 2021-08-02 18:09:45.183
stateChange system.adapter.info.0.cpu 0.13 true info.0 2021-08-02 18:09:45.183 2021-08-02 18:09:45.183
stateChange system.adapter.info.0.outputCount 11 true info.0 2021-08-02 18:09:45.156 2021-08-02 17:44:30.102
stateChange system.adapter.info.0.inputCount 0 true info.0 2021-08-02 18:09:45.155 2021-08-02 15:14:29.731
stateChange system.adapter.info.0.uptime 10550 true info.0 2021-08-02 18:09:45.155 2021-08-02 18:09:45.155
stateChange system.adapter.info.0.eventLoopLag 2 true info.0 2021-08-02 18:09:45.154 2021-08-02 18:08:15.152
stateChange system.adapter.info.0.memHeapUsed 15.1 true info.0 2021-08-02 18:09:45.154 2021-08-02 18:09:45.154
stateChange system.adapter.info.0.memHeapTotal 17.55 true info.0 2021-08-02 18:09:45.154 2021-08-02 17:45:00.103
stateChange system.adapter.info.0.memRss 62.52 true info.0 2021-08-02 18:09:45.153 2021-08-02 18:07:15.150
stateChange system.adapter.info.0.connected true true info.0 2021-08-02 18:09:45.153 2021-08-02 15:13:59.757
stateChange system.adapter.info.0.alive true true

[Ahnungsbefreit]

@searcher57 Der Loglevel steht überall auf Info oder Warn?

[searcher57]

@ahnungsbefreit Keine Ahnung! Hier ein neuer Auszug!

javascript.0	2021-08-02 18:17:00.758	info	(15776) Stop script script.js.NFC_HIFI_Schrank
javascript.0	2021-08-02 18:16:59.244	info	(15776) Stop script script.js.NFC_Schreibtisch
host.raspberrypi	2021-08-02 18:16:46.813	info	Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
telegram.0	2021-08-02 18:14:00.363	error	(16373) Cannot send message [chatId - 1470164179]: Error: ETELEGRAM: 400 Bad Request: message is too long
javascript.0	2021-08-02 18:08:48.719	info	(15776) script.js.NFC_HIFI_Schrank: registered 1 subscription and 0 schedules
javascript.0	2021-08-02 18:08:48.689	info	(15776) Start javascript script.js.NFC_HIFI_Schrank
javascript.0	2021-08-02 18:08:47.976	info	(15776) script.js.NFC_Schreibtisch: registered 1 subscription and 0 schedules
javascript.0	2021-08-02 18:08:47.913	info	(15776) Start javascript script.js.NFC_Schreibtisch
javascript.0	2021-08-02 18:08:43.167	info	(15776) Stop script script.js.NFC_HIFI_Schrank
telegram.0	2021-08-02 17:44:00.470	error	(16373) Cannot send message [chatId - 1470164179]: Error: ETELEGRAM: 400 Bad Request: message is too long
telegram.0	2021-08-02 17:14:00.503	error	(16373) Cannot send message [chatId - 1470164179]: Error: ETELEGRAM: 400 Bad Request: message is too long
telegram.0	2021-08-02 16:44:00.427	error	(16373) Cannot send message [chatId - 1470164179]: Error: ETELEGRAM: 400 Bad Request: message is too long
telegram.0	2021-08-02 16:14:00.483	error	(16373) Cannot send message [chatId - 1470164179]: Error: ETELEGRAM: 400 Bad Request: message is too long
telegram.0	2021-08-02 15:52:29.674	info	(16373) Receiving of system messages for user "1470164179" has been changed to true!
telegram.0	2021-08-02 15:52:28.253	info	(16373) Receiving of system messages for user "1470164179" has been changed to false!
javascript.0	2021-08-02 15:49:54.398	info	(15776) Stop script script.js.NFC_Schreibtisch
telegram.0	2021-08-02 15:44:00.403	error	(16373) Cannot send message [chatId - 1470164179]: Error: ETELEGRAM: 400 Bad Request: message is too long
telegram.0	2021-08-02 15:34:46.457	warn	(16373) Message from undefined ignored, because too old: (30300) /start
telegram.0	2021-08-02 15:34:45.318	info	(16373) starting. Version 1.10.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v12.22.4, js-controller: 3.2.16
host.raspberrypi	2021-08-02 15:34:43.311	info	instance system.adapter.telegram.0 started with pid 16373
host.raspberrypi	2021-08-02 15:34:43.199	info	"system.adapter.telegram.0" enabled