ewelink-api
ewelink-api copied to clipboard
skydiver
Can we have other APIs like register user, add wifi to device type?
Hello @BeepLoveKarki
I never saw any existing code or info for these functionalities, so i think some reverse engineering must be done on the app.
Will be great if someone has time and energy to make this research.
@BeepLoveKarki just wait for me to do it and then @skydiver will nicely copy-paste it ;) without adding any credits....
@skydiver Hi man, i'm on inspecting eWeLink-app i successfully Pair the devices with WIFI but i need your help for registering the device to SONOFF servers for example at: as-disp.coolkit.cc after the Pairing success i have payload for sending to register device but i need to send action to SONOFF Hardware via SOCKET action looks like this: 'register' same as other actions like 'update' and the URL looks like this: wss://as-disp.coolkit.cc:443 we don't need any SSL for this because it's on SONOFF servers not in our localServer so how can we done this via SOCKET? as i saw in your library supports Listening-events not Sending-events!
Thank you.
@skydiver Hi man, i'm on inspecting eWeLink-app i successfully Pair the devices with WIFI but i need your help for registering the device to SONOFF servers for example at: as-disp.coolkit.cc after the Pairing success i have payload for sending to register device but i need to send action to SONOFF Hardware via SOCKET action looks like this: 'register' same as other actions like 'update' and the URL looks like this: wss://as-disp.coolkit.cc:443 we don't need any SSL for this because it's on SONOFF servers not in our localServer so how can we done this via SOCKET?
We'd need a complete replacement for the sonoff server for registration process.
as i saw in your library supports Listening-events not Sending-events!
The listener is getting the events from the sonoff server not the local devices.
the ZeroConf stuff being added will allow local control after the devices are registered.
