Skip to content

Releases: bruxy70/Garbage-Collection

Going to Helper, Config refactoring

14 Jul 07:11
Compare
Choose a tag to compare
Pre-release

4.8.2

Fix date type during restore and checking the expiry time - hope to resolve (#413) (could not replicate)
Aligning attributes to standard.

4.8.1

Fix group sensor selector (#412)

4.8.0

MAJOR CHANGE (integration→helper) - PLEASE READ!

It has always been the case, that this component was not an integration - it does not talk to any device or cloud service. Instead, it computes its state internally. And this is what helpers do. But I still made it as integration, as there was not really a way to have a custom helper. This has now changed, Home Assistant went a long way towards improved usability. Not only we can now have custom helpers, but they can also be configured from GUI, and it has all the features as before. So I am moving that where it belongs.
So, from now on, you will find it under Helpers. You can create new helpers from there, or you can also create them in the integrations - but they will end up as a helper anyway.
If you'd like to change the configuration options, you find it here:
image
In the Related tab, you'll find other info, including the device where you can get the DIAGNOSTICS info.

Code improvements

Related to the above - they greatly improved the config flow experience, including a new set of selectors. So I took this opportunity and completely re-factored the configuration. Including moving up the configuration options where they belong - removing an old workaround that was irritating me. The configuration should be migrated automatically, so no work to be done (hopefully).

Fixed Danish translation

Fixes #234. Thanks to @OEHC for PR #410

Going to Helper, Config refactoring

10 Jul 16:11
Compare
Choose a tag to compare

4.8.1

Fix group sensor selector (#412)

4.8.0

MAJOR CHANGE (integration→helper) - PLEASE READ!

It has always been the case, that this component was not an integration - it does not talk to any device or cloud service. Instead, it computes its state internally. And this is what helpers do. But I still made it as integration, as there was not really a way to have a custom helper. This has now changed, Home Assistant went a long way towards improved usability. Not only we can now have custom helpers, but they can also be configured from GUI, and it has all the features as before. So I am moving that where it belongs.
So, from now on, you will find it under Helpers. You can create new helpers from there, or you can also create them in the integrations - but they will end up as a helper anyway.
If you'd like to change the configuration options, you find it here:
image
In the Related tab, you'll find other info, including the device where you can get the DIAGNOSTICS info.

Code improvements

Related to the above - they greatly improved the config flow experience, including a new set of selectors. So I took this opportunity and completely re-factored the configuration. Including moving up the configuration options where they belong - removing an old workaround that was irritating me. The configuration should be migrated automatically, so no work to be done (hopefully).

Fixed Danish translation

Fixes #234. Thanks to @OEHC for PR #410

Going to Helper, Config refactoring

10 Jul 13:31
Compare
Choose a tag to compare

MAJOR CHANGE (integration→helper) - PLEASE READ!

It has always been the case, that this component was not an integration - it does not talk to any device or cloud service. Instead, it computes its state internally. And this is what helpers do. But I still made it as integration, as there was not really a way to have a custom helper. This has now changed, Home Assistant went a long way towards improved usability. Not only we can now have custom helpers, but they can also be configured from GUI, and it has all the features as before. So I am moving that where it belongs.
So, from now on, you will find it under Helpers. You can create new helpers from there, or you can also create them in the integrations - but they will end up as a helper anyway.
If you'd like to change the configuration options, you find it here:
image
In the Related tab, you'll find other info, including the device where you can get the DIAGNOSTICS info.

Code improvements

Related to the above - they greatly improved the config flow experience, including a new set of selectors. So I took this opportunity and completely re-factored the configuration. Including moving up the configuration options where they belong - removing an old workaround that was irritating me. The configuration should be migrated automatically, so no work to be done (hopefully).

Fixed Danish translation

Fixes #234. Thanks to @OEHC for PR #410

Going to Helper, Config refactoring

10 Jul 06:31
Compare
Choose a tag to compare
Pre-release

MAJOR CHANGE

It has always been the case, that this component was not an integration - it does not talk to any device or cloud service. Instead, it computes its state internally. And this is what helpers do. But I still made it as integration, as there was not really a way to have a custom helper. This has now changed, Home Assistant went a long way towards improved usability. Not only we can now have custom helpers, but they can also be configured from GUI, and it has all the features as before. So I am moving that where it belongs.
So, from now on, you will find it under Helpers. You can create new helpers from there, or you can also create them in the integrations - but they will end up as a helper anyway.
If you'd like to change the configuration options, you find it here:
image
In the Related tab, you'll find other info, including the device where you can get the DIAGNOSTICS info.

Code improvements

Related to the above - they greatly improved the config flow experience, including a new set of selectors. So I took this opportunity and completely re-factored the configuration. Including moving up the configuration options where they belong - removing an old workaround that was irritating me. The configuration should be migrated automatically, so no work to be done (hopefully) - therefore beta 😊.
I have been tackling an issue that the version migration was called all the time. This should be fixed in 4.8.0b2. So I'd call it a release candidate.

Fixed Danish translation

Fixes #234. Thanks to @OEHC for PR #410

Going to Helper, Config refactoring

08 Jul 14:10
Compare
Choose a tag to compare
Pre-release

MAJOR CHANGE

It has always been the case, that this component was not an integration - it does not talk to any device or cloud service. Instead, it computes its state internally. And this is what helpers do. But I still made it as integration, as there was not really a way to have a custom helper. This has now changed, Home Assistant went a long way towards improved usability. Not only we can now have custom helpers, but they can also be configured from GUI, and it has all the features as before. So I am moving that where it belongs.
So, from now on, you will find it under Helpers. You can create new helpers from there, or you can also create in integrations - but they will end up as a helper anyway.
If you'd like to change the configuration options, you find it here:
image
In the Related tab you'll find other info, including the device where you can get the DIAGNOSTICS info.

Code improvements

Related to the above - they greatly improved the config flow experience, including a new set of selectors. So I took this opportunity and completely re-factored the configuration. Including moving up the configuration options where they belong - removing an old workaround that was irritating me. The configuration should be migrated automatically, so no work to be done (hopefully) - therefore beta 😊.

Fix calendar, Brazilian Portuguese translation

18 May 06:23
Compare
Choose a tag to compare

Bugfix

#398 - fixed broken calendar

New

#397 Added Brazilian Portuguese translation - thanks to @LeandroIssa

Improve Groups

17 May 20:02
ad47b36
Compare
Choose a tag to compare

Improvements

The group entities were skipping the update waiting for the entities to update. Now I am triggering their update, so it should speed up the group frequency update.
Also a general review of asyncio methods.
Finally, adding unit tests for collect_garbage service and group frequency configuration. These catch many bugs that would become issues.

Re-release

09 May 19:53
Compare
Choose a tag to compare

Is it just me, or did the releases disappear? Re-releasing the last release, anyway. No code change.

Performance and stability improvements

08 May 18:58
Compare
Choose a tag to compare

Code refactoring - quite a big change, improving the overall architecture - but it does not add any features. All tested on my instance, with unit testing, that (hopefully) tests all configurations, plus in beta. So this should be smooth.
Also, general code improvements, that should improve performance (not that it was an issue).
Also, unit testing is working again - it did not work with the newest release for a couple of days - otherwise it would have prevented the need for the last release.
Also will be traveling later this week, so I am releasing that over the weekend, so I have the time to catch and fix possible issues (should not happen).

Performance and stability improvements

08 May 09:13
Compare
Choose a tag to compare
Pre-release

Code refactoring, general code improvements, fixes (unit testing is working again)