Skip to content

Releases: sca075/mqtt_vacuum_camera

Added Auto Zoom function

25 Feb 10:13
Compare
Choose a tag to compare
Pre-release

What is new:

  • Camera text improvements with unicode characters, we changed the default font.
  • When the robot is in segment cleaning, and arrive to the specific room to clean the camera will auto zoom on that room. Function preview in announcement #85.

What is still to be implemented before the final release:

  • Refactoring of the camera is a slow but continues process, there will be some transparent minor changes in the code, not causing changes in performances of it.
  • Will implement the lock selected aspect ratio of the image in order to keep the dashboards not influenced from the automatic zoom.

Full Changelog: v1.5.9-beta.1...v1.5.9-rc1

v1.5.9-beta.1

21 Feb 21:21
Compare
Choose a tag to compare
v1.5.9-beta.1 Pre-release
Pre-release

What's Changed

  • Adding support for Japanese and Taiwanese Mandarin languages. by @kodbuzz in
  • Adding status text battery charge status updated (currently test on PI4 8GB).
  • Remodelling on the connector simplified version of update data to the camera (to be tested on Rand256).

New Contributors

Full Changelog: v1.5.8...v1.5.9-beta.1

if you use this camera and you like this project please take a moment and live us a star ;)

Proxmox VE supported and tested.

15 Feb 21:19
Compare
Choose a tag to compare

This release come with some new adjustments made to our Camera in order to fully support the Proxmox VE's.
It was a quite challenging troubleshooting but we are happy to confirm that the camera can be use also in VE environments.

Fix

  • Issues #75 and #78 related to PROXMOX camera frizzing. It works much better on VE with 4GB Ram but also with the 2GB run we were able to run stably two vacuums (on our tests). Thanks @kodbuzz, @cdrfun and @N1c093 for them cooperation and comments.
  • Issue #79 We tested the migration from v1.4.8 up to the newer 1.7.5 and confirmed the issue reported from @duffmiester that here we thanks for it, we also review the values and matched it to the last camera setup from scratch that of course was also tested before releasing this version.

What's new in this release.

  • The camera attributes are now improved in order to follow the Home Assistant required standard.
    Screenshot 2024-02-15 at 19 56 09
  • The logging improved too, removing the rooms data from the logs and also more clarity on them.
  • There isn't anymore the error "cant't get calibration data" = until there are data from the vacuum in MQTT (the connector was slightly improved) the camera will startup regularly and output eventually that he vacuum isn't connected to MQTT on the status tesxt.
  • The status text is improved in order to report also the battery status, thanks to the cool idea of @zecoj
    Screenshot 2024-02-15 at 19 53 36
  • We could finally confirm the camera also with Rand256 after the switch to multi threading so green light to the Rand users.

We count to implement the automatic zoom of the cleaning area of the vacuums

Purpose of this Release

  • It fix reported issues.
  • Breaking changes on HA.
  • Required improvement for HA.
  • Discussed improvements.

Checked Before Release

  • The integration can be setup from scratch.
  • The entity can be reconfigured or deleted.
  • Options selections working.
  • Go to and Zones Cleaning tested.
  • Segments cleaning tested.
  • There are fixes not causing breaking changes.
  • There are breaking changes.
  • Automatic Update (migration) of the integration configuration data confirmed.
  • Setup from scratch, when using options, when no options are setup.

Memory Shortage Check Review.

09 Feb 12:03
Compare
Choose a tag to compare

Fix:
Issue #78 reported by @cdrfun the memory shortage calculation (that was also review) did cause the camera to stop as per the level was set to Error, instead now it is set to Warning and also instead to count 12 arrays we are now counting the one necessary for the the next step only 2. This reduce the margin to the real need memory space.
I take also this occasion to tanks you all for your kind and rightly raised issues, this is helping us to fasten and make robust the code of this project. The patches released in this days are mainly addressing those issues, and we are trying to do our best to keep all in track also, the development of the V1.5.8 that soon should be out with some improvements (the round versions are fully tested).

Thanks once again for the cooperation and understanding.

Remodelling and Fixing Migration Issues

08 Feb 11:49
Compare
Choose a tag to compare

Fix:

  • Migration issues from config entry 2.1 to 2.2 fixed thanks @Cellivar that reported this issue.
  • Refactoring: Improving logs in general and also added docstrings on several modules.

Tested the migration from 1.4.8 to 1.5.7.4, no errors anymore, so #77 could be considered closed.

GC logging causing extreme performance hit for HA

07 Feb 16:10
Compare
Choose a tag to compare

Fix:

  • Removed GC completely from camera.py reported issue #76 thanks @droans

GC causing slow down of rendering.

05 Feb 09:59
Compare
Choose a tag to compare

What is for:

Testing once again the v1.5.7.1 I found some improvement could be done, this version purpose is to fix #75 and #74
Rand236 users be informed that the camera is now threading the image creation, and unfortunately I couldn't test it on this firmware yet, please wait for v1.5.8 within next week.

Patch release for reported issue.

04 Feb 22:10
Compare
Choose a tag to compare

FIX:

issue #74 discussed on conversation #73, this version wasn't fully tested on rand256 so please await the next v1.5.8 before to update it, reason behind is that the camera will create a new thread also for the rand256 (theoretically there should be no problem but again it was not yet test).

  • Added Garbage Collection to keep the memory consumption under control.
  • Added check when no memory available the image will be skipped and error will happen.
  • As well added some additional try on the image handler that anyhow will be remodelled in the next days.

This patch version was tested same as you can see on the video provided earlier today in the #74.

Threading the camera processing.

25 Jan 15:44
Compare
Choose a tag to compare

Fix:

  • The Hypfer vacuums images are now generated in a separate thread this should fix #71 as per the main_thread will be not overload from the camera image processing.

Enactments:

  • CameraShared module is sharing the data between modules. It will be used to refactor the camera.
  • CameraProcessor module is added to thread (or in future multiprocess) the images data. This module will evolve separating tasks that right now heavy to handle on py3b+ and py4 as well virtual environments.

Note:

As per at the moment was not possible to test the new threading functionality on rand256 vacuums there is no change for this firmware.

Purpose of this Release

  • It fix reported issues.
  • Breaking changes on HA.
  • Required improvement for HA.
  • Discussed improvements.

Checked Before Release

  • The integration can be setup from scratch.
  • The entity can be reconfigured or deleted.
  • Options selections working.
  • Go to and Zones Cleaning tested.
  • Segments cleaning tested.
  • There are fixes not causing breaking changes.
  • There are breaking changes.
  • Automatic Update (migration) of the integration configuration data confirmed.
  • Setup from scratch, when using options, when no options are setup.

Starting independent task from async

20 Jan 14:02
Compare
Choose a tag to compare

Fix:

  • In order to spawn a task that will not block the current async context, we modified the image update as a task on the event loop. This will then be executed in parallel.
  • A new image option is added (but is currently disabled) to export the SVG of the base layer (floor and walls). This is a patch release.

Note:

  • Current implementation can cause home assistant to do not respond when home assistant is running on systems < of Raspberry PI4
  • To solve the above mentioned limitation (unfortunately HAOS will not support OpenCV), we are currently working to implement python multiprocessing that will distribute the load of the image processing across all available cores. Target is v1.6.0.
  • As usual all test passed before releasing this patch.

Thanks for your kind understanding.