Hey guys,
v1.0.0 is published to test, and submitted for a stable version too.
@Radim_Kupcak, this should be included in v1.0.0.
@Fishflu, this should also be included in v1.0.0.
Enjoy!
Hey guys,
v1.0.0 is published to test, and submitted for a stable version too.
@Radim_Kupcak, this should be included in v1.0.0.
@Fishflu, this should also be included in v1.0.0.
Enjoy!
Hi @KennyMoens ,
thanks again for this gift.
I noticed that since the last version and even with this new one, the map is no more available for me, a black screen is displayed instead
I came here looking for easy way to turn roborock on with homey, i got one of best apps for homey with new functionality every week. Kudos for developers, you are true heroes of this community.
Roborock Qrevo S - all new features from v1.0 are working properly.
Hey guys,
@Moussa_BA
Thatās strange. Could you restart the app and submit a diagnostics report?
@Konrad_Kuczynski
Thanks! But donāt get your hopes up too high, I wonāt be able to keep adding new features ![]()
Additionally, is there someone in the forum we tried to add a device, succeeded with it, but as soon as it was added didnāt get any data at all?
Iāve seen in the automated crash reports of Homey that someone attempted to use protocol version A01, which I assumed was related Roborock Dyad Series (not the robot vacuums). If that person is on the forum, please reach out, Iām interested in which device you are using and seeing if it is feasible to support it. If it is the Dyad series, it will probably be as another device though, but it is possible in the app (I think).
Kind regards,
Hi @KennyMoens ,
Now the icon is no more available, very strange indeed.
Find below the diagnostic code:
f0c0d841-79f0-452a-a695-a91bcac0a40c
Regards
@KennyMoens map doesnāt work here either, I wasnāt test user so the map functionality just arrived for me with the 1.0 update, and it didnāt work from the beginning. Keeps refreshing. Restart of the app doesnāt help.
Diagnostic report:
aeb21608-8a35-4010-9e44-400484445e54
Hello guys,
@Arjank95, in your scenario I see this in the diagnostics report:
36m[2025-03-06T07:06:36.065] [DEBUG] RoborockMqttClient - e[39msending message 101/get_map_v1/true to 6ob7EJARSK5q6i3zcBixUh with id 22100
e[36m[2025-03-06T07:06:36.172] [DEBUG] RoborockApi - e[39mignoring protocol 102 response for 22100
e[36m[2025-03-06T07:06:36.320] [DEBUG] RoborockApi - e[39mreceived map message with id 22100
e[91m[2025-03-06T07:06:41.720] [ERROR] RoborockDeviceWorker - e[39mfailed to perform a sync operation: ReferenceError: fetch is not defined
Based on what I see in the code, the map is correctly retrieved, but then it fails somehow, I cannot pinpoint yet where it does though. Iāll investigate later today, maybe not with a direct solution, but at least with more debugging to try to figure out what is going wrong.
@Moussa_BA, in your case I donāt see any data coming in. Could you retry it, but wait a bit longer before you create the daignostics report? Letās say 1 minute?
Thanks!
Ok, here we go
e0f2bbf3-551b-48e5-9817-a4b5df40f4a3
Regards,
Moussa
Hey @Moussa_BA, @Arjank95
Good(?) news, I see the same in your diagnostics report as in the one of @Arjank95. The bad news though is that I donāt know what is happening.
Iāve pushed v1.0.1 towards test, this version will most likely not fix the problem, but will give me more debugging information.
Can you guys install this test version, and submit me a diagnostics report again?
Thanks!
Did what you asked, still not working indeed, but great that youāre diving into it!
99bfcbd8-1a37-4db8-81a3-e8271dab3399
@KennyMoens updated the report
Could you resubmit one? I think you submitted it too fast after the restart of the app.
Thanks,
Hi,
Submitted this one
85b40888-9616-4602-979b-40354a853237.
Thanks very much for the support
Hey guys,
Iāve pushed v1.0.2 to test.
This release should include the following fixes:
Enjoy.
Hi @KennyMoens,
First of all, I want to sincerely thank you for all the hard work you put into this appāI really appreciate it! Everything is working perfectly for me with my Roborock Q8.
I just have a few feature requests that you might consider for future updates if possible:
Would it be possible to add a setting to rotate the map?
Could there be an option to create zone cleaning buttons directly within the device, maybe through settings and coordinates?
Are you planning to develop a widget for the Homey dashboard in the future? It would be great if it also included the option to upload a custom vacuum image, similar to how Roborockās Android widgets work.
Thanks again for all your efforts!
@KennyMoens thanks for the effort youāve putting in again. It shows the map now of the last cleaning routine! Like youāve said: not the location of the robot, but thatās not the most important thing for me.
Hi @KennyMoens ,
Just testing it and it works like a charm.
Thanks again for this great application, we really appreciate it.
Hi @KennyMoens .
First of all thanks for the great work and very well working app. I have a Qrevo Edge that works like a charm, but now I just got a Saros 10. Could I help you to get it into the app?
If you need debugging or data, please let me know. It would be awesome to get it in the app.
Hello guys,
Great that it works, Iāll push v1.0.2 to stable too so that everyone can enjoy this ![]()
Iāve recorded issue #53 to support rotation of the map. Still have to think on how to implement it somehow.
Iām not sure how zone cleaning can work by means of the buttons. It would be quite complex since Homey does not allow me to show a popup for user input here, so we would need a combination of a settings entry and then a button. Doesnāt seem user-friendly for me.
At this moment Iām not considering a widget for the app. It might come one day on the roadmap, but I do think there are still quite many things I like to add before considering this (and besides that, I need to keep the wife happy, she does not want me to spend whole evenings on the app
)
@Jens.Hummelmose
Could you elaborate why the Saros 10 is not working?
If you go to the add device option, does it appear? Or doesnāt it appear at all?
If it appears, then it might be some changes in the protocol afterwards. In that case, please add the device, wait approx 1 minute and then submit a diagnostics report. That might give me a clue on what is happening.
If it doesnāt appear in the pairing device, I honestly donāt know directly why. I really hope this is not the case, since that probably implies that Roborock changed some APIs for newer devices.
Thanks!