Last update for 2024.

One year of challenges, and great cooperations.
Thanks to all of you :)

• With this release we defiantly solve #295 thanks to the help of @borgqueenx the Obstacle View is finally at a stable point and can be used (remember privacy first).. did also add [Redacted IP] on the logs and please note here that also the link on the state attributes will be removed at the next release 2025.02.0.
• Not as a PR bur advice @markus-seidl found and solved a configuration issue #300, thanks to this no matter the prefix used more than one vacuum to serve will be added.
• Cleaned the code of Camera.py and introduced a new attribute to the camera_mode, the Obstacles Images will be maintaining the same aspect ratio selected in the camera options.

What's Changed

• Improving Image Handler code. by @sca075 in #299
• Return to camera_view when the vacuum is cleaning by @sca075 in #301

Full Changelog: 2024.12.1...2024.12.2

If you use it and like it please star it ;)

Fixing issues with Obstacle View

##Beta Relese -> obstacle_view exit when the vacuum is docked.
The previous released version was attempting to solve the issue waiting for the data from the vacuum.
With this release we save the last image when the vacuum is docked and then reuse it when the camera go back to map_mode. This might be the solution to this phenomena as per it looks the V1 I used to test it before is producing a ton of data that other newer vacuums do not.

It is also included a fix for issue #300, that is quite a great point as per the prefix of the topic can be custom and it was't take in consideration during the development.

2024.12.2b0 Return to camera_view

This is a beta test mainly for the users of ObstacleImages.

Introducing the Obstacles View we also added the camera_modes, as a matter of fact the code had a major refactor and was improved in various sense. In the logs from home assistant the IP address (that are of course visible in the links of the obstacle as state attribute), will be now shown as Camera Mode Change to load_view: Downloading image: http://[Redacted IP]:5000/image?filename=_DSC0013.jpg also, the camera will attempt now to load the fist available data from the vacuum (that normally are sent at interval time to MQTT), ensuring that image might be redraw.

this pre-release is to test in the real world those modifications.

What's Changed

• Issue 297 by @sca075 in #298

Full Changelog: 2024.12.0...2024.12.2b0

Fixing issues with Obstacle View

Fix

• Thanks @RocketSience for raising issue #297 Rand256 Missing Calibration Data when no Loaded Map
• Thanks also @@marvinwankersteen for raising issue #294 this should help a lot who is using the new Obstacle View and now is fixed..
• Thanks to @borgqueenx for raising #295, in this version we added more logs for the camera_mode and also improved code wise the download of the obstacles.

What's Changed

• Fixing Issues by @sca075 in #298

Full Changelog: 2024.12.0...2024.12.1

Obstacle Images in Home Assistant and more.

What is new.

Mainly thanks @carefulcomputer and @borgqueenx for the inputs, between this new feature and some fix required by testing the integration with the betas of Home Assistant, this release is addressing two potential warning that will pop put on 2024.12.0 of Home Assistant. At time of this release we also updated our documentation in order setup the below..

New Features

• Enhanced camera functionality for obstacle detection and image processing when the vacuum support ObstacleImages. Specify the obstacle to view and created a service to obstacle_view for easy integrate this new functionality with the Xaiomi Vacuum Map Card.
• Refined error handling for better feedback when no vacuum entities are found. Event "valetudo_error" also report the current error from the vacuum. The robot will be changing colour too in the map.
  Updates

What's Changed

• Fix Uknown error occurred" when trying to add entity during setup #278. by @sca075 in #279
• Adding event "valetudo_error" by @sca075 in #280
• Fix issue AREA_SQUARE_METERS deprecated #282 by @sca075 in #283
• Adding Obstacle Images by @sca075 in #287 and #290
• Fix Set Options for Config_Flow deprecated #288 and minor corrections by @sca075 in #289
• Outer Robot lines to Black by @sca075 in #292

Full Changelog: 2024.11.1...2024.12.0

As usual, when you are using this integration and you like it, please star it ;)

Obstacle Images in Home Assistant -> Done

Note this is a Beta Release.

It is now possible, and this is also the purpose of this beta, to view the obstacles directly from the card with a simple addition of yaml code. At the end of the already defined map_modes this pointer enable you to click on the "red dot" indicating the obstacle the vacuum detect from the vacuum map. The integration will download and render the image from the vacuum. To go back to the map view please click back with this Obstacle View anywhere on the image of the Obstacle.

map_modes:
  ....
  - name: Obstacles View
    icon: mdi:map-marker
    run_immediately: false
    coordinates_rounding: true
    coordinates_to_meters_divider: 100
    selection_type: MANUAL_POINT
    max_selections: 999
    repeats_type: NONE
    max_repeats: 1
    service_call_schema:
      service: mqtt_vacuum_camera.obstacle_view
      service_data:
        coordinates_x: "[[point_x]]"
        coordinates_y: "[[point_y]]"
      target:
        entity_id: camera.valetudo_v1_silenttepidstinkbug_camera
      variables: {}

This new functionality download one file per time, using threading. Please report Issues (hopefully all works as tested) as soon it happens. Thanks again for testing this integration and giving feedback.

Thanks @carefullcomputer for #281 and @borgqueenx for #286

What's Changed

• Fix fo #278 by @sca075 in #279
• Adding event "valetudo_error" by @sca075 in #280
• fix issue #282 AREA_SQUARE_METERS deprecated by @sca075 in #283
• Adding Obstacle Images by @sca075 in #287
• Fix for #288 and minor corrections by @sca075 in #289
• Obstacle Images in HA via Camera phase 2 by @sca075 in #290
• Outer Robot lines to Black by @sca075 in #292

Full Changelog: 2024.11.1...2024.12.0b1

2024.12.0b0 Vacuums Errors state / obstacles images

Note:

This is a beta release, as so, please report the issues you face. Thanks for testing this release.
I'm aware that configuring the options HA beta release show a warning for the config_flow an issue will be opened soon for tracking.
@carefulcomputer thanks for the comments on the valetudo_error the robot icon will be RED at 70% in the next beta release.

What's Changed

• Fix fo #278 by @sca075 in #279
• Adding event "valetudo_error" by @sca075 in #280
• fix issue #282 AREA_SQUARE_METERS deprecated by @sca075 in #283
• Adding Obstacle Images Phase 1 by @sca075 in #287

Full Changelog: 2024.11.1...2024.12.0b0

Fixes Rand256 startup and minor Refactoring.

What's Changed

• Fix #271 Rand256 startup by @sca075 in #272
• Refactoring Services by @sca075 in #273
• Releasing 2024.11.1 after tests by @sca075 in #275

Full Changelog: 2024.11.0...2024.11.1

Easy Control with more Actions.

What's new

added vacuum Actions go_to, clean_zones and celan_segments (save an load maps for Rand256) and added also support for MapLoader, in order to simplify the scripts in Home Assistant. Each time the maps are re-load in the vacuums the camera reset_trims will be automatically triggered.

Thanks also to @Minims did add a temporary fix for the reported #263
As a side note, there could be some fix for this new function within the next week.

What's Changed

• Adding support for MapLoader (auto reset_trims) by @sca075 in #260
• Update dependency pillow to v11 by @renovate in #259
• chore(deps): update dependency janus to v1.1.0 by #264
• Create da.json (Danish translation) by @kibuan in #269
• Temporary fix for issue #263 and Adding Actions by @sca075 in #266

New Contributors

• @kibuan made their first contribution in #269

Full Changelog: 2024.10.0...2024.11.0

Fixing Issue with _handle_coordinator_update

It is taking longer than expected, but we will soon complete this challenging version.
This is a new beta release of 2024.11.0 that should fix #263 with a working workaround.
Please be so kind to repot any issue by testing this release, will be happy to address it as soon.

What's Changed

• Temporary Fix issue #263 by @sca075.
• Version 2024.11.0 by @sca075 in #260
• Update dependency pillow to v11 by @renovate in #259
• chore(deps): update dependency janus to v1.1.0 by @renovate in #264

Full Changelog: 2024.10.0...2024.11.0b1