Add address capability to v1 API calls #15
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
Changed documentation to fork repo, so it shows up in HACS properly.
…her. Either-or-ed it now.
|
@snicker any interest in reviewing and merging? seems like worthwhile functionality. |
|
@snicker @heythisisnate Any updates around having address support on the V1 API? |
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.
Adds in the address payload for alarm calls using the v1 API, since that appears to be preferred based on this message.
Verified the address gets passed to Noonlight with the populated information. It still requires a manual configuration.yaml edit, but since you have to paste in the Noonlight key regardless, that seems pretty trivial of a step.