PLEASE NOTICE: The latest update 1.5.2 requires you to re-add your device!! This is a one-time issue.
Seams that when you re-add a S6MaxV in 1.5.3 it shows up as S7 instead in homey after connect. Tried two times becuase i thought i clicked the wrong modelā¦ 
Thanks for reporting! Thatās an easy fix, I can name device whatever I want after adding Guess I added the wrong name in the wrong page. I will edit this!
1 Like
PLEASE NOTICE: The latest update 1.5.3 requires you to re-add your device!! This is a one-time issue.
1 Like
And donāt forget to copy your token before removing the device (so you donāt have to find the token again, itās already in the āoldā device settings 
3 Likes
hello everyone, sorry to bother you with a simple problem. I just heard about this app today and Iām super happy. But when I put the IP address and the token, it says āCould not connect to device, handshake timeoutā. Unable to connect. I have the S6 Pure model. Thanks for your help.
Good morning! Useally the handshake error shows up because of problems with the token. I encountered this error in the very beginning also.
Make sure that you reset wifi soo the ip settings are totally reset (itās also disconnected from the app), re-add the device and then search for your (new) token. This should work!
In addition to the advice of @justin: has the vacuum cleaner a static IP-adress? I experienced that without a static IP-adress the vacuum cleaner switched periodically between two IP-addresses.
Regards,
Paul
Thatās something that your router is doing. Itās probably setup as āshort lease periodā.
My advice would be to disable this. I do not advice to use static IP adresses since this might conflict in the future, but using the lease period isnāt convienent for Homeys apps!
Edit: using static adresses is always a discussion between ITāers. Yes, itās a solution for stuff like this, but it might conflict when youāre adding something else with the same IP. Using DHCP takes care of that.
There might be an issue when the complete network is resetted, but that wonāt happen very often.
By the way @Homykit, did you manage to succeed?
Same for me - S6 is added as S7 in 1.5.3ā¦
@Justin FYI, thank you.
Static vs DHCP will always be a discussion, and there is even a 3rd way, which is probably the best of both worlds, DHCP with reservation, that way a device will always get the same IP, but the DHCP server knows this address is taken and wonāt give it to any other device
1 Like
Thank you. I will take care of this in the next hotfix.
1 Like
The naming issue is solved in test and will be published soon. Iāve already asked for a release.
3 Likes
@Justin may I ask you - is the Flow āRooms have changedā supposed to be working for S6 ? Itās unfortunately not working for me and yes, I have re-added related Roborock devices.
Diag. log if you see there anything : 0798d972-f7ec-40b0-ba12-126c63df5424
Have you also splitted the rooms in the official Xiaomi app? And gave every room a name? If yes, your log shows a unresolved errorā¦ Please try to make a small change in your map and wait for the flow to trigger, see if something happens.
1 Like
Good hint! Thank you - it was necessary to name the rooms
Iāve another question about the app. Is there a way to send the roborock (s5max) to multiple zone cleaning targets in one flow. I 've used this flow to make a cross pattern while mopping.
No itās not possible within the firmware.
A workaround might be using a logic numeric value, when starting zone 1 set it to 1, when status changes and logic is set to 1; start zone 2ā¦ etcetera.
The only problem might be that polling interval kicks in when the vacuum is already back on the dock, and starts from there.
Thanks for your answer.
Iāll use my old app for mopping the floor. If the polling takes to long, homey will think the room is finished (when my roborock has returned to the dock a room is finished).
