v2.2.2: Fix ValidationError on missing ConfigVersionId

Apparently ConfigVersionId can sometimes be missing

v2.2.1: Fix ValidationError on some valid messages

Fix integration going offline sometimes, because some optional fields are missing in some messages.
This release updates pyechorobotics to tolerate that.

v2.2.0: Support for robotActionErrorMessages.contactError

Turns out when the robot cannot be reached, the current API endpoint behaves weirdly.
It returns json without any action_id, status nor message.
After about 30s it suddenly does return all that, with a new
message robotActionErrorMessages.contactError.

This release moves to pyechorobotics==1.1.0, which adds parsing support for this behaviour.

Additionally, an additional call to the current endpoint was added before running smartfetch.
This was found to prevent going unavailable in some scenarios.

Migrate to pydantic 2.0.0

This version migrates to pydantic 2.0.0, which is needed as of HA 2025.1: https://www.home-assistant.io/blog/2025/01/03/release-20251/

v2.0.0: lawn_mower entity

Feature

• Adds lawn_mower entity.
• Fixes SourceType warning.
• Adds some robustness to network issues, hopefully avoiding unavailable states

Breaking changes

main-switch is renamed to auto-mow, in accordance to home-assistant/architecture#40 and home-assistant/architecture#894.
Updating to this release will re-name the entity_id and unique_id. This will keep your history and hopefully also automations intact.

	entity_id	unique_id
old	switch.{robot_id}_none	{robot_id}-main-switch
new	switch.{robot_id}_auto_mow	{robot_id}-auto-mow-switch

Renaming the entity_id will not happen if your old entity_id is something different. You are also free to manually rename it in the UI.

v1.0.0

Initial version