WillCodeForCats/solaredge-modbus-multi

TODO: Research how async timeout context interacts with pymodbus timeout

Closed

#835 opened on Jun 7, 2025

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Python (26 forks)auto 404
help wanted

Repository metrics

Stars
 (306 stars)
PR merge metrics
 (Avg merge 5h 47m) (19 merged PRs in 30d)

Description

Research how async timeout context for reads added in PR #820 interacts with pymodbus timeout and retries. Adjust the async context timeout if needed.

Feedback should be added to this issue. To adjust the timeout value, edit file const.py and adjust the value of Read = 6000 in class SolarEdgeTimeouts(IntEnum) then restart Home Assistant. If the affected entities are going unavailable too often, try a value of Read = 9000.

https://github.com/WillCodeForCats/solaredge-modbus-multi/blob/d7026ef709ca2e6efad2c358d1d8e0543266fce0/custom_components/solaredge_modbus_multi/const.py#L87

Contributor guide

Research direction
Set up a local Home Assistant instance with the component, reproduce the timeout issue by monitoring entities going unavailable, then adjust the `Read` timeout value in `const.py` (class `SolarEdgeTimeouts`, currently 6000) to 9000 if needed. Test by restarting Home Assistant and observing stability.
Tech stack
python
Domain
backend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonHome AssistantGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70