yes, but if lights are on allready they should not be turned off once done, could be that we are at home doing something and dont want to sit in the dark. So my thought was something that remember the state of the light before a clean is started. And yes sadly the roomba is blind as a bat without the lights in these nordic winters
Hahaha… I have the same problem. Kinda awkward when you suddenly sit in darkness…
Hi,
I have added several zones and renamed them to understandable labels for my rooms. However doing so, I encountered this error when checked configuration:
Invalid config for [input_text]: [intitial] is an invalid option for [input_text]. Check: input_text->input_text->vacuum_clean_eating_room->intitial. (See ?, line ?).
Where do you need to add room’s, their names and other references in which files, and what are the conventions?
reading the code below, it seems those values are not required? In the payload array, we only need region_id and type that stored as secret, is that right?
{
"ordered": 1,
"pmap_id": "{{ state_attr('sensor.vacuum', 'pmap0_id') | string }}",
"regions": [{% for id in rooms %}
{% set room = 'input_text.vacuum_clean_' + id %} {{ states(room) | string }} {%- if not loop.last %},{%- endif %}
{%- endfor %}
]
}
so the actual payload is like below:
{"ordered": 1, "pmap_id": "123456", "regions": [{"region_id": "4", "type": "rid"}, {"region_id": "5", "type": "rid"}, {"region_id": "6", "type": "rid"}]}'
Is this correct?
Nevermind,
I made a typo
Hi,
is there a possibility to separately x-scale and y-scale the roomba-lines?
Hmm… perhaps call another automation first ? include condition for current lights status and have the action set a Input boolean to flag that the lights were turned on by the automation… this could still get messy however.
Yeah your right, i didnt read your question properly 
these fields used to be required, but not anymore 
Yeah, you could.
This is currently controlled by a single variable on line 20 which ammends the x and y variables on lines 128 and 129
example -
$x_scale=1.00; # Allows scaling of roomba x lines
$y_scale=1.00; # Allows scaling of roomba y lines
...
// Rotate Calculations
$x=($tmpx*cos(deg2rad($rotate_angle))+$tmpy*sin(deg2rad($rotate_angle)))*$x_scale;
$y=(-1*$tmpx*sin(deg2rad($rotate_angle))+$tmpy*cos(deg2rad($rotate_angle)))*$y_scale;
How does the graph work for multiple floor map?
I have home assistant running on a pi and am trying to get this very cool configuration set up. I’m a bit of a white belt when it comes to the technicals and have what may be pretty basic questions. 
I don’t use docker (and wish I knew more about it because so many step by steps involve docker!). when I attempt to run the rest980 docker image add-on (having set up configuration with blid and password) I get an error…
404 Client Error for http+docker://localhost/v1.40/containers/create?name=addon_39c40414_rest980: Not Found (“No such image: 39c40414/aarch64-addon-rest980:20200205”)
presumably because I don’t use docker? Do I need Docker for this to work? Thank you for your work and any help you can offer!
Hi,
I’m setting this up now for the second time and it appears that the first try had some beginners luck, as this time I don’t understand how the lovelace.yaml (https://github.com/jeremywillans/ha-rest980-roomba/blob/0d8817e7f1eb4ed1506b8e728e353893e5fcc875/lovelace.yaml) is used in my homeassistant environment. As soon as I copy this file one-on-one in the raw-editor of a view, it doesn’t get me anywhere. So either I need to cut and paste certain parts of that yaml file in different places or I paste the whole thing in a total wrong place.
Reading the directions in the GitHub isn’t helping me. There are too many assumptions (of level of knowledge) and too less information.
Costco has another mode of self-empty vacuum: https://www.costco.com/shark-iq-robot-self-empty-robot-vacuum-with-wi-fi-and-accessories.product.100644637.html
Does anyone have experience? How does it compare to i7+? HASS has shark iq integration but I don’t think it has realtime map function, right?
Thanks.
My currently configuration does not have a “solution” for multiple floors… as i do not have multiple floors to test with 
if/when i ever get some free time i do plan on working on this. others do talk about their options and ive provided some advise in the thread however.
That is unusual - if your running HA on a Pi, then it is already using docker (part of the underlying system). try removing the add-on and adding it again?
the lovelace.yaml file contains two “manaual” cards, so within a view, add a new manual card and copy the first card (lovelace.yaml lines 2-155) and then repeat for the second card (lines 158-161)
this is probably a topic for a different thread as its not related to deploying this integration.
Last line should be
type: vertical-stack
Which should give the card type 
Hi Syrius,
Thanks for your reply.
changing the last type to vertical-stack results in several elements, with all erroring:
Custom element doesnt exist: roomba-vacuum-card.
or
Custom element doesnt exist: fold-entity-row.
It appeared that my Frontend HACS Integrations were ‘Not loaded’. Reinstalling them did the trick.
But the question is: Do you have any idea why these integrations suddenly are ‘Not loaded’?
not sure did you recently upgrade? 
least its sorted 
1 Like
Thanks a million,
I have now another issue. In my first set-up (that I had to reinstall completely (yeah, I know…)), the last map was always stored and displayed so that you could see afterwards what the pattern was Roomba had run.
In my new setup, the camera.roomba picture-glans card only displays that whilst cleaning, but when it is done, it shows a ‘non-picture’ grey symbol.
In addition, the Maintenance Entities do not change from "Entity doesn’nt exist. Create?" to a value when double clicked on it as it worked before.
Where do I find the clue to these problems?
Hi, everyone.
For some reason, since the other day my roomba integrations (sensor.rest980) is unavailable. I cheked everything and it seems fine. I didn’t touch anything.
I have the rest980 docker image working and I can access to them but when I try to get the info state (http://homeassintant.local:3000/api/local/info/state) only shows an empty message “{}”.
What am I missing?
a-ha… I have much to learn. Mostly I’ve been building out my installation following step by steps and learning bits and pieces along the way, but there are still large fundamental technical bits that haven’t clicked into place yet in my understanding.
I tried uninstalling and re-installing a couple times. Each time, my pi hung and I needed to hard restart after which the plug-in seemed to have installed, but then I ran into the same error pasted above. Seems like there may be something more fundamental at play here preventing installation? If you have suggestions for diagnosis/things to try… or where I might read more about relevant factors, I’d appreciate them. I’ll continue exploring the forum in the meantime! Thanks, Syrius
Just reboot Roomba and everything is working again!