Notifications integration in RatOS >= v2.1 - telegram-bot, Pushover, MQTT?
I've been looking for a way to have notifications sent from my printer. I've been using OctoPrint for my Ender 3 Pro for years, and have acclimated to the abilities. In that same sense, as I've been looking for more options for my VCore 3.1 300 that I just upgraded to RatOS 2.1 RC3, I noticed that KIAUH support has been removed (temporarily???). To that, telegram-bot, Octoprint, Pushover, or any g-code shell command interfaces, etc. are no longer available for a more daring hobbyist to utilize on thier printer.
My intent is to send a notification for when the printer is paused so I can change filament. I am currently building an ERCF (may actually switch over to a BoxTurtle), but all filament swaps are akin to sneakernet checking when an internet/text message would be more appreciated from any of my printers. What then, are the plans for KIAUH support to enable other Klipper add-ons?
Will there be a RatOS store of options to select from, instead of the wild-west GitHub open-source?
Even as of last week when I had 2.0.2 installed, I could use klipper-backup to maintain my full config.
What is the roadmap here?
My intent is to send a notification for when the printer is paused so I can change filament. I am currently building an ERCF (may actually switch over to a BoxTurtle), but all filament swaps are akin to sneakernet checking when an internet/text message would be more appreciated from any of my printers. What then, are the plans for KIAUH support to enable other Klipper add-ons?
Will there be a RatOS store of options to select from, instead of the wild-west GitHub open-source?
Even as of last week when I had 2.0.2 installed, I could use klipper-backup to maintain my full config.
What is the roadmap here?
4 Replies
Hello.
Kiauh is not compatible with RatOS because it messes almost every single script on it.
Gcode shell commands are already part of RatOS, no issue there.
You can still install any of the notification systems with single commands instead of using any script (like kiauh).
It is the best way to have them working.
Let me also tell you that I used klipper-backup in the past but it uses a lot of resources in the PI. I would set it only to work on boot up instead of uploading after every change. Because the “sentinel/watch dog” is always looking for changes and keeps spending resources.
Good to know.
Can you provide an example of a single command install? Would it be more like a git clone statement, or something different?
I did have klipper-backup set to run at boot only, and good info nonetheless.
Thanks!
When I said single command, i meant line by line. Sorry, I was not clear. I mean using the commands found in github or product pages
No worries - I figured it out. Hadn't posted an update for solved. I started using mobileraker and octoapp. So far so good.
Actually just started running into troubles. An update was posted a few days ago and I just had to grab it I’m in the process of noting that issues during calibration. I’m seeing new notifications causing the print to halt.first one I saw after updating the RATOS packages was tolerances too great. Homing didn’t want to proceed after each axis so I had to manually run the homing sequence.