@KennyMoens I wonder why do I face temporary ban? I login with password, add the device and that’s all. Don’t have any issue during this process, other than what happens after that in the app (as shown before).
I removed the app now, will wait 24 hours and then try again. Do you perhaps want a new diagnostic report?
The Roborock Q7 and Q10 series are still a work-in-progress. Some functionality is available, but not all. I’m making progress on the cleaning routines, and you can expect a major bump in support for Q7 series later tonight.
Remember: local connectivity is not available for Q7 and Q10 series. These robots don’t offer this, so we cannot support it at all.
What has changed? This release mainly features drastic improvements in the support of Q7 series devices. In short the following functionalities are available now:
Status of the robot: is it cleaning? is it charging? ..?
Starting global, room-based, zone-based and spot-cleaning
Pausing cleaning operations
Resuming cleaning operations
Known shortcomings:
Room-based cleaning does not allow you to select the rooms yet, neither does it allow you to resolve the names of the rooms. You can trigger it, but you have to guess the index numbers of the rooms.
Zone-based cleaning should work, but the coördinates are different from in the older robots. What I see in the tracing is values around 1.0, 2.0 etc. So you might need to experiment with it if you want to use this.
I have a little delay on the status change from docked to cleaning, and cleaning to docked around 1-2 min in the lastest versions. Is that something that can be fixed?
Any chance for you to implant support for the Roborock zeo one washing machine? I see people have got it to work with HA, but I have not figured it out.
I would need to investigate that, unsure about why it is slower now. Which device do you have?
Related to the zeo one, I plan to support it, but as I don’t own one (and don’t plan to buy one) it is hard to develop support for it.
If you are willing to help out in this, I believe there was someone in this topic in the past too, I can dig deeper into it. What I would need is: what do you expect from the integration and are you willing to share the device (temporary) with my development account.
That I understand, yeh should be cool if you can dig deeper I don’t now for sure what is possible with the integration, some status? When it is on and off so you can build flows around it?
Is it possible to help you out and sharing the device then I think it is not a problem, but what is that mean exactly? Can you remote the machine? My wife will kill me haha, need to explain to her
Sharing the device allows me to effectively control the device yes, although you can be sure that I won’t abuse it.
I think if we go for status only first, the most important thing is observing what happens, and how the communication is structured, and being able to test if the status reports correctly.
I’ll share my dev account via PM with you, if you can convince your wife
GOT my q7 to work with the test app , but today it is not working in homey ( no updates) so tried to log in again and it said I needed two factor log in. Maybe I am troen out for pulling to many times ? Hmm
I fear your are blocked, based on the message you cannot sign in for 7 days. I would wait those 7 days, and then try again. I have not seen this yet though.
If you go to the settings of the robot in Homey (rightclick in the webui, hold in the app), you can disable the local connectivity for the robot. Be aware that there is currently a bug in there that it requires - after disabling - a restart of the application.
I just got the “need two step validate” error also on my local dev account. The trick here is to use authenticate with “email token” instaed of “password”.
I have to investigate further, but I do think password login might be broken for all at this moment.