I just updated to 0.88.2, but I can’t be sure if that caused this behavior so I wanted to post first before filing an issue. I have a Z-Uno board with a DS18B20 temperature probe and it’s reporting temps in Fahrenheit, confirmed by looking at the Open Z-Wave log. With the default zone (no explicit “zone:” component in configuration.yaml), and with “unit_system: imperial” specified, I see the correct “℉” in “unit_of_measurement” in the states view and elsewhere. If I simply add the “zone:” tag in configuration.yaml, it’s reported as Celcius everywhere. Here’s a snippet of configuration.yaml that correctly reports in Fahrenheit:
homeassistant:
#zone:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: xxx
longitude: xxx
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 340
# metric for Metric, imperial for Imperial
unit_system: imperial
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: America/Los_Angeles
With this, the unit_of_measurement switches to “℃”:
homeassistant:
zone:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: xxx
longitude: xxx
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 340
# metric for Metric, imperial for Imperial
unit_system: imperial
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: America/Los_Angeles
Am I missing something? Incidentally, I’m only interested in adding the “zone:” tag to be able to specify a radius of larger than 100M for Device Tracker, and it seems strange that that tag is only allowed with an explicit zone while the others are all valid in the default zone.