IP alarm reporting at the end of 2026, with SIA DC-09-2026 now published, and how that sits next to the existing forum threads t=13, t=14 and t=17. It is a buyer's and integrator's map, not a reproduction of the paid SIA specification.
Complexity
Moderate to read. Configuring a live monitoring path is work you do with the panel vendor and the monitoring centre — not from a forum post.
1. DC-09 is still the IP reporting standard to ask about
SIA DC-09 is the industry standard for sending alarm events over IP (and related paths) to a receiver. Many Australian panels and receivers already speak a DC-09 dialect. If a salesperson says "it reports over IP", the follow-up is still: which protocol, which encryption, and has the monitoring centre qualified that path?
2. What SIA publicly said about DC-09-2026
SIA announced DC-09-2026 in a public news item dated 3 March 2026. From that public announcement (not from the paid document):
- SIA describes DC-09 as an ANSI-approved standard for open, interoperable IP alarm transmission.
- The 2026 edition adds features around autocommissioning and encryption key rotation.
- It is described as backward compatible with earlier DC-09 deployments. That is a SIA claim to verify with your receiver and panel firmware, not a promise that every old communicator upgrades itself.
- The specification itself is sold by SIA (member and non-member shop prices are listed on their site). This thread does not quote or paraphrase the paid text.
3. Practical questions for a 2026 site
- Which DC-09 edition and encryption does the communicator firmware actually implement?
- Does the monitoring centre's receiver software already support DC-09-2026 features, or are you on an earlier qualified path?
- Is reporting dual-path (IP plus a radio or other backup), and who owns the failure-to-communicate procedure?
- Are the communicator and receiver on firmware versions the vendor will still support?
- Have you avoided exposing the panel or communicator administration interface to the internet "so IP reporting works"? Reporting is an outbound, monitored path — it is not a port forward.
A Home Assistant notification is useful for the occupier. It is not a substitute for a qualified alarm transmission path where the site needs monitored security or a fire/intruder response contract. Keep those roles separate.
Official / existing reading
SIA: DC-09-2026 announcement (3 March 2026)
Existing DC-09 discussion
Teletek / untested notes
Researched from official documentation on 15 November 2026 (Australia/Sydney). This is a planning and how-to guide, not a claim that the exact hardware combination was assembled and tested on a live site. Please correct anything that has moved on.