The settings would appear correct in the UI, but not actually be applied. Edit: Notes now that it’s workingĮxperienced multiple instances of settings not being applied after a save (“Submit”), and not even being applied after a soft restart. I’ve tried it both ways, but have mostly been conducting tests wired according to the Epever manual (linked above).

I’ve gotten mixed information about the polarity of the A and B side of the RS485 connection. Oh, I did have to wire a custom connector for this. So… I’ve been working on this for a lot of hours – juggling configurations as many different ways as I can think of, but I’m stumped.Īny ideas for getting this going in TCP/modbus or MQTT (or anything, really)? Mqtt-explorer 880×916 34.9 KB Inconclusion Here’s the Serial Port Settings for the EW11: If I set the Serial Port protocol in the EW11 to None, does that mean it passes raw RTU, in which case I would guess configuration.yaml should be set to rtuovertcp? If I set the Serial Port Protocol to Modbus, does HA want to see tcp in configuration.yaml? I don’t know, but I’ve tried all 4 permutations with no success. I’m not completely sure how to interpret that. Relevant parameters are set in Frame command. ◆ NONE: Default: None, transparent transmission, the received UART data will be directly sent to network. The EW11 manuals have a single mention of RTU in the UART section: I don’t know if HA should see TCP or RTU after being output from the EW11, so I’ve tried both. This introduces a fork I’m not sure how to traverse. The CC modbus register manual I found has the following statement:Ĭommunication protocol is standard Modbus-RTU protocol. Sensor section of configuration.yaml - platform: modbus I’m not sure which is correct for the Epever charge controller (CC). I have 2 hubs set up for testing purposes. Starting off, here’s my modbus config in HA: modbus: It would help more for you to share your modbus config and a link to the manual you have for your device please? TCP Server / Modbus

Epever wifi app download