Fix set_target_temperature() when called with 126.5

[rotdrop]

This happens if any of the preset modes eco or comfort are set to off in the Fritzbox UI for a thermostat, e.g. the 302.

Fixes #129.

Luckily 126.5 has an exact binary representation as floating point number ...

[mib1185]

Hi @rotdrop
nice catch 👍 I would think having an explizit "if" instead of an "if not" looks somehow better (but this is a bit opinionated).
But it would be good if we could have a test for this.
thx 👍

[mib1185]

Suggested change

	if temp < 16:
	if temp < 16 or temp == 253:

[mib1185]

Suggested change

	elif temp > 56 and not temp == 253:
	elif temp > 56:

[rotdrop]

Hi @rotdrop nice catch 👍 I would think having an explizit "if" instead of an "if not" looks somehow better (but this is a bit opinionated). But it would be good if we could have a test for this. thx 👍

I actually had the or temp == 253: first but the following line would then re-assign the same value to temp instead of just doing nothing. This is why I came up with the if not which simply skips an unnecessary re-assignment of just the same value. But, hey, it really just does not matter.

Can you change it to your liking (then just go ahead!) or is my interaction required?

[mib1185]

The part about "if" or "if not" was more an opinionated one (not crucial) but that we need a test is a necessary one, so we proof that the bug is fixed and avoid possible regressions in the future

[coveralls]

coverage: 96.906%. remained the same
when pulling c54f814 on rotdrop:bugfix/do-no-swith-to-boost-if-preset-modes-are-off
into 6d2653a on hthiery:master.