"Lost communication with panel" often

[fdcastel]

I'm looking for suggestions from the community.

I've been going crazy over the past few months. These errors are happening more and more frequently, without any clear pattern.

The worst part is that every disconnect triggers a loud beep on the alarm keypad, disturbing everyone in the house.

I don't think this is a bug from PAI. Looking at the source code, it seems the disconnects are reported from this code.

Questions (to anyone who can answer them):

• Is there a way to increase the timeout?
  • Could this potentially help?
  • or would it be ineffective? e.g. if the issue is caused by the IP150 module itself and waiting longer wouldn't make a difference
• I've seen some discussions (see below) mentioning that the problem may be related to a firmware bug in the IP150+ and that downgrading the firmware to a specific version can help.
  • However, I’m using the older IP150 version. Is there a similar issue or fix available for this model?
  • IP150+ module do support SWAN disable - only local LAN network #356
  • Connection was lost every 5 minutes. #405
• Upgrade the firmware from both panel and IP150 would help? Or just make things worse?
• Could reverting to an older version of PAI help? For example, if a significant change in the networking code is potentially causing this issue (just an assumption on my part, here).
  • Discarded. No updates related to communication for years.

I've had this system installed for about 3-4 years, but the problems have only worsened in the last ~6 months (I can't pinpoint exactly when). I haven’t updated the firmware on either the alarm panel or the IP150 during this time.

Related: #536

Environment:

• EVO192 version 7.52 build 1
• IP(IP150) Module version 20, firmware: 1.40
• Everything is connected via gigabit ethernet cable. No Wi-Fi.
• Both HA and PAI running with Docker on Intel(R) Core(TM) i5-13500 (CPU usage under 1%)

paradox.log:

2025-07-24 22:02:23,478 - ERROR    - PAI.paradox.paradox - Lost communication with panel
2025-07-24 22:02:23,481 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
2025-07-24 22:02:23,481 - ERROR    - PAI.paradox.connections.connection - Connection was lost
2025-07-24 22:58:38,232 - ERROR    - PAI.paradox.paradox - Lost communication with panel
2025-07-24 22:58:38,242 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
2025-07-24 22:58:38,242 - ERROR    - PAI.paradox.connections.connection - Connection was lost
2025-07-24 23:12:34,182 - ERROR    - PAI.paradox.paradox - Lost communication with panel
2025-07-24 23:12:34,183 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
2025-07-24 23:12:34,183 - ERROR    - PAI.paradox.connections.connection - Connection was lost
2025-07-24 23:45:11,312 - ERROR    - PAI.paradox.paradox - Lost communication with panel
2025-07-24 23:45:11,312 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
2025-07-24 23:45:11,312 - ERROR    - PAI.paradox.connections.connection - Connection was lost
2025-07-25 04:18:21,881 - ERROR    - PAI.paradox.paradox - Lost communication with panel
2025-07-25 04:18:21,891 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
2025-07-25 04:18:21,891 - ERROR    - PAI.paradox.connections.connection - Connection was lost
2025-07-25 05:32:01,213 - ERROR    - PAI.paradox.paradox - Lost communication with panel
2025-07-25 05:32:01,214 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
2025-07-25 05:32:01,214 - ERROR    - PAI.paradox.connections.connection - Connection was lost
2025-07-25 05:53:57,538 - ERROR    - PAI.paradox.paradox - Lost communication with panel
2025-07-25 05:53:57,538 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
2025-07-25 05:53:57,538 - ERROR    - PAI.paradox.connections.connection - Connection was lost
2025-07-25 06:21:54,045 - ERROR    - PAI.paradox.paradox - Lost communication with panel
2025-07-25 06:21:54,046 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
2025-07-25 06:21:54,046 - ERROR    - PAI.paradox.connections.connection - Connection was lost
2025-07-25 06:39:20,176 - ERROR    - PAI.paradox.paradox - Lost communication with panel
2025-07-25 06:39:20,177 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
2025-07-25 06:39:20,177 - ERROR    - PAI.paradox.connections.connection - Connection was lost

docker log (only the last 2 disconnects for conciseness):

ha-pai  | 2025-07-25 06:21:54,046 - INFO     - PAI - Starting...
ha-pai  | 2025-07-25 06:21:54,046 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
ha-pai  | 2025-07-25 06:21:54,046 - INFO     - PAI.paradox.paradox - Clean Session
ha-pai  | 2025-07-25 06:21:54,046 - INFO     - PAI.paradox.paradox - Connecting to interface
ha-pai  | 2025-07-25 06:21:54,046 - INFO     - PAI.paradox.connections.ip.connection - Connecting. Try 1/3
ha-pai  | 2025-07-25 06:21:54,047 - INFO     - PAI.paradox.connections.connection - Connection established
ha-pai  | 2025-07-25 06:21:54,047 - INFO     - PAI.paradox.connections.ip.commands - Authenticating with IP Module
ha-pai  | 2025-07-25 06:21:54,049 - INFO     - PAI.paradox.connections.ip.commands - Authentication Success. IP(IP150) Module version 20, firmware: 1.40, serial: [REDACTED]
ha-pai  | 2025-07-25 06:21:54,053 - INFO     - PAI.paradox.connections.ip.commands - Session successfully established with IP Module
ha-pai  | 2025-07-25 06:21:54,053 - INFO     - PAI.paradox.paradox - Connecting to Panel
ha-pai  | 2025-07-25 06:22:07,087 - INFO     - PAI.paradox.paradox - Panel Identified EVO192 version 7.52 build 1
ha-pai  | 2025-07-25 06:22:07,087 - INFO     - PAI.paradox.paradox - Initiating panel connection
ha-pai  | 2025-07-25 06:22:07,108 - INFO     - PAI.paradox.hardware.evo.panel - Installer login
ha-pai  | 2025-07-25 06:22:07,127 - INFO     - PAI.paradox.hardware.evo.panel - Authentication Success
ha-pai  | 2025-07-25 06:22:07,127 - INFO     - PAI.paradox.paradox - Connection OK
ha-pai  | 2025-07-25 06:22:07,127 - INFO     - PAI.paradox.paradox - Loading data from panel memory
ha-pai  | 2025-07-25 06:22:07,127 - INFO     - PAI.paradox.hardware.panel - Loading definitions
ha-pai  | 2025-07-25 06:22:07,127 - INFO     - PAI.paradox.hardware.panel - Updating Definitions from Panel
ha-pai  | 2025-07-25 06:22:07,329 - INFO     - PAI.paradox.hardware.panel - Zone definitions loaded (0.2s)
ha-pai  | 2025-07-25 06:22:07,338 - INFO     - PAI.paradox.hardware.panel - Partition definitions loaded (0.01s)
ha-pai  | 2025-07-25 06:22:11,586 - INFO     - PAI.paradox.hardware.panel - User definitions loaded (4.25s)
ha-pai  | 2025-07-25 06:22:11,606 - INFO     - PAI.paradox.hardware.panel - Loading labels
ha-pai  | 2025-07-25 06:22:11,606 - INFO     - PAI.paradox.hardware.panel - Updating Labels from Panel
ha-pai  | 2025-07-25 06:22:11,716 - INFO     - PAI.paradox.hardware.panel - Zone labels loaded (0.11s): [REDACTED]
ha-pai  | 2025-07-25 06:22:11,716 - INFO     - PAI.paradox.hardware.panel - Pgm labels loaded (0.0s):
ha-pai  | 2025-07-25 06:22:11,744 - INFO     - PAI.paradox.hardware.panel - Partition labels loaded (0.03s): [REDACTED]
ha-pai  | 2025-07-25 06:22:11,762 - INFO     - PAI.paradox.hardware.panel - User labels loaded (0.02s): [REDACTED]
ha-pai  | 2025-07-25 06:22:11,762 - INFO     - PAI.paradox.hardware.panel - Module labels loaded (0.0s):
ha-pai  | 2025-07-25 06:22:11,762 - INFO     - PAI.paradox.hardware.panel - Door labels loaded (0.0s):
ha-pai  | 2025-07-25 06:22:11,762 - INFO     - PAI.paradox.paradox - Running
ha-pai  | 2025-07-25 06:39:20,176 - ERROR    - PAI.paradox.paradox - Lost communication with panel
ha-pai  | 2025-07-25 06:39:20,176 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
ha-pai  | 2025-07-25 06:39:20,176 - INFO     - PAI.paradox.paradox - Clean Session
ha-pai  | 2025-07-25 06:39:20,176 - INFO     - PAI.paradox.paradox - Cleaning previous session. Closing connection
ha-pai  | 2025-07-25 06:39:20,177 - ERROR    - PAI.paradox.connections.protocols - Connection was closed: None
ha-pai  | 2025-07-25 06:39:20,177 - ERROR    - PAI.paradox.connections.connection - Connection was lost
ha-pai  | 2025-07-25 06:39:20,177 - INFO     - PAI.paradox.paradox - Disconnected from the Alarm Panel
ha-pai  | 2025-07-25 06:39:20,177 - INFO     - PAI - Starting...
ha-pai  | 2025-07-25 06:39:20,177 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
ha-pai  | 2025-07-25 06:39:20,177 - INFO     - PAI.paradox.paradox - Clean Session
ha-pai  | 2025-07-25 06:39:20,177 - INFO     - PAI.paradox.paradox - Connecting to interface
ha-pai  | 2025-07-25 06:39:20,177 - INFO     - PAI.paradox.connections.ip.connection - Connecting. Try 1/3
ha-pai  | 2025-07-25 06:39:20,178 - INFO     - PAI.paradox.connections.connection - Connection established
ha-pai  | 2025-07-25 06:39:20,178 - INFO     - PAI.paradox.connections.ip.commands - Authenticating with IP Module
ha-pai  | 2025-07-25 06:39:20,180 - INFO     - PAI.paradox.connections.ip.commands - Authentication Success. IP(IP150) Module version 20, firmware: 1.40, serial: [REDACTED]
ha-pai  | 2025-07-25 06:39:20,184 - INFO     - PAI.paradox.connections.ip.commands - Session successfully established with IP Module
ha-pai  | 2025-07-25 06:39:20,185 - INFO     - PAI.paradox.paradox - Connecting to Panel
ha-pai  | 2025-07-25 06:39:33,222 - INFO     - PAI.paradox.paradox - Panel Identified EVO192 version 7.52 build 1
ha-pai  | 2025-07-25 06:39:33,222 - INFO     - PAI.paradox.paradox - Initiating panel connection
ha-pai  | 2025-07-25 06:39:33,244 - INFO     - PAI.paradox.hardware.evo.panel - Installer login
ha-pai  | 2025-07-25 06:39:33,263 - INFO     - PAI.paradox.hardware.evo.panel - Authentication Success
ha-pai  | 2025-07-25 06:39:33,264 - INFO     - PAI.paradox.paradox - Connection OK
ha-pai  | 2025-07-25 06:39:33,264 - INFO     - PAI.paradox.paradox - Loading data from panel memory
ha-pai  | 2025-07-25 06:39:33,264 - INFO     - PAI.paradox.hardware.panel - Loading definitions
ha-pai  | 2025-07-25 06:39:33,264 - INFO     - PAI.paradox.hardware.panel - Updating Definitions from Panel
ha-pai  | 2025-07-25 06:39:33,471 - INFO     - PAI.paradox.hardware.panel - Zone definitions loaded (0.21s)
ha-pai  | 2025-07-25 06:39:33,482 - INFO     - PAI.paradox.hardware.panel - Partition definitions loaded (0.01s)
ha-pai  | 2025-07-25 06:39:37,738 - INFO     - PAI.paradox.hardware.panel - User definitions loaded (4.26s)
ha-pai  | 2025-07-25 06:39:37,758 - INFO     - PAI.paradox.hardware.panel - Loading labels
ha-pai  | 2025-07-25 06:39:37,758 - INFO     - PAI.paradox.hardware.panel - Updating Labels from Panel
ha-pai  | 2025-07-25 06:39:37,866 - INFO     - PAI.paradox.hardware.panel - Zone labels loaded (0.11s): [REDACTED]
ha-pai  | 2025-07-25 06:39:37,866 - INFO     - PAI.paradox.hardware.panel - Pgm labels loaded (0.0s):
ha-pai  | 2025-07-25 06:39:37,893 - INFO     - PAI.paradox.hardware.panel - Partition labels loaded (0.03s): [REDACTED]
ha-pai  | 2025-07-25 06:39:37,911 - INFO     - PAI.paradox.hardware.panel - User labels loaded (0.02s): [REDACTED]
ha-pai  | 2025-07-25 06:39:37,911 - INFO     - PAI.paradox.hardware.panel - Module labels loaded (0.0s):
ha-pai  | 2025-07-25 06:39:37,911 - INFO     - PAI.paradox.hardware.panel - Door labels loaded (0.0s):
ha-pai  | 2025-07-25 06:39:37,911 - INFO     - PAI.paradox.paradox - Running

[yozik04]

Is there a way to increase the timeout? Could this potentially help or would it be ineffective?

You can try, there is a setting for it, but I doubt it will help

I've seen some discussions (see below) mentioning that the problem may be related to a firmware bug in the IP150+ and that downgrading the firmware to a specific version can help.
However, I’m using the older IP150 version. Is there a similar issue or fix available for this model? Upgrade the firmware from both panel and IP150 would help? Or just make things worse?

The newer IP150 versions only make things worse.

Could reverting to an older version of PAI help? For example, if a significant change in the networking code is potentially causing this issue (just an assumption on my part, here).
#536 (comment). No updates related to communication for years.

True :) So it won't help.

Questions:

• Which way you connect? Local or via SWAN? (I should have added a log line to show connection method. I am already tired making this question over and over again :)
• Can it be that IP150 did update by itself?
• Did you tried to restart IP150? Unplug it and plug it back.
• Oxidized IP150 <-> Panel contacts? Try to move the contacts, maybe it will become better. But I recommend to buy a deoxidizer.
• Can network problems be the cause? Old dying switch or router, oxidized contacts, ...

[fdcastel]

Thank you, @yozik04, for your always-helpful insights.

You can try, there is a setting for it, but I doubt it will help

This one? IO_TIMEOUT?

It seems the default is 0.5. For now, I'll try increasing it to 5 (a 10× increase) just for testing.

• Which way you connect? Local or via SWAN? (I should have added a log line to show connection method. I am already tired making this question over and over again :)

I'm connecting locally.

Out of curiosity, though: I have to admit I’m not entirely sure I understand the question. Wouldn’t using the Paradox SWAN service completely override or block local communication? (as I’ve read that in multiple posts). Am I missing something here?

• Can it be that IP150 did update by itself?

As far as I know, there’s no specific configuration for this.

HOWEVER, I checked some old posts and saw that I was using firmware version 1.34 at the time (currently it's 1.40). You even advised me not to upgrade, and I followed your advice!

BUT some time ago my security company had to upgrade it. This was quite a while ago (around two years back, if memory serves). I recall discussing alternative options with them ('cause I didn't want to upgrade it), but the upgrade turned out to be the only viable solution, or I’d lose IP reporting with them.

So they updated it to the minimum firmware version they required and assured me it wouldn’t interfere with my home automation setup. And, in fact, it didn’t: everything continued working as expected.

• Did you tried to restart IP150? Unplug it and plug it back.

I just had a power outage around here a few days ago, so I’ll consider this one done. 😄

• Oxidized IP150 <-> Panel contacts? Try to move the contacts, maybe it will become better. But I recommend to buy a deoxidizer.

Hmm, I'll try unplugging it and plugging it back in. Just to be safe.

That said: Is this a common problem with paradox products? For the sake of reference: my equipment (both panel and IP150) is around ~4 years old.

• Can network problems be the cause? Old dying switch or router, oxidized contacts, ...

Definitely not the issue 😅. I’ve proudly set up a solid home network: Unifi UDM-PRO, Unifi Switch Pro PoE, CAT6 cabling throughout, the whole shebang.

If all else fails, I'm considering creating a dedicated VLAN exclusively for the IP150 and assigning it the highest priority for everything. I'm keeping this as a last resort, though, since it's probably overkill.

[yozik04]

I just had a power outage around here a few days ago, so I’ll consider this one done.

It is battery powered so most probably it did not.

[fdcastel]

Doh! 🤦🏻 Very well noted.

[fdcastel]

Actions Taken:

• Unplugged and replugged the IP150 module; contacts appeared clean with no visible oxidation.
• Set IO_TIMEOUT to 5.
• Started a continuous ping to monitor the IP150 Ethernet connection every 1 second, with output redirected to a .txt file.
• My wife and I have started keeping records whenever we hear a long beep from the keypad.

Current Observations:

• The issue persists: over 7 disconnections in the last 12 hours.
• Increasing IO_TIMEOUT had no effect.
• The ping command consistently showed successful responses, averaging 0.4–0.6 ms, even during panel disconnections.

I'm open to any other suggestions that might help resolve the issue.