Update SDName-schema to current API-version #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As far as I can see, somewhere between API versions 38 and 54 the field
globalIdwas added to the SDName-Model, which is not included here.This indirectly causes home-assistant/core#98362
The full resulting station of
checkNameis saved by the config flow there (without performing a validation against the schema, so no issues), and is then used directly as input for thegetSchedulemethod (with validation, which in turn fails due to the schema being outdated and not containing globalId).While the schema file should normally be automatically generated, the validation schema is no longer available/being provided, so auto-generation is currently not possible.