3D printers (the people using them) now almost universally use Celsius, not Fahrenheit. When my integration is being configured I’d like to default all the temperature units to Celsius and possibly also all length measurement units to mm to match that expectation so that few to no users need to do that manually for a whole bunch of sensors.
It does. That’s the problem. Everyone wants the integration to show temperature in Celsius because that is standard for the 3D printer community even when it’s not the standard for their country (US). So everyone in has to go change the many sensors over to Celsius individually.
The unit of measurement to be used for the sensor’s state. For sensors with a unique_id, this will be used as the initial unit of measurement, which users can then override. For sensors without a unique_id, this will be the unit of measurement for the sensor’s state. This property is intended to be used by integrations to override automatic unit conversion rules, for example, to make a temperature sensor always display in °C regardless of whether the configured unit system prefers °C or °F, or to make a distance sensor always display in miles even if the configured unit system is metric.
Yes, it works! Oddly the writable ‘number’ entities are already defaulting to celsius which I’d not noticed until now. And those don’t support the setting - it’s limited to sensor entities by the looks of it.