NOTE: All documents linked from this page are in 
PDF-format .
Interpretation 135-2016-1 – July 21, 2016 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.56, regarding the Network Port object.)
Interpretation 135-2016-2 – October 25, 2016 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 13.3.6, regarding the direct transitions.)
Interpretation 135-2016-3 – June 26, 2017 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clauses H.2.2.1 Offline Devices and H.2.3.2 Offline Devices, regarding consistent BACnet gateway behavior for offline devices.)
Interpretation 135-2016-4 – June 26, 2017 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause W.5.3 The .auth Data Item, regarding the format of public keys.)
Interpretation 135-2016-5 – October 24, 2017 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.12.21, regarding Event Enrollment Reliability property.)
Interpretation 135-2016-6 – October 24, 2017 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016 regarding the exact meaning of some defined units in the BACnet standard.)
Interpretation 135-2016-7 – October 24, 2017 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 16.1, regarding DeviceCommunicationControl for BACnet Router.)
Interpretation 135-2016-8 – October 24, 2017 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016 regarding adding properties from future protocol revisions.)
Interpretation 135-2016-9 – October 26, 2017 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause K.2.4 AE-ACK-A, and Clause K.2.2 AE-N-I-B, regarding date and time synchronization requirements.)
Interpretation 135-2016-10 – April 17, 2018 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause L.7 Miscellaneous Profiles, regarding B-BBMD, B-RTR, DS-WP-B, and WriteProperty Execution.)
Interpretation 135-2016-11 – April 17, 2018 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016 regarding BIBBs and Device Profiles.)
Interpretation 135-2016-12 – July 11, 2018 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.3.12, regarding Present_Value property.)
Interpretation 135-2016-13 – April 10, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Figure 6-12, regarding router discovery.)
Interpretation 135-2016-14 – April 12, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 13.15.1.1.6, regarding the ‘COV Increment’ parameter of the SubscribeCOVProperty service.)
Interpretation 135-2016-15 – June 20, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clauses 13.2.2.1 and 13.3, regarding Transitions out of FAULT while an OFFNORMAL condition exists.)
Interpretation 135-2016-16 – June 20, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause K.1.12, regarding devices claiming conformance to DS-COV-B.)
Interpretation 135-2016-17 – June 20, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.56 and Tables 12.71 and 12.72, regarding Required vs Optional properties of the Network Port object type.)
Interpretation 135-2016-18 – June 20, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clauses 13.1 and 13.15.1.1.6, regarding COV_Increment for numeric properties.)
Interpretation 135-2016-19 – October 30, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.56, regarding activating changes.)
Interpretation 135-2016-20 – October 30, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clauses 5.2.1.2, 9.7.1 and 19.4, regarding the requirements for devices to know the Maximum Conveyable APDU to remote networks.)
Interpretation 135-2016-21 – October 30, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 13.3.1, regarding BITSTRING Object.)
Interpretation 135-2016-22 – January 14, 2019 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Addendum bl, Clause 12.18.10, regarding Multi-state Input object when the Out_Of_Service property is TRUE and the resulting requirements of the Reliability and Status_Flags properties and the fault algorithm.)
Interpretation 135-2016-23 – February 1, 2020 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.56 and Table 12.71, regarding the presence of optional properties.)
Interpretation 135-2016-24 – February 1, 2020 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.57, regarding writing when State_Change_Values intends to relinquish on all transitions from RUNNING.)
Interpretation 135-2016-25 – February 1, 2020 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.56.11 Network_Number.)
Interpretation 135-2016-26 – July 6, 2020 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, regarding the ability to read property values.)
Interpretation 135-2016-27 – July 6, 2020 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016 Addendum bi, regarding the specified type of the Member_Of property.)
Interpretation 135-2016-28 – July 6, 2020 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clause 12.56.13 Changes_Pending.)
Interpretation 135-2016-29 – March 26, 2021 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clauses 12.24.8 and K.3, regarding BACnetTimeValue in a Schedule object’s Exception_Schedule, via Scheduling BIBBs.)
Interpretation 135-2016-30 – November 24, 2021 (Refers to the requirements presented in ANSI/ASHRAE Standard 135-2016, Clauses 12.21 and 21, regarding the use of Network Number in the Recipient_List property of Notification Class objects.)