-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Message #418
Comments
Register 6227 is "monthly PV energy yields" for January, and is not available via WiNet-S: https://github.com/Gnarfoz/Sungrow-Inverter/blob/main/Modbus%20Information/TI_20240924_Communication%20Protocol%20of%20Residential%20Hybrid%20Inverter-V1.1.5.pdf You have a SH10RT which has a dedicated Ethernet port just for Modbus. It's recommended to use that one instead of going through the WiNet-S dongle. If that's not possible, you can ignore the error or comment out all the sensors that the Modbus register documentation lists as unavailable on WiNet-S. |
Hi,
Iam using the dedicated Ethernet Port for modbus. I have connected Both
Ports Witz my Router. The dedicated one and the WiNet-S Dongle.
Christian Wissel ***@***.***> schrieb am Do. 19. Dez. 2024 um
13:21:
… Register 6227 is "monthly PV energy yields" for January, and is not
available via WiNet-S:
https://github.com/Gnarfoz/Sungrow-Inverter/blob/main/Modbus%20Information/TI_20240924_Communication%20Protocol%20of%20Residential%20Hybrid%20Inverter-V1.1.5.pdf
You have a SH10RT which has a dedicated Ethernet port just for Modbus.
It's recommended to use that one instead of going through the WiNet-S
dongle.
If that's not possible, you can ignore the error or comment out all the
sensors that the Modbus register documentation lists as unavailable on
WiNet-S.
—
Reply to this email directly, view it on GitHub
<#418 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A73GVWCQ3QC36EYIKWVFHUT2GK24ZAVCNFSM6AAAAABT4TG6OGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJTGY3DANBXGM>
.
You are receiving this because you authored the thread.Message ID:
<mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant/issues/418/2553660473@
github.com>
|
I'd double check IP addresses, just to be sure. Or unplug the dedicated Ethernet port. If your sensors still update while it's unplugged, you're accidentally using the WiNet-S. |
It seems that I had the wrong IP entered all along. Now the issue appears
to be resolved. I never noticed anything wrong during normal operation.
Thanks for the push to check that.
Am Do., 19. Dez. 2024 um 19:35 Uhr schrieb Christian Wissel <
***@***.***>:
… I'd double check IP addresses, just to be sure. Or unplug the dedicated
Ethernet port. If your sensors still update while it's unplugged, you're
accidentally using the WiNet-S.
—
Reply to this email directly, view it on GitHub
<#418 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A73GVWDIUI32KGFNGWUXKDL2GMGWHAVCNFSM6AAAAABT4TG6OGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJVGUZDEMRQHE>
.
You are receiving this because you authored the thread.Message ID:
<mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant/issues/418/2555522209@
github.com>
|
Excellent, glad to hear that. 🙂 |
Error Message in Home Assistant Core Version 2024.12.4
Supervisor Version 14.0
HA running on Proxmox
Sungrow SH10RT-V112
I am receiving the following error in the system log:
Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:306
Integration: Modbus (Documentation, Issues)
First occurred: 08:56:00 (12 occurrences)
Last logged: 10:46:00
Pymodbus: SungrowSHx: Error: device: 1 address: 6226 -> pymodbus returned isError True
Can I ignore this? I am only using the values for the Energy Dashboard. Everything seems to be working fine.
The text was updated successfully, but these errors were encountered: