INSTALLATION
Can be installed using HPM; just search for "Bambu Labs Printers".
Manual installation requires the parent and child drivers. All code can be found in my GitHub repo .
SETUP
Pretty straightforward.
Install the driver.
Create a virtual device using the "BambuLabs" device type.
On the device page, enter your IP address and access code* for the printer, and hit Save.
* The access code can be found on the network settings page on the printer. You may need to toggle "LAN mode" on to generate the code, but it can be turned back off.
The driver will connect to the MQTT server on the printer and automatically pull attribute information. The attributes are updated based on the set polling frequency using the "Attribute Update Schedule" command.
Has the presence/healthStatus attributes for monitoring the connection status in Rule Machine.
An option to automatically attempt to reconnect. This will run every few seconds, but there's a 1 minute timeout built into the MQTT connection. So, the reconnection attempt will happen every ~1 minute. Advised to disable this option if you plan to kill power between prints.
All commands can be used through Rule Machine using the "Custom Action" and "Actuator" capability. Anything that takes a parameter (fan speeds, temps) are 'type' of 'number'.
Thanks. I have a home built notification scheme for my other printers. I can modify your driver with a few lines. I'll send a pull request in a few days and you can decide whether you like the mod or not.
[quote="FriedCheese2006, post:2, topic:117942"]
I don't own an AMS and have only tested this with my X1C.
[/quote],
I do have an AMS. The driver works OK without dealing with one or more of them. I don't think we need to replace Bambu Studio or Orca Slicer with Hubitat controls to unload the filament, for example.
That is good information for me to know. I had the same issue with the 'common' HE octoprint drivers. My requirements are just status reporting - everything else just gets in the way - for me. I'll write my own driver instead of trying to fit into yours. Thanks.
I have three devices I built that display text messages on small lcds. They get the text from individual MQTT topic. There are HE device drivers for sending the notification to mqtt. Also on HE, there is a app and child app that accepts one notification and broadcasts it to multiple recipients. I have hubitat rules/devices that send notifcations and I have other processes on other computers that also send small messages to the display devices. Quite handy. For example when Ender 3's printers throw a fit. Restricting notifications to cell phones is very limiting, for no reason.
