Same for me 2021.7.3 fixed the problem 
still the error!
Pymodbus: Exception Response(131, 3, IllegalAddress)```
Mine is still not working properly.
I have this issue with Modbus RTU and 2021.7.3 did nont fix. I’m back again on 2021.6.6
Same with me. Back at 2021.6.6
Hi All,
Ive update my HA to 2021.7.3 and modbus switches and sensors stop working after an hour or so. If I keep restarting HA it comes back for a bit then all unavailable.
Ive updated my modbus config to the new modbus templates as the old ones are obsolete now.
Real bummer as my victron home storage battery is all controlled by HA :(.
Hopefully someone will come up with a fix soon. Found this. Looks like someone is working on a fix.
has something changed in the modbus.py library do you think?
Cheers
Gareth
Pymodbus: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
9:40:50 – (ERROR) Modbus
This is the error im getting
did you try adding these parameters in every hub?
delay: 5
close_comm_on_error: false
retry_on_empty: true
retries: 10
Hi Guys,
I just upgrade from Home Assistant 2021.7.2 to Home Assistant 2021.7.3 and now i see the modbus is broken. I have checked the logs and it doesnt report any errors. Im using modbus to connect to Victron Venus GX (Inverter)
any suggestions?
Regards
I’m on 2021.7.3 so far so good, modbus still working. Main use of HA for me is to talk to Victron Cerbo GX and manage my power, so would really suck if it stopped.
2021.7.4 is available and should fix this issue (PR #53020 merged).
Could you please report if it’s fixed now in your setups?
2021.7.4 works for me since 6 hours without problems.
after a (quick) test: Modbus seems working again! Thanks
hi tested with new update but still get either: entity not available or cant find entity, thanks
(querying Victron GX controller for modbus )
Francois
hi
I tested again and after updating my code to the config style all is working 
Oh, it was not me who repaired it, I just wanted to point to the update that should fix the issue and was interested in the results. Sorry if there was some confusion.
Just wondering what others have as settings for how often to read via modbus? Trying to find a balance between speed of reaction and not overloading the system
so, Modbus is working again 
BUT…
the sensor-readings are a bit out of scale… are there changes to the scaling?
Instead of 600W at the same time the day before i got 12000000W… so 10000x … 
i had to set the scale from …
scale: .01
…to…
scale: .000001
…to get in the same ballpark and i am still searching for the “times 2”-thing…
does anyone else have the same problems?
#EPEver eBox-Wifi-01 modbus
modbus:
- type: rtuovertcp
host: 10.0.0.63
port: 8088
name: "Solar2EP"
delay: 5
close_comm_on_error: false
retry_on_empty: true
retries: 10
# Modbus sensors for EPever Charge Controller 4 (4310 AN)
sensors:
- name: "Sol2 Battery Array Capacity 4"
unit_of_measurement: '%'
slave: 1
address: 12570
input_type: input
- name: "Sol2 Solar Power Watts 4"
unit_of_measurement: W
slave: 1
address: 12546
input_type: input
scale: .000001
count: 1
precision: 2
reverse_order: true
- name: "Sol2 Solar Amps 4"
unit_of_measurement: A
slave: 1
address: 12545
input_type: input
scale: 0.01
precision: 2
- name: "Sol2 Solar Voltage 4"
unit_of_measurement: V
slave: 1
address: 12544
input_type: input
scale: 0.01
precision: 2
- name: "Sol2 Battery Charging Watts 4"
unit_of_measurement: W
slave: 1
address: 12546
input_type: input
scale: .000001
count: 1
precision: 2
reverse_order: true
- name: "Sol2 Battery Charging Amps 4"
unit_of_measurement: A
slave: 1
address: 13083
input_type: input
scale: 0.01
precision: 2
count: 1
reverse_order: true
- name: "Sol2 Battery Voltage 4"
unit_of_measurement: V
slave: 1
address: 13082
input_type: input
scale: 0.01
precision: 2
- name: "Sol2 Load Watts 4"
unit_of_measurement: W
slave: 1
address: 12558 # low 12550 high 12551 #12558
input_type: input
scale: 0.01
precision: 2
- name: "Sol2 Load Amps 4"
unit_of_measurement: A
slave: 1
address: 12549
input_type: input
scale: 0.001
precision: 2
- name: "Sol2 Load Volts 4"
unit_of_measurement: V
slave: 1
address: 12548
input_type: input
scale: 0.01
precision: 2
- name: "Sol2 Battery Temperature 4"
unit_of_measurement: °C
slave: 1
address: 12560
input_type: input
scale: 0.01
precision: 2
- name: "Sol2 Controller Temperature 4"
unit_of_measurement: °C
slave: 1
address: 12561
input_type: input
scale: 0.01
precision: 2
- name: "Sol2 Energy Generated Today 4"
unit_of_measurement: KWh
slave: 1
address: 13068
input_type: input
scale: 0.00001
precision: 2
count: 2
reverse_order: true
- name: "Sol2 Energy Generated this Month 4"
unit_of_measurement: KWh
slave: 1
address: 13070
input_type: input
scale: 0.00001
precision: 2
count: 2
reverse_order: true
- name: "Sol2 Energy Generated this Year 4"
unit_of_measurement: KWh
slave: 1
address: 13072
input_type: input
scale: 0.00001
precision: 2
count: 2
reverse_order: true
- name: "Sol2 Total Energy Generated 4"
unit_of_measurement: KWh
slave: 1
address: 13074
input_type: input
scale: 0.00001
precision: 2
count: 2
reverse_order: true
I’m using 10s for reading PV power and net power from the inverter, 300s for “static” values and 60s for my ventilation system (could increase that interval some time… but doesn’t make any problems).
You find my modbus settings here, if you are interested:
3 Likes
OK, Scaling seems to be correct now, without me changing anything…
just restarted the pi instead of just reloading the core and supervisor
i changed scaling back to 0.01 and introduced scan_intervals - i only need minute-values here