Releases: Ekman/home-assistant-pure-i9
Bugfix "expected str instance, NoneType found"
Clean specific zones
- Added ability to clean specific zones. You can read more about it in the manual.
- Credits to @Phype, thank you.
- Added a sensor for the dustbin state as it's the proper way to handle it.
Bugfix invalid device info
Fixes error Invalid device info
that has been surfacing since Home Assistant version 2023.9.0.
Credits to @juulius for the fix, thank you.
Cloud API v3
The integration stopped working due to there being a new version of the Electrolux Cloud API. This fixes that.
Shout out to @Phype for maintaining the Electrolux API library and to @lorenzo-deluca for adapting this integration to the new API.
Extra cleaning attributes
The integration will now create three additional sensors that are linked to the same device as the vacuum. These sensors give you the vacuums:
- Last cleaning start, date and time.
- Last cleaning end, date and time.
- Last cleaning duration, in seconds.
Additionally, updated purei9_unofficial
to version 0.0.11
.
Data coordinator
- Update data using a coordinator.
- A coordinator is used to update devices that have multiple entities. Instead of each entity updating itself then the coordinator updates and distributes data to the entities.
- Remove
Electrolux
from the integration name for consistency with the rest of the integration.- The name will only update for new installs, but it does not matter for existing installs.
- Bugfix, reporting dustbin error messages.
Reminder: Please read the release notes for version 1.3.0
.
Integration UI
- Add the ability to configure the integration using the UI instead.
- This is now the recommended way of configuring the integration.
- Configuration using
configuration.yml
is now deprecated.
To upgrade the way of configuration:
- Delete the integration from
configuration.yml
. - Restart Home Assistant.
- Follow the steps as described in the configuration section in the readme.
NOTE! Entity IDs are still generated similarly so automation will not break.
Why are you changing the way to configure the integration?
The integration only supports creating one entity per vacuum. In order to support eg. showing floor maps, then the integration needs to create multiple entities per vacuum and the correct way to do that is to create one device per vacuum. In turn, one device can contain multiple entities. This new way of configuration supports devices.What if I don't upgrade to the new way of configuration?
Configuring using configuration.yml will still work for the foreseeable future so you don't need to worry about anything breaking. If version 2.0 of the integration is released, then the deprecated code will be cleaned up. This will not happen for a long time, possibly never.Update library
Update purei9_unofficial
to version 0.0.10
, the latest version.
Manifest version
Update manifest.json to correct version. This had been accidentally left at 1.1.0
.