Plugwise binding sometimes returning wrong values for currernt power usage

[GoogleCodeExporter]

What steps will reproduce the problem?
1. plugwise binding configured and running with 10 Circle
2.
3.

What is the expected output? What do you see instead?
ReadyNAS:/c/Software/openhab/openhab-1.4/distribution-1.4.0-SNAPSHOT-runtime/log
s#  grep "Power state updated" events.log | grep "[0-9][0-9][0-9][0-9][0-9]\."
2013-10-27 09:19:58 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 09:28:38 - EG_TV_TVPower state updated to 128935.266
2013-10-27 09:30:48 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 09:40:43 - EG_TV_TVPower state updated to 128935.266
2013-10-27 10:01:37 - EG_TV_TVPower state updated to 128935.266
2013-10-27 10:07:24 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 10:09:34 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 10:10:52 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 10:12:15 - EG_TV_TVPower state updated to 128935.266
2013-10-27 10:25:24 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 10:32:06 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 10:37:58 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 10:39:54 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 10:40:46 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 10:50:32 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 10:53:22 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 11:01:09 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 11:02:00 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 11:02:27 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 11:03:07 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 11:07:26 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 11:13:55 - EG_WZ_LampePower state updated to 127285.164
2013-10-27 11:14:22 - EG_WZ_LampePower state updated to 127285.164

What version of the product are you using? On what operating system?
Snapshot 1.4 on Linux

Please provide any additional information below.
Found someone else using some unofficial plugwise scripts with similar issue, 
will add corresponding thread later when found again. Note that the value 
returned is always the same, thus it looks like a communication error. The 
corresponding devices in those plugs most likely where turned off during all 
these occurrences, but not 100% sure about this.

Original issue reported on code.google.com by Max.Step...@gmx.de on 27 Oct 2013 at 10:35

[GoogleCodeExporter]

I can reproduce the same issue with 12 circles.

Here are some example logs:
2013-11-03 00:04:58 - Plugwise_Power_LED state updated to 121561.945
2013-11-03 00:05:58 - Plugwise_Power_WLAN state updated to 122336.71
2013-11-03 00:07:58 - Plugwise_Power_Printer state updated to 124758.48
2013-11-03 00:09:58 - Plugwise_Power_EatingRoom state updated to 123590.2
2013-11-03 00:20:58 - Plugwise_Power_LED state updated to 121561.945
2013-11-03 00:26:58 - Plugwise_Power_EatingRoom state updated to 123590.2
2013-11-03 00:41:58 - Plugwise_Power_Printer state updated to 124758.48
2013-11-03 00:43:58 - Plugwise_Power_Socket state updated to 128678.13
2013-11-03 00:44:58 - Plugwise_Power_Printer state updated to 124758.48
2013-11-03 00:46:58 - Plugwise_Power_Socket state updated to 128678.13
2013-11-03 00:54:58 - Plugwise_Power_WLAN state updated to 122336.71
2013-11-03 00:59:58 - Plugwise_Power_Amplifier state updated to 127673.85
2013-11-03 01:00:58 - Plugwise_Power_Printer state updated to 124758.48
2013-11-03 01:02:58 - Plugwise_Power_Printer state updated to 124758.48
2013-11-03 01:06:58 - Plugwise_Power_Printer state updated to 124758.48
2013-11-03 01:14:58 - Plugwise_Power_Printer state updated to 124758.48
2013-11-03 01:21:58 - Plugwise_Power_Socket state updated to 128678.13
2013-11-03 01:23:58 - Plugwise_Power_EatingRoom state updated to 123590.2
2013-11-03 01:26:58 - Plugwise_Power_LED state updated to 121561.945

Original comment by andan...@gmail.com on 3 Nov 2013 at 3:48

[GoogleCodeExporter]

Took me ages to find this again... Here is the promised link to the same (but 
fixed) issue in plugwise-python:

https://bitbucket.org/hadara/python-plugwise/issue/2/experiencing-spikes

plugwise binding should return error message as well when encountering max 
value for pulse counters

Original comment by Max.Step...@gmx.de on 3 Nov 2013 at 4:21

[GoogleCodeExporter]

Original comment by kai.openhab on 3 Nov 2013 at 7:21

[GoogleCodeExporter]

Thanks for finding this link. I will have a look at this asap as I am currently 
moving houses...

Original comment by karel.go...@pharco.be on 3 Nov 2013 at 7:51

[GoogleCodeExporter]

Original comment by teichsta on 5 Nov 2013 at 10:53

• Added labels: To-Github

[GoogleCodeExporter]

This issue has been migrated to Github. If this issue id is greater than103 its 
id has been preserved on Github. You can open your issue by calling the URL 
https://github.com/openhab/openhab/issues/<issueid>. Issues with ids less or 
equal 103 new ids were created.

Original comment by teichsta on 17 Nov 2013 at 8:08

• Added labels: Migrated-To-Github

[GoogleCodeExporter]

Set status to "invalid" to show that these issues are not tracked here anymore 
- please refer to GitHub instead!

Original comment by kai.openhab on 2 Dec 2013 at 7:12

• Changed state: Invalid