-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[plugwise] Fix 'power' channel not correctly updated with power production #11746
Conversation
…ction This fixes the issue that the 'power' channel would not update with the correct state because the number of pulses in the PowerInformationResponseMessage is signed instead of unsigned. When the binding detected these strange readings it would normally log: "Circle (...) is in a kind of error state ...". Signed-off-by: Wouter Born <github@maindrain.net>
Thank you @wborn for the fix, I'm still busy to capture the packets for the energy part. |
...and thank you for testing the changes! 👍 |
I am not sure about the cast to short but if it is tested and approved by users, that is fine for me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…ction (openhab#11746) This fixes the issue that the 'power' channel would not update with the correct state because the number of pulses in the PowerInformationResponseMessage is signed instead of unsigned. When the binding detected these strange readings it would normally log: "Circle (...) is in a kind of error state ...". Signed-off-by: Wouter Born <github@maindrain.net> Signed-off-by: Nick Waterton <n.waterton@outlook.com>
…ction (openhab#11746) This fixes the issue that the 'power' channel would not update with the correct state because the number of pulses in the PowerInformationResponseMessage is signed instead of unsigned. When the binding detected these strange readings it would normally log: "Circle (...) is in a kind of error state ...". Signed-off-by: Wouter Born <github@maindrain.net> Signed-off-by: Michael Schmidt <mi.schmidt.83@gmail.com>
…ction (openhab#11746) This fixes the issue that the 'power' channel would not update with the correct state because the number of pulses in the PowerInformationResponseMessage is signed instead of unsigned. When the binding detected these strange readings it would normally log: "Circle (...) is in a kind of error state ...". Signed-off-by: Wouter Born <github@maindrain.net>
…ction (openhab#11746) This fixes the issue that the 'power' channel would not update with the correct state because the number of pulses in the PowerInformationResponseMessage is signed instead of unsigned. When the binding detected these strange readings it would normally log: "Circle (...) is in a kind of error state ...". Signed-off-by: Wouter Born <github@maindrain.net>
…ction (openhab#11746) This fixes the issue that the 'power' channel would not update with the correct state because the number of pulses in the PowerInformationResponseMessage is signed instead of unsigned. When the binding detected these strange readings it would normally log: "Circle (...) is in a kind of error state ...". Signed-off-by: Wouter Born <github@maindrain.net>
…ction (openhab#11746) This fixes the issue that the 'power' channel would not update with the correct state because the number of pulses in the PowerInformationResponseMessage is signed instead of unsigned. When the binding detected these strange readings it would normally log: "Circle (...) is in a kind of error state ...". Signed-off-by: Wouter Born <github@maindrain.net>
…ction (openhab#11746) This fixes the issue that the 'power' channel would not update with the correct state because the number of pulses in the PowerInformationResponseMessage is signed instead of unsigned. When the binding detected these strange readings it would normally log: "Circle (...) is in a kind of error state ...". Signed-off-by: Wouter Born <github@maindrain.net> Signed-off-by: Andras Uhrin <andras.uhrin@gmail.com>
This fixes the issue that the 'power' channel would not update with the correct state because the number of pulses in the
PowerInformationResponseMessage
is signed instead of unsigned.When the binding detected these strange readings it would normally log: "Circle (...) is in a kind of error state ...".
See also: https://community.openhab.org/t/plugwise-cirle-connected-to-pv-panel-gives-no-power-data-in-oh3/123001