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, suggestions. And perhaps samples of automation you created, that could be helpful for others. You can send them as comments to the issue #287. Thank you!
Yes, this is an advanced feature. But if you do not configure it, the core functionality should work unchanged for now.
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). You can also send me your suggestions.
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.