BTW: Would it be possible to get the Device Name as a Variable / Tag. I have two Roborocks on different floors and would like to use the same flow based on what vacum that is triggering it. I use the name to log.
Hi.
I think Iâve found an error - I have two Roborocks. A Qrevo Edge and a Saros 10 in my homey, and after I added the Saros 10, I canât show the map from the Qrevo Edge. The Whenâs are working, but I send myself a message with the map after cleaning and after adding the Saros - I canât find the MAP of the Edge.
Hey @Jens.Hummelmose,
Iâve added issue #59 to add the device name as a tag.
For your other question, does the map still appear if you go to the device itself? To be honest I have not exprimented with that area yet so it can be there are bugs there 
Kind regards,
Hey there.
The answer to your question is No - The camera icon representing the map is gone from the Edge. And thanks for your great work.
Hey @Jens.Hummelmose ,
Could you restart the app, wait 1 minuten and send a diagnostics report?
Thanks!
Done 
LOL - Damn it - After restarting the app - Both vacums has map.
Why didnât I think of that.
@KennyMoens since the last stable update the cleaning doesnât work properly anymore, canât turn off the mop when I only want a vacuum. It looks like setting the suction power overrides the mop turned off. It worked with 2 seconds between each step before, but now even with 3 or more seconds it doesnât work. When I open the roborock app at the same time I see with the card âmop turned offâ that it changes to vacuum, but when the suction power is selected in the next card or the room is selected, it changes in the roborock app back to mop&vavuum. So it looks like just the latest flowcard is ârememberedâ and it overrides the settings before.
Also the connection is getting lost often when testing the stuff, maybe you can see something in the diagnostics
952c7df5-bcb3-41b0-8af3-e908be9f7ed9
Hey @Arjank95 ,
The diagnostics report is empty somehow.
Could you try restarting the app and see what it gives?
Are you using the local connection or the remote connection? I.e. did you enter the IP address in the settings (the next version will switch to local connection automatically).
Kind regards,
Ah it was connected by IP address, but now I see that after the last update the IP address field is empty. Maybe that made the connection unstable now! Filled back in the IP address, Iâll check some things out if it works again when back home! 
Hmm @KennyMoens filled in IP address again, tested the vacuum flows twice and it looked like everything is working again. But directly after that the robot is losing connection again, made a diagnostic report after that. I did the same yesterday so hopefully itâs not empty again and you can see why itâs losing connection (and the diagnostic report isnât directly wiped when the robot is losing connection)
e61e21a0-85b4-4e96-8064-6e9e1351bf1f
Hello all,
Iâve released v1.1.0 towards test. This release includes the following changes:
- Support of login by code, this will allow users which used the Google Authentication (or similar methods) to use the app without switching to a password authentication
- Support of the A01 protocol, I honestly donât know which devices use this, but I noted a number of crash reports related to it.
- Auto-Detection of the local IP address of the devices, so that the device will always switch to local connection when possible. If the connection fails, the app will fallback to cloud messages.
- A potential bugfix for older Homey devices where the robot is not rendering.
- A bugfix for some randrom crash report I saw popping up in the developer tools.
@Arjank95
Honestly I donât directly know what is going wrong with you⌠The diagnostic report is empty again, which makes it terribly hard to detect what is going on.
Could you maybe try submitting one after the restart of the app? And then maybe one 10 minutes later? And finally again when it stops working?
2 Likes
Hello all,
v1.1.0 is in the meantime published towards stable.
v1.2.0 is now published to test, it includes two changes related to the map:
- The map is now cropped towards the extends of it.
- The map can now be rotated by an option on the device.
Iâve investigated if it was possible to submit a tag/token with the trigger flows with the device name, sadly Iâm not able to do that easily, since the trigger flows which are available with the app are generated by Homey itself, I donât have control over them. The only way to implement such a feature is by implementing the flows myself.
Kind regards,
2 Likes
Awesome rotating of map! Love it. Suddenly youâre able to see the details.
I still have hallenge that the map does not update even after several hours of changing the location.
The update interval is one minute.
Hey @Paal_Aamaas
Could you describe exactly when the map does not update?
I programmed it that it only updates during initial startup and during a cleaning operation. Maybe I need to expand it to other operations too.
Kind regards,
I thought it would update when I changed the location with a flow and at least at the update interval or when I hit reload. So I guess I misunderstood.
Not a problem if it updates when it starts cleaning, just to get an understanding if I have a fault or not. Let me test tonight to see if your logic works as intended. Naturally you would start a cleaning very soon after moving it.
How can i see this nice map on my homey dash or somewhere else? I have the same robot.
Hey @marcel_ridder,
There is no support for widgets yet. This might be added in the future, but I first want to finish up a few other parts.
KInd regards,
1 Like
Use the camera widget and the flows or sensors.
I have something really strange with the âpoestâ card.
The flow i have starts when i push a virtual button â that sets a var and cleaning options â start to clean room x x times.
When i click the virtual button, the flow runs until the end but the cleaning isnât starting.
No errors appearâŚ
When i click in the advanced flow on test, then the flow runs until the end and the cleaning is starting.
Itâs strange behavior, can someone explain maybe?
This might be caused by some unsupported setting or similar on your robot.
You can try running the flow and sending a diagnostics report, that might give me some clues to help you out.
Kind regards,
