Fixed typos and adjusted for uniformity

[ksga]

Minor adjustments to increase uniformity and corrected a few typos.

[ksga]

Great effort by @mortenmathiasen
Just made a few proof changes

[mortenmathiasen]

Looks great @ksga - Thanks!

[mortenmathiasen]

Looks great @ksga - Thanks!

[jonasbkarlsson]

Thanks!

[jonasbkarlsson]

@ksga , @mortenmathiasen , does anyone of you use HA 2024.12 (or later)? A lot of my tests fails with HA 2024.12.5, but works fine with HA 2024.11.3. It seems to be related to translation, and maybe it is due to this: https://developers.home-assistant.io/blog/2024/11/21/unit-of-measurement-translations/

   @cached_property
    def _unit_of_measurement_translation_key(self) -> str | None:
        """Return translation key for unit of measurement."""
        if self.translation_key is None:
            return None
        if self.platform is None:
>           raise ValueError(
                f"Entity {type(self)} cannot have a translation key for "
                "unit of measurement before being added to the entity platform"
            )
E           ValueError: Entity <class 'custom_components.ev_smart_charging.sensor.EVSmartChargingSensorCharging'> cannot have a translation key for unit of measurement before being added to the entity platform

/home/vscode/.local/lib/python3.13/site-packages/homeassistant/helpers/entity.py:656: ValueError

[ksga]

I'm not sure I follow @jonasbkarlsson .
Actually I'm just using v2.0.1 as it is, waiting for the updated translation to be included in a future release.
On 2025.1.0 the only ev_smart_charging error I'm seeing is the config one mentioned in an issue already:

Logger: homeassistant.core
Kilde: helpers/deprecation.py:222
Første forekomst: 08.56.36 (1 forekomster)
Senest logget: 08.56.36

Config was used from ev_smart_charging, this is a deprecated alias which will be removed in HA Core 2025.11. Use homeassistant.core_config.Config instead, please report it to the author of the 'ev_smart_charging' custom integration

[jonasbkarlsson]

Thanks. I have now concluded that this problem "only" affect the test code, not the actual integration. So I need to make some updates of the test code...