BamBuddy Driver for Bambu 3D Printers

Custom Apps and Drivers
1

For the masses, I present to you the BamBuddy Printers Driver for BamBuddy.

Features

  • Connects to your BamBuddy instance via REST API
  • Optionally connects to a MQTT broker if you've got one setup

Hubitat Package Manager Installation

  1. Install HPM
  2. Open the HPM App, Install an app and search for BamBuddy. Select the one authored by jc21.
  3. Profit

Manual Installation

  1. In Hubitat → Drivers Code, click the "+ Add driver" button and paste contents of bambuddy-printers.groovy and click Save
  2. In the Devices section, create a new Virtual Device, choose driver BamBuddy Printers

Configure

  1. In your new device's preferences, set the host of the BamBuddy instance, an API Token with these permissions:
  • Read Status
  • Manage Queue
  • Control Printer
  1. Optionally add your MQTT server details (host:port, user/pass, topic prefix from BamBuddy settings)
  2. Turn on Debug Logging and check the logs, turn off when everything is working q

More info in the Github repo

Testers and feedback welcome :slight_smile:

2

This is only for control and rules? No display monitors or anything?

I’m running BamBuddy but really looking for some integration to have a RH display for all AMS.

Should I just try to get the generic MQTT integration going? Kinda chasing my tail on this one.

P.S. BamBuddy isn’t coming up in PM search, I had to manually install.

3

Yeah this is fairly light on the full API capabilities of bambuddy. I merely needed it for a button to clear the plate for my printer. But it’s a good starting point for future changes.

What exactly do you need from the integration? I’m sure I can get and store the states of the connected AMS’s if that’s all you need.

4

HPM listing is fixed, you can use the “Match Up” section in HPM to link it with your installed version.

5

I’ve had to modify the driver in un-pretty ways. There are several issues. One killer problem is that just like all the other bambu drivers for hubitat a couple of active printers can bring out the Hubitat too many events warnings because: there are really too many events. (for a c7 or c8 )

Part of that problem is that the mqtt topic has a retain = true setting from BamBuddy so it is constantly active. This is a BamBuddy issue so it needs addressing there. Or a fork in that code.

Another issue is that that the handling of mulitple printers should probably be done with multiple child drivers and a parent driver. That would be a major change in the code.

6

The child printers is a great idea. I implemented it in v0.1.0.

Read the release notes here: Release v0.1.0 - Child devices, smart plug control, chamber light sync · jc21/hubitat-bambuddy · GitHub

I don’t suggest updating alone for this release, but instead remove your Bambudy device and add a new one using these new drivers.

7

And for you @rjterry21 I’ve added AMS info v0.1.1

8

Thanks, I will take a look.

Sorry I went dark after posting, busy busy and travelling.