Add TIMEPROG data type

[liudger]

This pull request enhances the documentation and data modeling for hot water scheduling in the BSB-LAN integration. The main improvements clarify the handling and representation of time program schedules and introduce a new data type for these schedules.

Data modeling improvements:

• Added a new TIMEPROG value (9) to the DataType enum to represent time program (schedule slots) data types, improving clarity and type safety for schedule-related fields (src/bsblan/models.py).

Documentation enhancements:

• Expanded the docstring for the HotWaterSchedule class to explain the format and usage of daily time program fields, including examples and notes about the dhw_time_program_standard_values reset behavior (src/bsblan/models.py).
• Added a clarifying comment to the dhw_time_program_standard_values field to indicate it is a YESNO enum and describes its effect when set (src/bsblan/models.py).

[Copilot]

Pull request overview

This pull request adds a new TIMEPROG data type (value 9) to the DataType enum to represent BSB-LAN time program schedule data, and enhances the documentation for the HotWaterSchedule class to explain the format and behavior of daily time program fields.

Changes:

• Added TIMEPROG = 9 to the DataType enum for time program schedule slots
• Enhanced the HotWaterSchedule class docstring with details about time program format and usage
• Added an inline comment clarifying that dhw_time_program_standard_values is a YESNO enum that resets schedules

[Copilot]

The documentation claims that daily time programs use BSB-LAN dataType 9 (TIMEPROG), but the existing test fixture in test_hot_water_additional.py uses dataType 0 (PLAIN_NUMBER) for all schedule parameters (lines 153, 160, 167, 174, 181, 188, 195). This creates a discrepancy between the documentation and the test data. Either the test fixtures should be updated to use dataType 9, or the documentation should be corrected to reflect the actual dataType used by BSB-LAN devices for time program parameters.

[Copilot]

The new TIMEPROG data type is added to the DataType enum but is not handled in the _convert_bsblan_value function (lines 222-269). This function has explicit handling for PLAIN_NUMBER, ENUM, TIME, and WEEKDAY types, but other types including STRING, PPS_TIME, and now TIMEPROG fall through to the default string handling. While this may be intentional (keeping time program strings as-is), it should be verified that TIMEPROG values don't require special parsing, or explicit handling should be added for clarity and consistency with the comment on line 219.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.88%. Comparing base (195332c) to head (4e3b812).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1363   +/-   ##
=======================================
  Coverage   99.88%   99.88%           
=======================================
  Files           6        6           
  Lines         907      908    +1     
  Branches      128      128           
=======================================
+ Hits          906      907    +1     
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud