Replies: 5 comments 19 replies
-
|
In HA go into Settings, Devices & Services, click on the > next to Foxess Modbus, then CONFIGURE, Advanced Settings and change your ‘Max Read’ value to 40 And report back how that goes please |
Beta Was this translation helpful? Give feedback.
-
|
Thanks I'll try and report later |
Beta Was this translation helpful? Give feedback.
-
|
No didn't help... still having problems when I change Workmode I'm getting this message... restarting system and it works for a few hours... |
Beta Was this translation helpful? Give feedback.
-
|
hmmm that still looks to be a timing issue - have you ever modified your poll rate? (you'll find that in CONFIG with Max Read) I've seen this a couple of times recently on the H3 (even on v1.12.x and core 2024.12.x) Could you try reducing your Max Read a little further - down to 25 ? |
Beta Was this translation helpful? Give feedback.
-
|
I did not change anything just done the update and then the fails started... Should I set poll rate to 5? I'll try 25 and give you an update later |
Beta Was this translation helpful? Give feedback.
-
|
No 5 is too low, it should default to 10 - but if you do set it, make it 10 seconds |
Beta Was this translation helpful? Give feedback.
-
|
Ok, poll rate is 10 and 25 for max read. I'll test and let you know. |
Beta Was this translation helpful? Give feedback.
-
|
No just got the fail...
|
Beta Was this translation helpful? Give feedback.
-
|
ok i'm at a bit of a loss for now, it could be a problem with pymodbus 3.7.4 that HA 2025 mandates, although my system is running fine - or possibly a faulty modbus adapter?. I'd suggest you try to down grade your core and the integration to v1.12.2 you can downgrade the core by simply opening a terminal window and typing Alternatively try replacing the modbus adapter you are using, I highly recommend this one https://github.com/nathanmarlor/foxess_modbus/wiki/DSD-TECH-SH-U10 |
Beta Was this translation helpful? Give feedback.
-
|
I don't think that the Adapter is not working because on the 2024 system everything worked fine without any issues... There was a HA update today maybe that will fix my problem... |
Beta Was this translation helpful? Give feedback.
-
|
Have the same Problems here since core 2025 and a |
Beta Was this translation helpful? Give feedback.
-
|
with core 2024 it worked like a charm |
Beta Was this translation helpful? Give feedback.
-
|
I faced the same issue today:
I think it appeared after updating to OS 14.2 today, I restored the backup from last night then, but the issue persisted. What finally helped was a reboot of the Raspi. |
Beta Was this translation helpful? Give feedback.
-
|
Had same issues and after all updates I'm getting this... |
Beta Was this translation helpful? Give feedback.
-
|
We downgraded pymodbus in v1.13.1. Give that a try. |
Beta Was this translation helpful? Give feedback.
-
|
@miralemR Have you used an older version of the integration successfully in the past (and if so, what version and what HA version?), or are you a new user? |
Beta Was this translation helpful? Give feedback.
-
|
I'm not new user. I was using every modbus version until 1.13 and HA 2025 when it started to crash. I moved back on order version and it worked for a few weeks. A few days ago it stopped working without instaling any upgrades |
Beta Was this translation helpful? Give feedback.
-
|
@miralemR Did you use it successfully on HA 2024.7 or later? We're currently using the pymodbus version which HA included from July onwards, so if you did, your problems probably aren't related to the pymodbus version. |
Beta Was this translation helpful? Give feedback.
-
|
It did work after 2024.7. As i mentioned i tried 2025 versions and it didn't work so i downgraded back. First it worked fine and then it started more and more issues frequently over time (entity states either unknown or unavailable) wich is kind of weird. That continued until a few days ago where it completely stopped working. Yesterday i couldnt even connect to the ew11 with the newest versions of ha core and modbus but entity states are still unavailable. The problem could very likely be with my inverter since it is a star H3 but my provider changed it up a bit and I asked nathanmarlor if he could add it in foxess modbus. Any ideas on how to troubleshoot this or run any tests to see what exactly is wrong and try to fix this myself? |
Beta Was this translation helpful? Give feedback.
-
After 19 hours no issues 👍 |
Beta Was this translation helpful? Give feedback.
-
Hello,
I Updated to Core 2025.1.X (tryed every new Updates) and after that the HA Modbus FoxESS Update 1.13.
My System works but after a few hours my dashboard shows me fail message sensor battery soc is not numeric and im not able to get any information from my fox sensors.
Starting HA system again and it will work for a few hours and the fail is there again.
Deleted HA Modbus FoxESS on old core, updated and installed new, configured new with the same effect...
Anyone else having those problems?
Fox H3 10, USB Dongle worked Perfect with no issues until i updated to the new core...
Beta Was this translation helpful? Give feedback.
All reactions