Add initial compatibility profile for Daikin ERSQ016AV1 + EKHBRD016ADV1

[julianbl]

Summary

• add a manual EKHBRD ADV1 compatibility profile so default E-series behaviour stays unchanged
• publish trusted Heating_Enabled and DHW_Enabled booleans from the confirmed 000010... / 400010... frame family
• suppress several clearly implausible water-temperature entities for this profile and stop advertising them as current temperatures in HA climate configs
• document the confirmed mappings, sample frames, and remaining reverse-engineering gaps
• add a small validation script for the confirmed heat/DHW matrix

How the state mapping was confirmed

The profile uses the repeating 0x10 request/response family as the trusted source on this platform. The confirmed matrix is:

• 000010010101... = heat on, DHW on
• 000010010100... = heat on, DHW off
• 000010000101... = heat off, DHW on
• 000010000100... = heat off, DHW off
• 4000100100110130... = heat on, DHW on
• 4000100100110030... = heat on, DHW off
• 4000100000110130... = heat off, DHW on
• 4000100000110030... = heat off, DHW off

Captured transition pair used during validation:

00001001010130000A0020000000000200004001B1
4000100100110130000A00200018000000000002000939
00001001010030000A002000000000020000400131
4000100100110030000A002000180000000000020009E0
80001001010030000A0020000000000200000001A4

What remains uncertain

• the 400011... sensor/process frame family still needs more reverse engineering on this platform
• automatic profile detection is not implemented yet
• the 0x80 one-shot transition family is documented but not used as the steady-state source

Why some entities are intentionally hidden

Existing generic mappings expose several water-side temperatures that are clearly implausible on this hardware family, including leaving/return water values near zero while active and unstable DHW tank values. This patch keeps those entities out of the profile instead of presenting them as trusted sensors.