Is anyone else having this issue - I have a card setup with pause and a start clean button.
service: vacuum.pause & service: vacuum.start
In zone cleaning - pause and then sending vacuum.start works to resume the cleaning where it left off
Now I am using Room/segmented Cleaning and although pause still works - vacuum.start starts a brand new clean house cycle - so current room clean is ignored ? Have tried double pause but it doesn’t work. Any suggestions.
Usage of templates inside params for service vacuum.send_command is something i was looking for some time now. Your script seems to be an answer for my need. Point is, that it works only for zone cleaning while I’m using app_segment_clean where each specific room is defined as a number - see below. Would it be possible for you to adjust you script for such configuration? What I need as an input for params is a list of specific numbers. I would appreciate your support! Thanks!
My script is already adjusted to support app_segment_clean, but links to GitHub are altered by this forum to point to a version that is latest at the time of posting, so you just have to go to the latest version of the file to find features you need
Thanks for feedback! I have found it, but it seems to be too complicated for me as a newbie. I have no idea how my template should look like to generate proper input for params.
I was trying with below, but no success:
Nope, still nothing. When pasting it into HA templates seems to be OK, but there is an empty line created when some of the rooms are omitted - see below. Could it be the issue? Is your python script designed to work with such formatted data as an input?
Invalid config for [automation]: invalid template (TemplateAssertionError: no filter named 'expand') for dictionary value @ data['action'][0]['data_template']['params']. Got None. (See /config/configuration.yaml, line 155).
I’m not that good with coding but idea to use expand ('group.room_input_booleans') instead of 'group.room_input_booleans' | expand | is solving the issue. My automation is now working. Thanks for your effort @3_14( Piotr) You are my HERO!
@EdwardEnglish where you able to solve this issue?
I am trying to corner the issue piece by piece. First I wanted to see if vacuum.send_command is working correctly. If I use Developer Tools to call a service.
vacuum.start for example works perfectly fine.
Shouldn’t I get the same result using
service vacuum.send_command
entity_id: vacuum.rockrobo
command: start
Have a look here, I solved it using the new 0.117 template as list feature and can send it directly to the vacuum without using any python script at all.
One thing I’ve not been able to figure out yet is how to provide a payload of multiple segments to be cleaned though. Say like payload: ['20', '21', '22'].