Pioreactor / Pioreactor/pioreactor
[what happened] When a job loses connection to MQTT, and last-will is triggered, then reconnects, a new last-will is not added.
Open
Nobody has claimed this yet.
bug
mqtt
what-happened
- Dominant language
- Python
- Stars
- 149
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Python code that manages MQTT connections and last-will setup, then trace the disconnect and reconnect path. Reproduce the sequence described in the title and verify that reconnecting after a triggered last-will results in a new last-will being registered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, raspberry-pi
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100