Documenting impact of state restore change (#8019)

As it turns off all the automations without an `initial_state`, and it's hitting lots of folks, documenting it here ;)
This commit is contained in:
DubhAd 2019-01-02 11:28:43 +00:00 committed by Joakim Sørensen
parent 4e2055ae5e
commit bfc8cbc5e1

View File

@ -33,6 +33,8 @@ We have a new more reliable way of state restoration introduced by [@armills]. I
This comes with a downside: we will be unable to restore states the first time you start 0.84. This comes with a downside: we will be unable to restore states the first time you start 0.84.
This means that on upgrade to 0.84 any automation that doesn't have an `initial_state` defined **will be disabled**.
## {% linkable_title Improved service calling %} ## {% linkable_title Improved service calling %}
We have improved how we call services with better validation checks. This means that if you have an automation or a script that sends invalid data, we will now stop the execution and be better able to point out where your incorrect calls are coming from. We have improved how we call services with better validation checks. This means that if you have an automation or a script that sends invalid data, we will now stop the execution and be better able to point out where your incorrect calls are coming from.