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.

Sign up for GitHub

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

Jump to bottom

SCAN INTERVAL #156

Open
GPDixon opened this issue Mar 8, 2020 · 1 comment
Open

SCAN INTERVAL #156

GPDixon opened this issue Mar 8, 2020 · 1 comment

Comments

@GPDixon
Copy link

GPDixon commented Mar 8, 2020

Hi, I've been trying to use the scan_interval setting in configuration.yaml but it keeps defaulting to 5 seconds. When I look at binary_sensor.py it seems to be hardcoded at 5 seconds? Any chance of changing please? Thanks, Gavin.
@pnbruckner
Copy link
Owner

You don't say which custom integration you're referring to but I would have to guess amcrest. It hasn't been supported for a long time. You should use the standard integration. Most enhancements from the custom integration have been added to the standard integration. Having said that the scan_interval parameter hasn't worked for a long time and there's really no easy way to fix it. But the good news is I'll be submitting a new change that makes the binary motion detected sensor stream based instead of polled which will make it instantaneous.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pnbruckner @GPDixon