Thank you for reaching out, when you go to the app store it will be called smart things in the app store.
I apologize for the confusion, when you open the smart things app, there should be three lines at the top left of the app when you press that there should be an option for history close to the bottom and it should show the history.
@SamsungCaleb I have had this vacuum since 2017 and it is used daily. When I follow these instructions the history shows "No activities". I surely wish Samsung would either do as they advertise or change their advertising to reflect the reality of their vacuums. I am shopping for another robotic vacuum, but Samsung is not on the list of manufacturers I am considering. The battery is dying, the history does not work, the machine almost never finishes a vacuuming, the app is an absolute pain on the occasions that it decides to work. Goodbye, Samsung!
Samsung Support - Samsung Connect refers me to the Smarthings app, which I have downloaded and installed and set up. While it see and communicates with my R7040, it does not show anything in history, despite my having run the vacuum a number of times. Any suggestions??
I recommend reaching out to our SmartThings team, they can be reached at 866-813-2404
So we heard back from our specialists and they believe you need to be using Samsung Connect. If the powerbot purchased was manufactured during or after June 2017, you need to use Samsung connect rather than Smart Home. However, there is no mapping option in the Samsung Connect app, it does the mapping and then stores it internally. When it finishes vacuuming you can see the ”map” of where it has been by checking the history. In Device Control either swipe down from the top and pick history (or touch menu in the top right and select history).
So I have the same Powerbot and essentially the same issue. It does provide the map in the history section of the Samsung Connect app, but only on occasion. The vacuum does run on a daily schedule but I can't seem to figure out when/why if provides the map output and when/why it wont. I thought this was related to times an error was detected thinking maybe it wouldnt map that but there are times when there is no interruption in reporting that still yields no report.