-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modbux proxy is not working #66
Comments
This is a issue you have to open in evcc. what is the reason for proxying? |
hass and evcc have to connect to inverter. |
Did you close the usage out of HA to the inverter port? |
in my configuration you can see that only evcc is connecting to inverter but not HA |
I can’t, since there is no info what you configured in HA.
|
bro, i know therefore this issue here |
gtn! Both subnets are reachable? 192.168.5.x |
|
Hello, same Problem here. The modbusproxy in evcc is used for inverters, that only allow one modbus connection. There for a port is configured in evcc and this port must be connected from docker container to HAOS Port. In the Network Part of Configuration in HAOS evcc Page under "Change the ports on your host that are exposed by the add-on" there has to be perhaps three Ports (5021 - 5023) to configure into the evcc docker container. |
The above config by the opener of this issue is incorrect: In the meters config the setting needs to remain the same as before, so the IP:Port of the Modbus gateway of the inverter needs to be specified, NOT the IP:Port of the evcc Modbus Proxy. The way I understand it, the evcc Modbus Proxy is aware of evcc's connections / requests and then loops in other requests received by the proxy. Correct setting for the above config:
In HA Add-on config port 5200 needs to be specified for Modbus (which is default setting as far as I can tell). In HA integration config for the inverter you specifiy Modbus TCP/IP and evcc IP with port 5200. This is working for me. Please report back if this works so the issue can be closed. |
Ok. Thank you. |
not addon related, open it in : https://github.com/evcc-io/evcc or discuss it in https://github.com/evcc-io/evcc/discussions |
I am littlebit confused what are the network ports settings in the configuration page are for becuse this ports are not opened on the host.
Nevertheless I configured modbusproxy in evcc.yaml but the connection is timing out.
HASS IP: 192.168.1.50
[site ] ERROR 2023/08/05 12:14:12 grid meter: read failed: modbus: exception '4' (server device failure), function '3' [site ] ERROR 2023/08/05 12:14:12 grid meter: read failed: modbus: exception '4' (server device failure), function '3'
When I am using the Inverter IP in meters settings then the connection is working.
What is wrong here?
The text was updated successfully, but these errors were encountered: