FastPack Protocol

Disclaimer
This document contains information that is the proprietary and confidential property of INNCOM International Inc. By
acceptance hereof, each recipient agrees to use the information contained herein only for the purpose anticipated by
INNCOM, and not to disclose to others, copy or reproduce, any part hereof without the written consent of INNCOM. The
recipient agrees to return this document to INNCOM immediately upon request.

Table of Content

INTRODUCTION..................................................................................................................................................................................................................... 3

1. LINK SPECIFICATION ...................................................................................................................................................................................................... 3

2. PACKET ENCODING ......................................................................................................................................................................................................... 3

2.1. DATA TYPES ..................................................................................................................................................................................................................... 3
2.2. PACKET FORMAT .............................................................................................................................................................................................................. 3
3. PROTOCOL .......................................................................................................................................................................................................................... 3
3.1. ESTABLISH AND MAINTAINING A LINK ............................................................................................................................................................................. 3
3.2. SYNCHRONIZATION ........................................................................................................................................................................................................... 3
4. FASTPACK PRIMITIVES .................................................................................................................................................................................................. 4
4.1. TAG 0XFF02: USB DONGLE PACKET................................................................................................................................................................................ 4
4.2. TAG 0XFF77: GUESTROOM ONLINE STATUS .................................................................................................................................................................... 4
4.3. TAG 0XFF7A: LIGHT OUTPUT STATE SUMMARY .............................................................................................................................................................. 4
4.4. TAG 0XFF7B: LIGHT OUTPUT STATE SUMMARY REQUEST .............................................................................................................................................. 4
4.5. TAG 0XFF7F: ATTRIBUTE UPDATE(2) .............................................................................................................................................................................. 4
4.6. TAG 0XFF80: REQUEST ATTRIBUTE SYNCH ..................................................................................................................................................................... 4
4.7. TAG 0XFF81: ATTRIBUTE UPDATE ................................................................................................................................................................................... 4
4.8. TAG 0XFF82: HVAC USER INTERFACE UPDATE (NOT SUPPORTED) ............................................................................................................................. 5
4.9. TAG 0XFF83: GUESTROOM CONTROLS ............................................................................................................................................................................. 5
4.10. TAG 0XFF8B: TUNNEL SERVER ...................................................................................................................................................................................... 5
4.11. TAG 0XFF8C: TUNNEL ROOM......................................................................................................................................................................................... 5
4.12. TAG 0XFFA0: ASYNCHRONOUS ROOM UPDATE ............................................................................................................................................................. 5
4.13. TAG 0XFFA3: SYNCHRONIZATION REQUEST .................................................................................................................................................................. 5
4.14. TAG 0XFFA7: RAW ALARM/EVENT ................................................................................................................................................................................ 6
4.15. TAG 0XFFAC: SYNCHRONIZATION END ......................................................................................................................................................................... 6
4.16. TAG 0XFFFE: BEACON ................................................................................................................................................................................................... 6
4.17. TAG 0XFFFF: STARTUP .................................................................................................................................................................................................. 6
5. ALARMS AND EVENTS ..................................................................................................................................................................................................... 7
5.1. ALARM 0XE000: RENTED UPDATE ................................................................................................................................................................................... 7
5.2. ALARM 0XE001: OCCUPANCY UPDATE ............................................................................................................................................................................ 7
5.3. ALARM 0XE002: DND UPDATE ........................................................................................................................................................................................ 7
5.4. ALARM 0XE003: MUR UPDATE ....................................................................................................................................................................................... 7
5.5. ALARM 0XE004: BUTLER CALL UPDATE .......................................................................................................................................................................... 7
5.6. ALARM 0XE005: FOODTRAY UPDATE............................................................................................................................................................................... 7
5.7. EVENT 0XE006: SAFE LOCKED ON CHECK-OUT ............................................................................................................................................................... 7
5.8. ALARM 0XE007: VALET CALL UPDATE ............................................................................................................................................................................ 7
5.9. ALARM 0XE008: COMFORT STATUS ................................................................................................................................................................................. 7
5.10. ALARM 0XE009: HVAC EQUIPMENT ............................................................................................................................................................................. 7
5.11. ALARM 0XE00A: DOOR AJAR UPDATE........................................................................................................................................................................... 8
5.12. ALARM 0XE00B: DOOR OPEN TOO LONG ...................................................................................................................................................................... 8
5.13. EVENT 0XE010: HVAC USER INTERFACE UPDATE ........................................................................................................................................................ 8
5.14. ALARM 0XE011: AUXILIARY 1 UPDATE ......................................................................................................................................................................... 8
5.15. ALARM 0XE012: AUXILIARY 2 UPDATE ......................................................................................................................................................................... 8
5.16. ALARM 0XE013: ROOM DIRTY UPDATE ......................................................................................................................................................................... 8
5.17. ALARM 0XE014: SUPERVISOR REQUESTED .................................................................................................................................................................... 8
5.18. ALARM 0XE015: OUT-OF-ORDER UPDATE ..................................................................................................................................................................... 9
5.19. ALARM 0XE016: SMOKE DETECTOR UPDATE ................................................................................................................................................................. 9

Honeywell Internal
Monday, January 14, 2019 Page |2

5.20. ALARM 0XE017: AIR FILTER UPDATE ............................................................................................................................................................................ 9

6. HOST SOFTWARE ARCHITECTURE ........................................................................................................................................................................... 10

7. DOCUMENT INFORMATION......................................................................................................................................................................................... 11

Honeywell Internal
Monday, January 14, 2019 Page |3

2.2. Packet Format

Introduction Each packet contains a 12-byte header. The first field in
this header is the so-called Tag. The tag describes the
This document describes a TCP/IP-based binary server-
data section (data layout of the record encoded in the
to-server protocol. This protocol is used for linking third-
data section) of the packet. If the receiving station does
party systems with INNCOM’s server.
not support a specific tag, the packet is simply discarded
by the receiving station.
The maximal size of the data section is 1024 bytes (1
1. Link Specification kByte).
- INNCOM’s server is the TCP/IP server. Third
party system is the TCP/IP client. Data Type Description
- As with TCP/IP, link of the system established by USHORT Tag. A well defined value that
the client application. describes the data section of this
- Default port on INNCOM 3002. Alternate ports or packet.
mapped ports as advised. USHORT Data size. Size (in bytes) of the
data section without the header
size.
2. Packet Encoding USHORT SourceID. For point-to-point links,

Header
set to 0 and ignore upon
2.1. Data Types reception.
USHORT DestinationID. For point-to-point
Note: All multi-byte values are encoded big- links, set to 0 and ignore upon
endian. reception.
ULONG RequestID. For point-to-point
Data Type Description links, set to 0 and ignore upon
BYTE 8-bit unsigned char reception.
USHORT 16-bit unsigned char xxx Data field 1
ULONG 32-bit unsigned char xxx Data field 2
Data

BLOB[] A byte array. Size is flexible but this : :

data type is always the last parameter xxx Data field n-1
in any packet (allowing the receiver to xxx Data field n-2
assess the length of the field).
SBA Short binary array of dynamic length.
The first byte is the length of the 3. Protocol
following data section, followed by a
sequence of bytes that contain the
3.1. Establish and Maintaining a Link
content of the binary array. The length
of the data encoded is limited to 255 The client application establishes the TCP/IP socket
bytes. connection to the INNCOM server. Each host sends to
LBA Long binary array of dynamic length. each other an initial startup packet (Tag 0xFFFF). Once
The first two bytes (USHORT) are the this packet has been sent, then each host is allowed to
length of the following data section, send any packets in any order.
followed by a sequence of bytes that To maintain a minimal amount of traffic to monitor the
contain the content of the binary array. link, each host should send once a minute a beacon
The length of the data encoded is packet (Tag 0xFFFE).
limited by not exceeding the length of
the FastPack data section. If packets are exchanged with acknowledgement, then
STR String. The first byte is the length of the only one packet should be outstanding (sliding window
string (this includes a terminating 0- size of 1 packet).
character). The following bytes are the
content of the string that includes a 3.2. Synchronization
terminating 0. The length of the string is After the link is established, the third party host can
limited to 254 characters plus a submit a full synchronization request (Tag 0xFFA3). The
terminating 0-character. INNCOM server then will transmit blocks of relevant
TIMESTAMP Seconds since January 1st, 2004. information towards the third party host. After a block of
data, the server sends an end-synchronization event (Tag
0xFFAC). If the parameter of that event is set to 0, then
the synchronization is complete. If the parameter is not
zero, then the third party host will again request an
additional block of information by renewing the
synchronization request.

Honeywell Internal
Monday, January 14, 2019 Page |4

4.4. Tag 0xFF7B: Light Output State Summary

Request
4. FastPack Primitives
Third party system requests the INNCOM server to
update on the light output state of a particular room. The
4.1. Tag 0xFF02: USB Dongle Packet INNCOM server will generate the event 0xFF7A upon
This packet is used to transport PC503 RF packets receipt of this tag.
between a client application and the IRAS_USB driver Data Type Description of Data Section
software. USHORT RoomID (1..65535)
Data Type Description of Data Section USHORT Reserved for future. Set to 0.
BYTE Packet Type
0=Raw 802.15.4 packet 4.5. Tag 0xFF7F: Attribute Update(2)
1=Decrypted deep mesh packet
ULONG Timestamp (Micro second resolution) This event is pushed by the INNCOM server to the third
ULONG Client Request Identifier party host to notify on attribute values. Same as Tag
ULONG Client Request Parameter 0xFF81 FASTPACK_TAG_ATTRIBUTE_UPDATE but with
BYTE RSSI, Receive Signal Strength Indication Device Address field.
BYTE Unused
Data Type Description of Data Section
ULONG Flags (not used)
USHORT RoomID (1..65535)
ULONG Unused
BYTE Device Address (1…255)
SBA Payload (802.15.4 packet)
BYTE Attribute Type:
0x00: Background update / synch.
4.2. Tag 0xFF77: Guestroom Online Status 0x01: Synchronization
0x02: On change
When a third party host sends a Guestroom Control 0x03-0xFF: Undefined
message (0xFF83), this message will be generated as an USHORT Attribute ID (see separate document)
immediate reply (so it can be used as an USHORT Attribute Value (see separate document)
acknowledgement that the message was processed by
USHORT Auxiliary Value (see separate document)
the INNOM Server application). This gives the third party
application an immediate indication if there is any
likelihood that the message has a chance for success or
not. 4.6. Tag 0xFF80: Request Attribute Synch
Data Type Description of Data Section The third party system requests the synchronization of
USHORT RoomID (1..65535) the guestroom attributes.
BYTE Communication State.
0x00: Room Offline (for more than 15 Data Type Description of Data Section
minutes) USHORT RoomID (1..65535)
0x01: Room Online (has communicated
at least once in the last 15 minutes)
BYTE Communication Error Type
4.7. Tag 0xFF81: Attribute Update
BYTE Flags
This event is pushed by the INNCOM server to the third
party host to notify on attribute values.
4.3. Tag 0xFF7A: Light Output State Summary
Data Type Description of Data Section
This event is pushed by the INNCOM server to the third
USHORT RoomID (1..65535)
party host to notify the room light output states.
BYTE Attribute Type:
Data Type Description of Data Section 0x00: Background update / synch.
USHORT RoomID (1..65535) 0x01: Synchronization
USHORT Reserved for future. Set to 0. 0x02: On change
BYTE Logical Circuit ID [0] 0x03-0xFF: Undefined
BYTE Logical Circuit Level [0] (0..255) USHORT Attribute ID (see separate document)
: USHORT Attribute Value (see separate document)
USHORT Auxiliary Value (see separate document)
BYTE Logical Circuit ID [n-1]
BYTE Logical Circuit Level [n-1] (0..255)

Honeywell Internal
Monday, January 14, 2019 Page |5

4.8. Tag 0xFF82: HVAC User Interface Update 4.11. Tag 0xFF8C: Tunnel Room
(Not supported)
Tunnel a data packet from the INNCOM server towards
This is handled by Attribute Update (Tag 0xFF81) the FPS gateway in the room. For the NAT information,
for HVAC UI. the INNCOM server will include the information that it
learned from the data packets in reverse direction.
This event is pushed by the INNCOM server to the third
party host on change and about every 10 minutes for the The BLOB[] fields contains RoomID etc… but does not
purpose of synchronization. have to have a published layout as art of the FastPack
definition.
Data Type Description of Data Section
USHORT RoomID (1..65535) Data Type Description of Data Section
BYTE User selected display unit. SBA NAT information.
0=Fahrenheit, 1=Celsius BLOB[] Tunneled data
USHORT User selected target temperature,
clipped and rounded as per thermostat
display. Number is multiplied by 10. 4.12. Tag 0xFFA0: Asynchronous Room Update
Examples:71.5°F = 715; 21.5°C = 215. This event is pushed by the INNCOM server to the third
BYTE Manual fan speed (applicable for AC party host on changes to alarm/event conditions.
mode fixed fan). 0=off, 1=low,
2=medium, 3=high. Data Type Description of Data Section
BYTE AC-mode. 0=off, 1=fan only, 2=fan USHORT RoomID (1..65535)
fixed, 3=auto BYTE Alarm flags:
4.9. Tag 0xFF83: Guestroom Controls 0x01: Undefined
0x02: Value has changed
The third party host can control aspects of the guestroom 0x04: Undefined
with this command. Examples are toggling the DND 0x08: Undefined
state, changing temperature, etc. A listing of commands 0x10: Undefined
that are available are created in partner-specific 0x20: Undefined
documents provided by INNCOM. 0x40: Undefined
0x80: Undefined
Data Type Description of Data Section USHORT Alarm/Event code. For alarm and event
USHORT RoomID (1..65535) codes, see respective chapter.
BYTE Device address. Set to 0 for general USHORT Parameter 1
commands. USHORT Parameter 2
ULONG Flags. Set to 0. USHORT Parameter 3
USHORT Command Code (see separate USHORT Parameter 4
document).
TIMESTAMP Date/time when alarm condition became
USHORT Param0 active.
USHORT Param1 TIMESTAMP Date/time when alarm condition was
STR String Parameter acknowledged.
STR Name of the person/system that has
4.10. Tag 0xFF8B: Tunnel Server taken on the responsibility to handle the
alarm condition.
Tunnel a data packet from the FPS gateway in the room
to the INNCOM server. The routing network (e.g. third
party server infrastructure) will have to include NAT 4.13. Tag 0xFFA3: Synchronization Request
information so that the tunnel can be operated in reverse Send by the third party host to the INNCOM server to
direction as well. request the synchronization of information.
The BLOB[] fields contains RoomID etc… but does not
Data Type Description of Data Section
have to have a published layout as art of the FastPack
USHORT Set value of this parameter to 0xFFFF
definition.
for a full synchronization. To receive the
Data Type Description of Data Section next block of information during
SBA NAT information. synchronization, insert the value as
BLOB[] Tunneled data provided by the tag 0xFFAC (end
synchronization).

Honeywell Internal
Monday, January 14, 2019 Page |6

4.14. Tag 0xFFA7: Raw Alarm/Event

A guestroom device throws a raw alarm or event
condition. For examples of these events, see specific
controls manual.

Data Type Description of Data Section

USHORT RoomID (1..65535)
BYTE Device address.
BYTE Flags.
USHORT Alarm/Event code
USHORT Param1
USHORT Param2
USHORT Param3
USHORT Param4

4.15. Tag 0xFFAC: Synchronization End

Packet send by the INNCOM server to the third party host
to announce that a block of room synchronizations has
been completed. The third party server can then request
a further block of data.

Data Type Description of Data Section

USHORT If this value is 0, then the
synchronization has completed. If this
value is non-zero, insert this value into
the parameter field of tag 0xFFA3
(synchronization request) and order
another block of data to be
synchronized.

4.16. Tag 0xFFFE: Beacon

This packet should be sent once per minute to exercise
the TCP/IP link.

Data Type Description of Data Section

No data section (just a header).

4.17. Tag 0xFFFF: Startup

This is the first packet that should be transmitted over a
freshly established TCP/IP link.

Data Type Description of Data Section

ULONG Application ID. Announces identification
to the other station.
Definitions:
For this fixed code, see application
specific extensions.
ULONG Capability flags. Set to 0x00000000
STR Software driver name, e.g. “WSCon”.
STR Host identification that can possibly
identify the location of the host “IDF-2”.

Honeywell Internal
Monday, January 14, 2019 Page |7

5.6. Alarm 0xE005: Foodtray Update

5. Alarms and Events Parameter Description of Parameter
Below is a list of alarm and events that are being P1 0: No pending foodtray removal call
reported with the 0xFFA0 (Asynchronous Room Update) 1: Foodtray ready for pick-up
tag. P2 Undefined
The difference between alarms and events is as follows: P3 Undefined
An alarm contains a state that can be set and cleared. An P4 Undefined
event is stateless, meaning once it has fired, it is already
over.
5.7. Event 0xE006: Safe Locked on Check-Out
This condition is fired when the safe is locked at the time
5.1. Alarm 0xE000: Rented Update
the room became unrented.
Parameter Description of Parameter
P1 0: Unrented Parameter Description of Parameter
1: Rented P1 Undefined
P2 Undefined P2 Undefined
P3 Undefined P3 Undefined
P4 Undefined P4 Undefined

5.2. Alarm 0xE001: Occupancy Update 5.8. Alarm 0xE007: Valet Call Update

Parameter Description of Parameter Parameter Description of Parameter

P1 0: Un-occupied P1 0: Valet Call Cleared
1: Occupied 1: Valet Call Set
P2 Undefined P2 Undefined
P3 Undefined P3 Undefined
P4 Undefined P4 Undefined

5.3. Alarm 0xE002: DND Update 5.9. Alarm 0xE008: Comfort Status

Parameter Description of Parameter Parameter Description of Parameter

P1 0: DND Cleared P1 0: Room temperature appears to be OK.
1: DND Set 1: Room temperature does not appear
P2 Undefined to be OK and guest might be not
P3 Undefined comfortable. Condition not caused by
P4 Undefined equipment but by not allowing the
equipment to perform normally (e.g.
cooling prohibited or no cold water in
5.4. Alarm 0xE003: MUR Update the feeder pipe).
P2 Undefined
Parameter Description of Parameter
P3 Undefined
P1 0: MUR Cleared
P4 Undefined
1: MUR Set
P2 Undefined
P3 Undefined 5.10. Alarm 0xE009: HVAC Equipment
P4 Undefined
Parameter Description of Parameter
P1 0: HVAC equipment works normally
5.5. Alarm 0xE004: Butler Call Update 1: HVAC equipment appears to have a
problem.
Parameter Description of Parameter P2 Undefined
P1 0: Butler Call Cleared P3 Undefined
1: Butler Call Set
P4 Undefined
P2 Undefined
P3 Undefined
P4 Undefined

Honeywell Internal
Monday, January 14, 2019 Page |8

5.11. Alarm 0xE00A: Door Ajar Update Value AC-Mode

1 Fan Only (No Heating, No
Parameter Description of Parameter
Cooling, Fan adapting
P1 0: Door is in proper condition. automatically)
1: Door is in the frame but not latched.
2 Fan Fixed (Heating and
P2 Undefined Cooling Allowed but Fan
P3 Undefined stays steady)
P4 Undefined 3 Auto (Heating and Cooling
Allowed with Fan adapting
5.12. Alarm 0xE00B: Door Open Too Long automatically)

Parameter Description of Parameter

P1 0: Door is in proper condition.
1: Door is open for too long of a time.
P2 Undefined
P3 Undefined
P4 Undefined
5.14. Alarm 0xE011: Auxiliary 1 Update
A free assignable alarm condition. Context can change
5.13. Event 0xE010: HVAC User Interface Update from property to property.
This event triggers whenever the guest or a third party
system changes the HVAC settings of AC-mode, target Parameter Description of Parameter
temperature, etc… P1 0: Nominal condition
1: Alarm condition
Parameter Description of Parameter P2 Undefined
P1 To be defined. P3 Undefined
P2 Undefined P4 Undefined
P3 Undefined
P4 Undefined
5.15. Alarm 0xE012: Auxiliary 2 Update
HVAC UI State: A free assignable alarm condition. Context can change
15 14 13 12 11 10 9 8 7|6|5|4 3 2 1 0 from property to property.
C/F CompTT 0 FS ACM

Parameter Description of Parameter

C/F Bit 14; When set, the User Interface on the
P1 0: Nominal condition
INNCOM Thermostat is selected by the
1: Alarm condition
user to be in centigrade. When cleared, the
P2 Undefined
selection is in Fahrenheit.
P3 Undefined
CompTT Bits 13:8; Value that represents the target
temperature in a compressed format P4 Undefined
(Value - 40). The 0x00-0x3F range (0…63
decimal) allows for a selectable target 5.16. Alarm 0xE013: Room Dirty Update
temperature range of 40F – 103F which is
fine for guestroom controls. For example, Parameter Description of Parameter
71°F is represented as 0x1F or 31 decimal P1 0: Room Clear
(71 - 40). 1: Room Dirty
FS Bits 3:2; Defines the fan speed that is P2 Undefined
used for manual (fan fixed) mode: P3 Undefined
P4 Undefined
Value AC-Mode
0 OFF
1 Fan Low 5.17. Alarm 0xE014: Supervisor Requested
2 Fan Medium Parameter Description of Parameter
3 Fan High P1 0: No supervisor requested
1: Supervisor requested
ACM Bits 1:0; Defines the basic operating P2 Undefined
condition of the HVAC unit: P3 Undefined
P4 Undefined
Value AC-Mode
0 OFF

Honeywell Internal
Monday, January 14, 2019 Page |9

5.18. Alarm 0xE015: Out-of-Order Update

Parameter Description of Parameter

P1 0: Normal condition
1: Room out–of-order
P2 Undefined
P3 Undefined
P4 Undefined

5.19. Alarm 0xE016: Smoke Detector Update

Parameter Description of Parameter

P1 0: Normal condition
1: Smoke detector in active mode.
P2 Undefined
P3 Undefined
P4 Undefined

5.20. Alarm 0xE017: Air Filter Update

Parameter Description of Parameter

P1 0: Normal condition
1: Air filter needs cleaning.
P2 Undefined
P3 Undefined
P4 Undefined

Honeywell Internal
Monday, January 14, 2019 P a g e | 10

6. Host Software Architecture

In the example below, we briefly discuss a possible Events of type “Synchronization End” are forwarded
software implementation of a third party application that towards the synchronization thread to request the next
interfaces with FastPack to an INNCOM server. block of room synchronization data. Any incoming room
status or event is being put into a Room Status
Reference Data Base that stores the last reported
state. For example if an event “Butler Call for room 501
is set” is received, the record for that field is being
accessed. If the field contains the same value as before,
nothing much happens in the application. However, if the
field changed its value, an event is sent through the
Room Address Lookup Table towards the host’s
application. This table converts the INNCOM RoomID (16-
bit number) to a proprietary room number scheme of the
host application (assuming that the selected addressing
schemes are not necessarily directly compatible).
As the application controls aspect within the INNCOM
systems, the packets again pass through the Room
Address Lookup Table as to convert the hosts room
address into the INNCOM RoomID field. The control
packet is then forwarded towards the INNCOM server.

A key concept of such an implementation is that the host

is maintaining a reference dataset for each room.
INNCOM attempts not to store a state reference for all
the room attributes on its side – this would be impractical
as INNCOM would have to perform this function for all
different partner hosts it connects with. Further, INNCOM
does not necessarily understand how attributes are
filtered and passed towards the host’s application.

In brief terms, the elements are as follows: The

FastPack Protocol is a module that marshalls and
unmarshalls the data packets that are being sent over
the TCP/IP socket link between the host and the INNCOM
server. The thread Task: Startup Synchronization and
Beacon is used to send once per minute a sign of life (to
exercise mainly the link so that it can be detected if the
network or partner station has a problem). Also, as the
link is started, the thread will send a synchronization
request to the INNCOM server to request and update of
all room states. All incoming packets are being handled
by the Task: Packet Reception and Processing.

Honeywell Internal
Monday, January 14, 2019 P a g e | 11

7. Document Information
Author
Philipp Roosli, [email protected]
Michael Sobanko, [email protected]

INNCOM International Inc.

277 West Main Street
Niantic, CT 06357
(860) 739 4468

File
Source:
N:\R&D\Doc\EngManuals\Protocols\FastPack\TCP-
IP\FastPack Protocol.doc

Distribution: T:\Library\INNCOM Products\Systems\

Protocols\Generic_Protocols\FastPack
Protocol.pdf

References
• UDP Control Protocol
History
2008/06/06 First draft based on UDP control protocol.
2008/06/06 Reviewed by John Clark. Added commands
for synchronization request and end.
2008/09/11 PHR/MDS – Added HVACUI update and
guestroom control capability.
2008/09/12 PHR Added raw alarm/event flag 0xFFA7.
2008/09/16 PHR Host SW Architecture.
2009/01/06 PHR Added 0xFF80, 0xFF81 commands.
2009/03/17 MDS Added USHORT Auxiliary Value to the
0xFF81. Marked HVAC UI Update 0xFF82 not supported.
2015/04/03 MDS Added 0xFF7A and 0xFF7B for the
Light Output State reporting.
2016/01/05 MDS Added DataType HVAC UI State for
the 0xE010 event update.
2017/05/23 MDS Added Guestroom Communication
Status message 0xFF77.
2018/01/11 MDS Added Attribut Update (2) message
0xFF7F as it was somehow deleted from the document.

Honeywell Internal