Did you see my questions above? Hoping someone can help. Totally stuck.
vacuum.yaml file goes into the packages folder
you don’t copy the lovelace.yaml to any location, you copy the content of that file into a new view on your dashboard.
I just deleted all the maintenace stuff because i don’t have an mqtt server and wasn’t that interested in that info
Thanks for the response – really appreciate it. Definitely helped!
But I think I have bigger problems than the UI – my vacuum entities don’t exist (duh) despite following the steps very carefully.
Do you (or does anyone) know which of the add-ons to run? When I added the Willans add-ons, I get two pairs: “rest980 Docker Image” and “rest980_j7 Docker Image”. I understand that there’s a pair of each – one for a vacuum and one for a map, if you both. What I don’t understand is why there are two such pairs. I know “J7” is an iRobot vacuum model number, but nowhere that I could find does it say which pair of add-ons should be configured and run.
I’ve tried it both ways, and haven’t been successful so far. Appreciate any advice.
Make sure you have the following all done:
created a folder called vacuum in your config directory and copy the content from the vacuum folder in the repository to it
created a folder called packages in your configuration directory
copy the vacuum.yaml to the packages folder
add the required line to configuration.yaml to include the packages folder
add all the correct keys to the secrets.yaml file
what addon to use:
From what i understand is that for any iRobot you have, except for the J7, you use the rest980 docker image
whatever docker addon you ran to get the rid’s for the rooms was the correct one. You are probably missing something and that’s why it’s not creating the sensor.
Make sure th iRobot app is not running on your phone when you try all this
I’ve had the Roomba i7 integrated and working with Home Assistant for a couple of years… then when the update that broke the maps was installed it seemed to break the whole integration.
I’ve narrowed down the issue to the selective room cleaning… everything else seems to work. But, if I choose a room to clean the robot starts a clean but doesn’t actually go to the room it’s meant to clean, it just stumbled around the room where the base is located. I checked the “region id’s” and all seem correct… now I’m stuck.
Any direction on what to check would be so appreciated. Thanks.
Appreciate that “checklist” @CK77, but unfortunately I think I’ve done all that. Though I suspect it’s time for me to delete and start anew since I’ve done so much tweaking and changing.
One other potential problem area – I don’t currently use a secrets.yaml file. I have an empty one in my config folder and there’s no reference to it in my configuration.yaml. Once I edited the OP’s secrets.yaml, where does it go? If I’m not concerned about local security, do I need it?
The secrets file is crucial in this setup.
It’s used to fill in a lot of the input_text helpers with their original values. That’s how you get the room information from the robot into your text helpers, unless you replaced all the secrets with the correct values in the vacuum.yaml file
The secrets file just lives in the same folder as your configuration.yaml
argh I did all that too. Think I’ll reboot the effort and start from scratch. Must’ve missed something. Thanks for your help just the same.
When i got my iRobot, i looked at this project and it was back then just too daunting, so i took another route and used the Google Assistant SDK, that way you can just send spoken commands to your Google Assistant from HA and that worked for me.