-
Notifications
You must be signed in to change notification settings - Fork 2
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
Parallel timeout countdowns - wasp in box check triggered too early #4
Comments
riesch
changed the title
timeout period - triggered too early
timeout period - wasp in box check triggered too early
May 1, 2022
it seems to me that counting down the timeout period is not reset after box is newly closed. So that parallel timeout instances are being counted down, triggered at every box close. You can see that in these logs:
|
riesch
changed the title
timeout period - wasp in box check triggered too early
Parallel timeout countdowns - wasp in box check triggered too early
May 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version of the custom_component
Latest
Configuration
Describe the bug
The timeout is set at 185, yet before 185 seconds the check is done resulting in a false trapped wasp.
Box closed at 21:39:39 (empty room)
From that time no new ON triggers from any of the 3 PIR
Wasp in box at 21:41:38 (67 sec too soon)
Wasp seen off at 21:42:24
Debug log
The text was updated successfully, but these errors were encountered: