feat(crestron): fusion driver#344
Merged
Merged
Conversation
Contributor
Author
|
@w-le Do we require security level 2 or is level 1 going to be sufficiently given that we will be using HTTPS? |
Contributor
|
i'll ask the crestron fusion admin |
Contributor
|
They said the "current level" is sufficient, so sounds to me like level 1 |
This file contains hidden or 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
3 participants
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.
Add Crestron Fusion driver.
Based on documentation from 2021 and code samples from 2012.
Models have been left out due to the type of a lot of fields not being documented.
Could use a test system to improve the quality of this driver.
New docs around the Signal Values endpoint are good and it looks like we only need the Signal Values working for now.
Security levels 0 and 1 should be working.