Skip to content

Zwave: Apply refresh_node workaround on 1st instance only#7579

Merged
andrey-git merged 2 commits into
home-assistant:devfrom
andrey-git:zwave
May 21, 2017
Merged

Zwave: Apply refresh_node workaround on 1st instance only#7579
andrey-git merged 2 commits into
home-assistant:devfrom
andrey-git:zwave

Conversation

@andrey-git
Copy link
Copy Markdown
Contributor

Description:

Apply refresh_node workaround on 1st instance only.
The buggy device behavior is sending update on main instance (1) when another instance changed.
Thus it is enough to apply workaround on instance 1 only.

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
Copy link
Copy Markdown

@andrey-git, thanks for your PR! By analyzing the history of the files in this pull request, we identified @ChristianKuehnel, @turbokongen and @armills to be potential reviewers.

Copy link
Copy Markdown
Contributor

@emlove emlove left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets add a test that the node isn't refreshed for instance=2. Otherwise LGTM.

@andrey-git andrey-git merged commit 9270247 into home-assistant:dev May 21, 2017
@andrey-git andrey-git deleted the zwave branch May 21, 2017 14:33
@balloob balloob mentioned this pull request Jun 2, 2017
@home-assistant home-assistant locked and limited conversation to collaborators Sep 4, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants