Skip to content
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

Writing certain value fails (checksum = 5c) #83

Open
qabi opened this issue Dec 10, 2024 · 6 comments
Open

Writing certain value fails (checksum = 5c) #83

qabi opened this issue Dec 10, 2024 · 6 comments

Comments

@qabi
Copy link

qabi commented Dec 10, 2024

I don't know if this is an issue in my actual heat pump controller (VVM500) or in this project?

Writing to 47032 (external adjustment) works for values 3, 2, 1, 0, -1, -3 and -4 but NOT for -2. That seems very strange.

Actual data sent:

-1: c06b06b8b7ff0000005d (works)
-2: c06b06b8b7fe0000005c (no response)
-3: c06b06b8b7fd0000005f(works)

Just found out now, that it is very likely related to the checksum being 5c, which there is some code to remove duplicates, etc. Will look further into this.

@elupus
Copy link
Owner

elupus commented Dec 10, 2024

Yes 5c should be duplicated and/or replaced when its the checksum

@elupus
Copy link
Owner

elupus commented Dec 10, 2024

This must be done in the sending app i think. I think we precalculate the block before sending.

https://github.com/yozik04/nibe/blob/cfe4b8173b5fbbcefc9047842111761d9a45d5b7/nibe/connection/nibegw.py#L837

Likely needs the dedupe code of the response type.

@qabi
Copy link
Author

qabi commented Dec 10, 2024

This must be done in the sending app i think.

I introduced the if chksum == 0x5C then chksum = 0xC5logic, and that fixed it for me.

@qabi qabi closed this as completed Dec 10, 2024
@elupus elupus reopened this Dec 10, 2024
@elupus
Copy link
Owner

elupus commented Dec 10, 2024

Its not fixed yet in neither nibegw code nor nibe python lib so issue is still valid.

@qabi
Copy link
Author

qabi commented Dec 10, 2024

Its not fixed yet in neither nibegw code nor nibe python lib so issue is still valid.

Ok. I was of the understanding that it should be fixed in the sending app, and not nibegw.

@elupus
Copy link
Owner

elupus commented Dec 10, 2024

Yes, but we have no issue there yet :)

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

No branches or pull requests

2 participants