10E0: Device Information

Some devices will periodically send device information without solicitation:

069  I --- 30:082155 63:262142 --:------ 10E0 038 000001C90011006CFEFFFFFFFFFF090907E0425244472D30324A415330310000000000000000

Round thermostats appear to send this data once every 24 hours (and other device may send it upon startup):

2020-02-04T17:17:36.227 051  I --- 34:205645 63:262142 --:------ 10E0 038 000001C838...
2020-02-05T17:17:35.439 047  I --- 34:205645 63:262142 --:------ 10E0 038 000001C838...
2020-02-06T17:17:34.672 051  I --- 34:205645 63:262142 --:------ 10E0 038 000001C838...
2020-02-07T17:17:33.910 049  I --- 34:205645 63:262142 --:------ 10E0 038 000001C838...

Other Verbs

An evohome controller will respond to an RQ with this data.

095 RQ --- 18:002858 01:073076 --:------ 10E0 001 00
045 RP --- 01:073076 18:002858 --:------ 10E0 038 000002FF0163FFFFFFFF140B07E1010807DD45766F20436F6C6F720000000000000000000000

As will an OpenTherm Bridge:

095 RQ --- 18:056026 01:073076 --:------ 10E0 001 00
059 RP --- 10:138822 18:056026 --:------ 10E0 038 000002FF0A0CFFFFFFFF150507E31F0707DE523838313041204272696467650012DD06000000

However, a BDR91 will not respond to a RQ for 10E0, nor should any battery-powered device (although this has not been extensively tested during their wake cycle).

Payload Decode

Payload decode:	To do

Python Code

def parser_10e0(payload) -> Optional[dict]:
    assert len(payload) / 2 in [30, 38]

    return {
        "description": _str(payload[36:]),
        "date_1": _date(payload[20:28]),  # could be 'FFFFFFFF'
        "date_2": _date(payload[28:36]),
        "unknown_0": payload[:20],
    }