* Store instance name in Thread router discovery
Store the DNS-SD instance name in the Thread router discovery message.
The instance name is the actual name given to a Thread border router,
e.g. when configuring the name of a Thread border router in Apple Home
the name appears as the DNS-SD instance name. This will allow to make
the Thread border router list more user friendly.
* Use instance_name_from_service_info to get instance name
* Add Protocol Upload/Download for Deluge
* add unit test and fix typo in sensor.py
* remove unneeded import
* rename/unify the translation keys and entries in const.py
* split out const.py items into DelugeSensorType to avoid confusion with DelugeGetSessionStatusKeys
* change DelugeGetSessionStatusKeys to be a regular enum to satisfy mypy
* Add config_flow helper to get config entry from context
* Simplify
* Apply to aussie_broadband
* Another example
* Rename and adjust docstring
* Simplify
* Add test
* Refactor to hide context
* Raise
* Improve coverage
* Use AttributeError
* Use ValueError
* Raise UnknownEntry
* Tibber: Add extra test to expose aware/naive datetime issue
* Tibber: Fix get_prices action not working with aware datetimes
* Tibber: Simplify comparison
* Tibber: Combine timezone tests into single parametrized one
* Tibber: Split test again to prevent if statement
* 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>
