log stays empty

[prankousky]

Hi,

I just installed rest980 Docker Image and php-nginx Docker Image through hassOS addons. Configured it - I assume - correctly:
I can

• start the vacuum
• send it to room (for example, living room; it works, because I found the corresponding id, for exaample, region_id | "5"
• the lovelace card will show info about the vacuum

However, when I open http://hassos:3001/image.php in my browser, I get No Coordinates found in file, is it reachable and populated? Log file - http://hassos:3001/vacuum.log?. The logfile (located in /config/vacuum/vacuum.log is, indeed, empty.

However, data seems to constantly be loading while the robot runs

After manually starting, then stopping, the vacuum, I get The image “http://hass:3001/image.php” cannot be displayed because it contains errors.

While this was the case, the vacuum.log actually did contain some data

Home Assistant notifications (Log started: 2023-02-15T10:57:38.400271+00:00)
--------------------------------------------------------------------------------

I then started another room clean, kitchen this time. Like before, the addon keeps gathering data every second or so. Currently state looks like below, the log from the add-on is beneathh the screenshot.

GET /api/local/info/state 200 99.853 ms - 5505
GET /api/local/info/state 200 100.873 ms - 5505
GET /api/local/info/state 200 100.763 ms - 5505
GET /api/local/info/state 200 101.093 ms - 5505
GET /api/local/info/state 200 100.803 ms - 5505
GET /api/local/info/state 200 100.964 ms - 5505
GET /api/local/info/state 200 100.886 ms - 5505
GET /api/local/info/state 200 101.080 ms - 5505
GET /api/local/info/state 200 100.941 ms - 5505
GET /api/local/info/state 200 100.756 ms - 5505
GET /api/local/info/state 200 100.869 ms - 5505
GET /api/local/info/state 200 100.734 ms - 5505
GET /api/local/info/state 200 100.088 ms - 5505
GET /api/local/info/state 200 100.834 ms - 5505
GET /api/local/info/state 200 100.782 ms - 5505
GET /api/local/info/state 200 99.881 ms - 5505
GET /api/local/info/state 200 100.772 ms - 5505
GET /api/local/info/state 200 99.882 ms - 5505

While this is all happening, the log file stays empty. Could this have anything to do with permissions? I tried chown 1000:1000 vacuum.log, but it is currently owned by root again (unlike all other files in that directory). Just as a test, I tried chmod 0777 vacuum.log, so anybody would be able to write to it. No difference.

The api currently shows this as lastCommand

What can I do to make the map work? Thank you in advance for your help. This project seems so cool, and everything else seems to work fine, so I'm sure this can be fixed as well :)

--

UPDATE

Just to be sure about permissions, I also did this

• uninstall php-nginx Docker Image
• remove /config/vacuum directory
• create /config/vacuum directory (directly on the hassos machine)
• clone this repository and copy the contents of vacuum into /config/vacuum

This time, all files were owned by root.

When I manually started my roomba again while watching that folder, I noticed that it did create vacuum.log, however, the file stayed at 0 bytes; there was no log started or anything like this. At the same time, the rest980 addon did keep updating itself (or querying data from the robot, like in the screenshot / paste above).

So data comes in, but, for some reason, doesn't go into the logfile.

[jeremywillans]

Hey @prankousky,

Glad you like the project!

Unfortunately mapping has been broken for a while since iRobot removed the pose (aka location) data from the api.

There is an issue open on the dorita980 project (which this leverages), though there's not much progress

[maceace]

I can't agree that mapping has been paused
The robot knows well where it is and sends a report of its work from the dock to the cloud when the task is completed. We just don't hear it.
I don't need to know the online position of the robot, but a quick glance to check the map whether the robot had a problem or not is a desirable function.

[jeremywillans]

The mapping data is no longer exposed to the API that rest980 can access. It is present in the App and likely on AWS, but to my knowledge no one has been able to gain access to this data.