Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keys case sensitive #152

Closed
wants to merge 1 commit into from
Closed

Conversation

TeslaOwnerTips
Copy link
Contributor

When i use the api I get
{"success":true,"currentState":"","targetState":"0"}
{"success":true,"CurrentPosition":"1","TargetPosition":"1"}
But when I change the case I get
{"success":true}

When i use the api I get
{"success":true,"currentState":"","targetState":"0"}
{"success":true,"CurrentPosition":"1","TargetPosition":"1"}
But when I change the case I get
{"success":true}
@benzman81
Copy link
Owner

What url did you call and what did you want to achive?
From code I can tell, that if you call the url without currentstate and targetstate, the the current status will be returned as information and nothing happens to the accessory. If you send one of them, the corresponding value in the accessory will be changed and you will get success: true.

@TeslaOwnerTips
Copy link
Contributor Author

It the case. Capitalization documented vs actual.
Documented has the first character lowercase but actually needs to be upper case in the url sent.

So I first used the key name as provided in the document. The response was

{"success":true,"currentState":"","targetState":"0"}

I then changed the key capitalization to be
currentState and targetState and got back

{"success":true}

I think the documentation needs to change?

@benzman81
Copy link
Owner

Could you please post what url you call and what you want to achive and what is actually and expected behavior?
Just to make it better understandable for me :-)

@jsiegenthaler
Copy link
Contributor

@benzman81 I think this can be closed as the issue is addresses in #198

@benzman81
Copy link
Owner

Closed as suggested.

@benzman81 benzman81 closed this Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants