Cloud device list and Content-Type update #324
Merged
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.
Changes:
The
Content-type: application/jsonheader is now always added (can be disabled by setting_tuyaplatform( ..., content_type=None )If apiDeviceID is provided, the old device list fetching routine is used by default. Leave apiDeviceID empty or set
cloud.use_old_device_list = Falseto use the new routine.apiDeviceID can now be a comma-separated list of device IDs and it uses all of them to build a list of UIDs.
The cloud init function now ignores any extra/unknown arguments, so you can have extra fields in tinytuya.json and
tinytuya.Cloud( **config )will still work.Fixes #323