Add zone and reps for Xiaomi vacuum

[marcogazzola]

Description:

Add functionality to clean a specific zone and set the number of repetitions with Xiaomi Vacuum

Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#8047

Declare the data_template parameter for using templating repeats parameter.

Example entry for automation.yaml (if applicable):

automation:
#Inline array:
  - alias: Test vacuum zone3
    trigger:
    - event: start
      platform: homeassistant
    condition: []
    action:
    - service: vacuum.xiaomi_clean_zone
      data_template:
        entity_id: vacuum.xiaomi_vacuum
        repeats: '{{states.input_number.vacuum_passes.state|int}}'
        zone: [[30914,26007,35514,28807], [20232,22496,26032,26496]]

#Array with inline zone:
  - alias: Test vacuum zone3
    trigger:
    - event: start
      platform: homeassistant
    condition: []
    action:
    - service: vacuum.xiaomi_clean_zone
      data:
        entity_id: vacuum.xiaomi_vacuum
        repeats: 2
        zone: 
        - [30914,26007,35514,28807]
        - [20232,22496,26032,26496]

#Array mode:
  - alias: Test vacuum zone3
    trigger:
    - event: start
      platform: homeassistant
    condition: []
    action:
    - service: vacuum.xiaomi_clean_zone
      data:
        entity_id: vacuum.xiaomi_vacuum
        repeats: 1
        zone: 
        - - 30914
          - 26007
          - 35514
          - 28807
        - - 20232
          - 22496
          - 26032 
          - 26496

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• New dependencies have been added to the REQUIREMENTS variable (example).
• New dependencies are only imported inside functions that use them (example).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[homeassistant]

Hi @marcogazzola,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[homeassistant]

Hi @marcogazzola,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[rytilahti]

Just a very brief review, hopefully someone else will also chime in to review this.

[marcogazzola]

Just a very brief review, hopefully someone else will also chime in to review this.
All the problems have been fixed. Please approve it.

[syssi]

LGTM. Please do me a favor and update the log messages. :-)

[MartinHjelmare]

Last comment, I think. Then we should be good after the merge conflict is solved.

[MartinHjelmare]

The branch is polluted. Either try to fix it or open a new PR.

[marcogazzola]

The branch is polluted. Either try to fix it or open a new PR.

I'm sorry..
I think I've resolve the problem and now the branch is ok.