3 commits

Author	SHA1	Message	Date
Julian Pawlowski	95950f48c1	feat(services): add find_best_start and plan_charging services ... Add two new service actions for intelligent device scheduling: - find_best_start: Find optimal start time for run-once appliances - Considers price, optional energy estimates, optional PV power - Supports flexible time windows (HH:MM, ISO datetime, with/without timezone) - Prefers future candidates over past ones - Includes current interval by default (configurable) - Returns recommended start time with cost analysis - plan_charging: Create optimized charging schedule for energy storage - Supports EV, home battery, balcony battery use cases - Energy target or duration-based planning - Split or continuous charging modes - Efficiency factor support - Includes current interval by default (configurable) - Returns detailed slot-by-slot charging plan Common improvements: - Flexible datetime parsing (ISO 8601, with/without timezone, microseconds) - Time selector in GUI (better UX than text field) - Currency display based on config entry settings - Comprehensive error handling and validation - Detailed response envelopes with warnings/errors Impact: Users can automate appliance scheduling based on electricity prices without external automation rules.	2026-01-20 11:47:26 +00:00
Julian Pawlowski	e156dfb061	feat(services): add rolling 48h window support to chart services ... Add dynamic rolling window mode to get_chartdata and get_apexcharts_yaml services that automatically adapts to data availability. When 'day' parameter is omitted, services return 48-hour window: - With tomorrow data (after ~13:00): today + tomorrow - Without tomorrow data: yesterday + today Changes: - Implement rolling window logic in get_chartdata using has_tomorrow_data() - Generate config-template-card wrapper in get_apexcharts_yaml for dynamic ApexCharts span.offset based on tomorrow_data_available binary sensor - Update service descriptions in services.yaml - Add rolling window descriptions to all translations (de, en, nb, nl, sv) - Document rolling window mode in docs/user/services.md - Add ApexCharts examples with prerequisites in docs/user/automation-examples.md BREAKING CHANGE: get_apexcharts_yaml rolling window mode requires config-template-card in addition to apexcharts-card for dynamic offset calculation. Impact: Users can create auto-adapting 48h price charts without manual day selection. Fixed day views (day: today/yesterday/tomorrow) still work with apexcharts-card only.	2025-12-01 23:46:09 +00:00
Julian Pawlowski	ac24f6a8cb	refactor(services): split monolithic services.py into package ... Split services.py (1,097 lines) into modular package (6 files, ~200-600 lines each): Structure: - services/__init__.py: Service registration (70 lines) - services/helpers.py: Entry validation (55 lines) - services/formatters.py: Data transformation (380 lines) - services/chartdata.py: Chart data export handler (600 lines) - services/apexcharts.py: ApexCharts YAML generator (240 lines) - services/refresh_user_data.py: User data refresh (110 lines) Benefits: - Clear separation of concerns (helpers, formatters, handlers) - Each service isolated and independently testable - Consistent handler naming (handle_* pattern) - Better code reuse through formatters module All services working identically (get_chartdata, get_apexcharts_yaml, refresh_user_data). Updated __init__.py to import from services package. Impact: Improved maintainability, reduced max file size from 1,097 to 600 lines. Architecture quality improved from 7.5/10 to ~8.5/10.	2025-11-18 20:07:05 +00:00