Skip to content

Getting ready for Holiday blueprints
Compare
Choose a tag to compare
@bruxy70 bruxy70 released this 28 Jan 15:23
· 363 commits to master since this release
4.3
f6d6080
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Summary

With this change, I am making a few parameters obsolete. Review the documentation. In the next release, I will simplify the integration to focus on the calculation of the collection schedule, and leave all exception handling to the blueprints using the manual_update.

For the public Holidays, this is using the integration "Holidays", which has just been included in HACS as well (I've been waiting for that with this release). So you will need to install that to use the holidays.

I think I have created the blueprints with equal functionality and made them available in the README - check the video about how to import and use them. More importantly, I'd like to encourage you to create your own blueprints and share them with others - in the past, there were many requests to these custom exception scenarios that I had to reject - now it is possible.

!!If you use any of these parameters, please migrate them to the blueprints, so that the next update will be non-breaking!!

I am also simplifying the configuration. The YAML config is not supported anymore. If you have the integration configured in YAML, it will be automatically imported on the first restart, and you will be able to remove the YAML config after that. This will not only simplify it again but also allow for automatic conversion going forward.

Breaking Change

Migrating the config from configuration.yaml (so not really a breaking change - it is automatic)
The only thing you need to do, after the restart, check it has been imported to the Configuration/Devices & Services and remove it from the yaml file.

Updates

  • Documentation updates
  • New blueprints
Assets 3
Loading