v2025.01.3

Fix not closed port during configuration when xcom device detection fails to find any devices
Let aioxcom library trace at same level as the integration

v2025.01.2

Set StateClass to TotalIncreasing for some entities
In ReadMe, recomment not to run Configuration from a Nabu Casa cloud connection

v2025.01.1

Resolve inconsistent type use for user_level during config-flow. Leading to error message during 'add via numbers'

v2024.12.4

Resolve unclosed connection during Xcom web config discover

v2024.12.3

Resolve issue with mixup between BMS and BSP during config

v2024.12.2

Additional warnings logged when unexpected cache behavior is detected

v2024.12.1

Support to show RCC param 5012 (User Level).
This is a View-Only param, so not allowed to change.

v2024.11.4

Make datapoints parsing more robust (code change in aioxcom)

v2024.11.3

Fix issue with not existing default VT param 11042

v2024.11.2

Add better view and edit support for params with unit "Seconds" which represents seconds since 1 January 1970 at 00:00.
This applies to RCC param 5002 (Date).

Add better view and edit support for params with unit "Minutes", which represents minutes since midnight, 0=00:00 to 1440=24:00.
This applies to XT param 1206 (Start hour AUX1), 1207 (End hour AUX1) and many others.

Note:
This change allows to create an automation that will periodically correct the Studer system time. This is needed for some (off-grid) system, where the time slowly shifts byabout 1 minute per month.
Below is an example for such an automation:

alias: Studer RCC Sync Time
description: ""
triggers:
  - trigger: time_pattern
    hours: "0"
    minutes: "0"
    seconds: "0"
conditions: []
actions:
  - action: datetime.set_value
    metadata: {}
    data:
      datetime: "{{ now() }}"
    target:
      entity_id: datetime.studer_4001_rcc_5002
mode: single