1
0
Fork 0
mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 00:08:34 +02:00

[GH-ISSUE #1010] [Bug]: MQTT Smart Plug loses connection after every restart of Bambuddy #708

Closed
opened 2026-05-07 00:12:57 +02:00 by BreizhHardware · 8 comments

Originally created by @saint-hh on GitHub (Apr 17, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1010

Originally assigned to: @maziggy on GitHub.

Bug Description

I have a shelly Plug integrated in Bambuddy. I grab the data from ioBroker via MQTT.
It works fine, but loses the connection, as soon as Bambuddy is restarted.
The only way to get it connected again is to rename a MQTT topic as a dummy, safe, rename it to the original again. Then the connection is established again.

Expected Behavior

The connection should be established also after a restart of Bambuddy

Steps to Reproduce

See screenshots

Printer Model

P2S

Bambuddy Version

0.2.2.2

Printer Firmware Version

01.01.03.00

Installation Method

Manual (git clone)

Operating System

Linux (Other)

Relevant Logs / Support Package

No response

Screenshots

Image Image Image

Additional Context

No response

Checklist

  • I have searched existing issues to ensure this bug hasn't already been reported
  • I am using the latest version of Bambuddy
  • My printer is set to LAN Only mode
  • My printer has Developer Mode enabled
Originally created by @saint-hh on GitHub (Apr 17, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1010 Originally assigned to: @maziggy on GitHub. ### Bug Description I have a shelly Plug integrated in Bambuddy. I grab the data from ioBroker via MQTT. It works fine, but loses the connection, as soon as Bambuddy is restarted. The only way to get it connected again is to rename a MQTT topic as a dummy, safe, rename it to the original again. Then the connection is established again. ### Expected Behavior The connection should be established also after a restart of Bambuddy ### Steps to Reproduce See screenshots ### Printer Model P2S ### Bambuddy Version 0.2.2.2 ### Printer Firmware Version 01.01.03.00 ### Installation Method Manual (git clone) ### Operating System Linux (Other) ### Relevant Logs / Support Package _No response_ ### Screenshots <img width="470" height="491" alt="Image" src="https://github.com/user-attachments/assets/60aa735e-17b0-4974-ad85-67f3c814720f" /> <img width="475" height="906" alt="Image" src="https://github.com/user-attachments/assets/30d1a4a0-e523-44b5-ba02-b684b39abe2c" /> <img width="311" height="280" alt="Image" src="https://github.com/user-attachments/assets/f855c6ad-c7ba-4197-9f19-0b272cbbec08" /> ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled
BreizhHardware 2026-05-07 00:12:57 +02:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@maziggy commented on GitHub (Apr 18, 2026):

Please first update to the latest beta version.

<!-- gh-comment-id:4273040718 --> @maziggy commented on GitHub (Apr 18, 2026): Please first update to the latest beta version.
Author
Owner

@saint-hh commented on GitHub (Apr 19, 2026):

So, as I'm on the 0.2.3 final version now, I have to report that this issue is still the same.
Do you need a support package or me to test something?

<!-- gh-comment-id:4275551748 --> @saint-hh commented on GitHub (Apr 19, 2026): So, as I'm on the 0.2.3 final version now, I have to report that this issue is still the same. Do you need a support package or me to test something?
Author
Owner

@maziggy commented on GitHub (Apr 19, 2026):

Yes.

<!-- gh-comment-id:4275564181 --> @maziggy commented on GitHub (Apr 19, 2026): Yes.
Author
Owner

@saint-hh commented on GitHub (Apr 19, 2026):

Here you go

bambuddy-support-20260419-125026.zip

<!-- gh-comment-id:4275742738 --> @saint-hh commented on GitHub (Apr 19, 2026): Here you go [bambuddy-support-20260419-125026.zip](https://github.com/user-attachments/files/26867871/bambuddy-support-20260419-125026.zip)
Author
Owner

@maziggy commented on GitHub (Apr 19, 2026):

I cannot finds any related logs in your package.

<!-- gh-comment-id:4275751175 --> @maziggy commented on GitHub (Apr 19, 2026): I cannot finds any related logs in your package.
Author
Owner

@saint-hh commented on GitHub (Apr 19, 2026):

Yes, me too. But I did for this package exactly what I've described with screenshots above:
"The only way to get it connected again is to rename a MQTT topic as a dummy, safe, rename it to the original again. Then the connection is established again."
But it seems nothing will be logged with this action. But it is reproducible - every restart of Bambuddy leads to the loss of the connection.

<!-- gh-comment-id:4275770537 --> @saint-hh commented on GitHub (Apr 19, 2026): Yes, me too. But I did for this package exactly what I've described with screenshots above: "The only way to get it connected again is to rename a MQTT topic as a dummy, safe, rename it to the original again. Then the connection is established again." But it seems nothing will be logged with this action. But it is reproducible - every restart of Bambuddy leads to the loss of the connection.
Author
Owner

@maziggy commented on GitHub (Apr 19, 2026):

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now.


If you find Bambuddy useful, please consider giving it a on GitHub — it helps others discover the project!

<!-- gh-comment-id:4275837178 --> @maziggy commented on GitHub (Apr 19, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!
Author
Owner

@saint-hh commented on GitHub (Apr 20, 2026):

Confirmed fix with v0.2.3.1 - thank you very much!

<!-- gh-comment-id:4280118296 --> @saint-hh commented on GitHub (Apr 20, 2026): Confirmed fix with v0.2.3.1 - thank you very much!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy-maziggy-1#708
No description provided.