Bugfix: incorrectly inverted value when setting zwave cover position

[ej81]

Description:
Setting position for the zwave cover component submits the position to the open-zwave library as 100-position. This is not consistent with the rest of the code where the position is used as is. Setting the cover position to 80 sends the cover to position 20 and the state is read back correctly as 20.

This PR fixes the problem by removing the inversion in set_cover_position.

Related issue (if applicable): fixes #

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

Example entry for configuration.yaml (if applicable):

Checklist:

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

• Documentation added/updated in home-assistant.io

If code communicates with devices, web services, or a:

• Local tests with tox run successfully. Your PR cannot be merged unless tests pass
• New dependencies have been added to the REQUIREMENTS variable (example).
• New dependencies are only imported inside functions that use them (example).
• New 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:

• Local tests with tox run successfully. Your PR cannot be merged unless tests pass
• Tests have been added to verify that the new code works.

[turbokongen]

@nunofgs @kuhlivisj @mib2011 @wokar Any of you experiencing this?

[balloob]

I wouldn't be surprised if this was an artifact from the rollershutter, which had things in reverse.

[wokar]

Just tested my current 0.28.2 setup and I can confirm the behavior. Setting the rollershutter to 80 in the GUI opens it about 20% and after it stops the slider in the GUI jumps to 20.

After applying the patch it works as expected.

[balloob]

Alrighty, 🐬