Skip to content

Fix handling of holding register dump #198 - #225

Open
super-sonic-zero wants to merge 3 commits into
robertzaage:mainfrom
super-sonic-zero:bugfix-handleHoldingRegisterDump
Open

Fix handling of holding register dump #198#225
super-sonic-zero wants to merge 3 commits into
robertzaage:mainfrom
super-sonic-zero:bugfix-handleHoldingRegisterDump

Conversation

@super-sonic-zero

@super-sonic-zero super-sonic-zero commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Fix for parsing the holding register dump that is send every hour (#198)

@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@super-sonic-zero
super-sonic-zero marked this pull request as ready for review August 10, 2026 18:27
@super-sonic-zero
super-sonic-zero marked this pull request as draft August 10, 2026 18:35
@super-sonic-zero

Copy link
Copy Markdown
Contributor Author

Marked as draft again as I got a one warning in my log:

[WARNING] Parsing GrowattModbusBlock:

@super-sonic-zero
super-sonic-zero marked this pull request as ready for review August 15, 2026 06:29
@super-sonic-zero

Copy link
Copy Markdown
Contributor Author

The warning I got seemed to be related to other unknown message types. The "Unknown msg_type" output is tied to debug level "debug" so I don't normally see this message on debug level "info". I changed it locally for me from "debug" to "warning" and got this:

2026-08-14 11:51:18,042 [WARNING] Parsing GrowattModbusBlock:

2026-08-14 11:51:18,042 [WARNING] Unknown msg_type 262:...

@robertzaage

Copy link
Copy Markdown
Owner

I take a look 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants