-
Notifications
You must be signed in to change notification settings - Fork 9
MQTT api changed #14
Comments
Hi.
but I can't connect with any MQTT client. |
Hi @tomeko12 https://api.eu.ocp.electrolux.one/appliance/api/v2/appliances?includeMetadata=false I hope this can help, but I'm not to skilled(not really at all) in programming take a lead on this. |
I can provide URLs and clear text requests and responds with both gigya.com and further with Electrolux-cloud |
I was fiddling with the new oneapp API in my fork. https://github.com/Woyken/pyelectroluxconnect/blob/main/src/pyelectroluxconnect/oneApp/apiClient.py They are using websockets now, it does work. And seems quite responsive. |
Hi. |
@tomeko12 thanks for your response. |
@Woyken , You should publish Your API, because I'm worry about that Electrolux will close access to ECP. Old mobile apps still working, but with message "This app is closing down". |
@tomeko12 I'll slowly chip at it whenever I have some spare time. Life got quite busy lately 😅 |
Hey guys, this is probably more of a question to @Woyken as I cannot create issues in your repository. |
I haven't tried keeping it connected for so long. |
I see. The WebSocket is very responsive. As far as I know now it's just for getting updates on the device's status.
|
I thought I might make sense to keep polling every few minutes until device is "online" then websocket. If websocket disconnects, reconnect, but also fetch current status, to make sure we have all the lastest states. Until it's offline. Then keep on polling and waiting for it to be online. I don't know if all devices from Electrolux are like mine but it take like 2 minutes to connect to wifi after I turn it on. Probably no point in trying to keep websocket alive for that long while the washing machine is offline for 14 hours or so (I have to send a ping command every few minutes to keep it alive) |
I agree with the states. Upon starting you should poll I have my appliances set up to stay connected all the time. I have checked the WS, when the device loses connection and I get these messages (timestamps are UTC):
I think it's less of an engineering effort to keep the WS connected than implementing a polling mechanism for data you'd get from the WS anyway on the side. Of all the API's I have reverse engineered that provide a WS, I try to keep it always open because it provides realtime data as opposed to polling with an interval (for instance when starting my car or network events). |
Electrolux Life app has stopped working, have to use Electrolux app now so the old API is no longer working. There are a couple of projects that have popped up for the Electrolux OCP API for reference. https://github.com/mafredri/electrolux-ocp |
Ciao @tomeko12 and @Woyken, |
ping (want to follow) |
I tried using
session.registerMQTT()
It doesn't work anymore
missing parameter for
utils.registerMQTT(region)
Also API returns probably changed structure than it used to:
POST https://api.eu.ecp.electrolux.com/user-appliance-reg/api/v1.1/devices
so it no longer contains
DeviceToken
Where did you find those APIs? Mobile app?
I decompiled Android apk
com.electrolux.oneapp.android.aeg
, but couldn't find any references toMQTT
The text was updated successfully, but these errors were encountered: