Skip to content

Releases: bruxy70/Garbage-Collection

Bugfix for every_n_days on iOS

20 Dec 17:54
Compare
Choose a tag to compare

Bugfix

Fix the default date for the first date for every_n_days on iOS (#420)

Bugfix for every_n_days on iOS

19 Dec 10:02
Compare
Choose a tag to compare
Pre-release

Fixes

Fix the default date for the first date for every_n_days on iOS (fixes #420)

Bugfix for ignoring first and last months - from the last release

09 Dec 11:47
Compare
Choose a tag to compare

Compatibility with HA 2022.12

08 Dec 07:35
Compare
Choose a tag to compare

2022.12 changed the code for config flow, so new helpers could not be created, the configuration of old ones could not be changed. This is fixing it (issue #441 )

Compatibility with 2022.12.0

07 Dec 21:25
Compare
Choose a tag to compare
Pre-release

Fix #441
Pre-release

Compatibility with 2022.12.0

07 Dec 21:20
Compare
Choose a tag to compare
Pre-release

Fix #441
Pre-release

Bug Fixes

21 Nov 07:21
Compare
Choose a tag to compare

Addressing two bugs:
#438 - setting the state to None if there is no further date scheduled (that should only happen for blank frequency)
#439 - checking the attributes in the stored state. I could not reproduce the issue, but I guess this could happen in some update scenarios.

Going to Helper, Config refactoring

18 Jul 08:05
37fd4fa
Compare
Choose a tag to compare

4.8.3

Extending the period for daily frequency to 1000. Thanks to @mglants for PR. Resolves their #416.
Permanent fix for the update when options change (unblocking update on restore state).

4.8.2

Roll-back "restore entity state". It prevents the update when options change - hope to resolve (#413). Rolled back until I find a better solution.
Aligning attributes to standard.

4.8.1

Fix group sensor selector (#412)

4.8.0

MAJOR CHANGE (integration鈫抙elper) - 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

14 Jul 20:24
Compare
Choose a tag to compare

4.8.2

Roll-back "restore entity state". It prevents update when options change - hope to resolve (#413). Rolled back until I find a better solution.
Aligning attributes to standard.

4.8.1

Fix group sensor selector (#412)

4.8.0

MAJOR CHANGE (integration鈫抙elper) - 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

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

4.8.2

Fix date type during restore and check the expiry time & clearing state on options update - 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鈫抙elper) - 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