Hier noch mal der Log, mit Neustart und senden von Befehlen:
telegram.0
2025-02-01 13:23:46.092 warn Message from undefined ignored, because too old: (32000) Alarm Ein
telegram.0
2025-02-01 13:23:46.092 debug {"message_id":38969,"from":{"id":233794520,"is_bot":false,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","language_code":"de"},"chat":{"id":233794520,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","type":"private"},"date":1738412583,"text":"Alarm Ein"}
telegram.0
2025-02-01 13:23:46.092 debug Received message: {"message_id":38969,"from":{"id":233794520,"is_bot":false,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","language_code":"de"},"chat":{"id":233794520,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","type":"private"},"date":1738412583,"text":"Alarm Ein"}
telegram.0
2025-02-01 13:23:42.293 warn Message from undefined ignored, because too old: (32000) Temp
telegram.0
2025-02-01 13:23:42.293 debug {"message_id":38967,"from":{"id":233794520,"is_bot":false,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","language_code":"de"},"chat":{"id":233794520,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","type":"private"},"date":1738412580,"text":"Temp"}
telegram.0
2025-02-01 13:23:42.293 debug Received message: {"message_id":38967,"from":{"id":233794520,"is_bot":false,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","language_code":"de"},"chat":{"id":233794520,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","type":"private"},"date":1738412580,"text":"Temp"}
telegram.0
2025-02-01 13:23:37.308 warn Message from undefined ignored, because too old: (32000) Status
telegram.0
2025-02-01 13:23:37.308 debug {"message_id":38965,"from":{"id":233794520,"is_bot":false,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","language_code":"de"},"chat":{"id":233794520,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","type":"private"},"date":1738412575,"text":"Status"}
telegram.0
2025-02-01 13:23:37.307 debug Received message: {"message_id":38965,"from":{"id":233794520,"is_bot":false,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","language_code":"de"},"chat":{"id":233794520,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","type":"private"},"date":1738412575,"text":"Status"}
tuya.0
2025-02-01 13:23:22.813 info bfec618747cb2be16fqyt8: Error on Reconnect (7): connection timed out
tuya.0
2025-02-01 13:23:22.808 info bfb57ca31a04d31ee0uqcx: Error on Reconnect (7): connection timed out
tuya.0
2025-02-01 13:23:22.808 info bf6e3bf664db95b0b563pv: Error on Reconnect (7): connection timed out
tuya.0
2025-02-01 13:23:20.939 info bfd00e48eac1982331wna0: Error on Reconnect (7): connect EHOSTUNREACH 192.168.221.171:6668
tuya.0
2025-02-01 13:23:19.057 info bfefff66b01e1b11c4ifow: Error on Reconnect (7): connection timed out
tuya.0
2025-02-01 13:23:19.017 info bf6ca8fbf11f2b48fegk2u: Error on Reconnect (7): connect EHOSTUNREACH 192.168.221.174:6668
tuya.0
2025-02-01 13:23:15.196 info bff281bf90a49cd191hbxi: Error on Reconnect (7): connect EHOSTUNREACH 192.168.222.182:6668
telegram.0
2025-02-01 13:23:10.393 debug Message sent
telegram.0
2025-02-01 13:23:10.392 debug Request [saveSendRequest]: {"message_id":38964,"from":{"id":702553359,"is_bot":true,"first_name":"GartenBot","username":"AtomicGarten_Bot"},"chat":{"id":233794520,"first_name":"Christian","last_name":"xxxx","username":"AtomicIX","type":"private"},"date":1738412548,"text":"_Gartenbot Online"}
telegram.0
2025-02-01 13:23:10.392 debug Message sent
telegram.0
2025-02-01 13:23:10.391 debug Request [saveSendRequest]: {"message_id":38963,"from":{"id":702553359,"is_bot":true,"first_name":"GartenBot","username":"AtomicGarten_Bot"},"chat":{"id":369356584,"first_name":"Jasmin","last_name":"xxxx","username":"atoemchenIX","type":"private"},"date":1738412548,"text":"_Gartenbot Online"}
telegram.0
2025-02-01 13:23:10.319 debug Send message to [atoemchenIX]: "_Gartenbot Online"
telegram.0
2025-02-01 13:23:10.319 debug Send message to [AtomicIX]: "_Gartenbot Online"
telegram.0
2025-02-01 13:23:10.318 debug getMe: {"id":702553359,"is_bot":true,"first_name":"GartenBot","username":"AtomicGarten_Bot","can_join_groups":true,"can_read_all_group_messages":false,"supports_inline_queries":false,"can_connect_to_business":false,"has_main_web_app":false}
telegram.0
2025-02-01 13:23:10.048 debug Start polling with: 2000(number) ms interval
telegram.0
2025-02-01 13:23:09.887 info starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.18.1, js-controller: 7.0.6
telegram.0
2025-02-01 13:23:09.765 debug Plugin sentry Initialize Plugin (enabled=true)
telegram.0
2025-02-01 13:23:09.750 debug States connected to redis: 127.0.0.1:9000
telegram.0
2025-02-01 13:23:09.696 debug States create User PubSub Client
telegram.0
2025-02-01 13:23:09.696 debug States create System PubSub Client
telegram.0
2025-02-01 13:23:09.689 debug Redis States: Use Redis connection: 127.0.0.1:9000
telegram.0
2025-02-01 13:23:09.674 debug Objects connected to redis: 127.0.0.1:9001
telegram.0
2025-02-01 13:23:09.672 debug Objects client initialize lua scripts
telegram.0
2025-02-01 13:23:09.558 debug Objects create User PubSub Client
telegram.0
2025-02-01 13:23:09.558 debug Objects create System PubSub Client
telegram.0
2025-02-01 13:23:09.558 debug Objects client ready ... initialize now
telegram.0
2025-02-01 13:23:09.543 debug Redis Objects: Use Redis connection: 127.0.0.1:9001
host.ioBroker
2025-02-01 13:23:09.114 info instance system.adapter.telegram.0 in version "4.0.0" started with pid 190323
host.ioBroker
2025-02-01 13:23:05.906 info instance system.adapter.telegram.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
Hier noch mal der Auzug aus dem iob diag:
========== Start marking the full check here ===========
```bash
Script v.2024-10-19
*** BASE SYSTEM ***
Static hostname: ioBroker
Icon name: computer-container
Chassis: container ☐
Virtualization: lxc
Operating System: Ubuntu 24.10
Kernel: Linux 6.8.12-4-pve
Architecture: x86-64
OS is similar to: debian
model name : Intel(R) Core(TM) i7-10710U CPU @ 1.10GHz
Docker : false
Virtualization : lxc
Kernel : x86_64
Userland : 64 bit
Systemuptime and Load:
13:25:33 up 3 days, 20:44, 2 users, load average: 0.13, 0.35, 0.28
CPU threads: 4
*** LIFE CYCLE STATUS ***
Operating System codenamed 'oracular' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time!
*** TIME AND TIMEZONES ***
Local time: Sat 2025-02-01 13:25:33 CET
Universal time: Sat 2025-02-01 12:25:33 UTC
RTC time: n/a
Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no
*** Users and Groups ***
User that called 'iob diag':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout sudo audio video
User that is running 'js-controller':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout sudo audio video
A default user should be created! This user will be enabled to temporarily switch to root via 'sudo'!
A root login is not required in most Linux Distributions.
Run 'iobroker fix' or use the system tools to create a user.
*** DISPLAY-SERVER SETUP ***
Display-Server: false
Desktop:
Terminal: tty
System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix'
*** MEMORY ***
total used free shared buff/cache available
Mem: 6.4G 2.1G 2.1G 163K 2.2G 4.3G
Swap: 1.1G 4.1K 1.1G
Total: 7.5G 2.1G 3.2G
Active iob-Instances: 35
6144 M total memory
2038 M used memory
2009 M active memory
1935 M inactive memory
2007 M free memory
0 M buffer memory
2097 M swap cache
1024 M total swap
0 M used swap
1023 M free swap
*** top - Table Of Processes ***
top - 13:25:33 up 3 days, 20:44, 2 users, load average: 0.13, 0.35, 0.28
Tasks: 69 total, 1 running, 68 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 6144.0 total, 2005.4 free, 2040.7 used, 2098.1 buff/cache
MiB Swap: 1024.0 total, 1024.0 free, 0.0 used. 4103.3 avail Mem
*** FAILED SERVICES ***
UNIT LOAD ACTIVE SUB DESCRIPTION
* run-rpc_pipefs.mount loaded failed failed RPC Pipe File System
* sys-kernel-config.mount loaded failed failed Kernel Configuration File System
Legend: LOAD -> Reflects whether the unit definition was properly loaded.
ACTIVE -> The high-level unit activation state, i.e. generalization of SUB.
SUB -> The low-level unit activation state, values depend on unit type.
2 loaded units listed.
*** DMESG CRITICAL ERRORS ***
@Homoran ja das werde ich probieren. Aber alles was ich dazu gefunden habe, hat bis jetzt nicht funktioniert.
Mir ist eben aufgefallen, das die Web Version von Telegram nicht mehr geht. Ist das nur bei mir so, oder wurde die abgeschaltet?
Vielleicht opfere ich einfach einen Kanal von den 4Ch Geräten und synchronisiere ihn mit dem POW 
. 
