Epever wifi 2.4g rj45 d

[franck31195 (laussel)]

Hi, I followed the guide provided by ReRuBabs, but I’m having trouble connecting.
192.168.1.41 is the dongle’s IP address.

Here’s the error from the Epever solar client add-on:

Starting EPEVER solar client...
2025-05-06 23:13:50,502 - epever-solar-client - INFO - Program terminated.
2025-05-06 23:13:50,502 - epever-solar-client - INFO - Epever solar client started...
2025-05-06 23:13:50,502 - epever-solar-client - INFO - Running in hass.io add-on mode
2025-05-06 23:13:50,503 - epever-solar-client - INFO - Running method: get_device_info
2025-05-06 23:13:50,503 - epever-solar-client - INFO - Running...
2025-05-06 23:13:50,511 - pymodbus.logging - ERROR - Connection to (192.168.1.41, 9999) failed: [Errno 111] Connection refused
2025-05-06 23:13:50,511 - epever-solar-client - ERROR - Cannot connect to Epever server
2025-05-06 23:13:50,511 - epever-solar-client - ERROR - get_device_info
2025-05-06 23:13:50,511 - epever-solar-client - INFO - Running method: get_battery_settings
2025-05-06 23:13:50,514 - pymodbus.logging - ERROR - Connection to (192.168.1.41, 9999) failed: [Errno 111] Connection refused
2025-05-06 23:13:50,514 - epever-solar-client - ERROR - Cannot connect to Epever server
2025-05-06 23:13:50,514 - epever-solar-client - ERROR - get_battery_settings
2025-05-06 23:13:50,514 - epever-solar-client - INFO - Running method: get_data
2025-05-06 23:13:50,517 - pymodbus.logging - ERROR - Connection to (192.168.1.41, 9999) failed: [Errno 111] Connection refused
2025-05-06 23:13:50,517 - epever-solar-client - ERROR - Cannot connect to Epever server
2025-05-06 23:13:50,517 - epever-solar-client - ERROR - get_data
2025-05-06 23:13:50,518 - epever-solar-client - INFO - Running method: get_battery_stat
2025-05-06 23:13:50,520 - pymodbus.logging - ERROR - Connection to (192.168.1.41, 9999) failed: [Errno 111] Connection refused
2025-05-06 23:13:50,521 - epever-solar-client - ERROR - Cannot connect to Epever server
2025-05-06 23:13:50,521 - epever-solar-client - ERROR - get_battery_stat
2025-05-06 23:13:50,521 - epever-solar-client - INFO - Running method: get_battery_status
2025-05-06 23:13:50,524 - pymodbus.logging - ERROR - Connection to (192.168.1.41, 9999) failed: [Errno 111] Connection refused
2025-05-06 23:13:50,524 - epever-solar-client - ERROR - Cannot connect to Epever server
2025-05-06 23:13:50,524 - epever-solar-client - ERROR - get_battery_status
2025-05-06 23:13:50,524 - epever-solar-client - INFO - Running method: get_battery_load
2025-05-06 23:13:50,527 - pymodbus.logging - ERROR - Connection to (192.168.1.41, 9999) failed: [Errno 111] Connection refused
2025-05-06 23:13:50,527 - epever-solar-client - ERROR - Cannot connect to Epever server
2025-05-06 23:13:50,527 - epever-solar-client - ERROR - get_battery_load
2025-05-06 23:14:50,528 - epever-solar-client - INFO - Running method: get_data
2025-05-06 23:14:50,534 - pymodbus.logging - ERROR - Connection to (192.168.1.41, 9999) failed: [Errno 111] Connection refused
2025-05-06 23:14:50,534 - epever-solar-client - ERROR - Cannot connect to Epever server
2025-05-06 23:14:50,534 - epever-solar-client - ERROR - get_data```

And the error from the mosquitto broker add-on:

2025-05-06 23:15:07: New connection from 192.168.1.41:52309 on port 1883.
2025-05-06 23:15:07: Client 05490126093A5Q8H-00043 disconnected, not authorised.```

[shizenyasuya]

Thank you so much for documenting the how-to process you did to get this working. I am finally to a spot where I think it’s communicating, and the client doesn’t crash with errors, but I cannot find a user interface like in the picture here. where did you find that after you configured everything?.. / how did it show up for you? I’ve tried re-starting home assistant after everything says it’s communicating and the methods are running in the logs, but I cannot find the GUI

[shizenyasuya]

I have it set up and talking to the mqtt broker and I am getting messages in mqtt explorer now. can you tell me which configuration.yaml you added the sensor entries to? is that the main Home assistant configuration.yaml, just pasted in somewhere at the bottom? or specifically under the epever or Mqtt explorer or Mosquito configuration.yaml files?

[10der (Oleg Denisenko)]

yes, i can

configuration.yaml

mqtt: !include mqtt.yaml

mqtt.yaml

sensor:
  - name: "Mini Solar station input voltage"
    unique_id: mini_solar_station_input_voltage
    state_topic: "home/epever-solar/epever/data"
    value_template: '{{ value_json["chargingInputVoltage"] }}'
    unit_of_measurement: "V"
    device:
       identifiers: Tracer1206AN
       manufacturer: "Epever"
       name: My Mini Inverter 
       model: "V02.01+V01.22"

  - name: "Mini Solar station input current"
    unique_id: mini_solar_station_input_current
    state_topic: "home/epever-solar/epever/data"
    value_template: '{{ value_json["chargingInputCurrent"] }}'
    unit_of_measurement: "A"
    device:
       identifiers: Tracer1206AN
       manufacturer: "Epever"
       name: My Mini Inverter 
       model: "V02.01+V01.22"

  - name: "Mini Solar station input power"
    unique_id: mini_solar_station_input_power
    state_topic: "home/epever-solar/epever/data"
    device_class: power
    value_template: '{{ value_json["chargingInputPower"] }}'
    #last_reset_value_template: "{{value_json.lastUpdate | int | timestamp_custom('%d.%m.%Y %H:%M'}}"
    unit_of_measurement: "W"
    device:
       identifiers: Tracer1206AN
       manufacturer: "Epever"
       name: My Mini Inverter 
       model: "V02.01+V01.22"

  - name: "Mini Solar station energy today"
    unique_id: mini_solar_station_energy_today
    state_topic: "home/epever-solar/epever/stat"
    value_template: '{{value_json["generatedEnergyToday"] }}'
    device_class: energy
    #state_class: measurement
    state_class: total
    unit_of_measurement: "kWh" 
    last_reset_value_template: '{{today_at("00:00:00")}}'
    device:
       identifiers: Tracer1206AN
       manufacturer: "Epever"
       name: My Mini Inverter 
       model: "V02.01+V01.22"

  - name: "Mini Solar station consumed energy today"
    unique_id: mini_solar_station_consumed_energy_today
    state_topic: "home/epever-solar/epever/stat"
    value_template: '{{value_json["consumedEnergyToday"] }}'
    device_class: energy
    #state_class: measurement
    state_class: total
    unit_of_measurement: "kWh" 
    last_reset_value_template: '{{today_at("00:00:00")}}'
    device:
       identifiers: Tracer1206AN
       manufacturer: "Epever"
       name: My Mini Inverter 
       model: "V02.01+V01.22"

  - name: "Mini Solar station battery charge level"
    state_topic: "home/epever-solar/epever/data"
    unique_id: mini_solar_station_battery_charge_level
    value_template: '{{value_json["batterySoC"] }}'
    unit_of_measurement: "%"
    device_class: battery
    device:
       identifiers: Tracer1206AN
       manufacturer: "Epever"
       name: My Mini Inverter 
       model: "V02.01+V01.22"

[neomasters]

Hello everyone,

Today my Epever Wiki 2.4G RJ45 D adapter arrived.

• I connected it to my EPEver XTRA-N G3

• I was able to connect to the device locally via Wifi and read data.

• I created an account through the “Solar Guardian” app, added my gateway and my MPPT controller. Both offline.

• Then integrated the stick into my network and came to the surface

• I downloaded the repository of 10derOleg Denisenko as a zip, uploaded the files via the FileEditor in the path “/homeassistant/custom_components/hass-epever-solar-client/”

• I entered the host name through the IP of the gateway under /homeassistant/custom_components/hass-epever-solar-client/config.yaml on server and used the port 9999.

• I added my host, username and password in /homeassistant/custom_components/hass-epever-solar-client/config.yaml under MQTT

• I changed the typo to “from pymodbus.pdu.mei_message import ReadDeviceInformationRequest” under /homeassistant/custom_components/hass-epever-solar-client/epever-solar-client.py

• I have configured the following on the gateway under Other settings:
  

  

• My MQTT configuration looks like this:
  

  

Where do I make a mistake?

What is not the case with me:

• Nothing appears under AddOns by itself that shows me that the Aden is active (not even after several HA restarts)

• My MQTT Explorer shows me no entry

I would be really attached to you if you could help me

[neomasters]

@neomasters

from pymodbus.pdu.mei_message import ReadDeviceInformationRequest

In the meantime I have somehow got the add-on to work, but after the start I get the following error in the log:

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

Starting EPEVER solar client...

Traceback (most recent call last):

File "//./epever-solar-client.py", line 18, in <module>

from pymodbus.pdu.mei_message import ReadDeviceInformationRequest

ModuleNotFoundError: No module named 'pymodbus.pdu.mei_message'; 'pymodbus.pdu' is not a package

s6-rc: info: service legacy-services: stopping

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service legacy-cont-init: stopping

s6-rc: info: service legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service fix-attrs successfully stopped

s6-rc: info: service s6rc-oneshot-runner: stopping

s6-rc: info: service s6rc-oneshot-runner successfully stopped