-
-
Notifications
You must be signed in to change notification settings - Fork 31.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
Google Assistant and Homekit sending wrong target temp values #18524
Comments
I only know the situation with HomeKit: The Home App uses Celsius internally, but only rounded to the nearest I tried setting the temperature to |
Need to add rounding to the execute() function for all commands. |
Home Assistant release with the issue:
0.82.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io on Docker on CentOS 7
Component/platform:
Description of problem:
If I choose a temperature of 73°F in Google Assistant, the value of 72.99999122619629 is sent to my thermostat. My thermostat rounds this down to 72°F so I can not actually set a target temp of 73.
If I choose a temperature of 75°F in HomeKit, the value of 74.7 is sent to my thermostat. My thermostat rounds this down to 74°F so I can not actually set a target temp of 75.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
It looks like both components are working in Celsius and then converting to Fahrenheit. Ideally the components should work in the user's native unit measurement system (from configuration.yaml), but a possible short term fix would be to send a rounded integer to the thermostat.
The text was updated successfully, but these errors were encountered: