Epever wifi 2.4g rj45 d

[evrardt]

My epever is a bit far from wifi box (only 10% of reception but has an ip !) could it be the reason ? i’ll post screens of my configuration but did the same as the comment which was the better how to of this topic i may missed something

[Stiffy (Mike)]

Hi everyone,
I’m a total noob in HA.

The Add-On runs and shows me the values from my Epever Tracer4210AN in protocol but how do i get the entities in HA?

I copy paste the configuration.yaml entry from ReRuBabs in my config but i got no values (only the entities were created).

EDIT: I got it…i forgot to create a User

[HARW]

Hello, how can I add a second WiFi stick? I have two of these devices.

[10der (Oleg Denisenko)]

Sounds like you request to support multiply devices.
now dirty hack - copy foler ./hass-epever-solar-client with another name and rename all in ./config.yaml

[10der (Oleg Denisenko)]

fixed!

now you can define multiply devices

  server:
    - name: epever
      host: 192.168.88.78
      port: 9999
    - name: epever_2
      host: 192.168.88.178
      port: 9999
  mqtt:
    host: 'homeassistant.local'
    port: 1883
    username: 'mqtt'
    password: 'mqtt'
    topic: home/epever-solar

[evrardt]

[evrardt]

i’ve user for HA which serve for mosquito too called fabrique
can’t add more screenshots or more replies …

192.168.55.237 is epever ip

I’ve an epever upower high… i moved my pi next to inverter still can’t see something in mqtt explorer except $SYS …
heeeeelp … many thanks

[10der (Oleg Denisenko)]

can you look to HASS logs?
here is example

[evrardt]

hass-epever-solar-client log :

2025-01-01 12:22:14,726 - epever-solar-client - INFO - Running method get_data

2025-01-01 12:22:20,824 - epever-solar-client - ERROR - Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 4 bytes (0 received)

2025-01-01 12:22:20,824 - epever-solar-client - ERROR - get_data

---

seems like it connect to 192.168.55.237:9999 because when rj45 wifi not plugged in inverter it is written in log :
2025-01-01 12:20:11,651 - pymodbus.logging - ERROR - Connection to (192.168.55.237, 9999) failed: timed out
2025-01-01 12:20:11,652 - epever-solar-client - INFO - Cannot connect to Epever server

when connected shows the 1rst message with modbus error …

[Kev1 (Kevin Burr)]

Thanks for all this, I’ve just got my system working

I have a question, Is this read only? only I would like to control the Load On/Off switch.

[evrardt]

maybe something useful to debug my situation (@10der) UP5000-HM8042 use the db9 connection use this adapter : https://fr.aliexpress.com/item/1005006265455023.html?spm=a2g0o.order_list.order_list_main.58.6e505e5b6I0Aun&gatewayAdapt=glo2fra

could it be the problem ?

Edit : I’ve also a bms link

[asinthe]

i also stuck with this issue. anyone can help?

[10der (Oleg Denisenko)]

yes, this is ro addon I haven’t plans to send any data to device.
but feel free - you can add functionality to code.
link

[CMGeorge]

Hi,
I had the same problem but i fixed it . IF you have the upower-hi check my thread:

Epever wifi 2.4g rj45 d With UPower-Hi

Hi, I fight few days on adding Epver UPower in Home Assistant. Here is my working configuration. If it’s not working, comment all sensors except first, and test different slave values. For me the working one was 10. Maybe for others will be 2, or 4… modbus: - name: EPEVER type: rtuovertcp # type: tcp host: 192.168.8.156 port: 9999 timeout: 9 #close_comm_on_error: false #retry_on_empty: true sensors: # Utility - name: "Grid Voltage" unit_of_measurement: V …

I use modbus instead the mqtt trick,

@asinthe you can take a look also.

[asinthe]

thanks for this but its always says unavailable. do you have any idea

[evrardt]

so many thanks ! yes it was slave=10 for EPEver Upower high ! I did it with modbus as forking hass-epever-solar-client and modify code didn’t work for me and I wanted to try fast to know if it was the solution

[erlend_oyen]

hi

were you able to use the rj45 wifi adapter or did you end up with the wifi box?

[erlend_oyen]

hi

what other changes did you mage to get this working with UP HI other than changing the slave to 10?

Starting EPEVER solar client…

2025-02-01 15:54:16,027 - epever-solar-client - INFO - Program terminated.

2025-02-01 15:54:16,028 - epever-solar-client - INFO - Epever solar client started…

2025-02-01 15:54:16,028 - epever-solar-client - INFO - Running in hass.io add-on mode

2025-02-01 15:54:16,028 - epever-solar-client - INFO - Running method: get_device_info

2025-02-01 15:54:16,029 - epever-solar-client - INFO - Running…

2025-02-01 15:54:22,332 - epever-solar-client - INFO - Running method: get_battery_settings

2025-02-01 15:54:25,461 - epever-solar-client - ERROR - Exception Response(131, 3, IllegalAddress)

2025-02-01 15:54:25,462 - epever-solar-client - ERROR - get_battery_settings

2025-02-01 15:54:25,462 - epever-solar-client - INFO - Running method: get_data

2025-02-01 15:54:28,562 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:54:28,562 - epever-solar-client - ERROR - get_data

2025-02-01 15:54:28,562 - epever-solar-client - INFO - Running method: get_battery_stat

2025-02-01 15:54:31,666 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:54:31,666 - epever-solar-client - ERROR - get_battery_stat

2025-02-01 15:54:31,666 - epever-solar-client - INFO - Running method: get_battery_status

2025-02-01 15:54:34,770 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:54:34,770 - epever-solar-client - ERROR - get_battery_status

2025-02-01 15:54:34,771 - epever-solar-client - INFO - Running method: get_battery_load

2025-02-01 15:54:37,874 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:54:37,874 - epever-solar-client - ERROR - get_battery_load

2025-02-01 15:55:37,874 - epever-solar-client - INFO - Running method: get_data

2025-02-01 15:55:40,986 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:55:40,986 - epever-solar-client - ERROR - get_data

2025-02-01 15:55:40,987 - epever-solar-client - INFO - Running method: get_battery_stat

2025-02-01 15:55:44,091 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:55:44,091 - epever-solar-client - ERROR - get_battery_stat

2025-02-01 15:55:44,092 - epever-solar-client - INFO - Running method: get_battery_status

2025-02-01 15:55:47,194 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:55:47,194 - epever-solar-client - ERROR - get_battery_status

2025-02-01 15:55:47,195 - epever-solar-client - INFO - Running method: get_battery_load

2025-02-01 15:55:50,295 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:55:50,295 - epever-solar-client - ERROR - get_battery_load

2025-02-01 15:56:50,296 - epever-solar-client - INFO - Running method: get_data

2025-02-01 15:56:53,408 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:56:53,408 - epever-solar-client - ERROR - get_data

2025-02-01 15:57:53,409 - epever-solar-client - INFO - Running method: get_data

2025-02-01 15:57:56,523 - epever-solar-client - ERROR - Exception Response(132, 4, IllegalAddress)

2025-02-01 15:57:56,524 - epever-solar-client - ERROR - get_data

2025-02-01 15:58:56,524 - epever-solar-client - INFO - Running method: get

[superprip]

@sdalu

MQTT Username is “device:xyz”
MQTT Password is “xyz”
MQTT Client ID is “xyz”

where xyz is the dongle 22 characters serial number.

sorry but from what I understand , i have to set this parameter in the dongle MQTT settings and in the config client ?
I have a TRIRON 30A charger and i wanna connect with home assistant with the Epever wifi 2.4g rj45 d
i have already set the TCP-server mode in the dongle and i have installed the
hass epever client with success

thanks in advice

[wllms630]

I’d like help with this also I have 5 epever controllers setup in my greenhouses a home assistant access would be very much appreciated