fix zwave thermostat with multiple setpoints

[srirams]

Description: fix issue with zwave thermostats with multiple set points (one for cooling and one for heating). Also change operation property to return the current operating state rather than what mode its set at.

Related issue (if applicable): fixes #2189 (partially)

Checklist:

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

• Documentation added/updated in home-assistant.io

If code communicates with devices:

• 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]

Add , too-many-instance-attributes to this Line: https://github.com/srirams/home-assistant/blob/dd9dc24aa84b5a16eea31456a2fa95a3a37ea8e7/homeassistant/components/thermostat/zwave.py#L60

[srirams]

Ok I've done it and that made everything pass!

Thanks.

[balloob]

Looks good! 🐬

[xenoxaos]

Not to go around raising a horse from the dead just to kick it some more...but this is now merged and upstream. Correct? Is there a configuration change I need to make. This may be PEBKAC, but I'm still seeing multiple instances.

[srirams]

There have been many changes since this was committed and this is now in a new component so you should probably make a new bug report. I haven't used zwave in a while (waiting on some openzwave updates), but the last time I did there was still some issues with the way ha worked with my thermostat.