The integration now allows configuring parameter manual_update: true. Then, after calculating the collection schedule, it will not automatically update the entity state. Instead, it will fire an event garbage_collection_loaded, which will allow you to programmatically add and/or remove dates based on whatever custom logic (e.g. based on values from external API sensor, comparing the dates with a list of holidays, calculating custom offsets based on the day of the week etc.), and then manually trigger the update of the entity state and attributes by calling the service garbage_collection.update_state.
Check the example HERE
I will appreciate very much your feedback and suggestions. Samples of automation you created that could be helpful for others would be great. You can send them as comments to the "idea" #287. Thank you!
Yes, this is an advanced feature, but if you do not configure it, the core functionality should work unchanged for now.
But it should address requests implementing different specific patterns or exceptions, so I can address these requests through that.
Said that going forward, I might make some very specific and confusing parameters obsolete and simplify the configuration, and leave some of the specific scenarios for automation templates (with your help). I am even thinking of creating a separate integration for holidays and addressing the exceptions through a set of blueprints. And I am thinking of adding a blank frequency option, in case you want to generate the schedule entirely by automation. Now, this is a big change, and I have no effective way of getting your feedback. So please send me your suggestions or comments.
This is the result of refactoring described in #287. There were a number of feature-request for very specific custom collection schedules, that should be now doable with this. (including #305)
This also fixes bug #311