-
Notifications
You must be signed in to change notification settings - Fork 95
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
Unable to disarm during an alarm event #520
Comments
I have not seen this before probably some fresh firmware update has a bug. I can't do anything about it. |
It is still running firmware 4.90. Is there a method I can use to try to figure it out and help contribute to fix it?Kind Regards,Raine Pretorius
-------- Original message --------From: Jevgeni Kiski ***@***.***> Date: 2024/11/25 10:47 (GMT+02:00) To: ParadoxAlarmInterface/pai ***@***.***> Cc: Raine Pretorius ***@***.***>, Author ***@***.***> Subject: Re: [ParadoxAlarmInterface/pai] Unable to disarm during an alarm event (Issue #520)
I have not seen this before probably some fresh firmware update has a bug. I can't do anything about it.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Here is the weird issue in the logs where it disconnects just after the alarm event starts: -----BEGIN PGP MESSAGE----- wcFMA4hORRWTO2jFAQ/9Gl1p5sQ9nJImZTU7B/pylwRUQZn3Zu3xz7ms1X6facmQ |
Alarm system
Describe your panel model (ex: EVO192, Spectra SP4000, Magellan MG5050), access mode (Serial, IP150, etc..).
MG5050
Environment
Docker container
Git branch
Which Git branch you use. Did you tried "dev" branch? Please try before posting.
The one in the docker container
Describe the bug
A clear and concise description of what the bug is.
I am unable to disarm the alarm system when there is an alarm event that occurred. PAI stays stuck in the same state until I manually disarm the alarm via the keypad and restart the docker container. Else the Alarm Panel stays triggered.
To Reproduce
Steps to reproduce the behavior:
Logs
PLEASE DO NOT SEND LOGS IN CLEAR TEXT AS THEY MAY CONTAIN SENSITIVE INFORMATION
If you wish to add a log (which will greatly help us), please follow the following instructions:
The text was updated successfully, but these errors were encountered: