v0.1.0 - Child devices, smart plug control, chamber light sync
Breaking change
The driver is now split into two files: bambuddy.groovy (parent, replaces bambuddy-printers.groovy) and bambuddy-printer.groovy (new — one child device per printer). Both must be installed as separate Drivers Code entries; packageManifest.json now lists both.
It's recommended that you remove your existing Bambuddy printer device and add a new one with the new drivers.
Changed
The Switch capability (On/Off) on the printer child device now controls the printer's connected smart plug via BamBuddy's smart-plug API, instead of the chamber light.
Added
- Light On / Light Off commands on the printer child device, for chamber light control independent of the smart plug.
Smart plug on/off status is now tracked from the API response and reflected back onto the switch attribute, rather than assumed optimistically. - The light attribute now stays in sync with the printer's actual chamber-light state, reported via both MQTT and REST polling — previously it only reflected the last command sent from Hubitat.
- New hmsError attribute surfaces any active Bambu HMS error/warning codes reported by the printer's REST status.
Fixed
Child devices created by older versions of this driver were missing their internal printerId reference, causing On/Off (and other per-printer commands) to silently fail with a 422 from the smart-plug endpoint. Existing child devices now self-heal this on the next refresh poll.