NEWS
Telegram Meldung ignoriert, Uhrzeit falsch?
-
@atomicix sagte: "0_userdata.0.Aliase.USV.ALI-USV-Energie-I-Net" is missing the required property "common.type"
Korrigiere den Datenpunkt.
@paul53
Ja habe ich, hat ja aber nichts damit zutun.telegram.0 2025-01-26 19:58:51.426 warn Message from undefined ignored, because too old: (32000) Status telegram.0 2025-01-26 19:58:31.043 warn Message from undefined ignored, because too old: (32000) Status telegram.0 2025-01-26 19:58:29.005 warn Message from undefined ignored, because too old: (32000) Status -
@paul53
Ja habe ich, hat ja aber nichts damit zutun.telegram.0 2025-01-26 19:58:51.426 warn Message from undefined ignored, because too old: (32000) Status telegram.0 2025-01-26 19:58:31.043 warn Message from undefined ignored, because too old: (32000) Status telegram.0 2025-01-26 19:58:29.005 warn Message from undefined ignored, because too old: (32000) Status -
*** TIME AND TIMEZONES *** Local time: Sun 2025-01-26 20:30:55 CET Universal time: Sun 2025-01-26 19:30:55 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: no NTP service: inactive RTC in local TZ: noMOD-EDIT: Code in code-tags gesetzt!
Die Zeiten sehen gut aus, müßte aber bei NTP was drinnen stehen?
-
*** TIME AND TIMEZONES *** Local time: Sun 2025-01-26 20:30:55 CET Universal time: Sun 2025-01-26 19:30:55 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: no NTP service: inactive RTC in local TZ: noMOD-EDIT: Code in code-tags gesetzt!
Die Zeiten sehen gut aus, müßte aber bei NTP was drinnen stehen?
@atomicix sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
Die Zeiten sehen gut aus, müßte aber bei NTP was drinnen stehen?
Meine Systeme laufen alle mit NTP.
*** TIME AND TIMEZONES *** Local time: Sun 2025-01-26 21:08:14 CET Universal time: Sun 2025-01-26 20:08:14 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no -
@atomicix sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
Die Zeiten sehen gut aus, müßte aber bei NTP was drinnen stehen?
Meine Systeme laufen alle mit NTP.
*** TIME AND TIMEZONES *** Local time: Sun 2025-01-26 21:08:14 CET Universal time: Sun 2025-01-26 20:08:14 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no -
@thomas-braun ich habe den NTP nach installiert, aber bei der Systemzeit Synchronisation ist bei mir No.
Wie kann ich das ändern?
Warum passiert das, durch ändern der Fritzbox?
Das System lief 2 Jahre oder so einwandfrei.@atomicix sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
Wie kann ich das ändern?
Hängt von dem System ab, das du da fährst.
-
@atomicix sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
Message from undefined ignored, because too old
Das Problem gab es schon öfters hier im Forum, scheinbar lag es immer an der falschen Uhrzeit:
https://forum.iobroker.net/post/819850ioBroker@Ubuntu 24.04 LTS (VMware) für: >260 Geräte, 5 Switche, 7 AP, 9 IP-Cam, 1 NAS 42TB, 1 ESXi 15TB, 4 Proxmox 1TB, 1 Hyper-V 48TB, 14 x Echo, 5x FireTV, 5 x Tablett/Handy VIS || >=160 Tasmota/Shelly || >=95 ZigBee || PV 8.1kW / Akku 14kWh || 2x USV 750W kaskadiert || Creality CR-10 SE 3D-Drucker
-
@atomicix sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
Message from undefined ignored, because too old
Das Problem gab es schon öfters hier im Forum, scheinbar lag es immer an der falschen Uhrzeit:
https://forum.iobroker.net/post/819850@bananajoe
Danke, ja das hatte ich auch schon, aber ich finde halt die falsche Zeit nicht.
Ich muss heute Abend noch mal gucken, mit der Synchronisation, warum die nicht da ist, ob es vielleicht am Lxc liegt.
Dann wäre aber die Frage, was hat die Fritzbox damit zutun... 🤔🫣 -
Ich bekomme das nicht hin.
Local time: Mo 2025-01-27 18:21:36 CET Universal time: Mo 2025-01-27 17:21:36 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: no NTP service: active RTC in local TZ: noDie Zeit wird nicht Synchronisiert.
Auch wenn die Zeit richtig geht, bekomme ich in Telegram immer noch die Meldung.Das alles läuft über Proxmox auf einem LXC mit Ubuntu.
Aber wie schon geschrieben, das lief jetzt 2 Jahre oder so ohne Probleme. Habe nur die Fritzbox getauscht.
Ich werde wohl die Tage noch mal in Garten fahren und zum Test die alte Fritzbox einhängen.
Habe jetzt so viel an den NTP Einstellungen geändert,..... -
Ich bekomme das nicht hin.
Local time: Mo 2025-01-27 18:21:36 CET Universal time: Mo 2025-01-27 17:21:36 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: no NTP service: active RTC in local TZ: noDie Zeit wird nicht Synchronisiert.
Auch wenn die Zeit richtig geht, bekomme ich in Telegram immer noch die Meldung.Das alles läuft über Proxmox auf einem LXC mit Ubuntu.
Aber wie schon geschrieben, das lief jetzt 2 Jahre oder so ohne Probleme. Habe nur die Fritzbox getauscht.
Ich werde wohl die Tage noch mal in Garten fahren und zum Test die alte Fritzbox einhängen.
Habe jetzt so viel an den NTP Einstellungen geändert,.....@atomicix sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
Habe nur die Fritzbox getauscht.
Und die neue Fritte hat die gleiche IP und bietet auch NTP an?
-
Ich bekomme das nicht hin.
Local time: Mo 2025-01-27 18:21:36 CET Universal time: Mo 2025-01-27 17:21:36 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: no NTP service: active RTC in local TZ: noDie Zeit wird nicht Synchronisiert.
Auch wenn die Zeit richtig geht, bekomme ich in Telegram immer noch die Meldung.Das alles läuft über Proxmox auf einem LXC mit Ubuntu.
Aber wie schon geschrieben, das lief jetzt 2 Jahre oder so ohne Probleme. Habe nur die Fritzbox getauscht.
Ich werde wohl die Tage noch mal in Garten fahren und zum Test die alte Fritzbox einhängen.
Habe jetzt so viel an den NTP Einstellungen geändert,.....Du weißt, das die FritzBox als NTP-Server fungieren kann? Dann deren IP dort eintragen.
-
So, ich habe noch mal ein wenige probiert.
Ich habe im Schrebergarten meine alte Fritzbox wieder eingebaut. Hat aber keine Änderung gebracht, trotz Neustart ect.
Mein Proxmox System zeigt mir:
Der LXC Container :
Zu dem Zeitpunkt auch alles korrekt.Jetzt habe ich zuhause mein Testsystem gestartet, das ich eigentlich demnächst auch ersetzten wollte im Garten.
Selbe Hardware (Intel NUC) und Proxmox komplett neu aufgesetzt und alles neu installiert, nur halt ein Backup vom iobroker importiert.Das System läuft halt bei mir zuhause an einer anreden Fritzbox mit Kabelanschluss, im Garten läuft alles über Sim Karte.
Aber egal wie, der Bot will nicht auf Nachrichten reagieren. Es ist auch egal, wer die Nachrichten schickt. Meine Frau oder ich.
Also tippe ich eher darauf, daß es nichts mit der Fritzbox zutun hat, sondern was anderes. Das es zum Zeitpunkt des tausch der FB passiert ist, lag wahrscheinlich am Neustart des NUC/Proxmox.
Wie kann ich jetzt weiter vorgehen, um eine Lösung zu finden? Als telegram sendet Status Meldungen ect, reagiert aber nicht auf Befehle, die ausgeführt werden wollen Text to Command.
EDIT:
Hier noch mal ein Auszug aus dem Logo.
telegram.0 2025-01-30 21:54:53.644 warn Message from undefined ignored, because too old: (32000) Status telegram.0 2025-01-30 21:54:53.644 debug {"message_id":38864,"from":{"id":233794520,"is_bot":false,"first_name":"Christian","last_name":"XXX","username":"AtomicIX","language_code":"de"},"chat":{"id":233794520,"first_name":"Christian","last_name":"XXXX","username":"AtomicIX","type":"private"},"date":1738270451,"text":"Status"} telegram.0 2025-01-30 21:54:53.643 debug Received message: {"message_id":38864,"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":1738270451,"text":"Status"} telegram.0 2025-01-30 21:54:49.950 debug Message sent telegram.0 2025-01-30 21:54:49.950 debug Request [saveSendRequest]: {"message_id":38863,"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":1738270448,"text":"_Gartenbot Online"} telegram.0 2025-01-30 21:54:49.946 debug Message sent telegram.0 2025-01-30 21:54:49.946 debug Request [saveSendRequest]: {"message_id":38862,"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":1738270448,"text":"_Gartenbot Online"} telegram.0 2025-01-30 21:54:49.876 debug Send message to [atoemchenIX]: "_Gartenbot Online" telegram.0 2025-01-30 21:54:49.876 debug Send message to [AtomicIX]: "_Gartenbot Online" telegram.0 2025-01-30 21:54:49.874 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-01-30 21:54:49.602 debug Start polling with: 2000(number) ms interval telegram.0 2025-01-30 21:54:49.480 info starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.18.1, js-controller: 7.0.6 -
Kann mir irgendjemand weiterhelfen?
Wonach kann ich noch gucken? Was kann ich machen, um den Fehler zu finden?
Kann es was mit den Telegram Accounts zutun haben?@atomicix
du könntest mal das Logging verschärfen, also von Info auf Debug stellen, das ganz noch mal versuchen und die Logs hier einstellen.ist ja schon DebugVielleicht kann man dieses etwas entnehmen
Du hast ja oben in Zeile 5 z.B.2025-01-30 21:54:53.644 debug {"message_id":38864,"from":{"id":233794520,"is_bot":false,"first_name":"Christian","last_name":"XXX","username":"AtomicIX","language_code":"de"},"chat":{"id":233794520,"first_name":"Christian","last_name":"XXXX","username":"AtomicIX","type":"private"},"date":1738270451,"text":"Status"}Der Zeitstempel des Log-Eintrags ist
2025-01-30 21:54:53.644. Weiter hinten kommt auch ein Zeitstempel:"date":1738270451. Wenn ich den umrechne, z.B. per https://www.unixtime.de/index.php kommt da30.01.2025 - 21:54:11raus, immerhin 42 Sekunden unterschied. Muss nichts bedeuten.
Ein Eintrag bei mir wo ich mir etwas vom Handy sende sieht aber so aus:2025-02-01 12:45:22.442 - debug: telegram.0 (820625) {"message_id":33511,"from":{"id":643047793,"is_bot":false,"first_name":"Bernhard","last_name":"****","username":"Bernhard****","language_code":"de"},"chat":{"id":643047793,"first_name":"Bernhard","last_name":"****","username":"Bernhard****","type":"private"},"date":1738410322,"text":"Totaler Test"}Zeitstempel des Logs ist
2025-02-01 12:45:22.442, Zeit aus dem JSON ist"date":1738410322=>01.02.2025 - 12:45:22, also Abweichung < 1 SekundeWenn du nun die Meldung
2025-01-26 19:29:52.122 warn Message from undefined ignored, because too old: (32000) Statussteht davor eventuell mehr. Eventuell etwas mit falschen Zeitstempel, eventuell sieht man auch etwas anderes.
Und ein
iob diagkann auch nicht schaden, da könnte man deine Version etc. sehen.
ioBroker@Ubuntu 24.04 LTS (VMware) für: >260 Geräte, 5 Switche, 7 AP, 9 IP-Cam, 1 NAS 42TB, 1 ESXi 15TB, 4 Proxmox 1TB, 1 Hyper-V 48TB, 14 x Echo, 5x FireTV, 5 x Tablett/Handy VIS || >=160 Tasmota/Shelly || >=95 ZigBee || PV 8.1kW / Akku 14kWh || 2x USV 750W kaskadiert || Creality CR-10 SE 3D-Drucker
-
@atomicix
du könntest mal das Logging verschärfen, also von Info auf Debug stellen, das ganz noch mal versuchen und die Logs hier einstellen.ist ja schon DebugVielleicht kann man dieses etwas entnehmen
Du hast ja oben in Zeile 5 z.B.2025-01-30 21:54:53.644 debug {"message_id":38864,"from":{"id":233794520,"is_bot":false,"first_name":"Christian","last_name":"XXX","username":"AtomicIX","language_code":"de"},"chat":{"id":233794520,"first_name":"Christian","last_name":"XXXX","username":"AtomicIX","type":"private"},"date":1738270451,"text":"Status"}Der Zeitstempel des Log-Eintrags ist
2025-01-30 21:54:53.644. Weiter hinten kommt auch ein Zeitstempel:"date":1738270451. Wenn ich den umrechne, z.B. per https://www.unixtime.de/index.php kommt da30.01.2025 - 21:54:11raus, immerhin 42 Sekunden unterschied. Muss nichts bedeuten.
Ein Eintrag bei mir wo ich mir etwas vom Handy sende sieht aber so aus:2025-02-01 12:45:22.442 - debug: telegram.0 (820625) {"message_id":33511,"from":{"id":643047793,"is_bot":false,"first_name":"Bernhard","last_name":"****","username":"Bernhard****","language_code":"de"},"chat":{"id":643047793,"first_name":"Bernhard","last_name":"****","username":"Bernhard****","type":"private"},"date":1738410322,"text":"Totaler Test"}Zeitstempel des Logs ist
2025-02-01 12:45:22.442, Zeit aus dem JSON ist"date":1738410322=>01.02.2025 - 12:45:22, also Abweichung < 1 SekundeWenn du nun die Meldung
2025-01-26 19:29:52.122 warn Message from undefined ignored, because too old: (32000) Statussteht davor eventuell mehr. Eventuell etwas mit falschen Zeitstempel, eventuell sieht man auch etwas anderes.
Und ein
iob diagkann auch nicht schaden, da könnte man deine Version etc. sehen.
@bananajoe sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
immerhin 42 Sekunden unterschied.
Das wäre jetzt sehr interessant wie groß die differenz ist
so etwas hatte ich vermutet, dass es gar nicht sooo viel sri.
Sieh zu dass du deine ntp Synchronisation hinbekommst und gut ist. -
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?
-
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?
@atomicix sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
die Web Version von Telegram
was soll das sein?
Telegram für Win? -
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?
@atomicix sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
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"}
-
@homoran sagte in Telegram Meldung ignoriert, Uhrzeit falsch?:
1738412580
Ich bekomme das einfach nicht hin.
Egal ob auf dem System im Garten, das jetzt lange Zeit ohne Probleme lief, sowohl auch das relativ neue System 2 Monate alt, das hier zuhause steht, laufen nicht mit dem Bot und Commandos.
Die Zeit Sync soll wohl aus dem Hauptsystem von Proxmox kommen und dann an den LXC weitergereicht werden.Ich habe echt keine Ahnung was/wie/warum das zusammen hängt.
Werde gleich mal iobroker auf nen Raspaberry installieren und gucken ob es da läuft.
Es gibt sonnst Telegram direkt übern Browser: https://web.telegram.org/ aber das geht scheinbar auch nicht mehr.
729
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge