starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 05:35:30 +02:00

[GH-ISSUE #78] [Feature]: MQTT Support #35

New issue

Closed

opened 2026-05-06 12:25:06 +02:00 by BreizhHardware · 5 comments

BreizhHardware commented

2026-05-06 12:25:06 +02:00

Owner

Originally created by @JasonSwindle on GitHub (Jan 11, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/78

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

Howdy,

I would love if all aspects (the API) was in MQTT. To be able to do event-driven actions on my printer(s) would be great. Right now the power switch aspect is too limited, but this information was in MQTT, node-red could trigger events into my setup.

Proposed Solution

Expose the API via MQTT so event driven actions can happen.

Alternatives Considered

No response

Feature Category

Print Archiving

Priority

Nice to have

Mockups or Examples

No response

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @JasonSwindle on GitHub (Jan 11, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/78 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case Howdy, I would love if all aspects (the API) was in MQTT. To be able to do event-driven actions on my printer(s) would be great. Right now the power switch aspect is too limited, but this information was in MQTT, node-red could trigger events into my setup. ### Proposed Solution Expose the API via MQTT so event driven actions can happen. ### Alternatives Considered _No response_ ### Feature Category Print Archiving ### Priority Nice to have ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested

BreizhHardware

2026-05-06 12:25:06 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-06 12:25:07 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 11, 2026):

Just to understand the requirement: why can't you use the HTTP API?

@maziggy commented on GitHub (Jan 11, 2026): Just to understand the requirement: why can't you use the HTTP API?

BreizhHardware commented

2026-05-06 12:25:07 +02:00

Author

Owner

@JasonSwindle commented on GitHub (Jan 11, 2026):

To answer directly, nothing stops me per se, but the biggest benefit for MQTT is decoupling. Right now, integrations feel tied directly to the API's specific structure. MQTT acts as a universal translator; it allows me to broadcast Bambuddy events to a broker where any number of other apps (Node-Red / HASS with zigbee & zwave) can subscribe to them. It moves the platform away from a 'request-response' loop and into a modern, event-driven workflow.

This would allow for instant notifications, more responsive automations, and a much cleaner integration experience for anyone running a local server or smart home setup.

@JasonSwindle commented on GitHub (Jan 11, 2026): To answer directly, nothing stops me per se, but the biggest benefit for MQTT is decoupling. Right now, integrations feel tied directly to the API's specific structure. MQTT acts as a universal translator; it allows me to broadcast Bambuddy events to a broker where any number of other apps (Node-Red / HASS with zigbee & zwave) can subscribe to them. It moves the platform away from a 'request-response' loop and into a modern, event-driven workflow. This would allow for instant notifications, more responsive automations, and a much cleaner integration experience for anyone running a local server or smart home setup.

BreizhHardware commented

2026-05-06 12:25:07 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 12, 2026):

So you just want to subscribe to the MQTT stream and don't post anything?

@maziggy commented on GitHub (Jan 12, 2026): So you just want to subscribe to the MQTT stream and don't post anything?

BreizhHardware commented

2026-05-06 12:25:07 +02:00

Author

Owner

@JasonSwindle commented on GitHub (Jan 12, 2026):

At the moment my use case is subscribe, but I could see others wanting to have Pub/Sub.

@JasonSwindle commented on GitHub (Jan 12, 2026): At the moment my use case is subscribe, but I could see others wanting to have Pub/Sub.

BreizhHardware commented

2026-05-06 12:25:07 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 13, 2026):

Here you go...

Please use branch 0.1.6b8 and let me know if that works for you.

Docs -> https://wiki.bambuddy.cool/features/mqtt/?h=mqtt

@maziggy commented on GitHub (Jan 13, 2026): Here you go... Please use branch 0.1.6b8 and let me know if that works for you. Docs -> https://wiki.bambuddy.cool/features/mqtt/?h=mqtt