yep!
you should have the BLID/PW/IP added to the rest980 addon configuration
by default the rest980 uses port 3000 and nginx uses port 3001
so once vacuum is disabled, you should be able to browse to
http://192.168.1.198:3000/api/local/info/state
and this should give you the vacuum details
Thank you a ton man, you’ve been an amazing help! Removing the code from the configuration.yaml file worked. I’m able to see a bunch of data points when going to that page. I then figured that that meant that everything should point to 3000 vs 3001 (which I previously had). I replaced all entries w/ the correct port, and now I have a vacuum.log file.
The last hang up I’m running into now, is when adding the lovelace module, when I paste in the full content of the lovelace.yaml file, I get, `duplicated mapping key at line 160, column 1: type: picture-glance ^’
If I remove ### PICTURE GLANCE CARD ### aspect_ratio: 0% camera_image: camera.roomba entities: [] type: picture-glance
I can get it to load, and see the data points in there.
I did add all the lovelace plugins in the guide, and chose the “add to lovelace” option. I’m not sure if I’m missing something else?
ah, the lovelace configuration should actually be two separate manual cards
Thanks so much for your help!
I got most of this running. A couple of questions / challenges I’m running into on the map integration…
In the guide, it says - “You will need to update the variables at the top of the image.php and image_dev.php to align with your environment.” However, nowhere do I see an image.dev.php file anywhere.
Also, I uploaded a floor.php replacement, and I’ve run the roomba, but I’m not seeing any files as being created by it. I did insert the pmap and user pmap ID’s.
I also notice that there’s a reference to a floor.png file in the image.php doc, but no mention of it (that I could find) in the instructions.
At this point, I’m getting no map output w/ the lovelace module. I copied the code directly in.
1
BLID: 317***********890
2
PASSWORD: ‘:1:15*********6DowgNVQAynokui’’’
3
ROBOT_IP: 192.168.2.155
4
FIRMWARE_VERSION: ‘2’
5
Failed to save addon configuration, not a valid value for dictionary value @ data[‘options’]. Got {‘BLID’: 3175000042416890, ‘PASSWORD’: “:1:1565099596:K6DowgNVQAynokui’”, ‘ROBOT_IP’: ‘192.168.2.155’, ‘FIRMWARE_VERSION’: ‘2’}
No longer needed, this file was removed and ive since removed it from the README file.
If the automations are working correctly, the process should work like this -
Make sure all these automations are correctly firing and check your homeassistant log file for any potential errors being generated
Check Step 9
Does your password contain a " ?
Perhaps try PASSWORD: ‘:1:15*********6DowgNVQAynokui’
Sorry, I misspoke. As mentioned, I did upload my floor.png. I meant to say that there’s reference to a walls.png in the image file, but don’t see anything more in relation to it.
Also - I do see the log positions writing. However, the Picture Glance Card is still blank. I was unclear on the file being written 10 seconds after it completed. I did manually run it earlier, and manually tell it to finish, but didn’t see a new image, or anything in the Picture Glance Card. Maybe it’s misconfigured?
And, does telling the Roomba to stop cleaning via the app invalidate this process?
walls.png is a new undocumented feature requested by @austech360 
its used in conjunction with line_thickness to allow you to just fill the floor with the “cleaned” area, similar to the irobot app shows. to prevent overspray, you need to duplicate your floorplan with transparent floors and this is overlayed on the end map to make it look shiny.
so all the aformentined automations are showing a last triggered time? which aligns with what you are expecting (i.e. when you stopped the clening, etc) it wont matter than you stopped it manually, as the phase and cycle statuses will still update accordingly.
after a clean/test clean, confirm the vacuum.log file contains points and then try open the image.php file in a browser and see what you get?
I’m sorry (still a noob), but how do I do this? I tried the HA IP w/ the HA port, and the docker port w/ vacuum/image.php, and both returned nothing back.
Based on the info in previous posts, i presume the URL will be
http://192.168.1.198:3001/image.php
in image.php > change this line
$vacuum_log = 'http://192.168.1.198:3001/vacuum.log';
That worked!! Man, if I had just a small bit of your skill… Again, I really appreciate your time.
Now, it looks like I need to figure out why my floor.png file is all zoomed in and wrong.
Just takes time and practice 
make sure the floor.png file is the same dimensions as the height / width variables listed in image.php
also check the FAQ document, i added a new one recently for mapping tips which should help you out
I’m going through them now. In Section 7, it says - Delete the latest.png file in the vacuum directory (prevents image.php from displaying the cached file). However, I don’t have an image.php file. Am I missing something here?
image.php is in the vacuum directory? its the file you just edited to update $vacuum_log
Love the look of this card config. Unfortunately every time I try to use it, it crashes my lovelace view. I have to go in and remove it for the rest of my lovelace cards to show back up again. Any ideas? Or maybe an updated config?
Thanks!
no my mistake. here is what i type inn.
BLID: 317********16890
2
PASSWORD: ‘:1:15********96:K6DowgNVQAynokui’
3
ROBOT_IP: 192.168.2.155
4
FIRMWARE_VERSION: ‘2’
5
Failed to save addon configuration, not a valid value for dictionary value @ data[‘options’]. Got {‘BLID’: 3175000042416890, ‘PASSWORD’: ‘:1:1565099596:K6DowgNVQAynokui’, ‘ROBOT_IP’: ‘192.168.2.155’, ‘FIRMWARE_VERSION’: ‘2’}
BLID: ‘317*16890’
PASSWORD: '‘:1:156DowgNVQAynokui’’
ROBOT_IP: 192.168.2.155
FIRMWARE_VERSION: ‘2’
[email protected] start /usr/src/app
node ./bin/www
amd mpthing happens more
