[0.1.0] duplicate/multiple callbacks on reconnect?

Open
#19 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
networking

Research direction

Start by reviewing the attached octoprint.log around 2026-05-25 16:12:30,741 and trace the reconnect path that emits status updates. Reproduce a lost and restored connection, then verify that callbacks resume at second-level intervals without duplicates.

Written by the indexing model from the issue text.

Description

Testing the changes made in 0.1.0, relative to BPM losing it's connection, it seems when re-establishing the connection there are duplicate/multiple callbacks for status update based on the timestamps. See attached log after 2026-05-25 16:12:30,741, you'll see millisecond intervals rather than second intervals as expected.

octoprint.log

Dominant language
Python
Stars
6
Forks
3
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OctoPrint/OctoPrint-BambuConnector

All issues in OctoPrint/OctoPrint-BambuConnector

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.