chore(release): 3.2.1 [skip ci]

## [3.2.1](3.2.0...3.2.1) (2025-07-04)

### Bug Fixes

* bump plugp100 5.1.5 ([38d65e3](38d65e3))

chore(release): 3.2.0 [skip ci]

# [3.2.0](3.1.9...3.2.0) (2025-04-06)

### Bug Fixes

* light entity effects ([39c0dbe](39c0dbe))
* semantic versioning ([f9ef032](f9ef032))

### Features

* set min version ha to 2025.1.0 ([97e72f9](97e72f9))
* upgrade to plugp100 5.1.4 ([0df4735](0df4735))

fix: revert supported feature light bulb (#844)

fix: ATT_COLOR_TEMP deprecated constant (#840)

Fix #824

fix: AttributeError causing integration failure (fixes #812) (#837)

The issue stems from Home Assistant requiring the use of
async_update_entry to update the version number, which results in an
initialization failure.

---------

Co-authored-by: Daniel O'Connor <daniel.oconnor@gmail.com>

fix: Return LightEntityFeature(0) zero value in supported_features wh…

…en there are no effects (#826)

Fixes
#825

In HA 2025.1 support for using integers in `supported_features` was
removed home-assistant/core#132371

fix: german instead of dutch on some values (#818)

Hello, during integration i have seen that there is some dutch
description instead of german, sorry if you already knew this.

fix: check empty energy_info to avoid error (#780)

I have two P110, and the first one was not working after I added the
second one.
Based on the log, the energy_info is None when startup, so, the
following entities are all failed to load.
And from the Tapo app, the energy info is shown as "--" in the first
P110 as well.

After I have added the Null check, there is no startup error and the
first P110 is now working (at least can be turned on/off via HA)
Although the energy_info is still empty in HA, it is the same result as
Tapo app.

fix: Add hs null check to avoid light crash (#748)

Avoid a crash on the hs light check if none is set.

Fixes #746

fix(core): bump to 3.1.2