Blueprints are awesome, but it lacks a serious update engine, which would allow users to know when a new version is available and easily (1-click) update it.
The re-inport works ok, but it is far from what is available for other areas.
The other areas are third party integrations, HACS.
Yeah agreed, this is a big wishlist item for sure.
The problem has always been: We don’t know if the update will break stuff. There is no guarantee the new Blueprint is compatible with the existing automations or that they will behave differently completely.
In terms of breaking, if an input changes and is no longer compatible with an automation made from the Blueprint, the automation would fail to load and become invalid.
…/Frenck
versioning of automations too?
I see your point for not being able to check if the new Blueprint is still valid for the user’s automation, but that would be the case for any integration or HACS also, where you cannot ensure that new code is OK, but still be able to inform users about the new version, communicate the changes and allow for easy update if the user decide to proceed.
I believe it should be similar for blueprints, or at least some parts of this. The way it is today is quite hard to maintain and still leave space for breaking changes on HA side to stop the Blueprint.
This would be great if implemented. If HA would check for new updates on blueprints it could show a link to the blueprint and the description part of the new blueprint which would state (by the blueprint owner of course) if there is a breaking change or not). Then the user would know if they can click the update button or first make some preparations.