[APP][Pro] Roborock Cloud - Intelligent robot vacuum cleaners

Apps
,
552

Hey,

@Steven_Mollema

It seems you get regular disconnections similar as with @R.S_Kok, could you try if disabling the local connectivity helps with you?

@R.S_Kok

Could you enable the local connecitivty again, restart the app and send me a diagnostics report? Give it +/- 30-60 after the restart.

Thanks,

553

b27bece1-1897-45d7-860d-558394b8341a

Yes, itā€™s now solved. Even when I re-enable the local connection, everything stays stable. Thanks! I had already restarted the app, but hadnā€™t tried this yet.

The only thing still off is that Homey says the dust bag is full, while the Roborock itself doesnā€™t show that. If I can help you with that later on, just let me know.

554

Hey,

Does your Roborock app give any other error codes?

The status updates contain two error fields: error_code and dock_error_status.

In your case, based on the diagnostics report, they have the value:

"error_code": 0,
"dock_error_status": 34

The robot has no problems, as the error code is 0 for the robot. The dock however reports a problem, basically error code 34 which corresponds to duct_blockage which I map in the Homey app towards ā€œdust bin fullā€.

Kind regards,

555

Youā€™re right the dock was actually blocked.

1000035919
10000359191220Ɨ646 120 KB

I got confused because the app said the dust bag was full, but I had just replaced it. And since it happened around the same time as the update, I assumed it was related.

My bad :sweat_smile: Thanks for your help!

556

c89464e0-9893-464a-ad61-e0306e470205

557

Hey @R.S_Kok ,

I see the problem, Iā€™ll try to work on a patch for that later on. For now the workaround is to keep local connectivity disabled.

Note: this only applies to users of the Q10 series where the robot does not have local connectivity anymore.

Kind regards,

558

Hey,

Iā€™ve pushed v2.13.2 towards test, this should fix the issue.

Mvg,

2 Likes
559

Since first of Nov I dont get a stable connection to my S7 MaxV. cd06a193-c0d0-4c0f-9f70-fc77b60b4ef1

Tried so far: with/without local connection, static IP, Refresh period, reinstalled app, restarted app. Repaired many times but no luck. Before it was working great. App was/is amazing.

560

Hey @Moritz_Stosslein,

The diagnostics report doesnā€™t make me wiser in your case. Can you restart the application, wait 2-3 minutes and send me a new diagnostics report?

Thanks,

561

Hey @Moritz_Stosslein

Thanks for the updated report, sadly it was not enough yet, I still see nothing occuring. Basically any messages which I expect to be there, are not there, which indicates your problem, but there are also no errors, which makes it hard for me to help you out.

Could you restart the app, and submit a report at some different intervals? Letā€™s start with immediately after the restart, 30 seconds later and 2 minutes or something like that.

The reason why Iā€™m asking this, is that Homey does not provide me the full application log since the start of the app, i just get the latest X messages which makes it difficult to find out in several cases.

Thanks!

562

Hi,

thanks so much for your help. Will do one time at 30s, one at around 2min and then i do one 30min in.

Iā€˜m new to Homey and somewhat shocked I cant seem to get any decent systemlogs for debugging.

Edit: Funnily enought right now it randomly works again.

563

Hello guys,

Iā€™ve just pushed v2.14.0 towards test, will land on stable soon too.

This version brings:

  • A number of internal crashes, which you guys probably didnā€™t notice, but which spammed my mailbox :slight_smile:
  • A fix for the connectivity flipping for devices which donā€™t support local connectivity
  • A first and extremely basic support for the Q7 series. Basically you can see the last cleaning time, last cleaning area and battery state. Other parts are not yet included, I hope to add more during the coming days/weeks.

Enjoy!

564

Sorry for the late respons.

That would great, please let me know if you need anything from me?

Kind regards

565

Hi, thank you so much for the Roborock app. My Roborock S6 MaxV has been running flawlessly since you dropped the app :+1:t2:

Now Iā€™ve got a Q10 S5. All I really need is the start and return-to-charging-station functions. Unfortunately, this only works immediately after adding the vacuum or after restarting the app. The workaround with ā€œflowā€ (restarting the app + waiting 20 seconds) does work, but unfortunately not always. Is this a known issue? Do you need any further information?

Q10 S5

roborock.vacuum.ss07

Firmwareversion: 03.10.19

App-Version: 4.53.08

Plug-in-Version: 10065

800a2c6b-8119-44be-8b17-136facfd6ed4

566

Hey @ManuelKugler,

The support for the Q10 series is still preliminary and probably not fully working yet.

Could you submit me a diagnostics report where you tried to start the robot, but that it did not do it? I donā€™t get that info from your current report.

THanks,

1 Like
567

Hi, I tried to start it and then generated the report:

8c22412e-0d3b-4ae5-a883-82116bcb4ac7

568

Here I restart the app, followed by a successful start of the Q10.

612d256f-0059-47f5-80d5-ec58d2fcbd74

569

Hey @ManuelKugler

What I see that we get a connection failure on the MQTT, Iā€™ve seen this in the past too. The MQTT connection is far from stable, therefore I implemented the local connectivity which is much more stable.

Sadly speaking the newer robots (Q7 / Q10 series) donā€™t have local connectivity anymore as far as we know.

Iā€™ll see if I can add some further optimisations on the connectivity.

Kind regards,

1 Like
570

Hey guys,

v2.15.0 is now available for test using Roborock Cloud | Homey

This version hopefully brings improvements to connectivity, it also includes some internal refactorings in order to support the Q7 series better.

571

I have a Q7 TF model sc05.

Having issues. Canā€™t communicate at all with it after onboarding it. Testing 2.16.0.

Let me know if I can help. Iā€™m a bit new to this, but happy to help. Iā€™m also a developer. But different language