Update vera cover refresh logic

[pavoni]

Description:

This PR mainly bumps the vera version (which has an update that changes how thermostats are set - plus a change to how covers work - which fixes a bug where open and set_position didn't play well together.

I added some extra calls to self.schedule_update_ha_state() because I think some of the vera devices might not send async position updates correctly.

I'm not 100% these are needed (does the base cover code already schedule an update after a command).?

Related issue (if applicable): fixes #

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>

Example entry for configuration.yaml (if applicable):

Checklist:

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

• Documentation added/updated in home-assistant.github.io

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

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

[mention-bot]

@pavoni, thanks for your PR! By analyzing the history of the files in this pull request, we identified @robjohnson189, @arjenfvellinga and @balloob to be potential reviewers.

[balloob]

Home Assistant will automatically update the entity in the state machine if should_poll returns True for the entity. If it is False, we expect the component/platform to push a new state once it is known using schedule_update_ha_state.

[pavoni]

Thanks @balloob - VeraCover inherits from VeraDevice which implements should_poll and returns False. So this should be GTG.

[andrey-git]

Why add schedule_update_ha_state?

It takes data from device and updates the state machine. If something changed ozw would call the value_updated which will call schedule_update_ha_state anyway.

[andrey-git]

Disregard, I confused vera with ozw

[pavoni]

It's a good point though- and should be true with vera too - but seems like it might not always be with some devices (which is what this PR should fix)!