0.66.0 #13554
Merged
0.66.0 #13554
Conversation
This file contains hidden or 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
* Add camera proxy * Fix additional tox linting issues * Trivial cleanup * update to new async/await methods rather than decorators. Other minor fixes from code review
* Get zha switch and binary_sensor state on startup * Removed unused var * Make zha switch report status * Use right method name * Formatting fix * Updates to match latest dev * PR feedback updates * Use async for cluster commands
* Initial async_check_ha_config_file * check_ha_config_file * Various fixes * feedback - return the config * move_to_check_config
* Add consider_home and source_type to device_tracker.see service * Use schema instead of manual validation * Extend schema to validate all keys * Fix style * Set battery level to int
* Clean up Light Groups * Fix tests * Remove light group from .coveragerc * async_schedule_update_ha_state called anyway
* Marks Devices unavailable if they 'vanish' and clears media * Fixed PEP8 complaint * Fixed Linting * Lint Fix * Fix redine of id * More lint fixes * Removed redundant loop for setting availability of client Renamed '_is_device_available' to '_available' Renamed 'available_ids' to 'available_client_ids' * removed whitespace per houndCI
With homeassistant 0.65.0 the filter sensor is introduced. Now there is a common way to filter the peaks comming from the readings. Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
* Make Throttle async aware * Lint
* Fix display_names, changed default port (+1) * Revert port change
The super class has these as properties, not regular methods
* Added container count * Added container count * Change Name * Fix if * Added Docker cpu use and memory use
* Fix issue to ignore delete files * Updated lazytox
* Different types of light should have different supported features.
* update leak sensor * Fix error when insteon state type is unknown * Bump insteon version to 0.8.3 * Update requirements all and test * Fix requirements conflicts due to lack of commit sync * Requirements sync * Rerun script/gen_requirements_all.py * Try requirements update again * Update requirements
* Added test
* Construct added to the requirements * requirements_all.txt updated
* Handle turn_on situation when no color is set As is, an error gets thrown when turn_on is called without an HS value. By adding an if statement, we only try to set RGB if an HS value is applied. * Fix Whitespace Issues * Made Requested Changes
|
@balloob I remember having done that already but if I have to again I shall... |
|
Thank you @tadly ! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is the first release with our new release schedule. During the extra week we had a total of 4 beta releases with a total of 26 fixes.
So this release is full of a lot of goodies. 80 people contributed over 223 fixes, improvements and new integrations during the last 2 weeks of this release 😎 I want to highlight the work of two people who are doing an amazing job: @NovapaX has been doing a great job triaging and fixing weird quirks and bugs in the frontend. And I want to give a shout out to @armills who has enabled backend translations. This means that a bunch of things that did not have translations yet, will now soon be translatable. We're planning some cool things with this!
New Platforms
Breaking Changes
hostkey is now required and needs to be a valid ip address. Optionallow_in_emulated_huehas been removed. Exclude the lights via the emulated hue config. If you are using a custom component for Hue, this will break! Ask custom component author for an update. (@balloob - #13043) (hue docs) (light.hue docs) (breaking change)new_entity_idsconfiguration was added to Z-Wave to smooth the transition through the change. Support for old entity IDs is now removed, and the configuration is no longer necessary. If you are migrating from 0.63 or higher, your entity IDs will already be stored in the Entity Registry and no changes are required. If not, entity IDs can now be manually configured using the Entity Registry if necessary. (@armills - #12652) (zwave docs) (breaking change)pincodeparameter is deprecated, since theHomeKitcomponent will now generate one for you and display it as a persistence notification during setup. Additionally the defaultportchanged to51827to avoid potential conflicts withhomebridge. Lastly to fix a major bug, we needed to change the way accessory ids are generated. This means that in turn all previous accessory settings will need to be repeated. To avoid future conflicts, it is highly recommended to remove theHome Assistant Bridgefrom theHomeapp and repeat the setup process. (HomeKit Setup) (@cdce8p - #12997) (homekit docs) (breaking change) (new-platform)All changes