[Bug]: Not getting Status Updates (Similar to #126)

[qnicoud]

What happened and in what context?

Hello,

I tried to configure the bot to get status updates via the command and automatic updates but I have some issues with them :

• I don't get any automatic updates, whether when using time, percent (haven't tried height yet)
• status update request sent from the chat (/status) do not provide an up to date status. I can get the name of the file currently printing and the snapshot from the camera displayed properly, but all progress related info and ETA are as if the print had not started yet.

I the shared log, I set up progress_update_message = true but I also tried with the false value and the result is the same.

I tried to dig some info in the log but I see no errors even with debug.
Otherwise the bot is awesome, I tried some of the other functionalities and they work pretty well, thanks for the hard work :)

If needed, paste the relevant bot log contents here.

---

Current Moonraker telegram bot config
[bot]
server = localhost
debug = true

[camera]
host = http://localhost:8080/?action=stream
type = mjpeg
host_snapshot = http://localhost:8080/?action=snapshot

[progress_notification]
percent = 1

[telegram_ui]
progress_update_message = true
eta_source = file

---

2025-08-08 23:01:58,869 - camera - DEBUG - camera.py:152 -
General configuration for OpenCV 4.6.0 =====================================
Version control: unknown

Extra modules:
Location (extra): <>/contrib/modules
Version control (extra): unknown

Platform:
Host: aarch64
CMake: 3.25.1
CMake generator: Ninja
CMake build tool: /usr/bin/ninja
Configuration: Release

CPU/HW features:
Baseline: NEON FP16

C/C++:
Built as dynamic libs?: YES
C++ standard: 11
C++ Compiler: /usr/bin/c++ (ver 12.2.0)
C++ flags (Release): -g -O2 -ffile-prefix-map=<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fsigned-char -W -Wall -Wreturn-type -Wnon-virtual-dtor -Waddress -Wsequence-point -Wformat -Wformat-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Wsuggest-override -Wno-delete-non-virtual-dtor -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections -fvisibility=hidden -fvisibility-inlines-hidden -g -O2 -ffile-prefix-map=<>=. -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG
C++ flags (Debug): -g -O2 -ffile-prefix-map=<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fsigned-char -W -Wall -Wreturn-type -Wnon-virtual-dtor -Waddress -Wsequence-point -Wformat -Wformat-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Wsuggest-override -Wno-delete-non-virtual-dtor -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections -fvisibility=hidden -fvisibility-inlines-hidden -g -DDEBUG -D_DEBUG
C Compiler: /usr/bin/cc
C flags (Release): -g -O2 -ffile-prefix-map=<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fsigned-char -W -Wall -Wreturn-type -Waddress -Wsequence-point -Wformat -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections -fvisibility=hidden -g -O2 -ffile-prefix-map=<>=. -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG
C flags (Debug): -g -O2 -ffile-prefix-map=<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fsigned-char -W -Wall -Wreturn-type -Waddress -Wsequence-point -Wformat -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections -fvisibility=hidden -g -DDEBUG -D_DEBUG
Linker flags (Release): -Wl,-z,relro -Wl,-z,now -Wl,--gc-sections -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now
Linker flags (Debug): -Wl,-z,relro -Wl,-z,now -Wl,--gc-sections -Wl,--as-needed -Wl,--no-undefined
ccache: NO
Precompiled headers: NO
Extra dependencies: dl m pthread rt
3rdparty dependencies:

OpenCV modules:
To be built: alphamat aruco barcode bgsegm bioinspired calib3d ccalib core cvv datasets dnn dnn_objdetect dnn_superres dpm face features2d flann freetype fuzzy hdf hfs highgui img_hash imgcodecs imgproc intensity_transform java line_descriptor mcc ml objdetect optflow phase_unwrapping photo plot quality rapid reg rgbd saliency shape stereo stitching structured_light superres surface_matching text tracking video videoio videostab viz wechat_qrcode ximgproc xobjdetect xphoto
Disabled: python3 world
Disabled by dependency: sfm
Unavailable: cudaarithm cudabgsegm cudacodec cudafeatures2d cudafilters cudaimgproc cudalegacy cudaobjdetect cudaoptflow cudastereo cudawarping cudev gapi julia matlab ovis python2 ts
Applications: apps
Documentation: doxygen python javadoc
Non-free algorithms: NO

GUI: QT5
QT: YES (ver 5.15.8 )
QT OpenGL support: YES (Qt5::OpenGL 5.15.8)
OpenGL support: YES (/usr/lib/aarch64-linux-gnu/libOpenGL.so /usr/lib/aarch64-linux-gnu/libGLX.so /usr/lib/aarch64-linux-gnu/libGLU.so)
VTK support: YES (ver 9.1.0)

Media I/O:
ZLib: /usr/lib/aarch64-linux-gnu/libz.so (ver 1.2.13)
JPEG: /usr/lib/aarch64-linux-gnu/libjpeg.so (ver 62)
WEBP: /usr/lib/aarch64-linux-gnu/libwebp.so (ver encoder: 0x020f)
PNG: /usr/lib/aarch64-linux-gnu/libpng.so (ver 1.6.39)
TIFF: /usr/lib/aarch64-linux-gnu/libtiff.so (ver 42 / 4.5.0)
JPEG 2000: OpenJPEG (ver 2.5.0)
OpenEXR: OpenEXR::OpenEXR (ver 3.1.5)
GDAL: YES (/usr/lib/aarch64-linux-gnu/libgdal.so)
GDCM: YES (3.0.21)
HDR: YES
SUNRASTER: YES
PXM: YES
PFM: YES

Video I/O:
DC1394: YES (2.2.6)
FFMPEG: YES
avcodec: YES (59.37.100)
avformat: YES (59.27.100)
avutil: YES (57.28.100)
swscale: YES (6.7.100)
avresample: NO
GStreamer: YES (1.22.0)
PvAPI: NO
v4l/v4l2: YES (linux/videodev2.h)
gPhoto2: YES

Parallel framework: TBB (ver 2021.8 interface 12080)

Trace: YES (built-in)

Other third-party libraries:
Lapack: YES (/usr/lib/aarch64-linux-gnu/liblapack.so /usr/lib/aarch64-linux-gnu/libblas.so)
Eigen: YES (ver 3.4.0)
Custom HAL: NO
Protobuf: /usr/lib/aarch64-linux-gnu/libprotobuf.so (3.21.12)

OpenCL: YES (no extra features)
Include path: /usr/include/CL
Link libraries: Dynamic load

Python (for build): /usr/bin/python3

Java:
ant: /usr/bin/ant (ver 1.10.13)
JNI: /usr/lib/jvm/default-java/include /usr/lib/jvm/default-java/include/linux /usr/lib/jvm/default-java/include
Java wrappers: YES
Java tests: NO

Install to: /usr

2025-08-08 23:01:59,056 - apscheduler.scheduler - INFO - base.py:507 - Adding job tentatively -- it will be properly scheduled when the scheduler starts
2025-08-08 23:02:02,221 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getMe "HTTP/1.1 200 OK"
2025-08-08 23:02:02,248 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/deleteWebhook "HTTP/1.1 200 OK"
2025-08-08 23:02:02,252 - apscheduler.scheduler - INFO - base.py:1090 - Added job "start_scheduler" to job store "default"
2025-08-08 23:02:02,253 - apscheduler.scheduler - INFO - base.py:214 - Scheduler started
2025-08-08 23:02:02,254 - apscheduler.scheduler - DEBUG - base.py:1151 - Looking for jobs to run
2025-08-08 23:02:02,254 - apscheduler.scheduler - INFO - base.py:728 - Removed job 765a6c6410434c37be9d417ae0d0dfba
2025-08-08 23:02:02,255 - apscheduler.scheduler - DEBUG - base.py:1252 - No jobs; waiting until a job is added
2025-08-08 23:02:02,255 - apscheduler.executors.default - WARNING - base.py:176 - Run time of job "start_scheduler (trigger: date[2025-08-08 21:02:00 UTC], next run at: 2025-08-08 21:02:00 UTC)" was missed by 0:00:02.200285
2025-08-08 23:02:15,387 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:02:25,421 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:02:35,457 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:02:45,489 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:02:55,525 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:03:05,554 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:03:15,590 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:03:25,622 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:03:35,651 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:03:45,691 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:03:55,724 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:04:05,756 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:04:06,705 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:04:06,923 - httpx - INFO - _client.py:1740 - HTTP Request: GET http://localhost/printer/objects/query?webhooks&print_stats&display_status "HTTP/1.1 200 OK"
2025-08-08 23:04:06,938 - httpx - INFO - _client.py:1740 - HTTP Request: GET http://localhost/server/files/metadata?filename=CE3S1PRO_Ikea_Pax_Belt_holder_v1.gcode "HTTP/1.1 200 OK"
2025-08-08 23:04:07,314 - httpx - INFO - _client.py:1025 - HTTP Request: GET http://localhost:8080/?action=snapshot "HTTP/1.1 200 OK"
2025-08-08 23:04:10,545 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/sendChatAction "HTTP/1.1 200 OK"
2025-08-08 23:04:10,684 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/sendPhoto "HTTP/1.1 200 OK"
2025-08-08 23:04:16,749 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:04:26,780 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"
2025-08-08 23:04:36,810 - httpx - INFO - _client.py:1740 - HTTP Request: POST https://api.telegram.org/bot**************/getUpdates "HTTP/1.1 200 OK"

If needed, paste the relevant bot journal contents here.

No response

What branch does this occur on?

master

Reports only on latest master or development branches!

• I have updated to latest development/master version before submitting the bug

[qnicoud]

Hello,
Just tried to switch to development branch just in case, but with no luck

[uPagge]

I have the same problem for a long time. Is there a workaround?

RESPOND PREFIX=tgnotify MSG="text message"

Directly into Gcode for notifications.

I don't understand why the author didn't respond.

[nlef]

Hi @uPagge @qnicoud
I'm developing a bot in my spare time, so I'm responding with delays. This seems to be normal for an open-source project with a single developer.

Regarding the lack of any status information from the bot, I'd like to receive the logs as a file. Please add parem debug: true to the bot settings section and restart the bot. Print some parts and then send me the bot log file.

Unfortunately, there are currently many configuration options for both Klipper and Moonraker, as well as their builds from different printer manufacturers, and I can't test all of them.