Error code reported as decimal rather than int

[kchen]

The error code is reported as a decimal number (for example, 115.0) instead of an int (115). It would be ideal if the error code were reported as an int instead.

[joeblack2k]

Update: I opened the combined status/telemetry draft PR here:

#172

For the error-code part, the PR keeps publishing the same raw LG error byte and adds accuracy_decimals: 0 to the sensor schema/base YAML. It deliberately avoids adding a device class or state class so Home Assistant does not interpret it as a measurement.

Validation:

• Generated ESPHome code now calls error_code->set_accuracy_decimals(0).
• Live ESPHome logs on the Bioscoop LG Airco show Error Code >> 0.
• Home Assistant's backend state API still represents the value as a numeric string (0.0) on my existing entity, which appears to be HA/ESPHome state representation/caching rather than the firmware precision setting.