JSON encoded record_plan list value should not contains space #159
Conversation
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
For some reason, when Tapo sees space characters in the record_plan value, it will only take only the first item. This fix will let Tapo to accept all items inside the record plan.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
For some reason, when Tapo sees space characters in the record_plan value, it will only take only the first item. This fix will let Tapo to accept all items inside the record plan.
Example:
If we send
"sunday": "[\"0000-0900:2\", \"2200-2400:2\"]", Tapo would take only the "0000-0900:2" as the record plan for Sunday.To tell it accept all 2 slots, we will have to send
"sunday": "[\"0000-0900:2\",\"2200-2400:2\"]"(without the space between 2 items)