I got tired of Fibaro LUA and all the errors I got and so I used plain and simple Powershell script with Invoke-webrequest to confirm that I am going at it correctly and in it, the commands works, but I still don’t see the data - but as you don’t either, it really seams as API change…
Now I need to figure out why the LUA web request does not work and that will be fun…
I really like Electrolux purifier as its probably the most silent one I ever encountered, but I am also not happy about manufacturers claiming to have smart devices as long as they have some app without any automatization and API…
It does indeed work, but I have had some reports of people having trouble with adding devices on new accounts or newly purchased ones. I am starting to suspect there may be multiple versions of their cloud API out there. I only own the A9 from the original launch of the product so I haven’t been able to verify this.
If anyone who owns a newer device and/or account and has some time to run the app in debug mode we could try to dive into if any of the APIs have changed. They actually promised a public API long ago but I haven’t seen it materialize.
Hopefully the manufacturers will embrace Matter and that will be the end of these horrible proprietary cloud apps, but I wouldn’t bet on it
Thank you for your reply. I bought my device in 2019, but only recently discovered your app. I have no prior experience in running an app in debug mode unfortunately.
I see a lot of error reports from the last couple of weeks indicating network/connectivity issues. I wonder if the API endpoints are not that stable? Adding a simple retry/backoff logic to some of the calls might improve stability. I’ll think about it. Ideas are always welcome
New version is published that might improve reliability with newer A9 devices. It seems the newer devices do not have the luminance meter that older devices had. This could trigger errors in the caps update logic. Those of you that had issues with the A9 device sometimes stopped working, please check if version 0.1.7 is more stable.
I received the report, thank you. It seems there is a compatibility issue when logging in to your account, possibly the API was updated. I am however able to log in using my own account so it may be that this depends on the account itself. Some more digging is needed I think
For some reason the authentication is failing. This occured few weeks ago. I restarted the app and Homey but that didn’t help. Finally I removed the A9 and trying to add it again. I get constantly timeout error. Electrolux’s own app is working so this should not be an network issue. Is anyone else getting these symptons when trying to use A9 through Homey?
My native Electrolux Wellbeing app is communicating with https://api.eu.ocp.electrolux.one/ and seems to have being doing so for the past year. It will probably take some work to get this app working again. I will try to help out but no promises.
OK, thank you. I was planning to add airquality meter to my system to run the air purifier according to it’s readings. But wait and see. Electrolux is quite annoying since their air conditioners are controlled by different app than the air purifier. But I will wait to see if this can be fixed. Otherwise it is really nice app, the readings what the device gives through Homey app are fantastic.
