ewelink-api
ewelink-api copied to clipboard
skydiver
Thanks for the library
thanks for the library, have created a java one based on your logic
https://github.com/RealZimboGuy/ewelink-api-java
Any luck with getting websocket integrated @RealZimboGuy. I can’t figure out the login..
Yours doesn’t have websocket connection at present, didn’t know if you looked into it? I’m currently integrating into openhab and hate polling for states. Just can’t get the login to work on the websocket, just get an {error:406, sequence:1649374937395} response. Everything else is working fine. Pulling my hair out 😂 Have looked at this, alexit homeassistant, few .net ones and more.. everything seems to be right so sure I’m missing something silly
I had briefly looked into it but just opted for polling. i'll take another look into adding websockets and let you know. It didnt look too complex and if thats still the case i will do a new lib version.
-Julian
On Thu, 14 Jan 2021 at 01:22, Delid4ve [email protected] wrote:
Yours doesn’t have websocket connection at present, didn’t know if you looked into it? I’m currently integrating into openhab and hate polling for states. Just can’t get the login to work on the websocket, just get an {error:406, sequence:1649374937395} response. Everything else is working fine. Pulling my hair out 😂 Have looked at this, alexit homeassistant, few .net ones and more.. everything seems to be right so sure I’m missing something silly
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/skydiver/ewelink-api/issues/125#issuecomment-759821232, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADYYQWAHHJPSLJRRJ6SIQRLSZYTM3ANCNFSM4UMA4TSA .
It's easy enough and that's why I'm sure I'm missing something silly.
1: authenticate on api - ok 2: get ws server - ok 3: connect to websocket - ok 4: authenticate websocket - fail
Always a 406 error on sequence.
I've even tried the v2 api skydiver has published.
I'm wondering if it may be something to do with the jetty client I'm using within openhab (maven/eclipse).
I have done a release on my repo for support and handling of the websocket to ewelink. Also some extra stuff for handling socket drop/re-create. let me know if that helps.
When sonatype eventually indexes the jars
On Thu, 14 Jan 2021 at 10:50, Delid4ve [email protected] wrote:
I'm wondering if it may be something to do with the jetty client I'm using within openhab (maven/eclipse).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/skydiver/ewelink-api/issues/125#issuecomment-760030639, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADYYQWHYIWSJFKOWDPMK4X3SZ2V4XANCNFSM4UMA4TSA .
Cool I'll take a look tomorrow when I've got more time.
Spoke with alexIT, who made the Python integration for homeassistant. Knew it was something silly, websocket needed apikey not apiKey in the json 😩
Thanks tho as going to help a lot of people using openhab.
finally the maven repo is now public, seems issues at oss.sonatype yesterday trying to upload but this morning its all fine
On Thu, 14 Jan 2021 at 14:38, Delid4ve [email protected] wrote:
Cool I'll take a look tomorrow when I've got more time.
Spoke with alexIT, who made the Python integration for homeassistant. Knew it was something silly, websocket needed apikey not apiKey in the json 😩
Thanks tho as going to help a lot of people using openhab.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/skydiver/ewelink-api/issues/125#issuecomment-760170411, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADYYQWEVQ2OSHKVRN3IUW23SZ3QWFANCNFSM4UMA4TSA .
It's easy enough and that's why I'm sure I'm missing something silly.
1: authenticate on api - ok 2: get ws server - ok 3: connect to websocket - ok 4: authenticate websocket - fail
Always a 406 error on sequence.
I've even tried the v2 api skydiver has published.
Same issue. I had same issue. Debugging leaded me to conclusion that server in selected region ("us" by default) is on maintains. Changing target region (to "eu" in my case) resolved the issue.
