* Abort SmartThings flow if default_config is not enabled
* Abort SmartThings flow if default_config is not enabled
* Abort SmartThings flow if default_config is not enabled
ESPHome always uses .0 in the URL for the changelog,
and we never had a patch version in the stable
BLE version field so we need to switch it to
.0 for the URL.
* Fix ability to remove orphan device in Music Assistant integration
* Add test
* Remove orphaned device entries at startup as well
* adjust mocked client
* fix brigtness sensor having percent as unit.
* add test for percent-brightness-sensor
* remove valve position and update tests
* Removed test, because covered by Snapshots
* fix review comments
* move device calss to init.
* fix test
* fix review comments
* add battery sensor back to test fixture
* fix
* fix for exception for specific ventilation device type + tests
* fix for exception for specific ventilation device type + tests
* New Testset just for fan
* update test_sensor.ambr
* Create unique identifiers where multiple gateways are in use
Resolving issue https://github.com/home-assistant/core/issues/134497
* Added migration function to __init__.py
Added migration function to execute upon initialisation, to:
a) remove the erroneously-added config)_entry added to the device (gateway B gets added as a config_entry to a device associated to gateway A), and
b) swap out the non-unique identifiers for genuinely unique identifiers.
* Added tests to simulate migration from bad data scenario (i.e. explicitly executing migrate_entity_unique_ids() from __init__.py)
* Ammendments suggested in first review
* Changes after second review
* Rewrite of test_migrate_config_entry_and_identifiers after feedback
* Converted migrate function into major version, updated tests
* Finalised variable naming convention per feedback, added test to validate config entry migrated to v2
* Hopefully final changes for cosmetic / comment stucture
* Further code-coverage in test_migrate_config_entry_and_identifiers()
* Minor test corrections
* Added test for non-tradfri identifiers
Add native arm vacation mode support to elkm1
Vacation mode is currently implemented as a custom
service which will be deprecated in a future PR.
Note that the custom service was added long before
HA had a native vacation mode which was added
in #45980
Make the field descriptions of `source_ieee` and `install_code` UI-friendly by cross-referencing them using their friendly names to allow matching translations.
Better explain the alternative of using the `qr_code` field by adding that this contains both the IEEE address and the Install code of the joining device.
This reverts #116200
We changed the polling logic to avoid polling if all chars are marked as watchable
to avoid crashing the firmware on a very limited set of devices as it was
more in line with what iOS does. In the end, the user ended up replacing
the device in #116143 because it turned out to be unreliable in other
ways. The vendor has since issued a firmware update that may resolve
the problem with all of these devices.
In practice it turns out many more devices
report that chars are evented and never send events. After a few months
of data and reports the trade-off does not seem worth it since
users are having to set up manual polling on a wide range of
devices. The amount of devices with evented chars that do not
actually send state vastly exceeds the number of devices that
might crash if they are polled too often so restore the previous
behavior
fixes#138561fixes#100331fixes#124529fixes#123456fixes#130763fixes#124099fixes#124916fixes#135434fixes#125273fixes#124099fixes#119617
* fix(alert): check can_ack prior to acking
* fix(alert): add test for when can_acknowledge=False
* fix(alert): warn on can_ack blocking an ack
* Raise error when trying to acknowledge alert with can_acknowledge set to False
* Rewrite can_ack check as guard
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
* Make can_ack service error msg human readable because it will show up in the UI
* format with ruff
* Make pytest aware of service error when acking an unackable alert
---------
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
