- Remove the cached map from memory when unpairing so
we do not reuse it again if they unpair/repair
- Fixes for accessories that use a config number of
0
- General reliablity improvements to the pairing process
under the hood of aiohomekit
* Add add-on store info command
* Use add-on store info command in zwave_js
* Fix init tests
* Update tests
* Fix method for addon store info
* Fix response parsing
* Fix store addon installed response parsing
* Remove addon info log that can contain network keys
* Add supervisor store addon info test
* Default to version None if add-on not installed
Co-authored-by: Mike Degatano <michael.degatano@gmail.com>
Co-authored-by: Mike Degatano <michael.degatano@gmail.com>
* Add bluetooth discovery
* Use home assistant standard api
* Fixup manufacture data
* Adjust config flow to use standard features
* Fixup tests
* Mock bluetooth
* Simplify device check
* Fix missing typing
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* Moved color commands to a new ``async_handle_color_commands`` method
* Fixed tests
* Fix brightness jumping around during transitions
* Add config option to disable "Enhanced brightness slider during light transition"
* Set min transition time for Sengled lights in ZHA groups
* Change test to expect correct min transition time for group with Sengled light
* Fix turn_off with transition 0 for Sengled lights
* Fix bluetooth integration with service_data and service_uuids
We would only dispatch a new flow when the address was seen for
the first time or the manufacturer_data appeared in a followup
advertisement. Its also possible for the service_data and
service_uuids to appear in a followup advertisement so we
need to track these as well
* improve logging to avoid overly large messages
* improve logging to avoid overly large messages
* adjust
* adjsut
* split
* coverage
* coverage
* coverage
* coverage
* fix matcher
* more coverage
* more coverage
* more coverage
* revert switchbot changes and move to seperate PR
* Support for encrypted devices
* Sensor should use bindkey if available
* Error message if encryption fails
* Let mypy know this is always set by now
* Towards supporting encryption in step_user
* Add tests for the 4 new happy paths
* Add test coverage for failure cases
* Add strings
* Bump to 0.5.1. Legacy MiBeacon does not use an authentication token, so harder to detect incorrect key
* Add _title() helper
* Fix test after rebase
* Update homeassistant/components/xiaomi_ble/strings.json
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* Remove unused lines
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>