Today I noticed a huge problem. The vacuum robot has done its job, suddenly stopped at the end (running mode) and glowed white. It could no longer be operated at all, not with the “Clean” button or via the app or via HomeAssistant.
Only the hard reset allowed it to restart (over a minute on the clean button)
Any idea?
I also just noticed that the mop cannot be started via the dashboard. Whenever I press “clean”, the S9 starts instead of the Braava: /
The rest of the command is changed or not as follows: (or is it still called vaccum_action …)
PS: I renamed everything that was called “vaccum” to mop.
I looked further up, but unfortunately I couldn’t find a post where someone successfully integrated the Braava.
But I have now deleted everything that contains the base and the bin and now the error message is gone.
What is still stupid, however, is in the Lovelace the “dust bag” cannot hide: / see photo
have you defined the entities in the Lovelace card? you will also need to change the vacuum_action to reflect the rest_command for your braava also
- type: custom:roomba-vacuum-card
entity: sensor.vacuum or sensor.mop <----- define the correct entity here
vacuum_action: mop_action <----- add this and change to your rest_command name
this sounds like a vacuum specific issue, im not sure sorry
you need to change the vacuum_action command in your second instance of the lovelace card
please keep in mind that I created this for a Roomba and i dont own a Braava. I have a pending task to make the LL card modular however spare time is in short supply so i havent yet had a chance to implement it. anyone can feel free to raise a PR if they wish or donate me a braava
automation mop:
# Initiate Selective Room Clean
- alias: Mop Clean Rooms
trigger:
- platform: event
event_type: initiate_mop_clean
action:
- service: rest_command.mop_clean
data_template:
payload: >
{% set rooms = states('input_text.mop_rooms') %}
{% if rooms[-1:] == ',' %}
{% set rooms = rooms[:-1] %}
{% endif %}
{% set rooms = rooms.split(",") %}
{
"ordered": 1,
"pmap_id": "{{ state_attr('sensor.mop', 'pmap0_id') | string }}",
"regions": [{% for id in rooms %}
{% set room = 'input_text.mop_clean_' + id %} {{ states(room) | string }} {%- if not loop.last %},{%- endif %}
{%- endfor %}
]
}
So everything that had vacuum is changed to mop. I haven’t changed anything in the vacuum.yaml, so I’m v surprised that the existing card changed to track the braava instead.
name: vacuum_action: mop_action <----- add this entry
I’d added a completely separate section in secrets and had changed everything to mop_action, mop_state etc. and made the relevant changes in the mop.yaml too.
@clipse can I ask how you got the Braava image on this card?
Ah amazing thank you. Took me about 10 mins to realise I didn’t need to recreate the whole card and could just specify the same card with an image: /hacsfiles/lovelace-roomba-vacuum-card/braava.png line added in. Thank you!
Has anyone posted a configuration for the Bravaa Jet M6? As in getting the sensors from REST980 and adding it to the Vacuum card? I have it set up and it works, but I’d like to get more customized info into HA like the tank status, etc.
If somoene has a complete braava.yaml working copy, i might actually look to upload into this repo to make it essier for others, as well is incorporate some of the above changes into the lovelace card natively with a attribute to switch between roomba and braava.
I’ve now copied the code from the new yaml to my existing and changed the states again in german. But there is still no change. I can not use the buttons of the roomba vacuum card. After restoring the original yaml with english states it works again.
A second thing I recognized is that if I only select a zone for cleaning I’m not able to start with the clean rooms button on the lovelace card. It remains locked.
I have another question, in the Image.php file in line 23 “$ha_rest980 =”
There is the IP of HA and the associated port to enter, somewhere I have read here once an answer from you on it. If I use the correct address (by the way, I have to use HTTP instead of HTTPS) still comes the message “401: Unauthorized” if I try https comes “Page not found”.
Are you sure this is correct?
Camera image not updating >> Getting this error in my Log file:
Error getting new camera image from Roomba: 404 Client Error: Not Found for url: http://192.168.5.120:3002/config/vacuum/image.php For more information check: https://httpstatuses.com/404
Hey @Syrius - sorry that this is months later… not getting the time to root-cause these things Weird behaviour:
I can see the Rest980 Log is getting successful responses messages from the Get Info State (below), however when I try any commands manually in the browser, the browser simply says it times-out, and theres no response.
Any idea what I’m doing wrong? Thanks again.
GET /api/local/info/state 200 102.839 ms - 2
GET /api/local/info/state 200 103.302 ms - 2
GET /api/local/info/state 200 103.752 ms - 2
GET /api/local/info/state 200 102.396 ms - 2
GET /api/local/info/state 200 101.850 ms - 2
GET /api/local/info/state 200 101.310 ms - 2
GET /api/local/info/state 200 102.515 ms - 2
GET /api/local/info/state 200 102.198 ms - 2
GET /api/local/info/state 200 102.388 ms - 2
GET /api/local/info/state 200 101.549 ms - 2
GET /api/local/info/state 200 102.491 ms - 2
GET /api/local/info/state 200 102.524 ms - 2
GET /api/local/info/state 200 101.346 ms - 2
GET /api/local/info/state 200 102.463 ms - 2
GET /api/local/info/state 200 101.323 ms - 2
GET /api/local/info/state 200 107.691 ms - 2
GET /api/local/info/state 200 102.134 ms - 2
Been using this for a long time now and no worries
Btw, thanks for all the help with that
Now an interesting thing is that i need to change the maintaince intervals, the brushes are starting to break up and its still saying 2 months until replacement, where do i change that? i looked in image.php and index.php and nothing made a bell ring
if you have setup this using php-nginx, then the URL should just be http://192.168.5.120:3002/image.php
try and let me now
if you navigate in the browser to this url - http://<ip or fqdn of docker host>:<port-for-rest980>/api/local/info/state what do you get?
if its just {} then try restarting the container and make sure you dont have the official vacuum integration running in HA, as these dont play nice together.
report back with the outcome
if you mean change the interval? then yes, in the lovelace file is correct. this line in the lovelave.yaml. the lines above are used to dictate when to change the color to yellow and red.
however if you just want to indicate that you have changed them, then just click on the check-button-card and it will reset. the timing i put were based on the recommendations of irobot, but you can modify to suit your deployment
Weird behaviour: