Handle out of range values on rmu data

[elupus]

We need to apply the same out of range checks for RMU data, since these fields also send out range data on error values.

Swapping scale and offset and applying same range checks for RMU data.

[codecov]

Codecov Report

Attention: Patch coverage is 77.77778% with 6 lines in your changes missing coverage. Please review.

Project coverage is 57.84%. Comparing base (7943537) to head (e36130c).
Report is 6 commits behind head on master.

Files	Patch %	Lines
nibe/connection/nibegw.py	70.00%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #173      +/-   ##
==========================================
+ Coverage   57.69%   57.84%   +0.15%     
==========================================
  Files          14       14              
  Lines        1267     1274       +7     
==========================================
+ Hits          731      737       +6     
- Misses        536      537       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[elupus]

Ps. I'm starting to think there are no 2's complement signed values anywhere in the pump. All are unsigned values with some defined offset to make them signed.

[yozik04]

Would be great to add some test coverage on these changes.

[elupus]

Don't seem to be able to hit the error values with the FixedPointStrange, since with positive offsets we can never hit the limit values. I've not seen any error values on the outdoor temp field so far. In theory it could indicate errors with the unused values in the gap i suppose (ie a zero value). I've removed that check for now.

[yozik04]

Great, thank you. Merged. Do you need a new release?

[elupus]

Can hold of a bit. Got a weird 32 bit degree minutes parameter issue since the myuplink upgrade that need to be looked at.