MULDEX VS moonraker-telegram-bot

For a DIY IDEX machine the MULDEX would be a good place to start.

There is the Muldex project, which is a corexyu I believe.

If you really wanted a challenge/interesting experience you could go for IDEX with the Muldex.

Fewer macros, remote control without vpn, someone asking for the same feature https://github.com/nlef/moonraker-telegram-bot/issues/258 sounds like it will be worth the effort to try that.

moonraker-telegram-bot

# Please refer to the wiki(https://github.com/nlef/moonraker-telegram-bot/wiki) for detailed information on how to configure the bot [bot] server: localhost bot_token: ********************************************* chat_id: ************ [camera] host: http://localhost:8080/?action=stream [bot] server: localhost # This is the adress, where the moonraker of the desired printer is located at. # In most cases it will be 'localhost'. Alternatively, an ip:port, as in 192.168.0.19:7125 can be entered, # if you are running multiple moonraker instances on the machine, or if the bot is located not on the printer itself. # This value is not validated automatically. bot_token: 5413397009:AAFNB_H8nfbsi-dAFkbXMLjwU7kYL2-FTKQ # This is the bot token. Please keep it safe and do not post it online. # Only the chat with the correct chat_id can send/receive commands to/from the bot. # Alternatively can be stored in a file. See [secrets] section. # This value is not validated automatically. chat_id: 1781705190 # This is the ID of the chat, where the bot is supposed to be able to send updates to. # Alternatively can be stored in a file. See [secrets] section. # This value should be an integer. #api_url: https://api.telegram.org/bot # If you need it, you can specify a custom url for the telegram API. # This value is not validated automatically. #socks_proxy: 192.168.0.22:1080 # If needed, you can configure the bot to use a socks5 proxy. # This value is not validated automatically. #user: root # If you have moonraker authorization enabled, you can enter the user and password here. # My advice is to not expose your printer to the internet, but I am not your mother. # Alternatively can be stored in a file. See [secrets] section. # This value is not validated automatically. #password: qwerty # The password is stored in plain text. # Alternatively can be stored in a file. See [secrets] section. # This value is not validated automatically. #api_token: 86c4841ec730415da0a66064ceeaa99c # As an alternative to the password you can use a token. # Alternatively can be stored in a file. See [secrets] section. # This value is not validated automatically. #light_device: leds # This is the power device in moonraker, to which the lights of the printer/chamber are connected to. # If you do not have lights/have no need to cycle them, skip this parameter. # Default is to omit this. # This can be a klipper output_pin or a macro as well. Refer to moonrakers "klipper_device" documentation. # This parameter will be derpeciated in coming updates. #power_device: power # This is the power device in moonraker, to which the power of the printer slave boards are connected to. # A typical usage scenario is to shutdown power to the MCUs, but not to disable the host on which klipper is running. # If you do not have such a setup, skip this. # Default is to omit this. # This parameter will be derpeciated in coming updates. #debug: false # This enables extensive logging. Only use it for debugging/troubleshooting. # Default is to omit this/false. # This value should be boolean. #upload_path: myfolder/mysubfolder # This determines, to which folder the bot will upload the gcodes sent to it. # Default is to use the base gcode folder. # Any path entered is relative from the klippers gcode folder. # This value is not validated automatically. [camera] host: http://localhost:8080/?action=stream # This is the adress, where the desired webcam/webstream is located at. Enter this the same way you enter it in # your printers web interface/your player. If you can stream it, the bot supports it, native h264 streams, # for example a vlc stream from a runcam webcam is absolutely possible. Do not feel contstrained by mjpeg streams. # This value is not validated automatically. fps: 30 # If you want to use the "/video" button/command, you should set the camera fps. Not set by default. # This value should be a positive integer >0. #flip_vertically: false # You can flip the camera image vertically, if needed. Disabled by default. Set to true if needed. # This value should be boolean. #flip_horizontally: false # You can flip the camera image horizontally, if needed. Disabled by default. Set to true if needed. # This value should be boolean. #rotate: 90_cw # You can rotate the camera image, if needed. Disabled by default. # Allowed values: 90_cw, 90_ccw, 180. Default behaviour is not to rotate the image. #fourcc: x264 # You can change the opencv VideoWriter fourcc codec. The default value is 'x264'. # Allowed values: x264, mp4v # If you need specific codec support, please open an issue. #threads: 2 # You may limit the threads used for image processing. Default value is calculalated, (os.cpu_count() / 2) # This value should be and integer >0 and < os.cpu_count(). #video_duration: 5 # This is the length in seconds of the video, which is sent when requested with /video command. # Default length of a video is 5 seconds # This value should be a positive integer >0. #video_buffer_size: 2 # On most single-board computers the renderer does not manage to capture and process frames fast enough for a video. # If you are getting shorter videos than you requested in video_duration and have free RAM, you can increse this value. # Be careful - 1 uncompressed captured image weights about 6mb when in fullHD. # OpenCV libraries have a limit of 2 GB, so please calculate your maximum available buffer from your fps and resolution. # This value should be a positive integer >0. #light_control_timeout: 0 # When the bot toggles lights to take a picture, or record a video, most cameras need a couple of seconds to adjust to # the transition between full darkness and full brightness. This option tells the bot to wait n seconds, before # taking the picture, recording a video, doing timelapse photos. The default is not to use a delay. # This value should be an integer >=0. #picture_quality: high # This parameter controls the picture quality the bot uses for status and timelapse purposes. # Allowed values: low, high # Low uses jpeg with quality set to 80, high uses losless webp. # Default is "high"

From my understanding, moonraker-telegram-bot is more popular, and installable through KIAUH.

I am using the moonraker-telegram-bot nlef/moonraker-telegram-bot: Telegram bot to interact with Moonraker (Klipper Web API Server) (github.com) But i can't find a example how i can get a message when the print is finished? I can communicate with the printer and get messages like the status, etc or when the printer is online but not when the print job itself is finished

Yeah the moonraker-telegram-bot github page has an example that is almost exactly what you are looking for.

I’m also running the Telegram bot and exclude object feature in Klipper.

You can use Telegram (moonraker-telegram or moonraker-telegram-bot) or Discord (Mooncord)