-
Notifications
You must be signed in to change notification settings - Fork 108
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
invalid json response body #116
Comments
I add this code to mixins/makeRequest.js after line 42, because the API ramdomly answer with a crazy html shop code. Maybe is a bad solution but works for me.
|
Ok thanks I will test it! |
Work Great! |
I’m very happy it work!! Maybe the fix must be included in the oficial code. How? |
I'm writing here because I think my problem could fit in here. I have the following error: "FetchError: invalid json response body at https://eu-api.coolkit.cc:8080/api/user/login reason: Unexpected token < in JSON at position 0" I have Node-Red running via IOBroker. Unfortunately, I can only get about 6 power state nodes online. So when I try to use 20 nodes from ewelink, only about 6 remain online. The rest are offline, with the error message I inserted above. It is also not clear which are online and offline, this changes after small changes and a deploy. There are no wrong settings and all hardware devices are actually reachable. I can't find this file. I am using FileZilla and have searched the entire Pi. Can anyone help me? Where and what I need to change. Thanks a lot |
I get this error some times when use getDevicePowerState
g: FetchError: invalid json response body at https://eu-api.coolkit.cc:8080/api/user/device/status?deviceid=10007df37d&appid=YzfeftUVcZ6twZw1OoVKPRFYTrGEg01Q&nonce=uf1lhtn&ts=1604043174&version=8¶ms=switch%7Cswitches reason: Unexpected token < in JSON at position 0
at /usr/src/node/node_modules/ewelink-api/node_modules/node-fetch/lib/index.js:272:32
Thanks!
The text was updated successfully, but these errors were encountered: