Notification Targets

Within the CFLink Protocol, certain devices have the ability to send out unsolicited notifications based on events relating to their physical ports. For example, a SW16 can send CHA notifications when any of it's dry contact inputs change state. Or a CF Mini can send SPR notifications when incoming data is read from the on-board serial port.

These notifications by default are broadcast to all devices on the CFLink bus via the CFLink target ID of FF (See Broadcast ID for more information)

But in some cases you might want to target these notifications to only be sent to specific devices on the CFLink network, rather than broadcast to all devices. Reasons include increasing bus efficiency (less traffic on the bus), rule triggering, ensuring notification receipt (Broadcast messages cannot be guaranteed receipt by everyone on larger/busy networks).

All devices that send notifications can be configured to send to up to 5 unique CFLink IDs directly (including Broadcast ID), via the TGT command.

• LAN Bridge
  • LAN - Used for on-board serial port incoming data notifications (when COM slot is subscribed to the CFLink slot), incoming TCP/UDP communications (when TCP/UDP slot is subscribed to the CFLink slot).
• CF Mini
  • MIN - Used for on-board serial port incoming data notifications.
  • IOX - Used for IO port read state changes (dry contacts, resistance input, voltage input).
• IR Blaster
  • IRB - Used for IR receiving notification (via on-board receiver and external receiver port).
• SW16
  • SWX - Used for dry contact input read state changes.
• DIN-MOD4 and MOD4
  • MOD - Used for on-board serial port incoming data notifications, on-board dry contact input read state changes.
  • IOX - Used for IO module port read state changes (dry contacts, resistance input, voltage input).
  • COM - Used for COM module serial port incoming data notifications.
  • RLY - Used for Relay module port notifications when the test buttons on the front of the unit are pressed.

For more details on how to configure the notification targets for a specific notification type, please see the notifications section of the common protocol documentation.