DiscordRemote is a plugin allowing Octoprint to send notifications to a Discord channel. The plugin connects to a DiscordShim which manages the actual discord interactions.
There is an existing DiscordShim that is already setup, or users may create and use their own DiscordShim instance.
This is forked from https://github.com/bchanudet/OctoPrint-Octorant.
Note, using this plug-in requires either:
- Adding the existing discordshim bot to your server:
- Self host your own discordshim:
License : MIT
Benjamin Chanudet for their initial plugin, which this is based on.
OctopusProteins for their work on the enclosure plugin, file upload capabilities and presence updates.
megasaturnv for their assistance with configuring the access settings.
goscicki for their help testing the /gcode capability.
timothy-b for their help fixing the help command handling.
wchill for the custom embed in notification change.
SgtKiLLx for various typo fixes.
Zinc-OS for adding Raspberry Pi throttling status to the status message.
Stwend for adding split zip support, to get around the 8mb discord limit.
Mary for preventing the bot replying to other bots, and avoiding downloading non-gcode/zip files.
Milo Mirate for adding ETA to status.
jneilliii for Print Scheduler support.
grantrules for fixing presence.
MrFrickinFixit for assisting with debugging the network issues in v5.0
See the release history to get a quick summary of what's new in the latest versions.
Install via the bundled Plugin Manager or manually using this URL:
https://github.com/cameroncros/OctoPrint-DiscordRemote/archive/master.zip
- The Channel ID is the ID of the TEXT channel within the Discord Server that the bot is communicating with, not the Discord Server.
- If you reinstall your Octoprint system, you only need the channel ID, and DiscordShim address to get it back up and running.
There are currently 2 API's available for interacting with the bot.
These can be used by sending a POST request to [octoprint_url]/api/plugin/discordremote, with JSON in the body of the request.
This API lets you send a command as if you typed it in discord. The response will be sent to discord. The JSON format is:
{
"command": "executeCommand",
"args": "COMMAND GOES HERE"
}
This API lets you send a message directly to discord. The JSON format is:
{
"command": "sendMessage",
"title": "TITLE GOES HERE",
"description": "DESCRIPTION GOES HERE",
"color": 0x123456,
"image": "BASE64 ENCODED FILE DATA HERE",
"imagename": "IMAGE NAME GOES HERE"
}
- All fields are optional, but at least a title, description or image should be provided.
- The color is an integer value here that corresponds to the color you want.
- The image is base64 bytes.
- The image name defaults to "snapshot.png" if not provided.
To get a list of available commands and arguments, type /help into the discord channel. The bot will return all available commands.
Commands can also be sent via the web interface, by clicking the button in the top panel that looks like a game controller.
Files can be uploaded to the discord channel directly, and they will be downloaded into OctoPrint automatically. You can use the /unzip
command to manage zip files.
The plugin can be configured in the configuration panel, under the "DiscordRemote" panel.
- Channel ID: The ID of a channel the bot will listen and post to. Ensure that this is locked down so that strangers cannot send commands to your printer, or whitelist users using the "Access Settings"
In order for you to be sure these settings work, every time you change one of them, a test message will be sent to the corresponding Discord Channel. If you don't receive it, something is most likely wrong!
The access settings allow specific commands to be limited to specific users.
- In the commands section, put a comma-separated list of commands.
- Check out this wiki page for the list of commands
- The command list should look like "help, status, snapshot, mute, unmute" and is useful for tailoring access to any other users you might invite to avoid them issuing a command like /abort!
- In the users section, put a comma-separated list of user IDs.
- The user ID needs to be the numerical form, which is a number like: 165259232034275409
- In a text channel, find a message sent by you (or send one) and then right-click your name over that message and click "Copy ID"
- Or, join a voice channel, and then right-click your name in the sidebar, and click "Copy ID"
- The text user ID (like "MyUser" or "MyUser#1234") will result in "Permission Denied" responses to commands.
- A '*' in either section can be used to match all commands/users.
If the current command and user combination matches any of the rules, it will be executed. If additional rules are required, manually editing the config will be required.
Here you can customize every message handled by DiscordRemote.
- Toggle the message : by unchecking the checkbox in front of the message title, you can disable the message. It won't be sent to Discord.
- Message : you can change the default content here. See the section Message format for more information.
- Include snapshot : if you have a snapshot URL defined in the Octoprint settings, you can choose to upload a snapshot with the message to Discord.
- Notify every
XX% : specific to theprinting progressmessage, this settings allows you to change the frequency of the notification :10%means you'll receive a message at 10%, 20%, 30%, 40% ... 80%, 90% of the printing process.5%means you'll receive a message at 5%, 10%, 15%, 20% ... 80%, 85%, 90%, 95% of the printing process.- etc...
- Timeout : for small prints, prevents discord spam by only sending progress messages after the timeout has passed since the previous message.
Messages are regular Discord messages, which means you can use :
**markdown**format (see Discord Documentation):emoji:shortcuts to display emojis@mentionsto notify someone
Some events also support variables, here is a basic list : Common :
{ipaddr}: the internal IP address of the OctoPrint server{externaddr}: the external IP address of the OctoPrint server{timeremaining}: the time remaining for the print ('Unknown' if the print is not running){timespent}: the time spent so far on the print{eta}: the date+time which is{timeremaining}into the future
Printing process : started event :
{name}: file's name that's being printed{path}: file's path within its origin location{origin}: the origin storage location
Printing process : failed event :
{name}: file's name that's being printed{path}: file's path within its origin location{origin}: the origin storage location
Printing process : done event :
{name}: file's name that's being printed{path}: file's path within its origin location{origin}: the origin storage location{time}: time needed for the print (in seconds){time_formatted}: same as{time}, but in a human-readable format (HH:MM:SS)
Printing process : failed event :
{name}: file's name that's being printed{path}: file's path within its origin location{origin}: the origin storage location{position}: position of the hotend
Printing process : paused event :
{name}: file's name that's being printed{path}: file's path within its origin location{origin}: the origin storage location{position}: position of the hotend
Printing process : resumed event :
{name}: file's name that's being printed{path}: file's path within its origin location{origin}: the origin storage location{position}: position of the hotend
Printing progress event :
{progress}: progress in % of the print.
Printer state : error
{error}: The error received
For more reference, you can go to the Octoprint documentation on Events
If you encounter any trouble don't hesitate to open an issue. I'll gladly do my best to help you setup this plugin.