[Device Support Request] Danfoss Ally thermostat: specific device settings (i.e. display Viewing direction)

[SimpleUserHA]

Is your feature request related to a problem? Please describe.
Looking for support to configure the viewing direction of the LCD.

Not sure at which level additional device specific properties and their potential values are being defined to allow configuring them in other systems and user interfaces using zigpy.

Describe the solution you'd like
The thermostat supports configuring the viewing direction, in case it it mounted upside down.

= Cluster = 0x0204 Thermostat UI Configuration =
  * Attribute ID = 0x4000 Viewing Direction
     Range: 0 to 1
     0x00 = viewing direction 1
     0x01 = viewing direction 2
     Default is 0, but overwritten to value from production configuration at Init

Is it the reponsibility of zigpy or zha or homeassistant to provide this cluster and attribute to the user?

Device signature - this can be acquired by removing the device from ZHA and pairing it again from the add devices screen. Be sure to add the entire content of the log panel after pairing the device to a code block below this line.

{
  "node_descriptor": "NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4678, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=0)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0301",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x000a",
        "0x0020",
        "0x0201",
        "0x0204",
        "0x0b05"
      ],
      "out_clusters": [
        "0x0000",
        "0x0019"
      ]
    }
  },
  "manufacturer": "Danfoss",
  "model": "eTRV0100",
  "class": "zhaquirks.danfoss.thermostat.DanfossThermostat"
}

Additional context
Thread at HomeAssistant forum
full spec about the Danfoss thermostat

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.