WillCodeForCats / WillCodeForCats/solaredge-modbus-multi
Integration autodetects new Instance?
A pull request for this has already been merged.
- Dominant language
- Python
- Stars
- 326
- Forks
- 29
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 20
Description
Describe the bug
Hi, it seems that with the recent version the Integration somehow starts Auto-Detecting my Inverter - even the device is already setup and running.
(https://github.com/WillCodeForCats/solaredge-modbus-multi/pull/1057#issue-5284585805)
The issue seems to be the following here:
- The integration detects the TCP Gateway with its default address 192.168.52.41:1502
While I am using a Modbus Proxy in my Setup to connect multiple devices to the Inverter (Wallbox, Heatpump, HomeAssistant)
The only way right now is to ignore the newly detected device
Expected behavior
Screenshots
No response
Diagnostic File
none
Debug logs
Home Assistant Version
2026.9.0b4
solaredge-modbus-multi Version
3.3.8
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 reviewing the autodetection behavior changed around pull request #1057 and the integration's handling of the default TCP Gateway address 192.168.52.41:1502. Compare that path with the user's Modbus Proxy setup and clarify the expected discovery behavior before changing anything; done means an already configured device is not reported as a new device unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100