Open r-amado opened 1 year ago
@r-amado this part of EM functionality will be overhauled shortly to interface directly with the modbus integration.
It looks like I have same issue - using a Waveshare RS232/485/422 to RJ45 Ethernet Module, I have this integrated with HA using the FoxESS Modbus connection (over TCP) fine. Won't let me connect using this integration, I have 'multi-host' option enabled (although not sure whether the related parameters are correct). Is it still the case that this direct connection won't work and I'll need to stick to the cloud connection for this integration for the time being?
Version of the custom_component
1.8.0
Configuration
no configuration yet, still trying to add the integration.
Describe the bug
Inverter already being used through ModBus TCP with your Integration [nathanmarlor/foxess_modbus] When trying to configure the Integration gives error connecting to the inverter, on step 2/4.![image](https://github.com/nathanmarlor/foxess_em/assets/89645023/04d12093-7756-4a48-9a4b-8e599f797583)
Is it possible to have connection timeout due to having already an integration connected to the inverter? If so, does this integration gives all the information in realtime like the other one you have published? [nathanmarlor/foxess_modbus]
Debug log
2023-08-03 12:19:41.737 ERROR (SyncWorker_6) [pymodbus.logging] Connection to (192.168.68.152, 502) failed: timed out 2023-08-03 12:26:19.202 WARNING (MainThread) [custom_components.foxess_em.config_flow] ModbusIOException()