We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Before you create an issue, make sure to update to the current version of modbus_sungrow.yaml
Describe the bug: the export power shows very high values after the last Sungrow Firmware Update
A clear and concise description of what the bug is.
Your Sungrow inverter: SH8.0RT-V112
The inverter is connected via (mark one)
Are you using a Modbus Proxy (mark one)
Home Assistant version:
modbus_sungrow.yaml:
** Inverter Firmware Status:**
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Duplicate of #299.
Sorry, something went wrong.
No branches or pull requests
Before you create an issue, make sure to update to the current version of modbus_sungrow.yaml
Describe the bug:
the export power shows very high values after the last Sungrow Firmware Update
A clear and concise description of what the bug is.
Your Sungrow inverter: SH8.0RT-V112
The inverter is connected via (mark one)
Are you using a Modbus Proxy (mark one)
Home Assistant version:
modbus_sungrow.yaml:
** Inverter Firmware Status:**
] I made sure that the newest firmware is installed via the installers account
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: