wiregrid actuator agent crashes when it has device time out.
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
wiregrid actuator agent crashes when it has device time out.
This was observed in multiple SATs when site network was unstable.
2026-01-30T22:21:53+0000 acq:1 Status is now "done".
2026-01-30T22:21:53+0000 acq:1 acq(): ERROR!: Failed to get status from the actuator controller!--> Stop acq()! | Exception = "device timed out"
2026-01-30T22:21:53+0000 acq(): ERROR!: Failed to get status from the actuator controller!--> Stop acq()! | Exception = "device timed out"
2026-01-30T22:21:53+0000 Actuator:get_motor_onoff(): ERROR!: Failed to get motor on/off! | Exception = "device timed out"
2026-01-30T22:21:53+0000 Actuator:_command(): ERROR!: Exception = "device timed out"
2026-01-30T22:21:53+0000 Actuator:_command(): ERROR!: Failed to send command(MG _MOA).
Contributor guide
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 actuator agent paths named in the logs: acq(), Actuator:get_motor_onoff(), and Actuator:_command(). Reproduce a device timeout under an unstable or unavailable connection, then determine the expected behavior after the timeout and verify that the agent no longer crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100