Any idea why there wasn't a verbose trouble status updates around the period from 15:15-49?
Code: Select all
Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 840 - Partition Home Trouble LED ON
Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 840 - Partition 2 Trouble LED ON
Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 840 - Partition 3 Trouble LED ON
Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 840 - Partition 4 Trouble LED ON
Sep 07 15:11:28 - DEBUG - core/envisalink.py:handle_line@158: RX < 511 - Keypad Led Flash State - Partition 1
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 849 - Verbose Trouble Status 01
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 511 - Keypad Led Flash State - Partition 1
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 652 - Partition Home Armed Mode Away
Sep 07 15:12:32 - DEBUG - core/envisalink.py:handle_line@158: RX < 550 - Time/Date Broadcast 09/07/17 15:12
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 511 - Keypad Led Flash State - Partition 1
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 849 - Verbose Trouble Status 01
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 511 - Keypad Led Flash State - Partition 1
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 652 - Partition Home Armed Mode Away
Sep 07 15:16:32 - DEBUG - core/envisalink.py:handle_line@158: RX < 550 - Time/Date Broadcast 09/07/17 15:16
Sep 07 15:16:49 - DEBUG - core/envisalink.py:handle_line@158: RX < 814 - FTC Trouble
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 815 - FTC Trouble Restore
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 841 - Partition Home Trouble LED OFF
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 841 - Partition 2 Trouble LED OFF
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 841 - Partition 3 Trouble LED OFF
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 841 - Partition 4 Trouble LED OFF
Note: the initial trouble was due to a "T-Link Network Fault", which is visible in the eyez-on portal logs, but can't be seen from the Envisalink TPI. The sequence of events as seen from the portal's event log is:
Code: Select all
2017-09-07 15:19:13 - Phone Number 1 FTC Restore
2017-09-07 15:17:38 - T-Link Network Restore
2017-09-07 15:16:48 - Phone Number 1 FTC
2017-09-07 15:11:23 - T-Link Network Fault