Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase allowable zwave polling intensity values #3711

Merged
merged 1 commit into from
Oct 5, 2016

Conversation

mezz64
Copy link
Contributor

@mezz64 mezz64 commented Oct 5, 2016

Description:

Recent voluptuous migration for the zwave component limited the polling intensity values to (0, 1, 2), but openzwave will act on any multiple and doesn't actually have a limit. (See [http://www.openzwave.com/dev/classOpenZWave_1_1Manager.html#ab62582b7bcfec34574fb2aa7c54d147f])

This increases the allowable values up to 5, which is the max I use in my setup, but we may be better off just restricting it to int rather than a specific range.

If the code does not interact with devices:

  • [X ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

@mention-bot
Copy link

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

@turbokongen
Copy link
Contributor

Nice catch. I myself don't use polling. 👍

@turbokongen turbokongen merged commit 1bc6366 into home-assistant:dev Oct 5, 2016
@mezz64 mezz64 deleted the zwave_vol_fix branch October 5, 2016 17:12
hartmms pushed a commit to hartmms/home-assistant that referenced this pull request Oct 5, 2016
@home-assistant home-assistant locked and limited conversation to collaborators Mar 17, 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.

4 participants