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

Second triggering of device cancelled #8

Closed
daneedk opened this issue Jan 28, 2018 · 3 comments
Closed

Second triggering of device cancelled #8

daneedk opened this issue Jan 28, 2018 · 3 comments

Comments

@daneedk
Copy link
Owner

daneedk commented Jan 28, 2018

Wessel88 posted on the forum

@DaneeDeKruyff
Great app!
Used this afternoon for some testing in combination with Neocam Motion-sensor.
While testing I found out that when the motion-sensor activated the alarm-state, and I deactivate the alarm, there will be no new alarm when a new motion is detected. In the logging I see:

28-01-2018 16:57:57.302 Geactiveerd Heimdall Alarm is geactiveerd.Bewegingssensor woonkamer: Beweging gedetecteerd
28-01-2018 16:57:57.283 Geactiveerd Heimdall Bewegingssensor woonkamer motion activeerde Alarm.
28-01-2018 16:58:23.949 Geactiveerd Alarm Off Button Alarm is gedeactiveerd.

And after deactivating the alarm, the new log:
28-01-201816:58:33.895 Geactiveerd Heimdall Bewegingssensor woonkamer: Beweging gedetecteerd, no alarm trigger due to running delay countdown

When I restart the Heimdall-app, the alarm-state is activated by a new motion. When I won't restart the app, this is not happening.

Is this a normal thing, or is this a bug?

Keep up the great work!!

@daneedk
Copy link
Owner Author

daneedk commented Jan 28, 2018

Seems to be introduced on 0.1.6 where this functionality was included for a delayed trigger: #5

@daneedk
Copy link
Owner Author

daneedk commented Jan 28, 2018

Confirmed, it's a bug introduced in 0.1.6 Fix is ready and a new version is submitted to the App store for approval.

@daneedk
Copy link
Owner Author

daneedk commented Jan 30, 2018

Version 0.1.7 has been approved and published.

@daneedk daneedk closed this as completed Jan 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant