Pioreactor / Pioreactor/pioreactor
[what happened] power cycled a pioreactor worker, but status in UI is "lost"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 149
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
When a pioreactor is power cycled, the monitor connection to MQTT is servered, but there is a 60s window before the broker acknowledges it's missing. After 60 seconds, the lost message is sent. If the Pioreactor startups up within the 60s, and publshies it's own ready message, this can get overwritten by the broker's lost at t=60s.
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 tracing the monitor connection and MQTT status handling described in the issue, especially the 60-second broker timeout and the worker's ready message. Confirm the race between ready and lost after a power cycle, then verify that a worker which restarts within the window remains shown as ready.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, raspberry-pi
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100