[pull] dev from home-assistant:dev #1260
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
* Bug fix for light platform, when async_turn_on recieves multiple keys. * Changes according to @MartinHjelmare suggestion. * Moved effect set call in BleBoxLightEntity.async_turn_on method. * Added tests for effect in light platform. Added ValueError raise if effect not in effect list. * Removed duplicated line from test as @MartinHjelmare suggested.
* Remove lovelace from mypy ignore list * Raise error on failed config
* Remove evohome climate from mypy ignore list * Raise error
* migrate roku to new entity naming * Update binary_sensor.py * Update sensor.py * Update test_binary_sensor.py * Update sensor.py * Update entity.py * Update media_player.py * Update remote.py * Update media_player.py * Update remote.py * Update entity.py * Update entity.py * Update entity.py * Update entity.py
* Remove minecraft_server from mypy ignore list * Use new entity naming style
* Avoid importing MQTT into core for discovery dataclass Likely fixes #73863 * relo * adjust * rename * rename * rename * adjust missed imports * drop compat * fix conflict correctly * Update homeassistant/helpers/config_entry_flow.py * fix black from trying to fix the conflict in github
Use CO Device Class Instead of Gas Switches the carbon monoxide sensor from `Gas` to `CO`
* Upgrade to pyrisco 0.4.0 * Parametrized error tests in config flow * Inline error parameters * Switch to RiscoCloud
* Add Moat (BLE) integration * fix pin * resync * Update tests/components/moat/test_sensor.py Co-authored-by: Martin Hjelmare <[email protected]> * Update homeassistant/components/moat/sensor.py * backmerge from integration * purge dead code Co-authored-by: Martin Hjelmare <[email protected]>
Fix url redaction and add tests Co-authored-by: Dave T <[email protected]>
* Add Govee BLE integration * add missing files * remove test file not needed yet * fix * add bbq sensors * fixed lib * bump again to fix the names * fix discovery of the newer bbq devices * fix the test to test the right thing * verify no outstanding flows * only accept entities that match the platform * refactor * refactor * refactor * Refactor PassiveBluetoothDataUpdateCoordinator to support multiple platforms * cover * Update for new model * Update for new model * Update tests/components/govee_ble/test_sensor.py Co-authored-by: Martin Hjelmare <[email protected]> * purge dead code * backmerge from integration * Update docstring * Update docstring Co-authored-by: Martin Hjelmare <[email protected]>
* Update switchbot to be local push * fixes * fixes * fixes * fixes * adjust * cover is not assumed anymore * cleanups * adjust * adjust * add missing cover * import compat * fixes * uses lower * uses lower * bleak users upper case addresses * fixes * bump * keep conf_mac and deprecated options for rollback * reuse coordinator * adjust * move around * move around * move around * move around * refactor fixes * compat with DataUpdateCoordinator * fix available * Update homeassistant/components/bluetooth/passive_update_processor.py Co-authored-by: Martin Hjelmare <[email protected]> * Update homeassistant/components/bluetooth/passive_update_coordinator.py Co-authored-by: Martin Hjelmare <[email protected]> * Update homeassistant/components/bluetooth/update_coordinator.py Co-authored-by: Martin Hjelmare <[email protected]> * Split bluetooth coordinator into PassiveBluetoothDataUpdateCoordinator and PassiveBluetoothProcessorCoordinator The PassiveBluetoothDataUpdateCoordinator is now used to replace instances of DataUpdateCoordinator where the data is coming from bluetooth advertisements, and the integration may also mix in active updates The PassiveBluetoothProcessorCoordinator is used for integrations that want to process each bluetooth advertisement with multiple processors which can be dispatched to individual platforms or areas or the integration as it chooes * change connections * reduce code churn to reduce review overhead * reduce code churn to reduce review overhead * Update homeassistant/components/bluetooth/passive_update_coordinator.py Co-authored-by: Martin Hjelmare <[email protected]> * add basic test * add basic test * complete coverage * Update homeassistant/components/switchbot/coordinator.py Co-authored-by: Martin Hjelmare <[email protected]> * Update homeassistant/components/switchbot/coordinator.py Co-authored-by: Martin Hjelmare <[email protected]> * Update homeassistant/components/switchbot/__init__.py Co-authored-by: Martin Hjelmare <[email protected]> * Update homeassistant/components/switchbot/__init__.py Co-authored-by: Martin Hjelmare <[email protected]> * lint Co-authored-by: Martin Hjelmare <[email protected]>
* 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 <[email protected]> * Remove unused lines Co-authored-by: Martin Hjelmare <[email protected]>
…e_uuids (#75687) * 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )