Julian Pawlowski e01cc5d447 feat(services): allow entity IDs as service parameter values ... Add entity_resolver module that lets all service parameters accept HA entity references in place of literal values. The entity's current state (or a specific attribute via the @attr syntax) is resolved at call time and coerced to the expected Python type. Syntax: "sensor.washing_duration" → uses entity state "sensor.washing_duration@run_minutes" → uses entity attribute Apply or_entity_ref() and resolve_entity_references() to all five service handlers (get_price, find_cheapest_block, find_cheapest_hours, find_cheapest_schedule, get_chartdata) for every parameter where a dynamic value from another entity is useful (duration, start/end times, offsets, etc.). Add five new translation keys for entity-resolution error messages (invalid_entity_reference, entity_not_found, entity_attribute_not_found, entity_state_unavailable, entity_value_conversion_failed) across all five language files. Fix pytest warning filter to suppress AsyncMock cleanup noise, and update test_resource_cleanup to mock hass.config_entries.async_entries so the blueprint-removal path in async_remove_entry does not raise. Impact: Automations and scripts can pass sensor entity IDs as service parameters (e.g. duration from a sensor) instead of having to use template-based workarounds.		2026-04-20 18:44:24 +00:00
..
de.json	feat(services): allow entity IDs as service parameter values	2026-04-20 18:44:24 +00:00
en.json	feat(services): allow entity IDs as service parameter values	2026-04-20 18:44:24 +00:00
nb.json	feat(services): allow entity IDs as service parameter values	2026-04-20 18:44:24 +00:00
nl.json	feat(services): allow entity IDs as service parameter values	2026-04-20 18:44:24 +00:00
sv.json	feat(services): allow entity IDs as service parameter values	2026-04-20 18:44:24 +00:00