* feat: raise execption on hvac mode while device is locked
* fix: test for setting hvac mode while device is locked.
* feat: update translation
* feat: add separate translations for HVAC and temperature
* fix: test cases
* fix: test cases for test_set_preset_mode_boost
* rev: code review
* rev: exception string
* feat: updated error message and added helper function
* Update homeassistant/components/fritzbox/strings.json
Co-authored-by: Michael <35783820+mib1185@users.noreply.github.com>
* fix: translation key
* remove check_active_or_lock_mode from async_set_preset_mode
---------
Co-authored-by: Michael <35783820+mib1185@users.noreply.github.com>
* migrate climate attributes to own entities
* add a comment to make it searchable
* Apply suggestions from code review
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
* Apply suggestions from code review
* update snapshots
---------
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
* Use temperature of current preset when set fritz HVAC mode to HEAT
If the HVAC mode of the Fritzbox thermostats changes from `HVACMode.OFF`
to `HVAMode.HEAT`, the current preset (COMFORT / ECO) should be
observed. Depending on the status of the current preset, the set
temperature of comfort / eco is set as the new temperature.
* fixup do not use value_scheduled_preset
Co-authored-by: Michael <35783820+mib1185@users.noreply.github.com>
* Add current_preset value to test_set_hvac_mode
The current_preset parameter allows the mock to be set to an active
preset. When setting HVACMode.HEAT, the respective temperature of the
ECO/COMFORT preset should be set.
* fixup Use the updated value_scheduled_preset function
To distinguish which temperature should be used when setting the
`HVAMode.HEAT`, `value_schedules_preset` is now used again, which has
been updated since the first commit. If no schedule is active, the
comfort_temperature is used. Otherwise, the respective temperature of
the current preset.
Co-authored-by: Michael <35783820+mib1185@users.noreply.github.com>
---------
Co-authored-by: Michael <35783820+mib1185@users.noreply.github.com>
* Index config entry discovery_keys by discovery domain
* Add new signal
* Update tests
* Update homeassistant/config_entries.py
Co-authored-by: J. Nick Koston <nick@koston.org>
* Fix imports
---------
Co-authored-by: J. Nick Koston <nick@koston.org>
* Reinitialize zeroconf discovery flow on unignore
* Adjust tests
* Improve comments
* Fix logic for updating discovery keys
* Add tests
* Use mock_config_flow helper in new config_entries test
* Add discovery_keys attribute to ConfigEntry
* Update zeroconf rediscovery
* Change type of ConfigEntry.discovery_keys
* Update tests
* Fix DiscoveryKey.from_json_dict and add tests
* Fix test
---------
Co-authored-by: J. Nick Koston <nick@koston.org>
* Climate temperature out of range
* Fix test sensibo
* use temp converting for min/max
* Fix
* Fix mqtt tests
* Fix honeywell tests
* Fix Balboa tests
* Fix whirlpool test
* Fix teslemetry test
* Fix plugwise test
* Fix tplink test
* Fix generic thermostat test
* Fix modbus test
* Fix fritzbox tests
* Honewell
* fix: set state of the FritzBox-Switch to disabled if the option for manuel switching in the userinterface is disabled
* feat: raise an error instead of disabling switch
* feat: rename method signature
* fix: tests
* fix: wrong import
* feat: Update homeassistant/components/fritzbox/strings.json
Update error message
Co-authored-by: Michael <35783820+mib1185@users.noreply.github.com>
* Update tests/components/fritzbox/test_switch.py
feat: update test
Co-authored-by: Michael <35783820+mib1185@users.noreply.github.com>
* make ruff happy
* fix expected error message check
---------
Co-authored-by: Michael <35783820+mib1185@users.noreply.github.com>
* Mark executor jobs as background unless created from a tracked task
If the current task is not tracked the executor job should not
be a background task to avoid delaying startup and shutdown.
Currently any executor job created in a untracked task or
background task would end up being tracked and delaying
startup/shutdown
* import exec has the same issue
* Avoid tracking import executor jobs
There is no reason to track these jobs as they are always awaited
and we do not want to support fire and forget import executor jobs
* fix xiaomi_miio
* lots of fire time changed without background await
* revert changes moved to other PR
* more
* more
* more
* m
* m
* p
* fix fire and forget tests
* scrape
* sonos
* system
* more
* capture callback before block
* coverage
* more
* more races
* more races
* more
* missed some
* more fixes
* missed some more
* fix
* remove unneeded
* one more race
* two
