-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
H-WASHER 500 - Error while trying to get /commands/v1/retrieve #1
Comments
Hi, for my washing machine, it returns a {
"payload": {
"applianceModel": ...
"resultCode": "0",
"settings": ...
"pauseProgram": ...
"resumeProgram": ...
"stopProgram": ...
"startProgram": ...
"options": ...
"dictionaryId": 150
},
"authInfo": {}
} But I have no idea what your error message means, maybe the app works different for your machine and retrieving commands works in another way. But maybe it's just a missing parameter. Unfortunately, I can't help you to debug this, the api only allows to request information about personal registered models. I think you need to study the communication between the app and the hOn servers. I used a MITM proxy (HTTP Toolkit), but it's a bit complicated to setup, you need a rooted phone. Let me know if you have any questions about this 🙂 |
I'll try to intercept the requests and get back to you as soon as I get more info. Thanks |
Hello, I created the PR #2 for fixing this issue as I tested locally. Hope you can accept it and release the library version |
Hi, awesome! Thanks for your contribution 😃 |
I was trying to use the HA addon with my washing machine (HDQ 496AMBS/1-S). However it did not work. While I was trying to debug, I downloaded this library code and found that the following call is not working.
GET /commands/v1/retrieve
The Result is:
I tried and successfully replicated the error with Postman. However, even if I add a param named dictionaryId from my appliance info, it still not work properly.
This is my GET /commands/v1/appliance call
Any ideas how to debug or fix this issue?
The text was updated successfully, but these errors were encountered: