Add Solinteg Modbus TCP meter template

[vargai]

Adds a dedicated Solinteg Modbus TCP meter template.

Solinteg inverters are currently grouped under the existing Wattsonic template, but that template is configured for RS485-style defaults. In my setup, Solinteg over Modbus TCP requires Modbus ID 255, and the battery registers differ from the existing Wattsonic template.

This PR adds a separate solinteg template so the TCP configuration can work without changing the existing Wattsonic/RS485 behavior.

Tested locally

Tested with evcc 0.306.0 using Modbus TCP against a Solinteg inverter at port 502.

Working registers:

• Grid power: 11000, holding, int32, scale -1
• PV power: 11028, holding, uint32
• Battery power: 30258, holding, int32
• Battery SoC: 33000, holding, uint16, scale 0.01
• Battery minimum SoC: 52503, holding write, uint16, scale 10

Notes

The existing Wattsonic template is left unchanged to avoid affecting RS485 users.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider making the Modbus id and port configurable parameters (with sensible defaults of 255 and 502) instead of hardcoding them in the modbus preset, to accommodate installations that use different TCP settings.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider making the Modbus `id` and `port` configurable parameters (with sensible defaults of 255 and 502) instead of hardcoding them in the `modbus` preset, to accommodate installations that use different TCP settings.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[vargai]

These values are already configurable through evcc's Modbus template parameter expansion. The id: 255 and port: 502 entries here only define device-specific defaults for the generated id and port parameters.

Users can still override them, for example:

meters:
  - name: battery
    type: template
    template: solinteg
    usage: battery
    modbus: tcpip
    host: 192.168.1.129
    port: 1502
    id: 1

[andig]

Is the delay really needed?

[vargai]

Good point. The 'delay' parameter was inherited from the Wattsonic template, but it is not needed for Solinteg TCP template.
I removed the 'delay' parameter