search

ParadoxAlarmInterface / pai

Paradox Magellan, Spectra and EVO, with MQTT, Signal, Pushbullet, Pushover and others
https://gitter.im/paradox-alarm-interface
Eclipse Public License 2.0
344 stars 92 forks source link

Periodical disconnecting #284

Open proasnet opened 2 years ago

proasnet commented 2 years ago

Alarm system

EVO HD, IP100

Environment

RPI

Git branch

Which Git branch you use. Did you tried "dev" branch? Please try before posting.

Describe the bug

Periodical connecting/disconecting to panel

To Reproduce

After restart a host, or lost ethernet connection between HA and IP100 and renew

Logs

Some days PAI working, some days periodicaly connecting to panel, not working

2022-03-07 12:35:07,658 - ERROR - PAI.paradox.paradox - Timeout while connecting to panel. Is an other connection active? 2022-03-07 12:35:07,666 - ERROR - PAI - Unable to connect to alarm 2022-03-07 12:35:09,680 - ERROR - PAI.paradox.lib.handlers - No handler for message 5 Detail: Container: fields = Container: data = b'RC\x00\x00\x16|\x00\x00\x00H\x00\x00\x00\x00\x00\x00'... (truncated, total 66) value = Container: po = Container: command = 5 status = Container: reserved = False alarm_reporting_pending = False Winload_connected = True NeWare_connected = False packet_length = 67 control = Container: ram_access = False bus_address = 0 address = 5756 data = b'\x00\x00\x00H\x00\x00\x00\x00\x00\x00\x00\x00\x00H\x00\x00'... (truncated, total 60) offset1 = 0 offset2 = 66 length = 66 checksum = b'\xd7' (total 1) 2022-03-07 12:35:20,828 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel 2022-03-07 12:35:20,829 - INFO - PAI.paradox.paradox - Clean Session 2022-03-07 12:35:20,830 - INFO - PAI.paradox.paradox - Cleaning previous session. Closing connection 2022-03-07 12:35:20,838 - ERROR - PAI.paradox.connections.protocols - Connection was closed: None 2022-03-07 12:35:20,839 - ERROR - PAI.paradox.connections.connection - Connection was lost 2022-03-07 12:35:20,842 - INFO - PAI.paradox.paradox - Disconnected from the Alarm Panel 2022-03-07 12:35:25,674 - INFO - PAI - Starting... 2022-03-07 12:35:25,675 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel 2022-03-07 12:35:25,676 - INFO - PAI.paradox.paradox - Clean Session 2022-03-07 12:35:25,678 - INFO - PAI.paradox.paradox - Connecting to interface 2022-03-07 12:35:25,679 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3 2022-03-07 12:35:25,728 - INFO - PAI.paradox.connections.connection - Connection established 2022-03-07 12:35:25,730 - INFO - PAI.paradox.connections.ip.commands - Authenticating with IP Module 2022-03-07 12:35:25,880 - INFO - PAI.paradox.connections.ip.commands - Authentication Success. IP(IP100) Module version 101, firmware: 5.20, serial: 7000ee3e 2022-03-07 12:35:26,295 - INFO - PAI.paradox.connections.ip.commands - Session successfully established with IP Module 2022-03-07 12:35:26,296 - INFO - PAI.paradox.paradox - Connecting to Panel 2022-03-07 12:35:26,495 - INFO - PAI.paradox.paradox - Panel Identified EVOHD version 7.31 build 1 2022-03-07 12:35:26,496 - INFO - PAI.paradox.paradox - Initiating panel connection 2022-03-07 12:35:26,709 - INFO - PAI.paradox.hardware.evo.panel - Installer login 2022-03-07 12:35:26,899 - INFO - PAI.paradox.hardware.evo.panel - Authentication Success 2022-03-07 12:35:26,900 - INFO - PAI.paradox.paradox - Connection OK 2022-03-07 12:35:26,901 - INFO - PAI.paradox.paradox - Loading data from panel memory 2022-03-07 12:35:26,902 - INFO - PAI.paradox.hardware.panel - Loading definitions 2022-03-07 12:35:26,903 - INFO - PAI.paradox.hardware.panel - Updating Definitions from Panel 2022-03-07 12:35:28,283 - INFO - PAI.paradox.hardware.panel - Zone definitions loaded (1.38s) 2022-03-07 12:35:28,422 - INFO - PAI.paradox.hardware.panel - Partition definitions loaded (0.14s) 2022-03-07 12:35:33,680 - ERROR - PAI.paradox.paradox - Timeout while connecting to panel. Is an other connection active? 2022-03-07 12:35:33,684 - ERROR - PAI - Unable to connect to alarm 2022-03-07 12:35:35,670 - ERROR - PAI.paradox.lib.handlers - No handler for message 5 Detail: Container: fields = Container: data = b'RC\x00\x00\x0c,\x00\x00\x00H\x00\x00\x00\x00\x00\x00'... (truncated, total 66) value = Container: po = Container: command = 5 status = Container: reserved = False alarm_reporting_pending = False Winload_connected = True NeWare_connected = False packet_length = 67 control = Container: ram_access = False bus_address = 0 address = 3116 data = b'\x00\x00\x00H\x00\x00\x00\x00\x00\x00\x00\x00\x00H\x00\x00'... (truncated, total 60) offset1 = 0 offset2 = 66 length = 66 checksum = b'\x04' (total 1) 2022-03-07 12:35:46,636 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel 2022-03-07 12:35:46,637 - INFO - PAI.paradox.paradox - Clean Session 2022-03-07 12:35:46,638 - INFO - PAI.paradox.paradox - Cleaning previous session. Closing connection 2022-03-07 12:35:46,648 - ERROR - PAI.paradox.connections.protocols - Connection was closed: None 2022-03-07 12:35:46,649 - ERROR - PAI.paradox.connections.connection - Connection was lost 2022-03-07 12:35:46,654 - INFO - PAI.paradox.paradox - Disconnected from the Alarm Panel 2022-03-07 12:35:52,693 - INFO - PAI - Starting... 2022-03-07 12:35:52,694 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel 2022-03-07 12:35:52,696 - INFO - PAI.paradox.paradox - Clean Session 2022-03-07 12:35:52,698 - INFO - PAI.paradox.paradox - Connecting to interface 2022-03-07 12:35:52,699 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3 2022-03-07 12:35:52,749 - INFO - PAI.paradox.connections.connection - Connection established 2022-03-07 12:35:52,750 - INFO - PAI.paradox.connections.ip.commands - Authenticating with IP Module 2022-03-07 12:35:52,901 - INFO - PAI.paradox.connections.ip.commands - Authentication Success. IP(IP100) Module version 101, firmware: 5.20, serial: 7000ee3e 2022-03-07 12:35:53,317 - INFO - PAI.paradox.connections.ip.commands - Session successfully established with IP Module 2022-03-07 12:35:53,318 - INFO - PAI.paradox.paradox - Connecting to Panel 2022-03-07 12:35:53,516 - INFO - PAI.paradox.paradox - Panel Identified EVOHD version 7.31 build 1 2022-03-07 12:35:53,516 - INFO - PAI.paradox.paradox - Initiating panel connection 2022-03-07 12:35:53,731 - INFO - PAI.paradox.hardware.evo.panel - Installer login 2022-03-07 12:35:53,908 - INFO - PAI.paradox.hardware.evo.panel - Authentication Success 2022-03-07 12:35:53,909 - INFO - PAI.paradox.paradox - Connection OK 2022-03-07 12:35:53,910 - INFO - PAI.paradox.paradox - Loading data from panel memory 2022-03-07 12:35:53,911 - INFO - PAI.paradox.hardware.panel - Loading definitions 2022-03-07 12:35:53,912 - INFO - PAI.paradox.hardware.panel - Updating Definitions from Panel 2022-03-07 12:35:55,283 - INFO - PAI.paradox.hardware.panel - Zone definitions loaded (1.37s) 2022-03-07 12:35:55,423 - INFO - PAI.paradox.hardware.panel - Partition definitions loaded (0.14s)

proasnet commented 2 years ago

After some minutes...

value = Container: po = Container: command = 7 message_center = 2 new_protocol = 255 protocol_id = 4 protocol = Container: version = 2 revision = 0 build = 0 family_id = 161 product_id = (enum) (unknown) 109 talker = (enum) CONTROLLER_APPLICATION 1 application = Container: version = 7 revision = 31 build = 1 serial_number = b'\x07\x00p\xf1' (total 4) hardware = Container: version = 0 revision = 0 bootloader = Container: version = 1 revision = 6 build = 2 day = 32 month = 8 year = 32 processor_id = 19 encryption_id = 166 reserved0 = b'\xffW' (total 2) label = b'EVOHD \x00\x00' (total 8) offset1 = 0 offset2 = 36 length = 36 checksum = b'\x1d' (total 1) 2022-03-07 12:49:12,758 - ERROR - PAI.paradox.lib.handlers - No handler for message 7 Detail: Container: fields = Container: data = b'r\xff\x04\x02\x00\x00\xa1m\x01\x071\x01\x07\x00p\xf1'... (truncated, total 36) value = Container: po = Container: command = 7 message_center = 2 new_protocol = 255 protocol_id = 4 protocol = Container: version = 2 revision = 0 build = 0 family_id = 161 product_id = (enum) (unknown) 109 talker = (enum) CONTROLLER_APPLICATION 1 application = Container: version = 7 revision = 31 build = 1 serial_number = b'\x07\x00p\xf1' (total 4) hardware = Container: version = 0 revision = 0 bootloader = Container: version = 1 revision = 6 build = 2 day = 32 month = 8 year = 32 processor_id = 19 encryption_id = 166 reserved0 = b'\xffW' (total 2) label = b'EVOHD \x00\x00' (total 8) offset1 = 0 offset2 = 36 length = 36 checksum = b'\x1d' (total 1) 2022-03-07 12:49:16,096 - INFO - PAI - Starting... 2022-03-07 12:49:16,098 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel 2022-03-07 12:49:16,100 - INFO - PAI.paradox.paradox - Clean Session 2022-03-07 12:49:16,101 - INFO - PAI.paradox.paradox - Cleaning previous session. Closing connection 2022-03-07 12:49:16,113 - ERROR - PAI.paradox.connections.protocols - Connection was closed: None 2022-03-07 12:49:16,115 - ERROR - PAI.paradox.connections.connection - Connection was lost 2022-03-07 12:49:16,120 - INFO - PAI.paradox.paradox - Disconnected from the Alarm Panel 2022-03-07 12:49:16,122 - INFO - PAI.paradox.paradox - Connecting to interface 2022-03-07 12:49:16,124 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3 2022-03-07 12:49:16,304 - INFO - PAI.paradox.connections.connection - Connection established 2022-03-07 12:49:16,306 - INFO - PAI.paradox.connections.ip.commands - Authenticating with IP Module 2022-03-07 12:49:16,457 - INFO - PAI.paradox.connections.ip.commands - Authentication Success. IP(IP100) Module version 101, firmware: 5.20, serial: 7000ee3e 2022-03-07 12:49:16,872 - INFO - PAI.paradox.connections.ip.commands - Session successfully established with IP Module 2022-03-07 12:49:16,873 - INFO - PAI.paradox.paradox - Connecting to Panel 2022-03-07 12:49:17,070 - INFO - PAI.paradox.paradox - Panel Identified EVOHD version 7.31 build 1 2022-03-07 12:49:17,070 - INFO - PAI.paradox.paradox - Initiating panel connection 2022-03-07 12:49:17,285 - INFO - PAI.paradox.hardware.evo.panel - Installer login 2022-03-07 12:49:17,470 - INFO - PAI.paradox.hardware.evo.panel - Authentication Success 2022-03-07 12:49:17,472 - INFO - PAI.paradox.paradox - Connection OK 2022-03-07 12:49:17,473 - INFO - PAI.paradox.paradox - Loading data from panel memory 2022-03-07 12:49:17,474 - INFO - PAI.paradox.hardware.panel - Loading definitions 2022-03-07 12:49:17,475 - INFO - PAI.paradox.hardware.panel - Updating Definitions from Panel 2022-03-07 12:49:18,860 - INFO - PAI.paradox.hardware.panel - Zone definitions loaded (1.38s) 2022-03-07 12:49:19,007 - INFO - PAI.paradox.hardware.panel - Partition definitions loaded (0.15s)

yozik04 commented 2 years ago

Is it local connection or via SWAN?

proasnet commented 2 years ago

Thank you for interesting. Connection is only local via IP100. Connection bare is false.

yozik04 commented 2 years ago

Hmm. Strange. Are you sure your local network works well? I use EVO192 and IP150 and never experience any unexpected disconnects.

proasnet commented 2 years ago

I have a network with Mikrotik components, RouterBoard. My network working fine. I have not a IP150, but IP100. Yesterday, PAI working the whole day to now. I can't explain these outages, when the PAI tries to connect for cycles for several days, and then it suddenly works without any change.

yozik04 commented 2 years ago

@proasnet post config here. Do not hijack other threads

proasnet commented 2 years ago

My configuration is LOGGING_LEVEL_CONSOLE: 20 LOGGING_LEVEL_FILE: 40 CONNECTION_TYPE: IP SERIAL_PORT: /dev/ttyUSB0 SERIAL_BAUD: 57600 IP_CONNECTION_HOST: 192.168.0.180 IP_CONNECTION_PORT: 10000 IP_CONNECTION_PASSWORD: paradox KEEP_ALIVE_INTERVAL: 50 LIMITS: zone: auto user: 1-2 door: '' pgm: 1-5 partition: auto module: '' repeater: '' keypad: '' key-switch: '' SYNC_TIME: true SYNC_TIME_MIN_DRIFT: 120 PASSWORD: '2580' MQTT_ENABLE: true MQTT_HOST: core-mosquitto MQTT_PORT: 1883 MQTT_KEEPALIVE: 60 MQTT_USERNAME: pai MQTT_PASSWORD: Jirutka8011 MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true COMMAND_ALIAS: arm: partition all arm disarm: partition all disarm MQTT_COMMAND_ALIAS: armed_home: arm_stay armed_night: arm_sleep armed_away: arm disarmed: disarm HOMEASSISTANT_NOTIFICATIONS_EVENT_FILTERS:

yozik04 commented 2 years ago

KEEP_ALIVE_INTERVAL is quite large. Default 10 works ok. But that is not a solution to your disconnection problems.

proasnet commented 2 years ago

Keep alive interval 50 I tried today, from 10. This change was not effect for resolve problem. Now I have 10 back and still trying connect. I tried babyware over IP and working fine. I tried found any problem in the panel settings, nothing, all seems normally

proasnet commented 2 years ago

I am attaching some screenshots from HA. Thank you. pai1 pai2 pai3 pai4

yozik04 commented 2 years ago
  1. How frequent are these disconnects?
  2. For how long it happens?
  3. Any pattern?
  4. Did you ever registered Paradox cloud account on IP100?
  5. Are there any settings left from that?
  6. Did you ever tried an other software that could attempt to connect and hijack the connection. Maybe it is still running?
  7. Are there any other errors (excluding "No handler for message 5")
proasnet commented 2 years ago
  1. If I see a times in logs, every starting connections every about 25-26 seconds
  2. Are two states. Few days ago, I migrated HA from RPI3 to x86, both witch HASSOS, supervised. Before migrating, few days working fine, a few days this problem. Sometime help restart IP100 by re-connect cable from panel. After migrating, is not possible working connection to panel, the HA system is now very fast and quikly
  3. Before migrating, I noticed that this problem most often manifested itself if the communication between HA and PAI at the ethernet level was interrupted for a moment, e.g. switching off the switch, then I had to restart the IP100 to restore the communication
  4. I have not any cloud at paradox
  5. plugin settings remained the same after HA migration. The settings of the IP100 module are in the factory settings. Its IP address is fixedly assigned by the Mikrotik router according to the MAC address, so it is DHCP, but unchangeable.
  6. There is no software running at the same time that connects to the panel. If I connect with Babyware, I stop PAI, and vice versa. There is no other device on the network trying to connect to the IP100
  7. I noticed message 7 from previous posts in addition to message 5, but now I only see message 5.
yozik04 commented 2 years ago

So is it better now after migration?

proasnet commented 2 years ago

It depends on how this question is meant. The whole HA system is much faster and there is no problem with the system freezing. PAI had connection problems even before the migration, as you can see from my posts, I described the problem a long time ago. RPI3 was very slow for my amount of automations and CPU freezes 1-2 times a day. This problem is solved with the move to x86 and SSD Interestingly, it proved more after migrating to faster hardware, even though the software remained the same without the currency. RPI3 - export backup, x86 - import backup, nothing else.

proasnet commented 2 years ago

I also wondered if it is possible to use the Moxa nPort 5110, which I have unused at home, instead of the IP100 with your accessory. I once tried it as a connection bare, but it didn't work. It has different IP ports and does not support telnet, it is a virtual COM port, and is not supported by HA. I have a wired eth connection, and there is no wifi available, so I can't use the ESP32. Is it possible to add MOXA nPort support to PAI? It would be a solution between IP150 and ESP32 telnet. Please take this as an idea that can be rejected.

yozik04 commented 2 years ago

I used a USB to serial port adapter plugged into RPI to talk to the Panel with PAI. It works good enough. But connection still stalls 3-5 times per day. Which is not critical as it reconnects quite fast.

yozik04 commented 2 years ago

I have no idea what is Moxa nPort... If you can implement connection via that then I think I can accept a pull request for that.

proasnet commented 2 years ago

nPort is ethernet serial server, low cost, is similar as telnet via esp in your PAI project, but this device standard using drivers in OS and create remotelly COM port. That have linux TTY drivers ( or windows ). but I can not install this drivers to HASSOS. It using TCP/UDP, and maybe configured by web interface in some modes for a pc. Interesting is Reverse Telnet Mode, that is described on page 58 of a manual, I thing that in little bit may be implemented as an option to PAI, but I don't perfectly understand the possibilities of HASSOS and add-ons in containers, I'm a specialist in another type of programming, so please consider this just a small idea how to avoid IPxxx, arduins, etc. with available, ready-made and cheap HW. Maybe it won't work at all. I don't want to burden you with that, it's outside of this thread.

aelias-eu commented 2 years ago

Hi @proasnet if you configure the nport as serial server (tcp and maybe also udp), you can use it in python like this: ser = serial.serial_for_url('socket://IP_ADDRESS_OF_CONVERTER:TCP_PORT')

you have to set the serial communication settings on the nport directly (baudrate, parity, etc) and then you can use any tcp client to connect & communicate with it (netcat or so) i'm using the moxa nport like this in another project without any problems

yozik04 commented 2 years ago

I think PAI does support 'socket://IP_ADDRESS_OF_CONVERTER:TCP_PORT' already. So I think no updates on PAI side are required.

proasnet commented 2 years ago

Interesting. Thank you. I will test it in near time. Today, I get a new IP150S and I try replace old IP100, I will see, that this help me fix this problem with disconecting. But, IP150S is not IP150, this is a special version for service tasks, will with version 1.40 firmware. This gateway not support swan and other functions. I am not need swan, but I dont know about compatibility with PAI.

Update: Yesterday, I replaced old IP100 by new IP150S with FW 1.4 Perriodically disconecting is fixed, but now is perriodically in log this:

2022-08-11 03:55:45,179 - ERROR - PAI.paradox.hardware.evo.panel - ChecksumError Error in path (parsing) -> checksum wrong checksum, read b'00', computed b'd0', message: b'4780000009000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' 2022-08-11 04:33:17,554 - ERROR - PAI.paradox.hardware.evo.panel - ChecksumError Error in path (parsing) -> checksum wrong checksum, read b'00', computed b'cf', message: b'4780000010f80002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' 2022-08-11 05:02:58,728 - ERROR - PAI.paradox.lib.handlers - Already handled 2022-08-11 05:09:38,848 - ERROR - PAI.paradox.lib.handlers - Already handled 2022-08-11 05:15:09,075 - ERROR - PAI.paradox.lib.handlers - Already handled 2022-08-11 05:18:19,780 - ERROR - PAI.paradox.lib.handlers - Already handled 2022-08-11 05:30:39,871 - ERROR - PAI.paradox.lib.handlers - Already handled 2022-08-11 05:31:50,339 - ERROR - PAI.paradox.lib.handlers - Already handled 2022-08-11 05:52:01,384 - ERROR - PAI.paradox.lib.handlers - Already handled 2022-08-11 05:52:31,205 - ERROR - PAI.paradox.lib.handlers - Already handled etc.....

hardusmaritz commented 1 year ago

Having the same issue with disconnecting every 2 min. Have been using this for over a year now and only started about a week ago with no explanation why.

I'm using ESPHome with UART on a NodeMCU esp8266.

Log from PAI:

2023-03-03 07:13:57,832 - INFO - PAI.paradox.connections.connection - Connection established 2023-03-03 07:13:57,832 - INFO - PAI.paradox.paradox - Connecting to Panel 2023-03-03 07:14:03,025 - INFO - PAI.paradox.paradox - Panel Identified MG5050 version 5.21 build 2 2023-03-03 07:14:03,025 - INFO - PAI.paradox.paradox - Initiating panel connection 2023-03-03 07:14:03,270 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Installer login 2023-03-03 07:14:03,520 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Authentication Success 2023-03-03 07:14:03,520 - INFO - PAI.paradox.paradox - Connection OK 2023-03-03 07:14:03,520 - INFO - PAI.paradox.paradox - Loading data from panel memory 2023-03-03 07:14:03,520 - INFO - PAI.paradox.hardware.panel - Loading definitions 2023-03-03 07:14:03,520 - INFO - PAI.paradox.hardware.panel - Updating Definitions from Panel 2023-03-03 07:14:06,670 - INFO - PAI.paradox.hardware.panel - Zone definitions loaded (3.15s) 2023-03-03 07:14:07,770 - INFO - PAI.paradox.hardware.panel - Pgm definitions loaded (1.1s) 2023-03-03 07:14:07,772 - INFO - PAI.paradox.hardware.panel - Loading labels 2023-03-03 07:14:07,772 - INFO - PAI.paradox.hardware.panel - Updating Labels from Panel 2023-03-03 07:14:08,870 - INFO - PAI.paradox.hardware.panel - Zone labels loaded (1.1s): WINDOW BEAM FRON, KITCHEN BEAM, GARAGE EYE, BEAM SIDE GARAGE, LAPA BEAM, SUNROOM EYE, PATIO BEAM, CARPORT BEAM 2023-03-03 07:14:09,420 - INFO - PAI.paradox.hardware.panel - Pgm labels loaded (0.55s): Panic Radio, Burglary Radio, Status LED, Open/Close Radio 2023-03-03 07:14:09,723 - INFO - PAI.paradox.hardware.panel - Partition labels loaded (0.3s): Area 1, Area 2 2023-03-03 07:14:11,070 - INFO - PAI.paradox.hardware.panel - User labels loaded (1.35s): System Master, Master 1, Master 2, User 04, User 05, User 06, User 07, User 08, User 09, User 10 2023-03-03 07:14:11,070 - INFO - PAI.paradox.hardware.panel - Module labels loaded (0.0s): 2023-03-03 07:14:11,070 - INFO - PAI.paradox.hardware.panel - Repeater labels loaded (0.0s): 2023-03-03 07:14:11,070 - INFO - PAI.paradox.hardware.panel - Keypad labels loaded (0.0s): 2023-03-03 07:14:11,345 - INFO - PAI.paradox.hardware.panel - Site labels loaded (0.27s): Your Alarm Site 2023-03-03 07:14:11,894 - INFO - PAI.paradox.hardware.panel - Siren labels loaded (0.55s): Wireless Siren 1, Wireless Siren 2, Wireless Siren 3 2023-03-03 07:14:11,895 - INFO - PAI.paradox.paradox - Running 2023-03-03 07:15:18,683 - ERROR - PAI.paradox.lib.handlers - Already handled 2023-03-03 07:15:18,683 - ERROR - PAI.paradox.lib.handlers - No handler for message 5 Detail: Container: fields = Container: data = b'R\x00\x80\x05\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 36) value = Container: po = Container: command = 5 status = Container: reserved = False alarm_reporting_pending = False Winload_connected = True NeWare_connected = False validation = 128 address = 5 data = b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 32) offset1 = 0 offset2 = 36 length = 36 checksum = b'\xd7' (total 1) 2023-03-03 07:15:18,683 - ERROR - PAI.paradox.lib.handlers - Already handled 2023-03-03 07:15:18,684 - ERROR - PAI.paradox.lib.handlers - No handler for message 5 Detail: Container: fields = Container: data = b'R\x00\x80\x05\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 36) value = Container: po = Container: command = 5 status = Container: reserved = False alarm_reporting_pending = False Winload_connected = True NeWare_connected = False validation = 128 address = 5 data = b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 32) offset1 = 0 offset2 = 36 length = 36 checksum = b'\xd7' (total 1) 2023-03-03 07:17:18,806 - ERROR - PAI.paradox.paradox - Lost communication with panel 2023-03-03 07:17:18,806 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel 2023-03-03 07:17:18,806 - INFO - PAI.paradox.paradox - Clean Session 2023-03-03 07:17:18,806 - INFO - PAI.paradox.paradox - Cleaning previous session. Closing connection 2023-03-03 07:17:18,807 - ERROR - PAI.paradox.connections.protocols - Connection was closed: None 2023-03-03 07:17:18,807 - ERROR - PAI.paradox.connections.connection - Connection was lost 2023-03-03 07:17:18,808 - INFO - PAI.paradox.paradox - Disconnected from the Alarm Panel 2023-03-03 07:17:18,808 - INFO - PAI - Starting... 2023-03-03 07:17:18,808 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel 2023-03-03 07:17:18,808 - INFO - PAI.paradox.paradox - Clean Session 2023-03-03 07:17:18,808 - INFO - PAI.paradox.paradox - Connecting to interface 2023-03-03 07:17:18,808 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3 2023-03-03 07:17:18,814 - INFO - PAI.paradox.connections.connection - Connection established 2023-03-03 07:17:18,814 - INFO - PAI.paradox.paradox - Connecting to Panel 2023-03-03 07:17:24,041 - INFO - PAI.paradox.paradox - Panel Identified MG5050 version 5.21 build 2 2023-03-03 07:17:24,041 - INFO - PAI.paradox.paradox - Initiating panel connection 2023-03-03 07:17:24,316 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Installer login 2023-03-03 07:17:24,574 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Authentication Success 2023-03-03 07:17:24,574 - INFO - PAI.paradox.paradox - Connection OK 2023-03-03 07:17:24,574 - INFO - PAI.paradox.paradox - Loading data from panel memory 2023-03-03 07:17:24,574 - INFO - PAI.paradox.hardware.panel - Loading definitions 2023-03-03 07:17:24,574 - INFO - PAI.paradox.hardware.panel - Updating Definitions from Panel 2023-03-03 07:17:25,567 - INFO - PAI.paradox.hardware.panel - Zone definitions loaded (0.99s) 2023-03-03 07:17:26,567 - INFO - PAI.paradox.hardware.panel - Pgm definitions loaded (1.0s) 2023-03-03 07:17:26,568 - INFO - PAI.paradox.hardware.panel - Loading labels 2023-03-03 07:17:26,569 - INFO - PAI.paradox.hardware.panel - Updating Labels from Panel 2023-03-03 07:17:27,566 - INFO - PAI.paradox.hardware.panel - Zone labels loaded (1.0s): WINDOW BEAM FRON, KITCHEN BEAM, GARAGE EYE, BEAM SIDE GARAGE, LAPA BEAM, SUNROOM EYE, PATIO BEAM, CARPORT BEAM 2023-03-03 07:17:28,066 - INFO - PAI.paradox.hardware.panel - Pgm labels loaded (0.5s): Panic Radio, Burglary Radio, Status LED, Open/Close Radio 2023-03-03 07:17:28,345 - INFO - PAI.paradox.hardware.panel - Partition labels loaded (0.28s): Area 1, Area 2 2023-03-03 07:17:29,691 - INFO - PAI.paradox.hardware.panel - User labels loaded (1.35s): System Master, Master 1, Master 2, User 04, User 05, User 06, User 07, User 08, User 09, User 10 2023-03-03 07:17:29,691 - INFO - PAI.paradox.hardware.panel - Module labels loaded (0.0s): 2023-03-03 07:17:29,691 - INFO - PAI.paradox.hardware.panel - Repeater labels loaded (0.0s): 2023-03-03 07:17:29,691 - INFO - PAI.paradox.hardware.panel - Keypad labels loaded (0.0s): 2023-03-03 07:17:29,967 - INFO - PAI.paradox.hardware.panel - Site labels loaded (0.28s): Your Alarm Site 2023-03-03 07:17:30,516 - INFO - PAI.paradox.hardware.panel - Siren labels loaded (0.55s): Wireless Siren 1, Wireless Siren 2, Wireless Siren 3 2023-03-03 07:17:30,516 - INFO - PAI.paradox.paradox - Running

g-fusion commented 1 year ago

Same here. Posted my issue here: https://github.com/ParadoxAlarmInterface/pai/issues/349#issuecomment-1479380307

ptoump commented 4 months ago

UPDATE: Solved -- Irrelevant to the software, it was a network issue.

Sorry for resurfacing this, but I have the same issues.

EVO192 (2.60) with IP100 (5.10.06)

image

here it times out 300ms after "Partition Definitions Loaded". Could it be there is an aggressive timeout somewhere? IP100 is slower than the ip150..

2024-04-11 17:06:48,503 - INFO - PAI.paradox.hardware.panel - Updating Definitions from Panel 2024-04-11 17:06:49,698 - INFO - PAI.paradox.hardware.panel - Zone definitions loaded (1.19s) 2024-04-11 17:06:49,822 - INFO - PAI.paradox.hardware.panel - Partition definitions loaded (0.12s) 2024-04-11 17:07:19,691 - ERROR - PAI.paradox.paradox - Timeout while connecting to panel. Is an other connection active? 2024-04-11 17:07:19,698 - ERROR - PAI - Unable to connect to alarm 2024-04-11 17:07:21,669 - ERROR - PAI.paradox.lib.handlers - No handler for message 5

ptoump commented 4 months ago

UPDATE2: Solved -- Irrelevant to the software, it was a network issue.

UPDATE: I used the latest docker version (dev-latest), and set IO_TIMEOUT = 10, didn't make any difference..

yozik04 commented 4 months ago

2.60 is too old firmware.

ptoump commented 4 months ago

2.60 is too old firmware.

True, it's so old actually that I'm afraid to upgrade to be honest 😅

Update: it seems that it was a network problem, there was a rogue DHCP server enabled on a range extender that created trouble, for some devices IP100 included. It's weird that it only affected some devices, but it's corrected now..

yozik04 commented 4 months ago

But I doubt that PAI works correctly with firmware version 2.60.

ptoump commented 4 months ago

But I doubt that PAI works correctly with firmware version 2.60.

It works surprising well actually, integrated on home assistant for basic management and remote alerting.