Regular reporting of LS372 heater values
Open
Nobody has claimed this yet.
agent: ls372
enhancement
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
Currently it seems that the LS372 agents report heater values when they are changed through the agent, but it would be nice to have these be regularly queried and reported during the acquisition process.
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 locating the LS372 agents and the acquisition process that currently reports heater values after agent-driven changes. Trace how heater values are queried and reported, then determine the regular reporting cadence and verify that values appear during acquisition without relying on a change event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100