Hey @Erlend_Hansen,
You are probably right, I’ve created issue 67 to keep track of this.
Kind regards,
Hi there,
Awesome app, I’m using it a lot!
In the past weeks I experience a hit and miss with the “starts to clean” and “finished cleaning” IF-cards on the Roborock S7 max ultra. I got my curtains attached, so if it starts cleaning, the curtains open so it can reach the edges of my room. Vice versa for finished cleaning.
Sometimes they immediately open, but often they are delayed for 3 or 4 minutes or never open. As it should be changing a variable as first “then” step, which doesn’t take place, I can see these cards are not triggered.
Restarting the Roborock cloud app fixes the problem once. The flow has been working flawlessly in the past..
Any advice? Thanks!
Hey Kenny,
Here’s the code. I hope that helps!
a0c5e6de-b646-4e50-be3b-d3d49b602e98
Hey,
It can be a connectivity issue between Homey and the robot.
Could you send me a diagnostics report after the issue appeared, I’ll look into it.
Kind regards,
Hey guys,
I’ve just pushed v2.8.0 towards test, this version includes a few changes:
- A fix for issue 67, related to the resuming of the cleaning.
- A fix for issue 65, to automatically perform a switch using custom mode if you come from the smart mode to any other mode.
- Further improvements to the initial experiments with the B01 protocol, based on the work from the guys from Python Roborock.
People who have a device which works on the B01 protocol are encouraged to try this version and submit a diagnostics report. The previous implementation did not gave my any responses from Roborock, I hope that this version will do, but I did not test it.
It will not work for you though, I just log the responses, in hope that I get the requests which I send out correct already.
Thanks,
9816e50d-9908-4d1a-b638-3e040dfbb627
Hey @R.S_Kok ,
The app did not send the synchronisation request. Could you try again by submitted a diagnostics report after +/- 10 minutes?
Thanks,
Hello guys,
Exteremely good news today !
After digging for weeks on how to get the L01 encryption (i.e. the new local connectivity) working, we finally managed it. The encryption / decryption works correctly now.
I’m bring out v2.9.0 which includes this encryption/decryption as a test version. At first sight it looked like the contents of the local messages was the same, so I suspect that everything should work correctly.
Therefore, everyone who disabled the local connectivity, please give it a shot. Enable the local connectivity again with v2.9.0, you might need to restart the app though, and let’s see if it works.
If things don’t work, don’t hesisitate to submit a diagnostics report!
Kind regards,
3 Likes
e763884e-3a13-4e52-a882-02868d24c393
Hey @R.S_Kok ,
One step further, the initialization of the device failed. I fixed this, with v2.9.1, let’s see what that one gives.
Thanks,
fdc3cdb9-1df6-4263-8ba9-81456a03fde6 
Thanks again @R.S_Kok , seems there was another sync call which caused the initialisation to fail for B01 devices. Let’s try with v2.9.2
c3315ae8-3616-4697-a49e-afa03b60a364
22:34 : 6f570598-51cc-4438-8d3c-c1a9aabd46f5
Just sent you a DM. Many thanks!
@Kenny since the latest update (test version, 2.9.3) the “finished cleaning’“ trigger is set accidently. For example, when the robot goes back to it’s dock for a mop wash, it triggers the flag. This causes issues when using it to re-enable the alarm as it will continue to clean after and trip the alarm.
21df7e3b-1971-438e-8b22-45033893c9e1
I’m not a developer. 
Gr. Kenny
1 Like
2ebc302e-3f56-44bb-ae5a-94efaef5bee4
Not sure if I did it correctly last time, but here’s a new Diagnostic Report @KennyMoens
Thanks a mil..
Hello guys,
v2.9.4 is coming to test now. This version should fix the issue of the finished cleaning trigger not working properly.
@gioglifx, your diagnostics reports shows connectivity errors with the cloud api. I suggest to try repairing the device.
Kind regards,
1 Like
Hey Kenny,
Thank you for your reply. This is what shows when I try to repair it:
Error: The expression evaluated to a falsy value: (0, node_assert_1.default)(this.contexts.has(username))
Hello,
@gioglifx , you found a bug in the app. This should be resolved with v2.9.5.
Furthermore the v2.9.5 should include another fix for the L01 protocol… hope it starts working soon.
Kind regards,
