Do not convert the target temperature to integer

[vickyg3]

In places where Fahrenheit is the default temperature scale (like
US), home assistant UI shows the climate cards in Fahrenheit scale
and converts the temperature to Celcius implicitly for integrations
that use Celcius.

So the set_temperature() calls in this case will get a floating
point temperature value for celcius and converting that to an integer
before converting that to Kelvin makes setting certain temperature
values in Fahrenheit impossible because of the rounding errors.

Consider the following case:
User sets 74F -> Home assistant converts it to 23.3C -> Converting
that to integer becomes 23C which is equivalent to 73F. So setting
74F is impossible because of this rounding.

Not converting the value to integer and converting directly to a
floating point Kelvin temperature solves this issue and users would
be able to set any Fahrenheit temperatures they want. Note that the
underlying libdyson library supports setting any floating point
temperature in Kelvin and the rounding to integer was not really
necessary in the first place.

[FutureGUIs]

I like this, it's been a long time coming to fix this issue. Are there any side effects to removing that line and getting this done?

[vickyg3]

Are there any side effects to removing that line and getting this done?

I don't believe there are any side effects other than making Fahrenheit working as it should be. For users with locale set to Celcius, the existing behavior will continue to work (since the int() conversion has no effect in that case).

[Kakise]

I did some tests at home with this patch applied and I can confirm it did work with my phone set to celsius and my American friends phone that I added to my home.