WillCodeForCats / WillCodeForCats/solaredge-modbus-multi
Firmware 4.25.15 bug or solaredge is closing modbus?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 326
- Forks
- 29
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 20
Description
Describe the bug
Hi,
I have the latest firmware but now I can’t get data from older inverters with display anymore 😥.
Inverter model SE3680H-RW000BEN4 without a display is Master connectivity internet over WiFi.
Wattnode meter on RS485-1
Inverter with display and storage/ SESTI Tesla Powerwall gen 1 —> 2 batteries.
Your beautiful script can’t get data from the older inverters over modbus anymore. Is this a bug at SolarEdge side or just a step closer to facing out older hardware?
Expected behavior
?
Screenshots
No response
Diagnostic File
Is privé ask for it
Debug logs
Home Assistant Version
Latest
solaredge-modbus-multi Version
3.3.6
Installation Type
HAOS
Read the Instructions
- My configuration follows https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration
- I have read the Known Issues https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues
- This issue is not about a template error (do not report template errors, read https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Template-Design-Notes)
Additional Context
No response
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 reproducing the reported failure with solaredge-modbus-multi 3.3.6, Home Assistant, the SE3680H-RW000BEN4, and the older inverter setup described in the issue. Request and inspect the private diagnostic file and relevant debug logs, then compare behavior before and after firmware 4.25.15. Done means identifying whether the integration or SolarEdge firmware closes Modbus access and documenting a reproducible failure or confirmed fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100