Yes, stable version would be priority. And its a Saros 10R (forgot the R) nNot sure if the 10 also has this possibility
Hello guys,
Iāve just pushed v2.0.1 towards test, this version is a major refactoring of the application itself.
DISCLAIMER : This version is really what it says, a test version. It can and will be unstable! Use at your own risk!
What has happened?
- Iāve separated the app logic from the Roborock connection logic. The Roborock connection logic lives now in its own NPM package, so that it can be used in other NodeJS projects too.
- Iāve added a whole bunch of automated tests against the Roborock connection logic.
- Iāve done several improvements for memory usage, but not everything is optimized yet.
No features or functionality changes occured. This is purely a rewrite of internal logic to make it easier for me to expand the features in the past and optimize on the memory use.
Sadly speaking, the biggest memory consumer - the map - still consumes a lot of memory based on my tests. I suspect this is due to the case that Iām using a pure-Javascript library for image processing (Jimp), and Iām guessing that this one is consuming the memory a lot.
Iām still thinking what I can do to improve it, maybe swap out the library and look for others, or do the rendering of the map in a remote process (outside of Homey).
For now, the map is disabled by default, this gives the most stable solution for everyone. People who donāt experience troubles with the map can have it enabled, e.g. myself never had issues, maybe because I have less apps on my Homey as others, or maybe because the Homey Pro 2023 has more memory, I honestly donāt know.
The test version has a known issue, which Iām still investigating. Basically, sometimes it looses its connection and the only solution is to restart the app. Iāve done some improvements already, but I cannot do more debugging without publishing it towards test. This is because I cannot make a diagnostics report if I install it locallyā¦ (at least not that I know of).
Kind regards,
2 Likes
Hi Kenny, thanks for the great app.
For info, the testversion logged me out from my Roborock S6, and I could not log in again (timed out on login screen) but when i reverted to the official version (1.31) I could log in again.
So the new login version did not work for me (email login).
Hi,
Hereās an update on the situation on my end after installing the new update.
First of all, thank you for an amazing app ā itās been long-awaited and has worked flawlessly until now. Iāve been very happy with it and everything has worked 100%.
After installing the update yesterday, everything crashed. The Roborock app in Homey immediately crashed and keeps restarting continuously. Both of my robot vacuums also lost connection with the official Roborock app, showing a āData Acquisition Failureā error.
I had to reset the Wi-Fi on both vacuums to regain access in the Roborock app. I then installed Roborock Cloud v1.3.1, but both vacuums were very unstableāconstantly glitching in and out with repeated connection errors.
When I reinstalled the test version, things initially seemed stable. However, after a short while, the app in Homey crashed again, and once more Iāve lost connection with the Roborock app due to āData Acquisition Failure.ā
I have exactly the same problem. Have deactivated the Roborock app in homey for now.
Hey guys,
As said this version is very experimentalā¦ You can use the 1.3.1 version.
Kind regards
I reverted back to 1.3.1, but as mentioned itās very glitchy. Same as Jan-Thomas experienced
It seems I am facing the same issues, I will dig deeper the next days.
2 Likes
My Saros 10 stopped working within the app. At the beginning, a few months ago, it used to show the map and everything, but now it says request fails every time. I tried to repair, but it asks you for a password I donāt have because my account with Roborock goes through Google, and there is no option to add the token when repairing. So, I deleted the device and added it again to no avail. I am looking forward to support you if it worksā¦Thanks in advance!
Hey @djvagnetti
Did you submit a diagnostics report already? If not, please do so.
Kind regards
Kenny
Hi Kenny, I also got a very glichty behavior when reverting back to 1.3.1.
But I restarted the app in Homey and then logged in again via the maintenance/repair function in the same app (or vice versa, canāt remember), and now the 1.3.1 version seems to work again.
Try restart the app and go to maintenance - repair and log in again, that worked for me
Hi Kenny,
The app was working perfectly, but now Iām getting a timeout message and canāt use the Roborock anymore. I have the Saros 10 R&D. Iāll submit a diagnostics report.
I also tried all the usual steps first ā repairing, removing, reinstalling, etc.
Same here now. Only timeout. Have tried to repair, without luck. Same with V 1.3.1 and 2.1.0.
2.0.1 was a bit challenging. Continuous restart and crash. 2.1 is stable and good. The placement of the robot on the map is a bit off though, but anyways fantastic app!
Hey guys,
@Thomas_Reiten, the timeout on the settings page is something I need to dig deeper in. However it should not block the changes going through, certainly in v2.1.0.
Can you try to set āAllow Local Connectivityā to false? This helped with Dennis in v2.1.0 to resolve the issues.
@Paal_Aamaas
Thatās strange, Iāll look deeper into that 
1 Like
Hi. Yesterday i deleted, and reinstalled both the app and vacuum. I now have v1.3.1, and everything works fine again. 
Hi @KennyMoens since today? the vacuumcleaner doesnāt start anymore.
From the flows all the commands are coming trough, I can hear the pling sounds, but the last command āpoets ā¦ā doesnāt start the vacuumcleaner. See the flow below for example. This and all my flows like these were working for the last months. Restart of the app doesnāt work.
Any idea what causes the trouble? I can see the official Roborock app is updated, maybe that causes a problem?
Hey @Arjank95
Not directly, maybe a diagnostics report can help me to figure it out though.
Kind regards,
@KennyMoens Just started a flow to clean the kitchen. Vacuum cleaner didnāt start, directly made a diagnostic report:
96438c85-3120-45ec-899b-2f48d270b438
