* Add default device class display precision for Sensor
* Renaming, docstrings, cleanup
* Simplify units list
* Fix tests
* Fix missing precision when suggested is specified
* Update snapshots
* Fix when unit of measurement is not valid
* Fix tests
* Fix deprecated unit usage
* Fix goalzero tests
The sensor native_value method was accessing the data dict and trowing,
since the mock did not have any data for the sensors.
Since now the precision is always specified (it was missing for those
sensors), the throw was hitting async_update_entity_options in _update_suggested_precision.
Previously, async_update_entity_options was not called since it had no
precision.
* Fix metoffice
* Fix smartthings
* Add default sensor data for Tesla Wall Connector tests
* Update snapshots
* Revert spaces
* Update smartthings snapshots
* Add missing sensor mock for tesla wall connector
* Address review comments
* Add doc comment
* Add cap to doc comment
* Update comment
* Update snapshots
* Update comment
* Add WS command to help reset custom entity_id
* Calculate suggested object id from entity properties
* Fix logic and add additional tests
* Adjust test
* Update folder_watcher test
* Handle current entity id matches the automatic entity id
* Don't store calculated_object_id
* Update snapshots
* Update snapshots
* Update test
* Tweak logic for reusing current entity_id
* Improve test
* Don't assign same entity_id to several entities
* Prioritize custom entity name
* Update snapshots
* Update snapshots
* 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>
Michael
Erik Montnemeryandjbouwh
epenetandClaude Opus 4.8
Franck Nijhof
Artur Pragacz
chli1
Lars
Abílio Costa
Simone Chemelli
Florian SabonchiandMichael
Norbert Rittel
G Johansson
Sven SagerandMichael