#EVCC --> HA or HA --> EVCC, which way around?

1 messages · Page 1 of 1 (latest)

sleek cape
#

Hi,
as far as I was able to figure that out, I can go both ways, add all my PV and wallbox stuff to evcc and evcc reports back via MQTT to HA, or add PV and Wallbox to HA and HA reports via MQTT to EVCC.
What I can't do (or not easily) is to add the hardware to both as the inverters have a restriction to allow only one modbus client.
As my set-up is already a bit complex (3 Huawei Inverters each with a battery, 6 pv-strings, an openwb wallbox, a heat-pump and a pellet stove) I was wondering which way might be the best. Best in terms of stability and best in terms of maintainance and performance.
Would be glad to hear what others did or suggest. Are there any show-stoppers for one or the other way? Any pro and con?
Thanks

solemn hearth
#

You can use the modbus proxy addon to make the connection available to both

sleek cape
#

@solemn hearth if I get this right the addon works only for one modbus, but the underlying library could work with multiple modbus interfaces. I would need three for three inverters

solemn hearth
#

There's a modbus proxy library in python that can do that. You would just need to run it somewhere

#

If you dont want to do that i would just put everything in evcc