Taking Thermostat as an example. There are specified requirements what constructor and temperature getter/setter accept (or expect):
constructor accepts Fahrenheit temperature,
temperature getter gives temperature in Celsius,
temperature setter accepts temperature in Fahrenheit.
However there are no requirements how exactly class needs to keep the actual temperature internally. Due to using getter/setter, internally temperature can be kept either in Celsius or Fahrenheit (or any other temperature unit). And regardless of how that exactly is done temperature getter/setter can always fulfill requirements - getter gives Celsius and setter accepts (expects) Fahrenheit.
This might be a bit abstract in a case that you can change everything the way you want. Imagine there are parts that you cannot change, because somebody expects and depends on fact that temperature to give Celsius.
There are languages where such convention is a bit more formalized and it might be actually expected (otherwise it would be considered as error) that classes will always use getters/setters without even giving ability to be able to see what the internal representation might be.