Creating an Electric Heat Zone

First a zone called Test is created on the controller, which causes the following two packets,

15:37:55.299 046  I --- 01:145038 --:------ 01:145038 0004 022 07005465737400000000000000000000000000000000
15:37:55.308 045  I --- 01:145038 --:------ 01:145038 0005 004 0000FF00

At this stage, the heating type has not been specified.

Selecting ELECTRIC HEAT does cause any further packets to be sent - the following is identical if ZONE VALVE is selected instead.

Then a DTS92E is bound as a sensor (the controller is listening):

15:38:39.230 051  I --- 12:010740 --:------ 12:010740 1FC9 024 00-2309-3029F4 00-30C9-3029F4 00-0008-3029F4 00-1FC9-3029F4
15:38:39.240 045  W --- 01:145038 12:010740 --:------ 1FC9 006 07-2309-06368E

For the 1FC9 (bind) payloads, each entry is <zone_idx> <pkt_code> <device_id>:

• the DTS92E cant know what it is being bound to; it is offering 2309, 30C9, 0008 and 1FC9
• the sensor binding is for 2309 (setpoint); it appears 30C9 (temperature) is assumed

Finally, an actuator to the same zone (the BDR91A is in listen mode, the controller sends the first signal):

15:40:11.907 047  I --- 01:145038 --:------ 01:145038 1FC9 018 07-0008-06368E FC-3B00-06368E 07-1FC9-06368E
15:40:12.561 057  W --- 13:106039 01:145038 --:------ 1FC9 006 00-3EF0-359E37
15:40:12.575 046  I --- 01:145038 13:106039 --:------ 1FC9 006 00-FFFF-06368E

For the 1FC9 (bind) payloads:

• the controller is offering 0008, 3B00 (for FC, not for a zone) and 1FC9
• the actuator binding is for 3EF0
• the purpose of the 3rd packet is unclear