Set the subscription period using a secured OID that stores ValidFrom (bytes 0β7) and ValidTo (bytes 8β15) as 64-bit Unix epoch timestamps. The OID shall be written using D112 (Set Property β Secured) encapsulated in EEEE (Send Secured Command to Device).
The payload uses 64-bit Unix epoch timestamps for forward compatibility. On current devices, each timestamp shall fit within a 32-bit Unix epoch value; therefore, the most-significant four bytes of each 64-bit field shall be 00 00 00 00.
The payload consists of two 64-bit Unix epoch timestamps:
Bytes 0β7 β ValidFrom
Β· Unsigned 64-bit Unix epoch timestamp, little-endian
Bytes 8β15 β ValidTo
Β· Unsigned 64-bit Unix epoch timestamp, little-endian
Disable subscription: All 16 bytes = 0x00.
Enable example (2026-07-14 through 2027-07-14):
Β· ValidFrom: 0x000000006A557C00 (2026-07-14 00:00:00 UTC) LE
Β· ValidTo: 0x000000006C36AF80 (2027-07-14 00:00:00 UTC) LE
Β· Full payload: 00 7C 55 6A 00 00 00 00 80 AF 36 6C 00 00 00 00
Validation rules (SET rejected if violated):
Β· Length must be exactly 16 bytes.
Β· Both timestamps equal to 0x0 are accepted (disables subscription).
Β· One timestamp equal to 0x0 and the other non-zero is rejected.
Β· ValidFrom shall be less than or equal to ValidTo.
Β· Each timestamp shall have the most-significant four bytes set to 00 00 00 00 and shall not represent a date later than 2099-12-31 23:59:59 UTC.