Skip to content

PGM_5 control on EVO192 #580

@arnaudpn

Description

@arnaudpn

Feature request / investigation: PGM control on EVO192 (focus on onboard PGM_5 dry relay)

Hi,

I am trying to control PGMs on an EVO192 panel via Home Assistant using the PAI add-on.

Current behavior

  • No PGM activates when triggered from Home Assistant through PAI.
  • In contrast, PGMs work correctly when triggered from:
    • BabyWare (v5.5.65)
    • Paradox Insite Gold mobile app

From a practical standpoint, I am specifically interested in PGM_5, as it is the only onboard dry relay on the EVO192 mainboard.
The other PGMs are not dry relays and are therefore not suitable for my use case.

Relevant system details and prior discussion are documented here:
#292 (comment)


Question / hypothesis

Some online discussions suggest that PGM control (especially onboard PGMs) may only be supported via native Paradox applications (BabyWare / Insite), and not via third-party integrations such as PAI.

However, since PGMs are clearly controllable over IP from BabyWare, I would like to understand whether this is:

  • a protocol limitation,
  • a firmware restriction,
  • or a missing / unsupported feature in PAI.

Packet capture observations

I captured network traffic while activating PGM_5 from BabyWare using Wireshark.

1. Payload sent by BabyWare
aa170004090000640001ee0beeee2b14068530451be347cb8a3050b9952d45b765b7be37b4ceb7a342ebe0b9ee4d6a2a
2. Response sent by EVO192
aa0700026300000003ee00eeeeee1a0c77dce2b805d7ad760d3d348f5f614070

The exchange appears to be a valid command/ACK sequence for PGM activation.
The payload is encrypted, but the framing and command class appear consistent with other Paradox PGM operations.

As my wireshark is not compiled with the paradoxip-dissector from deonvdw, GPT helped me interpret these payloads:

1. Payload sent by BabyWare
Image

2. Response sent by EVO192
Image

Request

Would it be possible (or feasible) to support PGM activation on EVO192 panels within PAI?

If not, clarification on whether this is a known limitation would be very helpful.


Use case

My objective is to use the built-in PGM_5 dry relay to open a garage door, replacing an external Zigbee dry relay. This would improve reliability and reduce external hardware.


Originally posted by @arnaudpn in #292

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions