the addon is there, i just get an error when i try to install
EDIT: step 1+3+4 done
as for step 3 i have only copied the vacuum folder to config folder
step 4 i have just installed rest980 and php-nginx. the step does not explain how to configure
Sorry all - was on vacation hence the lack of responding.
glad its working!
yeah it would need some additional code to get it working properly - will need some magic to get the logging to the right files and matching the background to the floor selected.
The trusty have you tried turning it off and on again trick
what permissions are configured on this folder? does docker have the abillity to read/write to this folder? perhaps try setting full perms and work back
perform an example clean from the HA App and then navigate to - http://<ip or fqdn of docker host>:<rest980port>/api/local/info/state
the content of the “lastcommand” section will be the body of the HTTP POST Command that you will use to initiate this request
The actual POST URL is http://<ip or fqdn of docker host>:<rest980port>/api/local/action/cleanroom (this is the same as rest_command.vacuum_clean)
make sure your trying to pair a new handset, which should just be holding the home button, not both buttons.
user_pmapv_id is bascially a timestamp of the map version - this is constantly changing and for some reason rest980 dosent seem to obtain this correctly. However you dont actually need to send this anymore review the lastest vacuum.log file for changes needed.
not completley - there is underpinning missing attributes in rest980 for the braava. if i had one i would probably be fixing this myself - but unfortunatly i dont
yeah it does that sometimes… i did add an attribute in the image.php file to exclude a defined number of initial entries in the file - this might help your case?
This appears to be linked to an NPM issue. It is affecting the node:alpine image from which roomapw is using - I have switched it over to node:boron and it now builds for me - try and see if this now works for you
if you have the BLID/PW then you have completed step two - not skipped it
EDIT: vacuum_notify: notify.mobile_app_xxxxxxx # You can also use a notify group here
what do i replace xxxxxxx with? and how do i find what to replace with?
EDIT2:
yep works now, since i got the info via windows i dont need it but others might.
EDIT3:
vacuum.yaml what do we need to change in that one? i guess only parts where we see the list of rooms but i could be wrong. what i have in mind is the # Input Boolean section. It does have most of what i need except an office so i can remove those i dont need
EDIT4: floor.png and walls.png… can they be the same file? i have made a floorplan for the picture elemens thing on the front page. since that is made to scale (i spend hours with a messure tape to get it right) i thought that it would be perfect for this also. its made in svg (with inkscape) so i just need to save as png and mark the white as transparent?? OR as i just found out… maybe just have floor.png but do the floors need to be transparent? or ?
EDIT5: i copied over the example lovelace.yaml and i got this:
when trying to create the service items it says the service is not there (in lower left corner)
but i did install the broker with default settings (ie i did not change anything just did the install)
Hi Everyone - I’m new to HA and don’t have much programming experience. I love this integration and got it to work with my Roomba i3+. However, most of the status displays as “unavailable” but I am able to connect to my roomba and also start, pause, and also dock it. Here’s a screenshot for reference. Any ideas what else I need to do to get this to work? Thanks in advance!
no, secrets.yaml file should already exist in your config directory (next folder up) and for vacuum.yaml - you need to configure your HA enviornment to support packages (part of step 6)
if you have the iphone app installed and working, navigate to Developer Tools, and on the Services tab, enter notify.mobile_app and if its configured, the name should be displayed for your device.
you only need walls if your using fill mode.
for floors, nothing needs to be transparent. if you want to use fill mode, then you duplicate the floors file and make the floors transparent
the end result is layered
walls
robot lines
floors
so the result is a nice looking map
this wont work until you have the packages configued so all these entities actually exist.
do you have MQTT discovery enabled?
as above, need packages configued.
refer above.
these errors will go away once packages is configured.
you will need to run a clean first for the log to populate so it can generate a map
once the clean has run, in the vacuum directoy there should be a vacuum.log file which has a listing of the coordinates which the roomba has been. check that this exists first and is populated
“you don’t actually need this anymore” pointed me in the right direction - I had an old version vacuum.yaml (from an aborted attempt to make this work a few months ago). Grabbed the new one, threw all of my config stuff into it, restarted HA and I can now selectively clean rooms from the HA interface. Awesome, thanks heaps for all of your efforts!
do i assume correct that with no offset speced 0,0 is in the upper left corner and that X is left/right and y is up/down?
that would help greatly in understanding how to set the offset so i can move the lines so they match the floorplan
it did draw the green lines at some point but it does not seem to do it on every run even thou i delete the log before each try, making it a bit confusing if it works or not
so the logs is being build, sometimes i do see green lines on top of the floorplann, but mostly i just see a loading image error instead of the floorplan
correct, this gets layerted over the floor.png file
lines are generated based on the nav points in the vacuum.log file
in theory
the log should be deleted automaticlly based on the automations in place.
if the log file is populated, then it will show the green lines, if the log file is blank, then you will get the error.
if you try access this directly, then yes 401 indicates unauthoried. in the top of the image.php file you need to define a token which is uses for authentication to get the stats from HA